Version-Release number of selected component:
cmdline: /usr/bin/python /usr/bin/yum update
runlevel: N 5
sqlitesack.py:395:returnPrco:DatabaseError: database disk image is malformed
Traceback (most recent call last):
File "/usr/bin/yum", line 29, in <module>
File "/usr/share/yum-cli/yummain.py", line 316, in user_main
errcode = main(args)
File "/usr/share/yum-cli/yummain.py", line 172, in main
(result, resultmsgs) = base.buildTransaction()
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1146, in buildTransaction
(rescode, restring) = self.resolveDeps()
File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 877, in resolveDeps
CheckDeps, checkinstalls, checkremoves, missing = self._resolveRequires(errors)
File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 996, in _resolveRequires
thisneeds = self._checkRemove(txmbr)
File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 1111, in _checkRemove
for pkg, hits in self.tsInfo.getRequires(*prov).iteritems():
File "/usr/lib/python2.7/site-packages/yum/transactioninfo.py", line 657, in getRequires
result.update(self.getNewRequires(name, flag, version))
File "/usr/lib/python2.7/site-packages/yum/transactioninfo.py", line 638, in getNewRequires
for pkg, hits in self._inSack.getRequires(name, flag, version).iteritems():
File "/usr/lib/python2.7/site-packages/yum/packageSack.py", line 721, in getRequires
File "/usr/lib/python2.7/site-packages/yum/packageSack.py", line 655, in _checkIndexes
File "/usr/lib/python2.7/site-packages/yum/packageSack.py", line 855, in buildIndexes
File "/usr/lib/python2.7/site-packages/yum/transactioninfo.py", line 55, in _addPackageToIndex
for (n, fl, (e,v,r)) in obj.returnPrco('requires'):
File "/usr/lib/python2.7/site-packages/yum/sqlitesack.py", line 395, in returnPrco
for ob in cur:
DatabaseError: database disk image is malformed
Local variables in innermost frame:
cur: <sqlite3.Cursor object at 0x1cb01f0>
self: <YumAvailablePackageSqlite : nss-tools-3.15-2.fc19.x86_64 (0x4233790)>
ob: <sqlite3.Row object at 0x485b890>
prco_set: ('libnss3.so(NSS_3.9.2)(64bit)', None, (None, None, None))
sql: 'SELECT name, version, release, epoch, flags FROM requires WHERE pkgKey = ?'
Created attachment 766631 [details]
Created attachment 766632 [details]
Created attachment 766633 [details]
Thank you for the bug report. The stack trace reported indicates a corruption in the files holding the yum metadata. Please try yum clean all and retry the transaction.
You may also want to check your hardware in case your underlying hard disk is failing.
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
Thank you for reporting this bug and we are sorry it could not be fixed.