Portupgrade problem, possible pkgdb problem?
mnavarre at cox.net
Sat Sep 25 14:35:50 PDT 2004
I'm trying to upgrade gnucash, but portupgrade is choking:
reichlieu# portupgrade -R gnucash
/usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot convert
nil into String (PkgDB::DBError)
from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build'
from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each'
from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build'
from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each'
from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build'
from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build'
from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!'
from /usr/local/sbin/portupgrade:674:in `main'
from /usr/local/sbin/portupgrade:207:in `initialize'
from /usr/local/sbin/portupgrade:207:in `new'
from /usr/local/sbin/portupgrade:207:in `main'
It looks like the pkgdb has something wrong with it, but pkgdb -Fu doesn't
report anything that seems like it would cause portupgrade to bomb. There's a
duplicate origin for cdrtools, but that doesn't seem to pertain.
Should I move /var/db/pkg/pkgdb.db out of the way and regenerate it? Will
pkgdb -u recreate pkgdb.db?
"We all enter this world in the same way: naked, screaming,
and soaked in blood. But if you live your life right, that kind
of thing doesn't have to stop there." -- Dana Gould
More information about the freebsd-questions