I had the same rpm db problem that was reported here by a few others, and got
a few emails on the subject as well. Here is how to fix (at least this worked
for me).
1. Do not use Mandrake Update to update the RPM packages from 3.x to 4.x
there are a ton of dependencies that you need to resolve first. popt and db3
are some of the ones I know about. Mandrake Update will not install new
packages, it just updates existing ones.
2. If you already found out #1 the hard way (like me), go to /var/lib/rpm as
root and copy the *.rpm files to a safe location. Make sure that you have the
db3*, and popt* packages installed and resolved all the dependency issues.
3. Delete the following files (or if you're chicken move them to another
place):
Basenames Packages
Conflictname Providename
Group Requirename
Name Triggername
(DO NOT DELETE THE ONES WITH THE .rpm extension).
4. now do an rpm -qa and you should get a message telling you that you need
to do an rpm --rebuilddb as root. Now follow the instructions and type "rpm
--rebuilddb".
This solved the problem on one of my test machines. Note, you may also have
to run "update-menus" following the database rebuild as your menus may be
messed up as well.
Hope this helps someone!
-Chris
