Red Hat Bugzilla – Bug 455836
rpm doesn't automatically clean old db environment
Last modified: 2009-12-18 01:15:11 EST
rawhide running inside vmware
did a "yum upgrade -y" after not having used that image for a while
yum downloaded and installed and cleaned up, but then failed with an error message.
the command "rpm -qi rpm yum" produces more error messages
see attached text file
Created attachment 312105 [details]
output of yum update
Rpm itself got updated and the Berkeley DB version it uses for rpmdb changed,
nothing to worry about here: Just do "rm -f /var/lib/rpm/__db*" to clean up the
Berkeley DB environment from old version, it's not corrupted or anything.
The only bug here is that the environment cleanup isn't done automatically as it
Thanks a lot, after the removal I can use yum and rpm again.
Please feel free to resolve this as WORKSFORME (unless you want to keep it open
for the automatic cleanup on rpm update)
Changing summary to better describe the actual issue, leaving open as the issue
is something I want to get fixed soonish.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
*** Bug 485081 has been marked as a duplicate of this bug. ***
Occurred again in F11 rawhide when db4 upgrade from 4.5 to 4.7.
*** Bug 485142 has been marked as a duplicate of this bug. ***
*** Bug 489225 has been marked as a duplicate of this bug. ***
*** Bug 493470 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.