Red Hat Bugzilla – Bug 521888
Fix instances of #!/usr/bin/env python in mailman
Last modified: 2013-04-15 05:06:28 EDT
Escalated to Bugzilla from IssueTracker
Event posted on 09-08-2009 11:40am 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:
There's also a Fedora bug opened on this, and comments in there state
that this is a big priority for RHEL6:
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, mailman in RHEL5 has at least one instance of a
python script containing #!/usr/bin/env python.
/usr/lib/mailman/Mailman/Post.py in mailman-2.1.9-4.el5
/usr/lib/mailman/Mailman/Archiver/pipermail.py in mailman-2.1.9-4.el5
/usr/lib/mailman/bin/msgfmt.py in mailman-2.1.9-4.el5
/usr/lib/mailman/tests/onebounce.py in mailman-2.1.9-4.el5
/usr/share/doc/mailman-2.1.9/admin/www/reset_pw.py in mailman-2.1.9-4.el5
/usr/share/doc/mailman-2.1.9/contrib/migrate-fhs in mailman-2.1.9-4.el5
This event sent from IssueTracker by kbaxley [LLNL (HPC)]
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 "?".
Created attachment 406268 [details]
#! lines changed in those files
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
In accordance with current guidelines, all Python executables have been updated to use "#!/usr/bin/python" instead of "#!/usr/bin/env python".
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.