Your message dated Sun, 12 May 2013 14:49:03 +0200
with message-id <20130512124903.gl12...@radis.cristau.org>
and subject line Re: Bug#707494: dia-newcanvas: FTBFS: 
/usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found
has caused the Debian Bug report #707511,
regarding pida: FTBFS: /usr/bin/pygobject-codegen-2.0: 11: exec: 
/usr/bin/python2.6: not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
707511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pida
Version: 0.5.1-6
Severity: serious
Tags: jessie sid
User: debian...@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[1]: Entering directory `/«PKGBUILDDIR»/moo'
> echo '#include "moomarshals.h"' > moomarshals.c.tmp &&        \
>       glib-genmarshal --prefix=_moo_marshal --body    \
>              moomarshals.list >> moomarshals.c.tmp && mv moomarshals.c.tmp 
> moomarshals.c
> glib-genmarshal --prefix=_moo_marshal --header        \
>              moomarshals.list > moomarshals.h.tmp && mv moomarshals.h.tmp 
> moomarshals.h
> gdk-pixbuf-csource --static --build-list      \
>               MOO_HIDE_ICON hide.png                  \
>               MOO_CLOSE_ICON close.png                \
>               MOO_STICKY_ICON sticky.png              \
>               MOO_DETACH_ICON detach.png              \
>               MOO_ATTACH_ICON attach.png              \
>               MOO_KEEP_ON_TOP_ICON keepontop.png      \
>                       > stock-moo.h.tmp && mv stock-moo.h.tmp stock-moo.h
> pygtk-codegen-2.0 --prefix _moo_stub \
>               --register `pkg-config --variable=defsdir 
> pygtk-2.0`/gtk-types.defs \
>               --register `pkg-config --variable=defsdir 
> pygtk-2.0`/gdk-types.defs \
>               --override moo.override \
>               --outfilename moo-pygtk.c \
>               moo.defs > moo-pygtk.c.tmp && \
>               mv moo-pygtk.c.tmp moo-pygtk.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[1]: *** [moo-pygtk.c] Error 127

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

--- End Message ---
--- Begin Message ---
On Thu, May  9, 2013 at 10:53:05 +0200, Lucas Nussbaum wrote:

> > /usr/bin/pygobject-codegen-2.0: 11: exec: /usr/bin/python2.6: not found

Fixed in newer pygobject.  Closing these bugs.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to