Date: Mon, 06 Sep 2004 18:11:16 -0500 From: Chris <racerx@makeworld.com> To: Dustin <dustin@marsik.org> Cc: freebsd-questions@freebsd.org Subject: Re: Post Install Configuration Issues (ruby18 error) Message-ID: <413CEE94.5080003@makeworld.com> In-Reply-To: <5878D00B313A8D4E8D00B7E3082FC693067A1C@FF01.marsik.org> References: <5878D00B313A8D4E8D00B7E3082FC693067A1C@FF01.marsik.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Dustin wrote: > Thanks, that fixed my issue! > > Why did this happen anyway? > > Dustin That - I can't answer. Seems to be the million dollar question. > > -----Original Message----- > From: Chris [mailto:racerx@makeworld.com] > Sent: Mon 9/6/2004 1:11 PM > To: Dustin > Cc: freebsd-questions@freebsd.org > Subject: Re: Post Install Configuration Issues (ruby18 error) > > > > Dustin wrote: > > It's a fresh install of FreeBSD 5.2.1 REL, installed the "kern-developer" mode of install, immediately after install did the following: > > > > -installed cvsup-without-gui > > -updated ports tree using cvsup > > -attempted to install portupgrade from port and received following error: > > > > > > Ruby18 error > > dependency warning: used openssl version contains known vulnerabilities > > pleas update or define either WITH_OPENSSL_BASE or WITH_OPENSSL_PORT > > *** Error code 1 > > > > > > > > I then installed ruby18 from port using "make install clean", and then installed portupgrade, this time I received no errors. > > > > > > > > Then I attempted to run "portsdb -uU", and received the following errors: > > > > > > > > core dumped ruby18 portsdb > > > > > > > > What am I doing wrong here? > > > > > > > > -Dustin > > This is an ongoing issue with portsdb/ruby. > The way I see it, there are some easy fixes out there > > 0. install portindex > 1. cvsup (as you did) > 2. run portindex - this takes a while the 1st time. > 3. run portindexdb > 4. pkgdb -afuF (or what ever parms you use) > 5. portversion -vL= (this dumps out the ports that need updating) > 6. portupgrade -a (or what ever parms you use. > > > > > Another way: - this changes the default database (btriev) to hash > > setenv PORTS_DBDRIVER bdb1_hash > > then run your portdb -u > In fact, I opted for this one. I now run my ports tree updating scripts > as I did BEFORE these issues. > > > -- > Best regards, > Chris > > The organization of any program reflects the organization > of the people who developed it. > > -- Best regards, Chris Real programmers don't comment their code. if it is hard to write, it should be hard to understand.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?413CEE94.5080003>