Bug 119115
Summary: | RFE: real error mesage when dir repository backend can't access file | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Mike MacCana <mmaccana> |
Component: | up2date | Assignee: | Bret McMillan <bretm> |
Status: | CLOSED WONTFIX | QA Contact: | Fanny Augustin <fmoquete> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | Keywords: | Reopened |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 19:28:32 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: | 120092 |
Description
Mike MacCana
2004-03-25 06:28:51 UTC
Internal RFE bug #119630 entered; will be considered for future releases. Thank you for the suggestion. It was passed along to product management, but not committed for a future release. Closing this as notabug is *terrible*. * The message clearly is a bug. A Python traceback does not constitute an error message. * Having something like this in a supposedly finished OS look really unprofessional. * The bug shouldn't be difficult to fix. Ping? Seriously, we should not consider crashing Python an adequate error message. I think the bug was originally closed because it was marked as an RFE when it got imported into the feature request tracker. REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred. This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |