Hide Forgot
Description of problem: Pirut fails to resolve dependencies for packages when adding the Development Libraries, Development Tools and Java Development categories to a newly installed Core 7 Test3 system Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. Select Add/Remove software from the Applications menu 2. Add Development Libraries, Development Tools and Java Development 3. Click Apply Actual results: Component: Software Manager Summary: TB8a9b4f2f packageSack.py:600:returnNewestByNameArch:PackageSackError: No Package Matching glibc.i686 Traceback (most recent call last): File "/usr/sbin/pirut", line 336, in _apply self.applyChanges(self.mainwin) File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 698, in applyChanges self.checkDeps(mainwin) File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 467, in checkDeps (result, msgs) = self.buildTransaction() File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 543, in buildTransaction (rescode, restring) = self.resolveDeps() File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 972, in _resolveDeps (checkdep, missing, conflict, errormsgs) = self._processReq(dep) File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 437, in _processReq requirementTuple, errormsgs) File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 558, in _requiringFromInstalled po = self.pkgSack.returnNewestByNameArch((name,arch))[0] File "/usr/lib/python2.5/site-packages/yum/packageSack.py", line 308, in returnNewestByNameArch return bestofeach.returnNewestByNameArch(naTup) File "/usr/lib/python2.5/site-packages/yum/packageSack.py", line 600, in returnNewestByNameArch raise PackageSackError, 'No Package Matching %s.%s' % naTup PackageSackError: No Package Matching glibc.i686 Local variables in innermost frame: highdict: {} self: <yum.packageSack.ListPackageSack object at 0x6355d10> naTup: ('glibc', 'i686') where: None Expected results: Software install Additional info:
What versions of pirut and yum do you have installed? If you update both of them to the current development versions, does this still occur?
After running the update to the latest versions (as found by the auto updater) the problem no longer occurs. The problem occurred when using the "stock" versions delivered with the x86_64 versions of Fedora Core 7 Test3.