[Debian-med-packaging] Bug#1049635: libgzstream: Fails to build binary packages again after successful build

Lucas Nussbaum lucas at debian.org
Wed Aug 16 08:42:49 BST 2023


Source: libgzstream
Version: 1.5+git20171107.9a20658-1
Severity: minor
Tags: trixie sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build
User: debian-qa at lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to do build a binary-only build (not source) after a
successful build (dpkg-buildpackage ; dpkg-buildpackage -b).

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/DoubleBuild

Relevant part of the build log:
> cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -b
> -----------------------------------------------------------------------------------------------------------------------------------------------
> 
> dpkg-buildpackage: info: source package libgzstream
> dpkg-buildpackage: info: source version 1.5+git20171107.9a20658-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Andreas Tille <tille at debian.org>
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --no-parallel
>    debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_clean || true # In clean stage the Makefile is not patched yet and thus might stumble upon removal of not existing files
> 	make -j1 clean
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> rm -f *.o
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_autoreconf_clean -O--no-parallel
>    debian/rules override_dh_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_clean
> rm -rf debian/tmplibs
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>  debian/rules binary
> dh binary --no-parallel
>    dh_update_autotools_config -O--no-parallel
>    dh_autoreconf -O--no-parallel
>    dh_auto_configure -O--no-parallel
>    dh_auto_build -O--no-parallel
> 	make -j1 "INSTALL=install --strip-program=true"
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> make[1]: *** No rule to make target 'gzstream.h', needed by 'gzstream.o'.  Stop.
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_build: error: make -j1 "INSTALL=install --strip-program=true" returned exit code 2
> make: *** [debian/rules:14: binary] Error 25
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
> 
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -b' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/16/libgzstream_1.5+git20171107.9a20658-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.



More information about the Debian-med-packaging mailing list