portupgrade-2.2.2_1,2 corrupts portsdb

[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 +0000
> [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.........10000.........11000.........12000.........13000.........14000.........15000.... 
> ..... done]
> missing key: categories: Cannot read the portsdb!
> --->  Session ended at: Wed, 31 Jan 2007 15:44:50 +0000 (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 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
> 


-- 
Regards,
Eric