GNOME Bugzilla – Bug 552601
pyconsole.py plug-in is installed, but not executable
Last modified: 2008-10-30 20:16:07 UTC
Please describe the problem: SSIA, the plug-in file is installed in the gimp/2.0/plug-ins directory, but not executable. Steps to reproduce: nils@gibraltar:~> ls -l /usr/lib64/gimp/2.0/plug-ins/pyconsole.py Actual results: -rw-r--r-- 1 root root 21009 2008-05-30 17:10 /usr/lib64/gimp/2.0/plug-ins/pyconsole.py Expected results: -rwxr-xr-x 1 root root 21009 2008-05-30 17:10 /usr/lib64/gimp/2.0/plug-ins/pyconsole.py Does this happen every time? Yes Other information: This is the same in current SVN trunk.
Just noticed that the example above is from a machine with 2.4.6 -- the results on another one with 2.4.7 are similar, though.
Why do you expect that this plug-in should be installed as executable?
This is not a plug-in but just a piece of data used my python-console.py
Then why is it put into the plug-ins directory and not e.g. into $libdir/gimp/2.0/python? And why does it have a she-bang line -- "#!/usr/bin/env python" -- at the top of the file, which is meaningless unless the file is executable? This is a bit inconsistent and has been flagged as an error by rpmlint during the review of the gimp package in Fedora (cf. https://bugzilla.redhat.com/show_bug.cgi?id=225799): gimp.i386: E: non-executable-script /usr/lib/gimp/2.0/plug-ins/pyconsole.py 0644 This text file contains a shebang or is located in a path dedicated for executables, but lacks the executable bits and cannot thus be executed. If the file is meant to be an executable script, add the executable bits, otherwise remove the shebang or move the file elsewhere.
gimp-2.4 doesn't contain python-console.py BTW. Is the situation different on 2.4.x?
Addressed in trunk: 2008-09-17 Sven Neumann <sven@gimp.org> * plug-ins/pygimp/plug-ins/pyconsole.py: removed she-bang as this file is not a plug-in. Addresses bug #552601.