Source: damapper Version: 0.0+git20210330.ab45103-1 Severity: minor Tags: trixie sid ftbfs User: [email protected] Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: [email protected] 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 damapper > dpkg-buildpackage: info: source version 0.0+git20210330.ab45103-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Shayan Doust <[email protected]> > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean > dh_auto_clean > make -j8 clean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > rm -f damapper HPC.damapper > rm -fr *.dSYM > rm -f damapper.tar.gz > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_clean > debian/rules binary > dh binary > dh_update_autotools_config > dh_autoreconf > dh_auto_configure > dh_auto_build > make -j8 "INSTALL=install --strip-program=true" > make[1]: Entering directory '/<<PKGBUILDDIR>>' > cc -O3 -Wall -Wextra -Wno-unused-result -fno-strict-aliasing > -D_FORTIFY_SOURCE=2 -z now -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -o damapper > damapper.c map.c align.c DB.c QV.c -lpthread -lm > cc -O3 -Wall -Wextra -Wno-unused-result -fno-strict-aliasing > -D_FORTIFY_SOURCE=2 -z now -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -o HPC.damapper > HPC.damapper.c DB.c QV.c -lm > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_auto_test > create-stamp debian/debhelper-build-stamp > dh_prep > dh_auto_install --destdir=debian/damapper/ > make -j8 install > DESTDIR=/<<BUILDDIR>>/damapper-0.0\+git20210330.ab45103/debian/damapper > AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" > make[1]: Entering directory '/<<PKGBUILDDIR>>' > mkdir bin/ > mkdir: cannot create directory âbin/â: File exists > make[1]: *** [Makefile:19: install] Error 1 > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_auto_install: error: make -j8 install > DESTDIR=/<<BUILDDIR>>/damapper-0.0\+git20210330.ab45103/debian/damapper > AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" returned exit > code 2 > make: *** [debian/rules:12: 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/damapper_0.0+git20210330.ab45103-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.
