Date: Thu, 18 Nov 2004 00:03:56 +0100 From: Ronald Klop <ronald-freebsd8@klop.yi.org> To: Brian Szymanski <ski@indymedia.org> Cc: freebsd-stable@www.freebsd.org Subject: Re: portupgrade crash on 4.9-stable Message-ID: <opshms0unr8527sy@smtp.local> In-Reply-To: <2761.10.0.0.26.1100726478.squirrel@10.0.0.26> References: <2761.10.0.0.26.1100726478.squirrel@10.0.0.26>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 17 Nov 2004 16:21:18 -0500 (EST), Brian Szymanski <ski@indymedia.org> wrote: > Hi, I'm having a problem with portupgrade on 4.9: > > # portupgrade -f sudo\* > Updating the ports index ... Generating INDEX.tmp - please wait.. Done. > done > [Updating the portsdb <format:bdb1_btree> in /usr/ports ... - 11962 port > entries found > .........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000....../usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: > [BUG] Segmentation fault > ruby 1.8.2 (2004-07-29) [i386-freebsd4] > > Abort trap (core dumped) > > I'm not sure why /usr/ports/INDEX isn't there anymore - it's a problem > I'm > having on all of my 4.x machines - everytime I cvsup portupgrade wants to > generate an INDEX.tmp before it doesn anything... But the real problem is > the segfault with ruby, which can be reliably reproduced ad infinitum. > > Any ideas? > > Thanks in advance. Read /usr/ports/UPDATING and /usr/ports/CHANGES after updating your ports tree. There is the removal of INDEX documented. About the ruby thing. Try deinstall/reinstall of ruby and portupgrade manually and try again. (This is my best guess.) Ronald. -- Ronald Klop, Amsterdam, The Netherlands
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?opshms0unr8527sy>