By upgrading to rpm 4.0 I noted the old database was unavailable. The
problem happened as rpm initializes the base instead of rebuilding it.
Besides, after this one cannot rebuild the old database while the new
one remains in /var/lib/rpm. So one needs to remove the new database
files (nfl: keep the *.rpm's in place! They ARE the old database) and
only then start rpm --rebuild. For a newbye this may be not so evident
or clear. And he will get the painful path of fighting missing
dependencies of packages that in fact are in their places. Sincerly such
situation turns rpm into a completely useless tool, so think that this
should be corrected as soon as possible.
Ektanoor
