[Python-modules-team] Bug#733425: blist: FTBFS: dpkg-buildpackage: dpkg-source: error: unrepresentable changes to source

David Suárez david.sephirot at gmail.com
Sat Dec 28 20:51:04 UTC 2013


Source: blist
Version: 1.3.4-2
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20131226 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»'
> echo gcc
> gcc
> rm -f blist.egg-info/PKG-INFO blist.egg-info/SOURCES.txt
> dh_clean
> make[1]: Leaving directory `/«PKGBUILDDIR»'
>  dpkg-source -b blist-1.3.4
> dpkg-source: info: using source format `3.0 (quilt)'
> dpkg-source: info: building blist using existing ./blist_1.3.4.orig.tar.gz
> dpkg-source: warning: ignoring deletion of file blist.egg-info/SOURCES.txt
> dpkg-source: warning: ignoring deletion of file blist.egg-info/PKG-INFO
> dpkg-source: error: cannot represent change to distribute-0.6.12-py2.7.egg: binary file contents changed
> dpkg-source: error: add distribute-0.6.12-py2.7.egg in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to distribute-0.6.12.tar.gz: binary file contents changed
> dpkg-source: error: add distribute-0.6.12.tar.gz in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: unrepresentable changes to source
> dpkg-buildpackage: error: dpkg-source -b blist-1.3.4 gave error exit status 2
> ────────────────────────────────────────────────────────────────────────────────
> Build finished at 20131227-0322

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/12/26/blist_1.3.4-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 Python-modules-team mailing list