[Python-apps-team] Bug#917729: weresync: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

Lucas Nussbaum lucas at debian.org
Sat Dec 29 22:28:51 GMT 2018


Source: weresync
Version: 1.0.7-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild 
>    dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.7 setup.py clean 
> running clean
> removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.7/build' (and everything under it)
> 'build/bdist.linux-amd64' does not exist -- can't clean it
> 'build/scripts-3.7' does not exist -- can't clean it
>    dh_autoreconf_clean -O--buildsystem=pybuild
>    dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building weresync using existing ./weresync_1.0.7.orig.tar.gz
> dpkg-source: error: cannot represent change to src/weresync/resources/locale/en/LC_MESSAGES/weresync.mo: binary file contents changed
> dpkg-source: error: add src/weresync/resources/locale/en/LC_MESSAGES/weresync.mo 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 . subprocess returned exit status 2
> --------------------------------------------------------------------------------
> Build finished at 2018-12-29T12:40:29Z

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/weresync_1.0.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.



More information about the Python-apps-team mailing list