Bug 587288
| Summary: | repomanage tracebacks, when given a bad path | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Eduard Benes <ebenes> | ||||
| Component: | yum-utils | Assignee: | James Antill <james.antill> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 6.0 | ||||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | abrt_hash:b190182a | ||||||
| Fixed In Version: | yum-utils-1.1.26-10.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 620652 (view as bug list) | Environment: | |||||
| Last Closed: | 2010-11-10 22:01:20 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 620652 | ||||||
| Attachments: |
|
||||||
Created attachment 410123 [details]
File: backtrace
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 inclusion. 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. http://admin.fedoraproject.org/updates/yum-utils-1.1.27-1.fc13 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. |
abrt 1.0.7 detected a crash. architecture: x86_64 cmdline: /usr/bin/python /usr/bin/repomanage - component: yum-utils executable: /usr/bin/repomanage kernel: 2.6.32-22.el6.x86_64 package: yum-utils-1.1.26-7.el6 reason: repomanage:53:getFileList:Error release: Red Hat Enterprise Linux release 6.0 Beta (Santiago) backtrace ----- repomanage:53:getFileList:Error Traceback (most recent call last): File "/usr/bin/repomanage", line 234, in <module> main(sys.argv[1:]) 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) Error Local variables in innermost frame: extlen: 4 path: '-' ext: '.rpm' e: OSError(2, 'No such file or directory') filelist: [] How to reproduce ----- 1. repomanage - 2. 3.