On Thu, 15 Jun 2000, Edward S. Marshall wrote:
>
> http://home.xnet.com/~emarshal/rpm/
>
> If you're brave, go ahead and give them a try; as soon as I've had a
> chance to test them, I'll let everyone know.
Just as an FYI, the upgrade went semi-smoothly. Here's what I discovered:
- you'll need to define %_dbapi to be 1, since your database will still be
in the old format; you can do that by editing ~/.rpmmacros (or the
global file /etc/rpm/macros) and adding a line "%_dbapi 1", or from the
command line, do "rpm --define '_dbapi 1' [...]". If you don't, you'll
be greeted with a message telling you essentially what I just did. ;-)
- DON'T try something silly like:
rpm --define '_dbapi 1' --define '_dbapi_convert 3' --rebuilddb
This will work (ie. RPM will no longer complain about the versioning
of the API interface), but you'll discover that the only thing that
works is "rpm -qa"...only the Packages file gets updated, and all the
rest remain untouched. RPM gurus: am I missing something, or is the
new version simply not updating Names, etc?
- If you find you want to downgrade again, here's my step-by step. It
seems to have worked without problems (ie. when I shot myself in the
foot with the above step ;-), so I've got a path back and forth between
versions. :-)
a) grab 3.0.x RPMs (ftp.rpm.org or the RH 6.2 CD, for example), you'll
probably want all of rpm, rpm-build, rpm-devel, rpm-python, and popt.
b) "rpm -Uvh --nodeps rpm* popt*"
c) "rpm --rebuilddb"
d) "rpm -q redhat-release" just to verify you're back in business.
So, anyone have any suggestions for getting my existing RPM database
successfully converted to db3 format? :-)
--
Edward S. Marshall <[EMAIL PROTECTED]> UNIX Administrator
http://www.nyx.net/~emarshal/ Mercantec, Inc.
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
