On Tue, Jul 27, 2010 at 11:41:19AM +0200, Emilio Pozuelo Monfort wrote: > On 27/07/10 08:54, Sandro Tosi wrote: > > On Tue, Jul 27, 2010 at 08:48, Josselin Mouette <j...@debian.org> wrote: > >> Le mardi 27 juillet 2010 à 10:33 +0900, Shyouzou Sugitani a écrit : > >>> After upgrading from 2.17.0-2 to 2.17.0-3 I got an error > >>> "pygtk was not compiled with Numeric Python support". > >>> > >>> $ python > >>>>>> import gtk > >>>>>> pixbuf = gtk.gdk.Pixbuf(gtk.gdk.COLORSPACE_RGB, True, 8, 100, 100) > >>>>>> pixbuf.get_pixels_array() > >>> Traceback (most recent call last): > >>> File "<stdin>", line 1, in <module> > >>> RuntimeError: pygtk was not compiled with Numeric Python support > >> > >> I guess this is caused by the NumPy ABI disaster. > > > > Can you please try to rebuild it with the current numpy in unstable? > > that should be fixed. > > Indeed, the problem was the include files you fixed in -3: > > > checking for numpy/arrayobject.h... no > [...] > Numpy support: no > > Rebuilding with -3 installed fixes it. > > > > Dear wanna-build maintainers: > > Can you binNMU pygtk_2.17.0-3 on sparc s390 mipsel mips kfreebsd-i386 > kfreebsd-amd64 ia64 hurd-i386 hppa armel i386 > > Also dep-wait it for python-numpy 1:1.4.1-3, which is the fixed package we > need.
This already seems to have been done. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
