Description of problem: Relying on env to execute python can cause unreliable results if the user were to install python from another source (upstream perhaps). Version-Release number of selected component (if applicable): 1.7.x How reproducible: 100% Steps to Reproduce: 1.install a separate python 2. 3. Actual results: [user@host ~]$ sudo sysreport Traceback (most recent call last): File "/usr/sbin/sysreport", line 31, in ? import sos.policyredhat ImportError: No module named sos.policyredhat [user@host ~]$ which python /tool/pandora64/bin/python Expected results: no import failure Additional info:
Created attachment 305001 [details] Proposed patch Just replace #!/usr/bin/env python with #!/usr/bin/python.
Cloned Bugzilla Bug 446081 for RHEL 4.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Customer has verified that packages built with the patch in Comment #2 work on their system with a second Python interpreter.
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. http://rhn.redhat.com/errata/RHBA-2009-0171.html