Description of Problem:
This is not a big deal but it does need to be fixed.
Some (all?) rpm messages which refer to the database specifically say "db3"
rather than "db4".
An example of this can be seen by attempting to install/update a package as a
REGULAR (non root) user:
error: cannot get exclusive lock on /var/lib/rpm/Packages
error: cannot open Packages index using db3 - Operation not permitted (1)
error: cannot open Packages database in /var/lib/rpm
For all that matter, why does rpm need to mention "db3" at all ... why not
The explicit "db3" is a remnant from the
elimination of db-1.85 usage. FWIW, "db3"
is perfectly accurate, even though db-4.1.17
is the current implementation internal to
rpm, as that's rpm's name for the type of
database used. Yes, confusing.
Simply punting to "database" in error messages will happen
eventually, but there is still content in the token "db3",
describing which of several possible database API's caused
the message to be printed.