Red Hat Bugzilla – Bug 587288
repomanage tracebacks, when given a bad path
Last modified: 2014-01-21 01:17:32 EST
abrt 1.0.7 detected a crash.
cmdline: /usr/bin/python /usr/bin/repomanage -
release: Red Hat Enterprise Linux release 6.0 Beta (Santiago)
Traceback (most recent call last):
File "/usr/bin/repomanage", line 234, in <module>
File "/usr/bin/repomanage", line 133, in main
rpmList = getFileList(mydir, '.rpm', rpmList)
File "/usr/bin/repomanage", line 53, in getFileList
raise Error, 'Error accessing directory %s, %s' % (path, e.message)
Local variables in innermost frame:
e: OSError(2, 'No such file or directory')
How to reproduce
1. repomanage -
Created attachment 410123 [details]
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
This is fixed upstream, it's a simple patch (just don't throw an exception as well as tell the user the path is bad). I also only happens when the user specifies a path that doesn't exist, so...
yum-utils-1.1.27-1.fc13 has been submitted as an update for Fedora 13.
yum-utils-1.1.27-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
Still reproducible with: yum-utils-1.1.26-9.el6.noarch
Can you not see -10?
The traceback is gone. Should we open a separate tracking bug for the deprecation warning?
$ repomanage -
/usr/bin/repomanage:52: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
errorprint('Error accessing directory %s, %s' % (path, e.message))
Error accessing directory -,
No files to process
I applied a patch upstream that gets fixes the deprecation warning from this message, though it is completely harmless itself.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.