The following was filed automatically by anaconda: anaconda 14.19 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/yum/sqlitesack.py", line 55, in newFunc raise Errors.RepoError, str(e) File "/usr/lib/python2.7/site-packages/yum/sqlitesack.py", line 298, in _loadFiles "WHERE packages.pkgId = ?", (self.pkgId,)) File "/usr/lib/python2.7/site-packages/yum/sqlitesack.py", line 372, in returnFileTypes self._loadFiles() File "/usr/lib64/python2.7/site-packages/pyanaconda/yuminstall.py", line 900, in getDownloadPkgs for filetype in txmbr.po.returnFileTypes(): File "/usr/lib64/python2.7/site-packages/pyanaconda/yuminstall.py", line 1492, in doPostSelection (self.dlpkgs, self.totalSize, self.totalFiles) = self.ayum.getDownloadPkgs() File "/usr/lib64/python2.7/site-packages/pyanaconda/backend.py", line 277, in doPostSelection return anaconda.backend.doPostSelection(anaconda) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 212, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 131, in gotoNext self.moveStep() File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1190, in nextClicked self.anaconda.dispatch.gotoNext() RepoError: database disk image is malformed
Created attachment 453389 [details] Attached traceback automatically from anaconda.
Created attachment 453406 [details] Attached traceback automatically from anaconda.
Steps: 0. Prepared a F-13 minimal installed system in KVM. 1. Boot F14-Final-TC1-disc1.iso on the system. 2. Choose 'upgrade system' and select 'Create new bootloader configuration'. Click 'Next' 3. You'll see a screen popped up saying: The software you have selected for install require the following discs: #1, #2. 4. Don't click 'continue'. Just force off the guest 5. Execute the above step1 and 2 again, exception occurred during checking dependencies. Reproducible: 100%
Sounds like turning off the guest has somehow corrupted the RPM database, since it was likely open at the time. I'm not sure there's anything anyone can do about this
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping