Source: python-pqueue
Version: 0.2-7.1
Severity: serious
Tags: jessie sid
User: [email protected]
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> debian/rules build
> dh_testdir
> (set -e; for v in python2.7; do mkdir build-$v; cd build-$v; ../configure
> --prefix=/usr --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info
> --with-python=/usr/bin/$v; /usr/bin/make; cd ..; done)
> creating cache ./config.cache
> checking for python... /usr/bin/python2.7
> checking python version... 2.7
> checking python installation prefix... /usr
> checking python installation exec_prefix... /usr
> sed: can't read /usr/lib/python2.7/config/Makefile: No such file or directory
> checking definitions in Python library makefile... done
> checking for install... /usr/bin/install
> checking location of python library... $(prefix)/lib/python2.7
> checking location of python shared modules...
> $(exec_prefix)/lib/python2.7/lib-dynload
> checking for inline... no
> checking how to run the C preprocessor... /lib/cpp
> checking for ANSI C header files... no
> updating cache ./config.cache
> creating ./config.status
> creating Setup
> creating Makefile.pre
> creating pqueuemodule-config.h
> creating Makefile
> ./config.status: 240: ./config.status: /usr/lib/python2.7/config/makesetup:
> not found
> make[1]: Entering directory `/«PKGBUILDDIR»/build-python2.7'
> make[1]: *** No targets specified and no makefile found. Stop.
> make[1]: Leaving directory `/«PKGBUILDDIR»/build-python2.7'
> make: *** [build-stamp] Error 2
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/python-pqueue_0.2-7.1_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.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
