Red Hat Bugzilla – Bug 471731
Yumex Error Type: <class 'yum.update_md.UpdateNoticeException'>
Last modified: 2009-01-06 05:17:12 EST
Description of problem:
Since November 13th, many users encounter the same problem : yumex fails with Error Type: <class 'yum.update_md.UpdateNoticeException'>
Error messages are the following :
Error Type: <class 'yum.update_md.UpdateNoticeException'>
Error Value: No id element found
File : /usr/share/yumex/yumex.py , line 737, in <module>
mainApp = YumexApplication()
File : /usr/share/yumex/yumex.py , line 446, in __init__
File : /usr/share/yumex/yumex.py , line 467, in setupYum
File : /usr/share/yumex/yumapi.py , line 80, in _setupBase
File : /usr/share/yumex/yumapi.py , line 137, in _setupUpdateMetadata
File : /usr/lib/python2.5/site-packages/yum/update_md.py , line 319, in add
un = UpdateNotice(elem)
File : /usr/lib/python2.5/site-packages/yum/update_md.py , line 69, in __init__
File : /usr/lib/python2.5/site-packages/yum/update_md.py , line 146, in _parse
raise UpdateNoticeException("No id element found")
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Every time Yumex is started
Yumex aborts with error above
try to do a 'yum clean all'
and start yumex again.
i have made a new release of yumex, there will handle these kind of error a lot better.
they will hit updates-testing at next push.
but the main issue is that the update metadata is corrupted in some way, but yumex should be able to handle that and the new release should do that.
yum clean all doesn't help.
I installed yumex-2.0.5-1.fc9.noarch.rpm and it run fine.
Version number has not been changed and window tittle and About box still display 2.0.4 and not 2.0.5.
the version number is fixed in yumex-2.0.5-3.fc9.noarch.rpm :)
there must be some problem with the update metadata, could you please
attach the following file
so i can check it out.
*** Bug 471786 has been marked as a duplicate of this bug. ***
Created attachment 323719 [details]
yumex-2.0.5-3.fc9 fixed here.
(In reply to comment #7)
> Created an attachment (id=323719) [details]
are there other update metadata files ?
the one you attached look ok at first look.
Created attachment 323758 [details]
Created attachment 323759 [details]
Created attachment 323760 [details]
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
this should be fixed in 2.0.5