FS#21459 - [gimp] python extesions are all broken

Attached to Project: Arch Linux
Opened by Skottish (skottish) - Monday, 25 October 2010, 03:10 GMT
Last edited by Eric Belanger (Snowman) - Thursday, 28 October 2010, 01:56 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Eric Belanger (Snowman)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The python upgrade broke all of GIMP's python extensions.

Additional info:

I looked around the source for a quick and easily solution. I thought that a simple change in the py-compile.py file in the top-most directory of the source tree would be the key, but modifications there didn't seem to change anything:

if [ -z "$PYTHON" ]; then
PYTHON=python
fi

-->>

if [ -z "$PYTHON" ]; then
PYTHON=python2
fi
This task depends upon

Closed by  Eric Belanger (Snowman)
Thursday, 28 October 2010, 01:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in :
gimp-2.6.11-1
gimp-devel-2.7.1-3
Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 25 October 2010, 22:27 GMT
Please post a list of affected [extra] packages, so I can assign this to maintainers...
If there are [community] packages affected, please open another bug report.
Comment by Skottish (skottish) - Tuesday, 26 October 2010, 01:22 GMT
gimp and gimp-devel are the two that I'm aware of.
Comment by Rémy Oudompheng (remyoudompheng) - Tuesday, 26 October 2010, 06:15 GMT
Could you please give details about how to notice that anything is broken?
Comment by Eric Belanger (Snowman) - Tuesday, 26 October 2010, 07:29 GMT
Yes, a method to replicate would be helpful as in the current package, the #! line at beginning of python scripts had been fixed already.

Maybe we need to use something like:
PYTHON=python2 PYTHON_VERSION=2.7 ./configure --prefix=/usr --sysconfdir=/etc \
--enable-mp --enable-gimp-console --enable-gimp-remote \
--enable-python --with-gif-compression=lzw \
--without-aa

instead of the sed line in the PKGBUILD.
Comment by Skottish (skottish) - Wednesday, 27 October 2010, 01:58 GMT
I discovered this when I tried to run one of my gimp-python scripts that have run for years with only tiny modifications and it failed with a Python error (I did change the python directive in the file). So, since there was a giant Python ugrade, I decided to try to see if anything in GIMP using Python-Fu works; Nothing that I've tried does. This is an error message from attempting to start the PythonFu console in gimp-devel from the repos:

( Filters--> PythonFu --> Console ):

Traceback (most recent call last):
File "/usr/lib/gimp/2.0/python/gimpfu.py", line 807, in _run
res = apply(func, params[1:])
File "/usr/lib/gimp/2.0/plug-ins/python-console.py", line 32, in do_console
import sys, gobject, gtk, gimpenums, gimpshelf, gimpui, pyconsole
File "/usr/lib/gimp/2.0/python/gimpui.py", line 35, in <module>
from _gimpui import *
RuntimeError: could not find _PyGtk_API object

***

pygtk is installed and at least pygtk-demo seems to be working properly.

Snowman,

See bleow
Comment by Skottish (skottish) - Wednesday, 27 October 2010, 02:01 GMT
Err.. Whoops.

Snowman,

I rebuilt the package with your configure line and it did nothing. Then I decided to install the package. Then it worked.

*** Solved and run away, run away.... ***

Yes, Eric's config does work and yes, it's probably a good thing that I'm not on the Arch team right now.
Comment by Eric Belanger (Snowman) - Wednesday, 27 October 2010, 10:35 GMT
The new config line is not necessary, in fact it breaks some stuff. A simple rebuild fix it.

While the python rebuild was in testing, we had to fix pygtk and rebuild a couple other packages against the fixed pygtk. It looks like gimp had to be rebuilt too.
Comment by Skottish (skottish) - Thursday, 28 October 2010, 00:48 GMT
Interesting. My rebuild before I started this report failed to fix the problem (yes, I actually installed that one before I did something retarded). Anyway, this is solved and I can go on happily running Pythonified batch scripts for GIMP.

Loading...