RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #952227 +++

+++ This bug was initially created as a clone of Bug #521273 +++

Escalated to Bugzilla from IssueTracker

--- Additional comment from Issue Tracker on 2009-09-04 11:46:36 EDT ---

Event posted on 09-04-2009 11:44am 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, gimp in RHEL5 has at least one python executable containing #!/usr/bin/env python
This event sent from IssueTracker by kbaxley  [LLNL (HPC)]
 issue 339039

This is a purely cosmetic issue. GIMP maps script hashbangs to a fixed interpreter internally. This system skips over /usr/bin/env if present. For python, it would map both "#!/usr/bin/env python" and "#!/usr/bin/python" to /usr/bin/python, cf.: ${libdir}/gimp/2.0/interpreters/pygimp.interp

I'll leave this bug open in the even I fix it upstream, but this should really have no impact beyond the confusion of people looking at the hashbang line.

This is fixed in gimp-2.8.4-5.el7 already, and later versions which we already have in RHEL-7.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.