Date: Sun, 19 Sep 2004 12:45:06 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Anthony Philipp <philipp1@itg.uiuc.edu> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: core dump with portupgrade Message-ID: <20040919114506.GE51161@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <20040918215538.GA18451@zeus.itg.uiuc.edu> References: <20040918215538.GA18451@zeus.itg.uiuc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Sat, Sep 18, 2004 at 04:55:38PM -0500, Anthony Philipp wrote:
> Hello, when I was trying to upgrade my laptop with the latest ports this is what happened.
>
>
>
> (16:50:29) root@jigen /home/philipp1 1# portupgrade -arR
> Stale dependency: ORBit-0.5.17_1 --> gettext-0.12.1 -- manually run 'pkgdb -F' t
> o fix, or specify -O to force.
> (16:51:17) root@jigen /home/philipp1 2# pkgdb -F
> ---> Checking the package registry database
> Duplicated origin: textproc/expat2 - expat-1.95.6_1 expat-1.95.7
> Unregister any of them? [no]
> Duplicated origin: databases/ruby-bdb1 - ruby-bdb1-0.2.1 ruby18-bdb1-0.2.2
> Unregister any of them? [no] yes
> Unregister ruby-bdb1-0.2.1 keeping the installed files intact? [no] yes
> -> ruby18-bdb1-0.2.2 is kept.
> --> Saving the ruby-bdb1-0.2.1's +CONTENTS file as /var/db/pkg/ruby18-bdb1-0.2.2/+CONTENTS.ruby-bdb1-0.2.1
> --> Unregistering ruby-bdb1-0.2.1
> --> Done.
> [Updating the pkgdb <format:bdb1_btree> in /var/db/pkg ... - 284 packages found (-1 +0) (...) done]
> Stale dependency: ORBit-0.5.17_1 -> gettext-0.12.1 (devel/gettext):
> [Failed `Inappropriate file type or format'] [Updating the portsdb <format:bdb1_btree> in /usr/ports ... - 11733 port entries found .........1000.........2000.........3000.........4000.........5000......./usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Segmentation fault
> ruby 1.8.2 (2004-07-29) [i386-freebsd5]
>
> Abort trap (core dumped)
>
>
>
> Also the same thing happened when I did portsdb -Uu or portversion -l "<"
> I can post those if required, and this is highly reproducible, so just ask if you need more info.
You're not the only one to have been bitten by this. Search the
archives for extensive mailing list traffic on this subject -- but in
short, a work around is:
# setenv PORTS_DBDDRIVER bdb1_hash
before you start running portsdb(1) or portupgrade(1).
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
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)
iD8DBQFBTXFCiD657aJF7eIRAidEAJ90CViSPBG2gkOjX1qCnNzdnqryRQCgqpcg
OWDQTEROVf55QC9CVBs585Y=
=xLBM
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040919114506.GE51161>