portupgrade-2.2.2_1,2 corrupts portsdb
in [Ports]
|
From: Karol Kwiatkowski on 31 Jan 2007 21:05 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig91A084AB1B2B616AE3D654C3 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Csaba Molnar wrote: > I deleted /var/db/pkg/pkgdb.db, then rebuilt it with pkgdb -u I think, = and=20 > that seems to have worked.=20 >=20 > While I was updating ports before this error showed up, the options scr= een for=20 > portupgrade showed up - and option WITH_BDB4 was unchecked. I changed t= hat=20 > (so portupgrade was now built with bdb4) - and the problems began right= after=20 > this update.=20 To help to narrow the problem (both using portsnap and today's ports tree= ): FreeBSD 6.2-STABLE portupgrade-2.2.2_1,2 ruby18-bdb-0.5.9_2 db44-4.4.20.4 format:bdb_btree =3D problem FreeBSD 6.2-RELEASE portupgrade-2.2.2_1,2 ruby18-bdb-0.5.9_2 db44-4.4.20.4 format:dbm_hash =3D no problem HTH, Karol --=20 Karol Kwiatkowski <karol.kwiat at gmail dot com> OpenPGP 0x06E09309 --------------enig91A084AB1B2B616AE3D654C3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFwUNnezeoPAwGIYsRCLU1AJwMS4XAsuDgfDroV5NvykomNQ9F+wCeLsOs UHqeI4TJ6qMhQOfDLQWBFqM= =Zd7V -----END PGP SIGNATURE----- --------------enig91A084AB1B2B616AE3D654C3--
From: Philip Kizer on 1 Feb 2007 01:58 On 2007, Jan 31, at 18:45, Csaba Molnar wrote: > I deleted /var/db/pkg/pkgdb.db, then rebuilt it with pkgdb -u I > think, and > that seems to have worked. > > While I was updating ports before this error showed up, the options > screen for > portupgrade showed up - and option WITH_BDB4 was unchecked. I > changed that > (so portupgrade was now built with bdb4) - and the problems began > right after > this update. I think you are on the right track, I had a working stable portupgrade/portsdb environment and after the last update I started getting that as well...my options for portupgrade to use BDB4 were unchanged from before through after the upgrade: WITH_BDB4 was true for both cases. If I recompile portupgrade with: WITHOUT_BDB4=true WITH_BDB1=true which also requires me to pkg_delete ruby-bdb, then it all seems to work just fine with no more warnings or errors. After a bit more trial and error, I find I can replicate the problem by performing the following: # portinstall databases/ruby-bdb # portversion -l'<' -v [missing key: categories] [Updating the portsdb <format:bdb_btree> in /usr/ports ... - 16414 port entries found ......... 1000.........2000.........3000.........4000.........5000.........6000... ....... 7000.........8000.........9000.........10000.........11000.........12000 ..........13000.........14000.........15000.........16000.... ..... done] missing key: categories: Cannot read the portsdb! [...snip...] # portversion -l'<' -v [missing key: categories] [Updating the portsdb <format:bdb_btree> in /usr/ports ... - 16414 port entries found ......... 1000.........2000.........3000.........4000.........5000.........6000... ....... 7000.........8000.........9000.........10000.........11000.........12000 ..........13000.........14000.........15000.........16000.... ..... done] missing key: categories: Cannot read the portsdb! and then I can remove any visible problems by performing: # pkg_delete ruby18-bdb-0.5.9_2 # portversion -l'<' -v [Updating the pkgdb <format:bdb1_btree> in /var/db/pkg ... Failed `Inappropriate file type or format'; rebuild needed] [Rebuilding the pkgdb <format:bdb1_btree> in /var/db/pkg ... - 428 packages found (-0 +428) .................................................................. ......................................................................... ......................................................................... ......................................................................... ......................................................................... ......................................................................... ... done] [Failed `Inappropriate file type or format'] [Updating the portsdb <format:bdb1_btree> in /usr/ports ... - 16414 port entries found ......... 1000.........2000.........3000.........4000.........5000.........6000... ....... 7000.........8000.........9000.........10000.........11000.........12000 ..........13000.........14000.........15000.........16000.... ..... done] [...snip...] # portversion -l'<' -v [...snip...] -philip _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: "=?ISO-8859-1?Q?Murilo_Opsfelder_Ara=FAjo?=" on 1 Feb 2007 08:03 On 2/1/07, Philip Kizer <pckizer(a)nostrum.com> wrote: > On 2007, Jan 31, at 18:45, Csaba Molnar wrote: > > I deleted /var/db/pkg/pkgdb.db, then rebuilt it with pkgdb -u I > > think, and > > that seems to have worked. > > > > While I was updating ports before this error showed up, the options > > screen for > > portupgrade showed up - and option WITH_BDB4 was unchecked. I > > changed that > > (so portupgrade was now built with bdb4) - and the problems began > > right after > > this update. > > I think you are on the right track, I had a working stable > portupgrade/portsdb environment and after the last update I started > getting that as well...my options for portupgrade to use BDB4 were > unchanged from before through after the upgrade: WITH_BDB4 was true > for both cases. > > If I recompile portupgrade with: > > WITHOUT_BDB4=3Dtrue > WITH_BDB1=3Dtrue > > which also requires me to pkg_delete ruby-bdb, then it all seems to > work just fine with no more warnings or errors. > > After a bit more trial and error, I find I can replicate the problem > by performing the following: > > # portinstall databases/ruby-bdb > # portversion -l'<' -v > [missing key: categories] [Updating the portsdb <format:bdb_btree> > in /usr/ports ... - 16414 port entries found ......... > 1000.........2000.........3000.........4000.........5000.........6000... > ...... > 7000.........8000.........9000.........10000.........11000.........12000 > .........13000.........14000.........15000.........16000.... ..... done] > missing key: categories: Cannot read the portsdb! > [...snip...] > # portversion -l'<' -v > [missing key: categories] [Updating the portsdb <format:bdb_btree> > in /usr/ports ... - 16414 port entries found ......... > 1000.........2000.........3000.........4000.........5000.........6000... > ...... > 7000.........8000.........9000.........10000.........11000.........12000 > .........13000.........14000.........15000.........16000.... ..... done] > missing key: categories: Cannot read the portsdb! > > > and then I can remove any visible problems by performing: > > # pkg_delete ruby18-bdb-0.5.9_2 > # portversion -l'<' -v > [Updating the pkgdb <format:bdb1_btree> in /var/db/pkg ... Failed > `Inappropriate file type or format'; rebuild needed] [Rebuilding the > pkgdb <format:bdb1_btree> in /var/db/pkg ... - 428 packages found (-0 > +428) .................................................................. > ........................................................................ > ........................................................................ > ........................................................................ > ........................................................................ > ........................................................................ > .. done] > [Failed `Inappropriate file type or format'] [Updating the portsdb > <format:bdb1_btree> in /usr/ports ... - 16414 port entries > found ......... > 1000.........2000.........3000.........4000.........5000.........6000... > ...... > 7000.........8000.........9000.........10000.........11000.........12000 > .........13000.........14000.........15000.........16000.... ..... done] > [...snip...] > # portversion -l'<' -v > [...snip...] > > > > -philip > Hi all, Yesterday I had the same problem and garga@ helped me to solve that. He told me to change my ports database to dbm_hash. Just add these two lines in /usr/local/etc/pkgtools.conf around line number= 160: ENV['PKG_DBDRIVER'] ||=3D 'dbm_hash' ENV['PORTS_DBDRIVER'] ||=3D 'dbm_hash' Remove your pkgdb.db and INDEX.db and rebuild them. The dbm_hash is a little bit more slow, but don't crash :) This change is recommended to servers. I hope this help you. Best regards. --=20 <about> <name>Murilo Opsfelder Ara=FAjo</name> <linux_user>#391561</linux_user> <e-mail>mopsfelder [saispam] gmail [ponto] com</e-mail> </about> _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Sergey Matveychuk on 1 Feb 2007 08:39 Murilo Opsfelder Ara�jo wrote: > Yesterday I had the same problem and garga@ helped me to solve that. > He told me to change my ports database to dbm_hash. It's not a fix really. A fix was committed. Well, it's worth to add a few sanity checks for DB. Really working with DB should be complete rewritten but I have a hard lack of time lately. -- Dixi. Sem. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Laganakos Vassilis on 1 Feb 2007 08:55
Hi, Done that too (pkgdb -fu) , but didn't work for me... :( I use FreeBSD6-stable Vassilis On Thu, Feb 01, 2007 at 01:45:55AM +0100, Csaba Molnar wrote: > 2007. February 1. 00.34 d?tummal Joachim Bethke ezt ?rta: > > Hallo, > > > > I get the same error on two machines too. Have someone a practical idea > > <http://dict.leo.org/ende?lp=ende&p=/gQPU.&search=idea> how to fix it. > > > > Joachim > > > I deleted /var/db/pkg/pkgdb.db, then rebuilt it with pkgdb -u I think, and > that seems to have worked. > > While I was updating ports before this error showed up, the options screen for > portupgrade showed up - and option WITH_BDB4 was unchecked. I changed that > (so portupgrade was now built with bdb4) - and the problems began right after > this update. > _______________________________________________ > freebsd-ports(a)freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" -- _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |