Date: Thu, 29 Jul 2004 00:34:01 +0300 From: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> To: Garance A Drosihn <drosih@rpi.edu> Cc: ports@freebsd.org Subject: Re: ruby18 fails as dependecy of sysutils/portupgrade with make: don't know how to make INSTALLS_DEPENDS Message-ID: <20040729003401.32bc2dc7@it.buh.tecnik93.com> In-Reply-To: <p06110415bd2dbf38487e@[128.113.24.47]> References: <20040727233948.15640c99@it.buh.tecnik93.com> <20040728184935.GA715@voodoo.laverenz.de> <20040728223439.783ab556@it.buh.tecnik93.com> <p06110415bd2dbf38487e@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 28 Jul 2004 16:42:05 -0400 Garance A Drosihn <drosih@rpi.edu> wrote: > At 10:34 PM +0300 7/28/04, Ion-Mihai Tetcu wrote: > >On Wed, 28 Jul 2004 20:49:35 +0200 > >Uwe Laverenz <uwe@laverenz.de> wrote: > > > >> On Tue, Jul 27, 2004 at 11:39:48PM +0300, Ion-Mihai Tetcu wrote: > >> > > > > This happens on a 5.2.1-RELEASE with ports up-to-date, with > > > > only perl, postfix and cvsup-without-gui installed. > > > > > > I guess this happens because you use -RELEASE and not RELENG_5_2. > > > If you update the base system to 5.2.1-p9 you get some fixes that > > > will satisfy the ruby port (probably the OpenSSL bug, see below *). > > > >I see. My plan was to update to -CURRENT and see how this little > >Pentium 120MHz behaves, but since current's waters seems to be > >very troubled right now I postponed that. > > Your plan is a very reasonable one. Note that RELENG_5_2 is an > actual CVS tag, and it is *NOT* the same as 5.2-current. It is > 5.2-RELEASE plus a very few security fixes. Yes, thanks you. Leaving aside two servers running a patched 4.7, the rest are running -current. I just don't want to update right now this one since on -current since a little bit unstable now and I don't feel like re-making world on a Pentium 120MHz with 40MB RAM each next day. I was thinking to use Colin's freebsd-update for the first time. Despite his page saying only 5.2R is supported, running freebsd-update -v fetch told only about kernel and linux.ko not being update-able (I've recompiled the kernel so this seems normal and I don't load linux.ko). -- IOnut Unregistered ;) FreeBSD "user"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040729003401.32bc2dc7>