Red Hat Bugzilla – Bug 860721
The /usr/bin/meld script does not use the system Python binary, instead picking the first python on PATH
Last modified: 2013-08-01 13:01:40 EDT
Description of problem:
The /usr/bin/meld executable script starts with "#! /usr/bin/env python",
thus trying to use the Python binary that is first in PATH, instead
of the system Python /usr/bin/python.
Version-Release number of selected component (if applicable):
I have verifiered that this problem is present in F17, F16 and EPEL 6.
First in PATH, put a "python" bin directory belonging to a Python installation
that does not have all the modules needed by meld.
Cannot import: pygtk
No module named pygtk
meld starting OK
Change /usr/bin/meld during packaging, so that it uses
"#!/usr/bin/python" instead of "#! /usr/bin/env python"
Start meld with "/usr/bin/python /usr/bin/meld" when a non-system
python binary is first on PATH.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.