Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Choose Software Update or ADD/Delete program from menu and fill out password Result: Component: Software Manager Summary: TB8a9160cb comps.py:143:parse_package_list:CompsException Traceback (most recent call last): File "/usr/sbin/pirut", line 453, in ? main() File "/usr/sbin/pirut", line 449, in main pm.run() File "/usr/sbin/pirut", line 358, in run self.doRefresh() File "/usr/sbin/pirut", line 373, in doRefresh self.reposSetup(pbar) File "/usr/lib/python2.4/site-packages/pirut/__init__.py", line 153, in reposSetup self.doGroupSetup() File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 408, in doGroupSetup self.comps.add(groupfile) File "/usr/lib/python2.4/site-packages/yum/comps.py", line 339, in add group = Group(elem) File "/usr/lib/python2.4/site-packages/yum/comps.py", line 57, in __init__ self.parse(elem) File "/usr/lib/python2.4/site-packages/yum/comps.py", line 133, in parse self.parse_package_list(child) File "/usr/lib/python2.4/site-packages/yum/comps.py", line 143, in parse_package_list raise CompsException CompsException Local variables in innermost frame: genre: optinoal self: Graphics package: digikam packagelist_elem: <Element 'packagelist' at 0x18ba090> child: <Element 'packagereq' at 0x18b8c60>
Created attachment 146513 [details] dump: Pirut instant crash on package info retrieval x86_64 t5600 merom
Comment on attachment 146513 [details] dump: Pirut instant crash on package info retrieval same here. Linux oplaport4 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:39:22 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
Same here. Linux yoda.darkside 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 18:32:37 EST 2007 i686 i686 i386 GNU/Linux
Seems that someone botched the description for one of the packages in the database (it's near digicam). Where it should've said "optional" it says "optinoal". Modifying 2 lines of code in /usr/lib/python2.4/site-packages/yum/comps.py solved my problem (it's a quick and dirty hack, nevertheless). I guess we need to wait until they correct the typo in the repos.
*** This bug has been marked as a duplicate of 224292 ***