Bug#1048662: hex-a-hop: Fails to build source after successful build

[Lucas Nussbaum]

Source: hex-a-hop
Version: 1.1.0+git20140926-1.1
Severity: minor
Tags: trixie sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian-qa at lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -S
> -------------------------------------------------------------------------------------------------------------------------------------
> 
> dpkg-buildpackage: info: source package hex-a-hop
> dpkg-buildpackage: info: source version 1.1.0+git20140926-1.1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Holger Levsen <holger at debian.org>
>  dpkg-source --before-build .
>  fakeroot debian/rules clean
> dh clean
>    dh_auto_clean
> 	make -j8 distclean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> Making distclean in src
> make[2]: Entering directory '/<<PKGBUILDDIR>>/src'
> test -z "hex-a-hop" || rm -f hex-a-hop
> rm -f *.o
> rm -f *.tab.c
> test -z "" || rm -f 
> rm -f config.h stamp-h1
> test . = "." || test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> rm -f ./.deps/hex_a_hop-gfx.Po
> rm -f ./.deps/hex_a_hop-hex_puzzzle.Po
> rm -f ./.deps/hex_a_hop-i18n.Po
> rm -f ./.deps/hex_a_hop-sfx.Po
> rm -f ./.deps/hex_a_hop-system-directory.Po
> rm -f ./.deps/hex_a_hop-system-relative.Po
> rm -f ./.deps/hex_a_hop-text.Po
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/src'
> Making distclean in data
> make[2]: Entering directory '/<<PKGBUILDDIR>>/data'
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/data'
> Making distclean in po
> make[2]: Entering directory '/<<PKGBUILDDIR>>/po'
> rm -f *.insert-header
> rm -f remove-potcdate.sed
> rm -f stamp-poT
> rm -f core core.* hex-a-hop.po hex-a-hop.1po hex-a-hop.2po *.new.po
> rm -fr *.o
> rm -f Makefile Makefile.in POTFILES *.mo
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/po'
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> test . = "." || test -z "" || rm -f 
> rm -f cscope.out cscope.in.out cscope.po.out cscope.files
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> rm -f config.status config.cache config.log configure.lineno config.status.lineno
> rm -f Makefile
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_autoreconf_clean
>    dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building hex-a-hop using existing ./hex-a-hop_1.1.0+git20140926.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: error: cannot represent change to po/bg.gmo: binary file contents changed
> dpkg-source: error: add po/bg.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/de.gmo: binary file contents changed
> dpkg-source: error: add po/de.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/es.gmo: binary file contents changed
> dpkg-source: error: add po/es.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/it.gmo: binary file contents changed
> dpkg-source: error: add po/it.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/ja.gmo: binary file contents changed
> dpkg-source: error: add po/ja.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/nl.gmo: binary file contents changed
> dpkg-source: error: add po/nl.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/pl.gmo: binary file contents changed
> dpkg-source: error: add po/pl.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/ru.gmo: binary file contents changed
> dpkg-source: error: add po/ru.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/ta.gmo: binary file contents changed
> dpkg-source: error: add po/ta.gmo in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: error: cannot represent change to po/vi.gmo: binary file contents changed
> dpkg-source: error: add po/vi.gmo 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 1
> 
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -S' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/13/hex-a-hop_1.1.0+git20140926-1.1_unstable.log

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.