Description of problem: Running debuginfo-install using the --skip-broken option causes python traceback attached. Version-Release number of selected component (if applicable): yum-3.2.10-3.fc9.noarch yum-utils-1.1.11-1.fc9.noarch Steps to Reproduce: 1. debuginfo-install firefox epiphany galeon 2. due to libgnat issue in rawhide today this fails, see attach 3. using --skip-broken produces the traceback
Created attachment 294181 [details] debuginfo-skip-broken.txt, traceback
The traceback itself is: (for bugzilla searches) Traceback (most recent call last): File "/usr/bin/debuginfo-install", line 116, in <module> util = DebugInfoInstall() File "/usr/bin/debuginfo-install", line 42, in __init__ self.main() File "/usr/bin/debuginfo-install", line 70, in main self.buildTransaction() File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 587, in buildTransaction rescode, restring = self._skipPackagesWithProblems(rescode, restring) File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 622, in _skipPackagesWithProblems rescode, restring = self.resolveDeps() File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 738, in resolveDeps CheckDeps, checkinstalls, checkremoves, missing = self._resolveRequires(errors) File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 832, in _resolveRequires (checkdep, missing, errormsgs) = self._processReq(po, dep) File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 260, in _processReq CheckDeps, missingdep = self._requiringFromInstalled(po, requirement, errormsgs) File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 375, in _requiringFromInstalled pkgs = self.pkgSack.returnNewestByName(name) File "/usr/lib/python2.5/site-packages/yum/packageSack.py", line 347, in returnNewestByName return bestofeach.returnNewestByName(name) File "/usr/lib/python2.5/site-packages/yum/packageSack.py", line 752, in returnNewestByName raise PackageSackError, 'No Package Matching %s' % name yum.Errors.PackageSackError: No Package Matching libgconf-java
This error is fixed in upstream yum HEAD, so it sould work when yum 3.2.11 is released soon.
Problem appears to be fixed, just tested a case that should have triggered it like before.