portupgrade-2.2.2_1,2 corrupts portsdb
in [Ports]
|
From: "[LoN]Kamikaze" on 31 Jan 2007 17:07 Eric Schuele wrote: > I'm seeing this as well. Though I had thought it was because my > `/usr/ports/make fetchindex` had failed. > > Anyone else? Me too, on two 6-Stable machines. _______________________________________________ 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 31 Jan 2007 17:28 Same here... Out of the blue... Removing old files and directories... done. Extracting new files: /usr/ports/audio/prokyon3/ /usr/ports/devel/cogito/ /usr/ports/net/ipw-firmware-kmod/ /usr/ports/net/iwi-firmware-kmod/ /usr/ports/textproc/xmlto/ /usr/ports/www/libwww/ Building new INDEX files... done. Updating the ports db file INDEX.db [Updating the portsdb <format:bdb_btree> in /usr/ports ... - 16412 port entries found ..........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000.........11000.........12000.........13000.........14000.........15000.........16000.... ...... done] Done... Upgrading all outdated ports, and all the depended and depending ones, using portupgrade. It will update dependencies and make a pkgdb -aF to record them Press any key to continue, or CTRL-C to abort within 10 secs Proceeding... ---> Session started at: Wed, 31 Jan 2007 22:21:17 +0000 [missing key: categories] [Updating the portsdb <format:bdb_btree> in /usr/ports ... - 16412 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! ---> Session ended at: Wed, 31 Jan 2007 22:21:47 +0000 (consumed 00:00:29) /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:548:in `open_db': database file error (PortsDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:702:in `port' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:890:in `all_depends_list' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:809:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:801:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:801:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:823:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:827:in `sort_build!' from /usr/local/sbin/portupgrade:721:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 I recreated the database (pkgdb -fu), nothing.. I rebuilt the ruby18-portupgrade, nothing... I Rechecked the /usr/ports/UPDATING for sth that I might have missed because I didn't remember any reference to one of my ports. Help! Regards, Vassilis On Wed, Jan 31, 2007 at 11:04:04PM +0100, [LoN]Kamikaze wrote: > Eric Schuele wrote: > > I'm seeing this as well. Though I had thought it was because my > > `/usr/ports/make fetchindex` had failed. > > > > Anyone else? > > Me too, on two 6-Stable machines. > _______________________________________________ > 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"
From: Bartosz Fabianowski on 31 Jan 2007 19:03 > Something broken in INDEX :( For the record: I am using p5-FreeBSD-Portindex-1.8 to build INDEX-6 and have received a reply off list from somebody who has the same problems with an INDEX-6 retrieved via make fetchindex. So, it's not just a single broken INDEX-6 file on the server that needs rebuilding, it's something deeper within the ports infrastructure that will keep corrupting index builds until it gets fixed. - Bartosz _______________________________________________ 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: Csaba Molnar on 31 Jan 2007 20:17 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"
From: Karol Kwiatkowski on 31 Jan 2007 20:46
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig472BA81B4FBF48E0B2D53A1E Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Resending. I made a mistake, on 6.2-RELEASE portupgrade-2.2.2,2 is installed. Sorry! 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,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 --------------enig472BA81B4FBF48E0B2D53A1E 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 iD8DBQFFwUXNezeoPAwGIYsRCB0oAJ93xRkytEM26slXqViD3vMi1qTnpgCdFEW0 SSyMPrVz/T4XzY5wUTOcZn0= =KkVv -----END PGP SIGNATURE----- --------------enig472BA81B4FBF48E0B2D53A1E-- |