Bug#1048997: libgpod: Fails to build source after successful build
Source: libgpod
Version: 0.8.3-18
Severity: minor
Tags: trixie sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian-qa@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 libgpod
> dpkg-buildpackage: info: source version 0.8.3-18
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Bastian Germann <bage@debian.org>
> dpkg-source --before-build .
> debian/rules clean
> dh clean
> debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> rm -f gtk-doc.make m4/gtk-doc.m4 po/libgpod.pot
> rm -rf build/
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_autoreconf_clean
> dh_clean
> rm -rf debian/tmp-*
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building libgpod using existing ./libgpod_0.8.3.orig.tar.bz2
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: ignoring deletion of file install-sh, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file aclocal.m4, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file INSTALL, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file py-compile, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file compile, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file ltmain.sh, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file configure, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file config.h.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file depcomp, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file gtk-doc.make, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file missing, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/ltsugar.m4, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/intltool.m4, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/lt~obsolete.m4, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/ltversion.m4, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/libtool.m4, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/gtk-doc.m4, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file m4/ltoptions.m4, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file tests/Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file docs/Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file docs/reference/Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file src/Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file po/Makefile.in.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file tools/Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file bindings/Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file bindings/python/Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file bindings/python/examples/Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file bindings/python/tests/Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file bindings/mono/Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file bindings/mono/libgpod-sharp-test/Makefile.in, use --include-removal to override
> dpkg-source: warning: ignoring deletion of file bindings/mono/libgpod-sharp/Makefile.in, use --include-removal to override
> dpkg-source: info: local changes detected, the modified files are:
> libgpod-0.8.3/gtk-doc.m4
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/libgpod_0.8.3-18.diff.7zX01W
> dpkg-source: info: Hint: make sure the version in debian/changelog matches the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
>
> 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/libgpod_0.8.3-18_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.
Reply to: