abrt 1.1.1 detected a crash.
cmdline: /usr/bin/python -E /usr/share/yumex/yumex-yum-backend --help
comment: Yumex-backend keeps cashing before yumex starts
reason: yumex-yum-backend:65:<module>:NameError: name 'yum_conf' is not defined
release: Fedora release 13 (Goddard)
yumex-yum-backend:65:<module>:NameError: name 'yum_conf' is not defined
Traceback (most recent call last):
File "/usr/share/yumex/yumex-yum-backend", line 65, in <module>
my = YumServer(debuglevel, plugins, offline, repos, yum_conf)
NameError: name 'yum_conf' is not defined
Local variables in innermost frame:
signal: <module 'signal' (built-in)>
__builtins__: <module '__builtin__' (built-in)>
sys: <module 'sys' (built-in)>
YumexBackendFatalError: <class 'yumexbase.YumexBackendFatalError'>
yum: <module 'yum' from '/usr/lib/python2.6/site-packages/yum/__init__.pyc'>
sigquit: <function sigquit at 0x7f375e455320>
os: <module 'os' from '/usr/lib64/python2.6/os.pyc'>
__doc__: '\nThe yum child task started by yumex in the background\n'
YumServer: <class 'yumexbackend.yum_server.YumServer'>
Created attachment 426943 [details]
This is in the current release in testing.
yum --enablerepo=updates-testing update yumex
yumex-3.0.0-1.fc13 has been submitted as an update for Fedora 13.
yumex-3.0.0-1.fc14 has been submitted as an update for Fedora 14.
yumex-3.0.0-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update yumex'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/yumex-3.0.0-1.fc14
yumex-3.0.0-2.fc13 has been submitted as an update for Fedora 13.
yumex-3.0.0-2.fc14 has been submitted as an update for Fedora 14.
yumex-3.0.0-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
yumex-3.0.0-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.