Created attachment 449751 [details] This shows the current problem (: unable to update some packages Description of problem: During the regular update of packages in Fedora, the laptop overheated and powered down suddenly. Then, after I booted Fedora and ran "yum complete transaction", the transaction could not be completed or rolled back because the RPM database was corrupted. Thus no update was possible. "yum clean all" and rebuilding the database (deleted /var/lib/rpm/__db* and then ran "rpm --rebuilddb -vv") made the update possible and I updated all the packages. Still, there are some packages reported to have "duplicities" in the RPM database that I cannot update. Version-Release number of selected component (if applicable): yum-3.2.28-4.fc13.noarch rpm-4.8.1-2.fc13.i686 How reproducible: While updating the system, cut power (pull out the power cord and remove the battery, if there is any). But I think there is no reliable way to reproduce this error. It's non-deterministic. Actual results: RPM database corrupted, unable to use yum to update anything. After rebuliding the RPM database, update works but some packages still cannot be updated. Expected results: The RPM database uses transactions. That means, this state (stuck with a corrupted database, unable to rollback) should not be possible to happen even if the power is cut down on any time. Safe rollback should be always possible. Yet it happened and that means something is broken there. The update mechanism does not guarantee safe rollback despite using a database with transactions where it theoretically should be guaranteed. Note: Both the disk partitions my Fedora uses are Ext3.
> The RPM database uses transactions. That means, this state (stuck with a > corrupted database, unable to rollback) should not be possible to happen even > if the power is cut down on any time. Safe rollback should be always possible. I will note that this is "optimistic", in that even if the software side will guarantee that ... it requires that your HW not do anything weird. And in cases like "my laptop got too hot, and did an emergency power off" I would not assume the HW was acting perfectly.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.