Re: portupgrade-2.2.2_1,2 corrupts portsdb
On 2/1/07, Philip Kizer [EMAIL PROTECTED] 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=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.1.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.1.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.1.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'] ||= 'dbm_hash' ENV['PORTS_DBDRIVER'] ||= '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. -- about nameMurilo Opsfelder Araújo/name linux_user#391561/linux_user e-mailmopsfelder [saispam] gmail [ponto] com/e-mail /about ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
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=endep=/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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
On 2/1/07, Sergey Matveychuk [EMAIL PROTECTED] wrote: 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. Thanks Sergey. Works now. -David -- [EMAIL PROTECTED] ~]# fortune Happiness is just an illusion, filled with sadness and confusion. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
Have you updated portupgrade to the last one (2.2.2_3,2)? Do it please. Laganakos Vassilis wrote: 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=endep=/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. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
On Thu, Feb 01, 2007 at 04:37:02PM +0300, Sergey Matveychuk wrote: 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. Goood to hear thhere's a fix. What do I need to pkg_delete and what rebuild? I have 5 FBSD severs that are constantly being portmanager'd or portupgraded. thanks! gary -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
Gary Kline wrote: On Thu, Feb 01, 2007 at 04:37:02PM +0300, Sergey Matveychuk wrote: 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. Goood to hear thhere's a fix. What do I need to pkg_delete and what rebuild? I have 5 FBSD severs that are constantly being portmanager'd or portupgraded. thanks! gary -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] I did a portsnap, followed by make deinstall and make install on portupgrade, followed by a portupgrade and was successful. brian ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
On Thu, Feb 01, 2007 at 11:55:21AM -0800, Brian wrote: Gary Kline wrote: On Thu, Feb 01, 2007 at 04:37:02PM +0300, Sergey Matveychuk wrote: 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. Goood to hear thhere's a fix. What do I need to pkg_delete and what rebuild? I have 5 FBSD severs that are constantly being portmanager'd or portupgraded. thanks! gary -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] I did a portsnap, followed by make deinstall and make install on portupgrade, followed by a portupgrade and was successful. That's what I did as a test. I've got that string aliased as kdr:). One down, 4 togo. gary brian -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
That worked :D I updated portupgrade and then the portupgrade was smooth! Thanx! Vassilis On Thu, Feb 01, 2007 at 09:46:59PM +0300, Sergey Matveychuk wrote: Have you updated portupgrade to the last one (2.2.2_3,2)? Do it please. Laganakos Vassilis wrote: 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=endep=/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. -- Dixi. Sem. -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade-2.2.2_1,2 corrupts portsdb
Hi all As part of the daily portupgrade run on my 6-STABLE box, I upgraded sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried running this version, I got the following error message: %portupgrade -ai --- Session started at: Wed, 31 Jan 2007 15:44:44 + [missing key: categories] [Updating the portsdb format:bdb_btree in /usr/ports ... - 15487 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000 . done] missing key: categories: Cannot read the portsdb! --- Session ended at: Wed, 31 Jan 2007 15:44:50 + (consumed 00:00:05) /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 Apparently, the portsdb database is corrupted somehow, gets rebuilt but is still not acceptable. According to the error message, a key named categories seems to be missing from some table. Has anyone else experience this? Is there a workaround or a fix? - Bartosz ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
On 01/31/2007 09:48, Bartosz Fabianowski wrote: Hi all As part of the daily portupgrade run on my 6-STABLE box, I upgraded sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried running this version, I got the following error message: %portupgrade -ai --- Session started at: Wed, 31 Jan 2007 15:44:44 + [missing key: categories] [Updating the portsdb format:bdb_btree in /usr/ports ... - 15487 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000 . done] missing key: categories: Cannot read the portsdb! --- Session ended at: Wed, 31 Jan 2007 15:44:50 + (consumed 00:00:05) /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 Apparently, the portsdb database is corrupted somehow, gets rebuilt but is still not acceptable. According to the error message, a key named categories seems to be missing from some table. Has anyone else experience this? Is there a workaround or a fix? I'm seeing this as well. Though I had thought it was because my `/usr/ports/make fetchindex` had failed. Anyone else? - Bartosz ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- Regards, Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
Ons 2007-01-31 klockan 11:29 -0600 skrev Eric Schuele: On 01/31/2007 09:48, Bartosz Fabianowski wrote: Hi all As part of the daily portupgrade run on my 6-STABLE box, I upgraded sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried running this version, I got the following error message: %portupgrade -ai --- Session started at: Wed, 31 Jan 2007 15:44:44 + [missing key: categories] [Updating the portsdb format:bdb_btree in /usr/ports ... - 15487 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000 . done] missing key: categories: Cannot read the portsdb! --- Session ended at: Wed, 31 Jan 2007 15:44:50 + (consumed 00:00:05) /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 Apparently, the portsdb database is corrupted somehow, gets rebuilt but is still not acceptable. According to the error message, a key named categories seems to be missing from some table. Has anyone else experience this? Is there a workaround or a fix? I'm seeing this as well. Though I had thought it was because my `/usr/ports/make fetchindex` had failed. Anyone else? I get the same error. -- Joel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
Joel Dahl a écrit : Ons 2007-01-31 klockan 11:29 -0600 skrev Eric Schuele: On 01/31/2007 09:48, Bartosz Fabianowski wrote: Hi all As part of the daily portupgrade run on my 6-STABLE box, I upgraded sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried running this version, I got the following error message: %portupgrade -ai --- Session started at: Wed, 31 Jan 2007 15:44:44 + [missing key: categories] [Updating the portsdb format:bdb_btree in /usr/ports ... - 15487 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000 . done] missing key: categories: Cannot read the portsdb! --- Session ended at: Wed, 31 Jan 2007 15:44:50 + (consumed 00:00:05) /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 Apparently, the portsdb database is corrupted somehow, gets rebuilt but is still not acceptable. According to the error message, a key named categories seems to be missing from some table. Has anyone else experience this? Is there a workaround or a fix? I'm seeing this as well. Though I had thought it was because my `/usr/ports/make fetchindex` had failed. Anyone else? I get the same error. Me too: files/1fba0d7141faec5fdd5806962c8df4b6eed5bcd9e5da53243d4a1813a94de21c.gz not found -- snapshot corrupt. and now I had some file in /usr/ports that i cannot remove... i had to boot in single user mode to do a fsck ... fuck Nomad ___ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
Joel Dahl a écrit : Ons 2007-01-31 klockan 11:29 -0600 skrev Eric Schuele: On 01/31/2007 09:48, Bartosz Fabianowski wrote: Hi all As part of the daily portupgrade run on my 6-STABLE box, I upgraded sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried running this version, I got the following error message: %portupgrade -ai --- Session started at: Wed, 31 Jan 2007 15:44:44 + [missing key: categories] [Updating the portsdb format:bdb_btree in /usr/ports ... - 15487 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000 . done] missing key: categories: Cannot read the portsdb! --- Session ended at: Wed, 31 Jan 2007 15:44:50 + (consumed 00:00:05) /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 Apparently, the portsdb database is corrupted somehow, gets rebuilt but is still not acceptable. According to the error message, a key named categories seems to be missing from some table. Has anyone else experience this? Is there a workaround or a fix? I'm seeing this as well. Though I had thought it was because my `/usr/ports/make fetchindex` had failed. Anyone else? I get the same error. for info i use portsnap ___ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
* Bartosz Fabianowski ([EMAIL PROTECTED]) wrote: As part of the daily portupgrade run on my 6-STABLE box, I upgraded sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried running this version, I got the following error message: %portupgrade -ai --- Session started at: Wed, 31 Jan 2007 15:44:44 + [missing key: categories] [Updating the portsdb format:bdb_btree in /usr/ports ... - 15487 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000 . done] missing key: categories: Cannot read the portsdb! Same here. Though I don't think portupgrade's upgrade is the cause, as I've used portupgrade-2.2.2_1,2 for some time already without problems. So more likely the cause is new category in ports (ports-mgmt) or new virtual category gnustep. -- Best regards, Dmitry Marakasov mailto:[EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
Hi Portupgrade problems here as well. Rico ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
On 1/31/07, Bartosz Fabianowski [EMAIL PROTECTED] wrote: Hi all As part of the daily portupgrade run on my 6-STABLE box, I upgraded sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried running this version, I got the following error message: %portupgrade -ai --- Session started at: Wed, 31 Jan 2007 15:44:44 + [missing key: categories] [Updating the portsdb format:bdb_btree in /usr/ports ... - 15487 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000 . done] missing key: categories: Cannot read the portsdb! --- Session ended at: Wed, 31 Jan 2007 15:44:50 + (consumed 00:00:05) /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 Apparently, the portsdb database is corrupted somehow, gets rebuilt but is still not acceptable. According to the error message, a key named categories seems to be missing from some table. Has anyone else experience this? Is there a workaround or a fix? I too am having the same issue, though I had thought it was because I accidentily interrupted (Ctrl-C) portsdb from updating. However, even when running 'portsdb -FUu', or even removing all of /usr/ports and retrieving the tree again I still see the same error: [EMAIL PROTECTED] ~]# portupgrade -airR --- Session started at: Wed, 31 Jan 2007 16:01:28 -0500 [missing key: categories] [Updating the portsdb format:bdb_btree in /usr/ports ... - 16411 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000 . done] missing key: categories: Cannot read the portsdb! --- Session ended at: Wed, 31 Jan 2007 16:01:39 -0500 (consumed 00:00:11) /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 -David -- [EMAIL PROTECTED] ~]# fortune Happiness is just an illusion, filled with sadness and confusion. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
David Stanford wrote: missing key: categories: Cannot read the portsdb! Something broken in INDEX :( -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
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.1.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 + [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.1.11000.12000.13000.14000.15000.16000 . done] missing key: categories: Cannot read the portsdb! --- Session ended at: Wed, 31 Jan 2007 22:21:47 + (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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade-2.2.2_1,2 corrupts portsdb
Hallo, I get the same error on two machines too. Have someone a practical idea http://dict.leo.org/ende?lp=endep=/gQPU.search=idea how to fix it. Joachim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
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=endep=/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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade-2.2.2_1,2 corrupts portsdb
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. 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 = 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 = no problem HTH, Karol -- Karol Kwiatkowski karol.kwiat at gmail dot com OpenPGP 0x06E09309 signature.asc Description: OpenPGP digital signature
Re: portupgrade-2.2.2_1,2 corrupts portsdb
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.1.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.1.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.1.11000.12000 .13000.14000.15000.16000 . done] [...snip...] # portversion -l'' -v [...snip...] -philip ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
