Date: Thu, 7 Oct 2004 10:45:46 -0500 From: "Mire, John" <jmire@lsuhsc.edu> To: Matthew Seaman <m.seaman@infracaninophile.co.uk>, Matt Navarre <mnavarre@cox.net> Cc: freebsd-questions@freebsd.org Subject: RE: Portupgrade problem, possible pkgdb problem? Message-ID: <F414F4699FE1CF46B9DB1CE71D04BACB0E0C50F5@sh-exch.lsuhsc-s.edu>
next in thread | raw e-mail | index | archive | help
I'm still getting this error after a cvsup+buildworld, a make fetchindex and I have deleted /var/db/pkg/pkgdb.db and rebuilt it, what's the patch?: test# uname -v FreeBSD 5.2.1-RELEASE-p11 #12: Wed Oct 6 17:13:13 CDT 2004 root@test:/usr/obj/usr/src/sys/TEST test# cd /usr/ports test# make fetchindex Receiving INDEX-5 (5881230 bytes): 100% 5881230 bytes transferred in 16.9 seconds (339.01 kBps) test# portupgrade -R sudo [Failed `Inappropriate file type or format'] [Updating the portsdb <format:bdb1_btree> in /usr/ports ... - 11735 port entries found .........1000.........2000.........3000.........4000.........5000.........60 00.........7000.........8000..../usr/local/lib/ruby/site_ruby/1.8/portsdb.rb :587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd5] Abort (core dumped) test# rm /var/db/pkg/pkgdb.db test# portupgrade -R sudo [Rebuilding the pkgdb <format:bdb1_btree> in /var/db/pkg ... - 54 packages found (-0 +54) ...................................................... done] [Failed `Inappropriate file type or format'] [Updating the portsdb <format:bdb1_btree> in /usr/ports ... - 11735 port entries found .........1000.........2000.........3000.........4000.........5000.........60 00.........7000.........8000..../usr/local/lib/ruby/site_ruby/1.8/portsdb.rb :587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd5] Abort (core dumped) test# -- "Ethernet (n): something used to catch the etherbunny" John Mire: jmire@lsuhsc.edu Network Administration 318-675-5434 LSU Health Sciences Center - Shreveport The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of > Matthew Seaman > Sent: Sunday, September 26, 2004 4:14 AM > To: Matt Navarre > Cc: freebsd-questions@freebsd.org > Subject: Re: Portupgrade problem, possible pkgdb problem? > > On Sat, Sep 25, 2004 at 06:14:18PM -0700, Matt Navarre wrote: > > On Saturday 25 September 2004 05:13, Alex de Kruijff wrote: > > > > It could be a problem with the DBDriver. You could try this: > > > Edit /root/.cs... > > > and add > > > PORTS_DBDRIVER=bdb1_hash > > > PKG_DBDRIVER=bdb1_hash > > > Doesn't the DBDRIVER bug result in ruby dumping core? 'Cuz > it isn't in this > > case, it fails gracefully. > > The core dump is seen with portsdb(1) trying to create > /usr/ports/INDEX.db -- however, the underlying bug can affect anywhere > that ruby uses bdb1_btree files. pkgdb(1) occasionally going a bit > funny is a problem that's been known about for some time; usually just > deleting and rebuilding /var/db/pkg/pkgdb.db will sort things out. > However, I don't think anyone had ever tracked down the root cause of > the problem. Then the portsdb coredumping thing came along, and it > seems an obvious conclusion that the same thing might be affecting > both programs. > > Note that a fix for the bdb1_btree problem has been in HEAD for a few > weeks, and was MFC'd to both RELENG_4 and RELENG_5 a week or so ago. > So an alternative fix could be cvsup+buildworld. Unfortunately, I > don't think the fix will be applied to any of the existing 4.x-RELEASE > or 5.x-RELEASE branches -- it will of course be in 5.3-RELEASE when > that comes out, and it's pretty easy to do if you want to patch things > yourself. > > > I'll go ahead and try this, but I suspect that the > /var/db/pkg info for > > gnucash or one of it's dependancies got horked up. We'll see. > > > > > Then execute this in your shell also. Then do: > > > pkgdb -u && portsdb -u && portupgrade -R gnucash > > Yup. That should ensure you get a clean install of gnucash and all of > its dependencies. > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks > Savill Way > PGP: http://www.infracaninophile.co.uk/pgpkey Marlow > Tel: +44 1628 476614 Bucks., > SL7 1TH UK >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F414F4699FE1CF46B9DB1CE71D04BACB0E0C50F5>