Red Hat Bugzilla – Bug 979397
[abrt] yum-3.4.3-54.fc18: sqlitecachec.py:46:getPrimary:TypeError: Parsing primary.xml error: Document is empty
Last modified: 2014-02-05 18:12:39 EST
Version-Release number of selected component:
cmdline: /usr/bin/python /usr/bin/yum update
runlevel: N 5
sqlitecachec.py:46:getPrimary:TypeError: Parsing primary.xml error: Document is empty
Traceback (most recent call last):
File "/usr/bin/yum", line 29, in <module>
File "/usr/share/yum-cli/yummain.py", line 319, in user_main
errcode = main(args)
File "/usr/share/yum-cli/yummain.py", line 144, in main
result, resultmsgs = base.doCommands()
File "/usr/share/yum-cli/cli.py", line 485, in doCommands
return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
File "/usr/share/yum-cli/yumcommands.py", line 405, in doCommand
return base.updatePkgs(extcmds, update_to=(basecmd == 'update-to'))
File "/usr/share/yum-cli/cli.py", line 899, in updatePkgs
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 4739, in update
updates = self.up.getUpdatesTuples()
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1033, in <lambda>
up = property(fget=lambda self: self._getUpdates(),
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 840, in _getUpdates
self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList())
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1014, in <lambda>
pkgSack = property(fget=lambda self: self._getSacks(),
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 780, in _getSacks
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 352, in populateSack
sack.populate(repo, mdtype, callback, cacheonly)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 257, in populate
dobj = repo_cache_function(xml, csum)
File "/usr/lib64/python2.7/site-packages/sqlitecachec.py", line 46, in getPrimary
TypeError: Parsing primary.xml error: Document is empty
Local variables in innermost frame:
self: <sqlitecachec.RepodataParserSqlite instance at 0x3bf4cb0>
Potential duplicate: bug 879069
Created attachment 766552 [details]
Created attachment 766553 [details]
Created attachment 766554 [details]
Can you check that '/var/cache/yum/x86_64/18/adobe-linux-x86_64/gen/primary.xml' is indeed an empty file? There might be a bug in MD verification or decompression code, but I'm afraid this is not going to be easy to reproduce.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.
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 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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 to Fedora 18's end of life.
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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.