How to Upgrade Berkeley DB? (Was Re: How to Upgrade Portupgrade?)
On 4/27/2007 10:58 AM Lowell Gilbert wrote: 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 in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid argument; rebuild needed] [Rebuilding the pkgdb 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. I just searched /usr/ports/UPDATING. I only find two entries, neither of which seems to cover my situation: 20061130: AFFECTS: users of net/openldap2[34]-server AUTHOR: [EMAIL PROTECTED] The default Berkeley DB version has been changed from 4.3 to 4.4, as suggested by OpenLDAP developers. 0060403: AFFECTS: users of databases/db* AUTHOR: [EMAIL PROTECTED] Most of the ports that depend on Berkeley DB have been updated to use Mk/bsd.database.mk. Mk/bsd.database.mk is used to include MySQL, PostgreSQL, Berkeley DB, and SQLite in a port. A quick Google search didn't reveal anything specific to FBSD and portupgrade on how to upgrade Berkeley DB. However I will keep looking. If you come across something on how I should update my systems to use the latest stable Berkeley DB and convert all dbs to that version, I'd appreciate the link. Thanks, Drew -- Be a Great Magician! Visit The Alchemist's Warehouse http://www.alchemistswarehouse.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to Upgrade Portupgrade?
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 in /var/db/pkg ... > /var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid argument; > rebuild needed] [Rebuilding the pkgdb 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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to Upgrade Portupgrade?
On 4/27/2007 6:40 AM Lowell Gilbert wrote: Kevin Kinsey <[EMAIL PROTECTED]> writes: Drew Tomlinson wrote: So this seems like updating portupgrade should be trivial but I am stuck. Suggestions appreciated. Yeah, I missed the note on this one, too. Not the change note, but I don't recall seeing the instructions on what to do about it. Tried deinstalling portupgrade and reinstalling? The catch-22, of course, is that you can't "cd /usr/ports/sysutils/portupgrade" in order to `make deinstall`. However, this might work (and I believe it's the kludge I used to get around the issue): $ rm -rf /var/db/pkg/portupgrade* $ cd /usr/ports/ports-mgmt/portupgrade $ make install clean A little safer would be to replace the first line with "pkg_delete portupgrade*". If you're not going to go with the "portupgrade -o" solution that someone already posted. 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. Next I attempted "pkgdb -L" suggested in the pkg-message file. It returned this error: blacksheep# pkgdb -L [Updating the pkgdb in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid argument; rebuild needed] [Rebuilding the pkgdb 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? Thanks, Drew -- Be a Great Magician! Visit The Alchemist's Warehouse http://www.alchemistswarehouse.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to Upgrade Portupgrade?
Lowell Gilbert wrote: Kevin Kinsey <[EMAIL PROTECTED]> writes: Drew Tomlinson wrote: So this seems like updating portupgrade should be trivial but I am stuck. Suggestions appreciated. Yeah, I missed the note on this one, too. Not the change note, but I don't recall seeing the instructions on what to do about it. Tried deinstalling portupgrade and reinstalling? The catch-22, of course, is that you can't "cd /usr/ports/sysutils/portupgrade" in order to `make deinstall`. However, this might work (and I believe it's the kludge I used to get around the issue): $ rm -rf /var/db/pkg/portupgrade* $ cd /usr/ports/ports-mgmt/portupgrade $ make install clean A little safer would be to replace the first line with "pkg_delete portupgrade*". If you're not going to go with the "portupgrade -o" solution that someone already posted. Yeah, I think Chris hit that one right. Portupgrade_guru hat to him ;-) KDK -- The more they over-think the plumbing the easier it is to stop up the drain. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to Upgrade Portupgrade?
Kevin Kinsey <[EMAIL PROTECTED]> writes: > Drew Tomlinson wrote: > >> So this seems like updating portupgrade should be trivial but I am >> stuck. Suggestions appreciated. > > Yeah, I missed the note on this one, too. Not the change note, but > I don't recall seeing the instructions on what to do about it. > Tried deinstalling portupgrade and reinstalling? The catch-22, > of course, is that you can't "cd /usr/ports/sysutils/portupgrade" > in order to `make deinstall`. However, this might work (and I believe > it's the kludge I used to get around the issue): > > $ rm -rf /var/db/pkg/portupgrade* > $ cd /usr/ports/ports-mgmt/portupgrade > $ make install clean A little safer would be to replace the first line with "pkg_delete portupgrade*". If you're not going to go with the "portupgrade -o" solution that someone already posted. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to Upgrade Portupgrade?
Drew Tomlinson wrote: So this seems like updating portupgrade should be trivial but I am stuck. Suggestions appreciated. Yeah, I missed the note on this one, too. Not the change note, but I don't recall seeing the instructions on what to do about it. Tried deinstalling portupgrade and reinstalling? The catch-22, of course, is that you can't "cd /usr/ports/sysutils/portupgrade" in order to `make deinstall`. However, this might work (and I believe it's the kludge I used to get around the issue): $ rm -rf /var/db/pkg/portupgrade* $ cd /usr/ports/ports-mgmt/portupgrade $ make install clean HTH, Kevin Kinsey -- Schmidt's Observation: All things being equal, a fat person uses more soap than a thin person. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to Upgrade Portupgrade?
Drew Tomlinson wrote: I'm attempting to update my systems. I see that portupgrade has been moved to ports-mgmt/portupgrade in early February. I've Googled but can not find any posts (there must be some?) on the proper steps to update. I tried the standard and here is the output: lacksheep# portupgrade -n ports-mgmt/portupgrade cd: can't cd to /usr/ports/sysutils/portupgrade ---> Session started at: Fri, 27 Apr 2007 05:16:17 -0700 ** No such installed package: ports-mgmt/portupgrade ** None has been installed or upgraded. Hi Drew, Try portupgrade and specify the origin using the new path and the name of the installed portupgrade package, e.g.: portupgrade -f -o ports-mgmt/portupgrade portupgrade-2.0.1_1,1 You can get the exact name of the installed portupgrade package by running the following: pkg_info | grep portupgrade I hope this helps! All the best. - Chris Slothouber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to Upgrade Portupgrade?
I'm attempting to update my systems. I see that portupgrade has been moved to ports-mgmt/portupgrade in early February. I've Googled but can not find any posts (there must be some?) on the proper steps to update. I tried the standard and here is the output: lacksheep# portupgrade -n ports-mgmt/portupgrade cd: can't cd to /usr/ports/sysutils/portupgrade ---> Session started at: Fri, 27 Apr 2007 05:16:17 -0700 ** No such installed package: ports-mgmt/portupgrade ** None has been installed or upgraded. So I thought maybe my package database needed to be updated (a guess). Here is that output: blacksheep# pkgdb -F cd: can't cd to /usr/ports/sysutils/portupgrade ---> Checking the package registry database Missing origin: bsdpan-CPAN-1.90 -> Ignored. (the package is held; specify -f to force) Missing origin: bsdpan-Term-ReadLine-Perl-1.0302 -> Ignored. (the package is held; specify -f to force) Missing origin: bsdpan-TermReadKey-2.30 -> Ignored. (the package is held; specify -f to force) Missing origin: bsdpan-libnet-1.20 -> Ignored. (the package is held; specify -f to force) Duplicated origin: net/p5-NetPacket - bsdpan-NetPacket-0.04 p5-NetPacket-0.04 Unregister any of them? [no] Nothing about portupgrade. However I don't understand all the "Missing origin" lines or what I should do to fix them. So this seems like updating portupgrade should be trivial but I am stuck. Suggestions appreciated. Thanks, Drew -- Be a Great Magician! Visit The Alchemist's Warehouse http://www.alchemistswarehouse.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
