Description of problem: Prior to this this I have updated 4 times with no problem. Software updater caused and unhandled exception error when selecting view updates. See log data in Acutual result section below. Version-Release number of selected component (if applicable): How reproducible: Always when selecting view updates. 25 updates were available for installation. Steps to Reproduce: 1.Select update 2.Select view update 3.Exception Occurred Box appears Actual results: Component: Software Updater Summary: TB8a9160cb comps.py:143:parse_package_list:CompsException Traceback (most recent call last): File "/usr/sbin/pup", line 659, in ? main() File "/usr/sbin/pup", line 655, in main pup.run() File "/usr/sbin/pup", line 494, in run self.doRefresh() File "/usr/sbin/pup", line 269, 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 0x89ec068> child: <Element 'packagereq' at 0x89e3f68> Expected results: Additional info:
This looks like it was caused by a mistyped entry in the comps XML file (which stores the packages and grouping information). I've fixed this in CVS and it should go out with the next Extras push (likely tomorrow). Please let us know if that resolves your issue when the next Extras release is pushed. Thanks for your bug report.
[ Oops; Changing the component. ]
Just got this same crash. I have used pirut many times since fresh FC6 install two weeks ago. Here is my crash dump: ---------------------------------------------------------------- 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 0x94fd110> child: <Element 'packagereq' at 0x94fd020> ---------------------------------------------------------------- This also appears to be the same problem for bug #224290
Beside fixing the comps.xml... shouldn't pirut be able to cope with bad input data ? I do not think that throwing an exception and dying in pain is the right choice... a better way would be to sanitize the input, wouldn't it ?
*** Bug 224314 has been marked as a duplicate of this bug. ***
*** Bug 224290 has been marked as a duplicate of this bug. ***
*** Bug 224326 has been marked as a duplicate of this bug. ***
*** Bug 224345 has been marked as a duplicate of this bug. ***
*** Bug 224287 has been marked as a duplicate of this bug. ***
*** Bug 224319 has been marked as a duplicate of this bug. ***
*** Bug 224321 has been marked as a duplicate of this bug. ***
My apologies, the comps typos were committed by me yesterday.
updated comps files have been pushed to fedoraproject.org master repo
*** Bug 224366 has been marked as a duplicate of this bug. ***
*** Bug 224382 has been marked as a duplicate of this bug. ***
*** Bug 224323 has been marked as a duplicate of this bug. ***
*** Bug 224358 has been marked as a duplicate of this bug. ***
*** Bug 224391 has been marked as a duplicate of this bug. ***
*** Bug 224372 has been marked as a duplicate of this bug. ***
*** Bug 224403 has been marked as a duplicate of this bug. ***
*** Bug 224404 has been marked as a duplicate of this bug. ***
*** Bug 224426 has been marked as a duplicate of this bug. ***
*** Bug 224375 has been marked as a duplicate of this bug. ***
*** Bug 224337 has been marked as a duplicate of this bug. ***
*** Bug 224356 has been marked as a duplicate of this bug. ***
*** Bug 224428 has been marked as a duplicate of this bug. ***
*** Bug 224423 has been marked as a duplicate of this bug. ***
*** Bug 224419 has been marked as a duplicate of this bug. ***
*** Bug 224425 has been marked as a duplicate of this bug. ***
*** Bug 224376 has been marked as a duplicate of this bug. ***
*** Bug 224386 has been marked as a duplicate of this bug. ***
*** Bug 224384 has been marked as a duplicate of this bug. ***
*** Bug 224390 has been marked as a duplicate of this bug. ***
*** Bug 224389 has been marked as a duplicate of this bug. ***
*** Bug 224401 has been marked as a duplicate of this bug. ***
*** Bug 224410 has been marked as a duplicate of this bug. ***
*** Bug 224374 has been marked as a duplicate of this bug. ***
*** Bug 224362 has been marked as a duplicate of this bug. ***
*** Bug 224355 has been marked as a duplicate of this bug. ***
*** Bug 224353 has been marked as a duplicate of this bug. ***
*** Bug 224354 has been marked as a duplicate of this bug. ***
*** Bug 224348 has been marked as a duplicate of this bug. ***
*** Bug 224349 has been marked as a duplicate of this bug. ***
*** Bug 224339 has been marked as a duplicate of this bug. ***
*** Bug 224342 has been marked as a duplicate of this bug. ***
*** Bug 224325 has been marked as a duplicate of this bug. ***
*** Bug 224333 has been marked as a duplicate of this bug. ***
*** Bug 224293 has been marked as a duplicate of this bug. ***
*** Bug 224330 has been marked as a duplicate of this bug. ***
*** Bug 224300 has been marked as a duplicate of this bug. ***
*** Bug 224307 has been marked as a duplicate of this bug. ***
*** Bug 224303 has been marked as a duplicate of this bug. ***
*** Bug 224308 has been marked as a duplicate of this bug. ***
*** Bug 224288 has been marked as a duplicate of this bug. ***
*** Bug 224396 has been marked as a duplicate of this bug. ***
In Bug 224288 (which has been marked a duplicate of this bug) I could update using 'yum -y update' but still recieved the error with both Yumex And Software Updater. I ran 'yum clean all' and then ran 'yum -y update' and now the error is gone. Yumex still hangs on intial start and Pirut (Software Updater) doesn't give any errors. It seems to me that both programs are having issues with reading yum's cache properly and is throwing incorrect errors and failing because of that problem.
*** Bug 224383 has been marked as a duplicate of this bug. ***
*** Bug 220673 has been marked as a duplicate of this bug. ***
*** Bug 224309 has been marked as a duplicate of this bug. ***
I see comment #1 says the problem has been cleared up ... but how exactly are we supposed to get this update if we are affected by this problem? What package do we need to update to get a new comps.xml? $ rpm -q --whatprovides /var/cache/yum/extras/comps.xml file /var/cache/yum/extras/comps.xml is not owned by any package
*** Bug 224286 has been marked as a duplicate of this bug. ***
*** Bug 216529 has been marked as a duplicate of this bug. ***
I got the same problem, when I ran Package Updater (twice). Last use of the updater, was on Tuesday. A test with "yum update", had no problems and nothing to update.
yum will update the comps.xml as it reaches the timeout for the cache. And I've committed a change to upstream yum to be more forgiving of things like this.
*** Bug 224312 has been marked as a duplicate of this bug. ***
Well, 'yum clean metadata' (which removes /var/cache/yum/extras/comps.xml) and then re-running pup doesn't fix the problem. Have I just not waited long enough?
*** Bug 224450 has been marked as a duplicate of this bug. ***
Just a comment. It seems as if this event has exposed 2 obvious issues/bugs. 1. A metadata file was generated with a typo. This file has been fixed (comment 1). 2. Yum was barfing on bad files. This has been fixed, apparently (comment 64). I would like to suggest (and maybe this belongs in another bug report) that there's another bug: 3. It was even possible to generate a metadata file with a typo. This was obviously a simple typo - but why are these files being hand-generated *and* not pre-tested for accuracy, etc.? You guys need to generate those files with tools, and you also need a tool that verifies the files before they go out to the masses. My 2c. Thanks for the quick fix!
The fix is to run 'yum clean all' and then ran 'yum -y update' as said earlier it does work. Thanks for getting the fixes out there so quickly for us guys! Appreciate it!
*** Bug 224459 has been marked as a duplicate of this bug. ***
*** Bug 224466 has been marked as a duplicate of this bug. ***
*** Bug 224463 has been marked as a duplicate of this bug. ***
*** Bug 224470 has been marked as a duplicate of this bug. ***
I ran 'yum clean all' and then 'yum -y update' But Package Updater still gives the same error. Component: Software Updater Summary: TB8a9160cb comps.py:143:parse_package_list:CompsException Not sure if I've missed something ... since this but is marked closed and nextrelease ...
*** Bug 224474 has been marked as a duplicate of this bug. ***
*** Bug 224478 has been marked as a duplicate of this bug. ***
*** Bug 224486 has been marked as a duplicate of this bug. ***
*** Bug 224485 has been marked as a duplicate of this bug. ***
*** Bug 224492 has been marked as a duplicate of this bug. ***
*** Bug 224469 has been marked as a duplicate of this bug. ***
*** Bug 224495 has been marked as a duplicate of this bug. ***
*** Bug 224502 has been marked as a duplicate of this bug. ***
Just like Comment #75, above, from Rob, I ran 'yum clean all' and then 'yum -y update'. The update command ran in terminal and said it completed successfully. I rebooted the machine and then attempted to run the Package Manager again from the Applications/Add-Remove Software menu. The window popped up requesting my root p/w, which I input and was accepted. The Package Manager opened a window and began to run, but soon ended with a crash - same as before (Bug # 244463). I copy the crash dump below: 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 0x9193110> child: <Element 'packagereq' at 0x9193020> The above two commands did not resolve my original problem. How do I re-open this bug, or do I need to re-enter the bug as NEW?
I have run 'yum clean all' and then 'yum -y update', and both pirut and yumex have successfully run, updated, searched for software, and installed it. Thank you!
re comment #75: software updater seems to work this morning Thanks folks.
*** Bug 224508 has been marked as a duplicate of this bug. ***
*** Bug 224525 has been marked as a duplicate of this bug. ***
*** Bug 224505 has been marked as a duplicate of this bug. ***
*** Bug 224517 has been marked as a duplicate of this bug. ***
*** Bug 224520 has been marked as a duplicate of this bug. ***
*** Bug 224533 has been marked as a duplicate of this bug. ***
*** Bug 224513 has been marked as a duplicate of this bug. ***
(In reply to comment #84) > Just like Comment #75, above, from Rob, I ran 'yum clean all' and then 'yum -y > update'. The update command ran in terminal and said it completed successfully. > I rebooted the machine and then attempted to run the Package Manager again from > the Applications/Add-Remove Software menu. The window popped up requesting my > root p/w, which I input and was accepted. The Package Manager opened a window > and began to run, but soon ended with a crash - same as before (Bug # 244463). I > copy the crash dump below: > > 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 0x9193110> > child: <Element 'packagereq' at 0x9193020> > > The above two commands did not resolve my original problem. How do I re-open > this bug, or do I need to re-enter the bug as NEW? > UPDATED Jan 26, 2007 I just ran the Package Manager (yum) and Software Updater (pirut) again today, and they ran without error. Not sure what happened there. I did have a filesystem problem (different problem altogether) that I fixed this AM - so maybe that was causing my difficulty listed above. Everything seems to be working fine now. Thanks for the help on this one!
I hit this(?) problem, but seem to have landed in a worse boat than most, yum absolutely refuses to do anything now, yumex hangs yum clean all hangs yum --disablerepo=* --noplugins clean all hangs when I say hangs, even ctrl-c wont kill it, needs to be killed -9 from another session, tried purging /var/cache/yum, no help I seem trapped :-(
*** Bug 225047 has been marked as a duplicate of this bug. ***
*** Bug 224503 has been marked as a duplicate of this bug. ***
*** Bug 224368 has been marked as a duplicate of this bug. ***
*** Bug 224371 has been marked as a duplicate of this bug. ***