[Debian-olpc-devel] Bug#707519: pyabiword: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found

[Lucas Nussbaum]

Source: pyabiword
Version: 0.8.0-11
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[2]: Entering directory `/«PKGBUILDDIR»/build/src'
> /usr/bin/pygtk-codegen-2.0 --prefix pyabiword			\
> 	--register /usr/share/pygtk/2.0/defs/gdk-types.defs	\
> 	--register /usr/share/pygtk/2.0/defs/gtk-types.defs	\
> 	--override /«PKGBUILDDIR»/./src/pyabiword.override /«PKGBUILDDIR»/./src/pyabiword.defs > pyabiword.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[2]: *** [pyabiword.c] Error 127

The full build log is available from:
   http://people.debian.org/~lucas/logs/2013/05/09/pyabiword_0.8.0-11_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.