Red Hat Bugzilla – Bug 867400
RpmDBError: Package tuple ('m17n-contrib', 'noarch', '0', '1.1.14', '1.fc18') could not be found in rpmdb
Last modified: 2014-06-16 08:47:58 EDT
Description of problem:
I know there was a repository problem with pulseaudio, I kept changing repositories and having it recheck my package list...
Version-Release number of selected component:
libreport version: 2.0.14
cmdline: /usr/bin/python /sbin/anaconda
:The following was filed automatically by anaconda:
:anaconda 18.16 exception report
:Traceback (most recent call first):
: File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3837, in getInstalledPackageObject
: raise Errors.RpmDBError, _('Package tuple %s could not be found in rpmdb') % str(pkgtup)
: File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 1249, in _checkFileRequires
: po = self.getInstalledPackageObject(pkgtup)
: File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 882, in resolveDeps
: for po, dep in self._checkFileRequires():
: File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1120, in buildTransaction
: (rescode, restring) = self.resolveDeps()
: File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1106, in checkSoftwareSelection
: (code, msgs) = self._yum.buildTransaction(unfinished_transactions_check=False)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/software.py", line 89, in checkSoftwareSelection
: File "/usr/lib64/python2.7/threading.py", line 504, in run
: self.__target(*self.__args, **self.__kwargs)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run
: threading.Thread.run(self, *args, **kwargs)
:RpmDBError: Package tuple ('m17n-contrib', 'noarch', '0', '1.1.14', '1.fc18') could not be found in rpmdb
Created attachment 628774 [details]
Created attachment 628775 [details]
Created attachment 628776 [details]
Created attachment 628777 [details]
Created attachment 628778 [details]
Created attachment 628779 [details]
Created attachment 628780 [details]
Created attachment 628781 [details]
Created attachment 628782 [details]
Created attachment 628783 [details]
Created attachment 628784 [details]
Created attachment 628785 [details]
Created attachment 628786 [details]
Created attachment 628787 [details]
I've been trying without succeeding to reproduce this for a little while now. Since it was reported, however, I've also committed a fix related to changing settings in the software spoke, so perhaps I have inadvertently fixed this bug. Can you please retest with a tree containing anaconda-18.22 (not built yet, check back soon) and see if this is fixed for you? Thanks.
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.