Bug#1044205: findimagedupes: Fails to build source after successful build

Lucas Nussbaum lucas at debian.org
Sun Aug 13 17:56:54 BST 2023


Source: findimagedupes
Version: 2.20.1-2
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 findimagedupes
> dpkg-buildpackage: info: source version 2.20.1-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Étienne Mollier <emollier at debian.org>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean
>    debian/rules override_dh_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> [ ! -f findimagedupes.pristine ] || mv findimagedupes.pristine findimagedupes
> rm -f C.pm Makefile.PL
> dh_clean
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building findimagedupes using existing ./findimagedupes_2.20.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: newly created empty file '_Inline/.lock' will not be represented in diff
> dpkg-source: warning: newly created empty file 'blib/arch/.exists' will not be represented in diff
> dpkg-source: warning: newly created empty file 'blib/arch/auto/findimagedupes/C/.exists' will not be represented in diff
> dpkg-source: error: cannot represent change to blib/arch/auto/findimagedupes/C/C.so: binary file contents changed
> dpkg-source: error: add blib/arch/auto/findimagedupes/C/C.so in debian/source/include-binaries if you want to store the modified binary in the debian tarball
> dpkg-source: warning: executable mode 0555 of 'blib/arch/auto/findimagedupes/C/C.so' will not be represented in diff
> dpkg-source: warning: newly created empty file 'blib/bin/.exists' will not be represented in diff
> dpkg-source: warning: newly created empty file 'blib/lib/auto/findimagedupes/C/.exists' will not be represented in diff
> dpkg-source: warning: newly created empty file 'blib/lib/findimagedupes/.exists' will not be represented in diff
> dpkg-source: warning: newly created empty file 'blib/man1/.exists' will not be represented in diff
> dpkg-source: warning: newly created empty file 'blib/man3/.exists' will not be represented in diff
> dpkg-source: warning: newly created empty file 'blib/script/.exists' will not be represented in diff
> dpkg-source: warning: executable mode 0755 of 'blib/script/findimagedupes' will not be represented in diff
> dpkg-source: warning: newly created empty file 'pm_to_blib' will not be represented in diff
> 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/findimagedupes_2.20.1-2_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.



More information about the debian-science-maintainers mailing list