Bug 521880
Summary: | Fix instances of #!/usr/bin/env python in librsvg2 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Issue Tracker <tao> |
Component: | librsvg2 | Assignee: | Matthias Clasen <mclasen> |
Status: | CLOSED WONTFIX | QA Contact: | desktop-bugs <desktop-bugs> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.4 | CC: | cww, tao |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-02 13:20:59 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: | 502912, 521940, 590060 |
Description
Issue Tracker
2009-09-08 15:23:25 UTC
Event posted on 09-08-2009 11:21am EDT by kbaxley There's a project underway in Fedora 12 to finally resolve the issues with Red Hat including #!/usr/bin/env python in our python executables: https://fedoraproject.org/wiki/Features/SystemPythonExecutablesUseSystemPython There's also a Fedora bug opened on this, and comments in there state that this is a big priority for RHEL6: https://bugzilla.redhat.com/show_bug.cgi?id=518994 For RHEL5, we've been instructed by Product Management to open bugs on a package-by-package basis to address the problem. In this case, librsvg2 in RHEL5 has at least one instance of a python script containing #!/usr/bin/env python. # head -1 /usr/bin/rsvg #!/usr/bin/env python This event sent from IssueTracker by kbaxley [LLNL (HPC)] issue 339850 This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?". What's the justification for this? I don't like touching RHEL packages just for the sake of it. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug. Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support). The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |