Description of problem: Can't use Package/Software Manager (or Yum) to install glibc for x86_64. I need gcc to be able to compile the Nvidia kernel for the latest 100.14.11 binary driver. This is on a fresh install of F7 KDE (for AMD64). Exception Occured error dump: 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 337, in _apply self.applyChanges(self.mainwin) File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 718, in applyChanges self.checkDeps(mainwin) File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 481, in checkDeps (result, msgs) = self.buildTransaction() File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 549, in buildTransaction (rescode, restring) = self.resolveDeps() File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 853, in resolveDeps (checkdep, missing, conflict, errormsgs) = self._processReq(dep) File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 337, in _processReq requirementTuple, errormsgs) File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 456, 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 0x681bc50> naTup: ('glibc', 'i686') where: None
I think I might have found a way around it. I tried doing this in a console... yum install glibc yum install gcc ... and it seemed to work. The gcc wouldn't install unless glibc had been installed or updated first. I managed to get the Nvidia driver working after this. Associated with bug #232378
*** This bug has been marked as a duplicate of 252378 ***