Re: portupgrade failing, portsdb error

On Fri, 20 Apr 2007, Drew Sanford wrote:

I get the following error:

root@drew(/usr/ports)# portupgrade gnome-vfs
[Updating the portsdb <format:bdb_btree> in /usr/ports ... - 16885 port entries found .........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000.........11000.........12000.........13000.........14000.........15000.........16000........ ..... done]
[missing key: categories] [Updating the portsdb <format:bdb_btree> in /usr/ports ... - 16885 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!
/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've got Index up to date, I've run portsdb -u, and it seems to think everything is good. Any recommendations? I've not seen this error before. Thanks in advance.

I saw this when I didn't have the portupgrade port upgraded properly. It has changed the location.

From /usr/ports/UPDATING:

20070205:
AFFECTS: everybody
AUTHOR: pav@xxxxxxxxxxx

New ports category was created - /usr/ports/ports-mgmt

Most significant port moved to this new category is portupgrade.
So don't be alarmed, it was not deleted. You can find it now in

/usr/ports/ports-mgmt/portupgrade

_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: portsdb problem
    ... Out of the blue portsdb has become foobar'd. ... The only change I've made recently is installing portsearch and running ... I've tried the two recovery methods in the portupgrade ... currently 2.2.2,2 and as soon as the cvs mirrors are free I'll be giving it ...
    (comp.unix.bsd.freebsd.misc)
  • portupgrade errors
    ... beichuan# portupgrade -a ... missing key: categories: Cannot read the portsdb! ...
    (freebsd-current)
  • portupgrade errors
    ... beichuan# portupgrade -a ... missing key: categories: Cannot read the portsdb! ...
    (freebsd-questions)
  • Re: Portupgrade and "Updating the portsdb"
    ... Then I say "portupgrade samba" on 2nd server it says again ... and rebuild portsdb. ... INDEX INDEX-5 DESCRIBE.5 ...
    (freebsd-questions)
  • Re: portupgrade -arR errors
    ... missing key: categories: Cannot read the portsdb! ... database file error from ... portupgrade, reinstalling portupgrade then ...
    (freebsd-stable)