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. -- Brian Szymanski ski@indymedia.org I prefer pgp encrypted email: keyid: 4E7A4703 server: keys.indymedia.org fingerprint: 5BD3 0B0C C8E3 0746 3550 5648 0CFE 1BE7 4E7A 4703
Hi Brian, Just add: ENV['PORTS_DBDRIVER'] = 'bdb1_hash' to your /usr/local/etc/pkgtools.conf. Ran into that yesterday and came across a page on the web that helped me. Good luck. Cheers -- Ricardo Oliva Core Systems Administrator Zoology Department University of British Columbia Ph.: 604-822-3882 E-mail: ricardo@zoology.ubc.ca On 17-Nov-04, at 1:21 PM, Brian Szymanski 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. > > -- > Brian Szymanski > ski@indymedia.org > > I prefer pgp encrypted email: > keyid: 4E7A4703 > server: keys.indymedia.org > fingerprint: 5BD3 0B0C C8E3 0746 3550 5648 0CFE 1BE7 4E7A 4703 > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org"
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
On Thursday, 18. November 2004 00:03, Ronald Klop wrote:> > But the real problem is > > the segfault with ruby, which can be reliably reproduced ad infinitum.> About the ruby thing. Try deinstall/reinstall of ruby and portupgrade > manually and try again. (This is my best guess.)Known problem - the berkeley db in libc is buggy and causes the crash. Workaround: Set PORTS_DBDRIVER in your environment (or in pkgtools.conf) to bdb_hash (or install databases/ruby-bdb and set PORTS_DBDRIVER to bdb_btree). -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20041118/98872e3e/attachment.bin
Hi! I had the same problem months ago in 4.8. Is not related to the distribution, the problem is in portupgrade. Please update the ports tree, and then deinstall and reinstal portupgrade. This was the solution in my case. Regards, Mauricio. -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Brian Szymanski Sent: Wednesday, November 17, 2004 6:21 PM To: freebsd-stable@lists.freebsd.org Subject: portupgrade crash on 4.9-stable 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.........60 00.........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. -- Brian Szymanski ski@indymedia.org I prefer pgp encrypted email: keyid: 4E7A4703 server: keys.indymedia.org fingerprint: 5BD3 0B0C C8E3 0746 3550 5648 0CFE 1BE7 4E7A 4703 _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"