Drew Tomlinson <[EMAIL PROTECTED]> writes: > Thanks for all the replies. Funny thing is that when trying the > "portupgrade -o" solution and using "pkg_info | grep portupgrade", no > results were returned. The /var/db/pkg directory had no portupgrade* > entries. Thus I just used "portupgrade -N portupgrade" to upgrade. > All seemed OK. I did notice a "make config" window that asked me > which version of Berkeley DB to use for the backend. Not knowing, I > just chose the default of ">=2" and the port built without error.
Missing entries in the package database? Could be a problem, although more likely it's just a mistake of some sort. > Next I attempted "pkgdb -L" suggested in the pkg-message file. It > returned this error: > > blacksheep# pkgdb -L > [Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... > /var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid argument; > rebuild needed] [Rebuilding the pkgdb <format:bdb_btree> in /var/db/pkg ... > /var/db/pkg/pkgdb.db: unexpected file type or format -- > Invalid argument: Cannot update the pkgdb!]: Cannot update the pkgdb!] > > I assume this is due to choosing the incorrect Berkeley DB version? > So should I rebuild the portupgrade port and choose Berkeley DB 1.85 > or is it recommended to convert the pkgdb to the newer version? If I > should convert, how? My build machine is powered down today, so I can't get the exact answer, but it was in /usr/ports/UPDATING at the time. _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"