Bug#707493: gnome-python-desktop: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found

Lucas Nussbaum lucas at lucas-nussbaum.net
Thu May 9 08:53:43 UTC 2013


Source: gnome-python-desktop
Version: 2.32.0+dfsg-2
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130509 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[3]: Entering directory `/«BUILDDIR»/gnome-python-desktop-2.32.0+dfsg/debian/build/wnck'
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I/«BUILDDIR»/gnome-python-desktop-2.32.0+dfsg/./wnck -I.. -I/usr/include/python2.7 -I/usr/include/python2.7 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/pygtk-2.0    -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/libwnck-1.0 -I/usr/include/startup-notification-1.0   -DWNCK_I_KNOW_THIS_IS_UNSTABLE -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -std=c9x -fno-strict-aliasing -c -o wnck_la-wnckmodule.lo `test -f 'wnckmodule.c' || echo '/«BUILDDIR»/gnome-python-desktop-2.32.0+dfsg/./wnck/'`wnckmodule.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/«BUILDDIR»/gnome-python-desktop-2.32.0+dfsg/./wnck -I.. -I/usr/include/python2.7 -I/usr/include/python2.7 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/pygtk-2.0 -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/libwnck-1.0 -I/usr/include/startup-notification-1.0 -DWNCK_I_KNOW_THIS_IS_UNSTABLE -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -std=c9x -fno-strict-aliasing -c /«BUILDDIR»/gnome-python-desktop-2.32.0+dfsg/./wnck/wnckmodule.c  -fPIC -DPIC -o .libs/wnck_la-wnckmodule.o
> (cd /«BUILDDIR»/gnome-python-desktop-2.32.0+dfsg/./wnck \
> 	 && /usr/bin/pygtk-codegen-2.0 \
> 	    --py_ssize_t-clean \
>             --register /usr/share/pygtk/2.0/defs/gtk-types.defs \
>             --register /usr/share/pygtk/2.0/defs/gdk-types.defs \
> 	    --override wnck.override \
> 	    --prefix pywnck wnck.defs) > gen-wnck.c \
> 	&& cp gen-wnck.c wnck.c \
> 	&& rm -f gen-wnck.c
> note: pygtk-codegen-2.0 is deprecated, use pygobject-codegen-2.0 instead
> note: I will now try to invoke pygobject-codegen-2.0 in the same directory
> /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found
> make[3]: *** [wnck.c] Error 127

The full build log is available from:
   http://people.debian.org/~lucas/logs/2013/05/09/gnome-python-desktop_2.32.0+dfsg-2_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.




More information about the pkg-gnome-maintainers mailing list