Bug#1049755: ap-utils: Fails to build binary packages again after successful build
Source: ap-utils
Version: 1.5-5
Severity: minor
Tags: trixie sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build
User: debian-qa@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:
> Making install in po
> make[2]: Entering directory '/<<PKGBUILDDIR>>/po'
> /bin/sh `case "config/mkinstalldirs" in /*) echo "config/mkinstalldirs" ;; *) echo "../config/mkinstalldirs" ;; esac` /<<PKGBUILDDIR>>/debian/ap-utils/usr/share
> /bin/sh: 0: cannot open ../config/mkinstalldirs: No such file
> make[2]: *** [Makefile:187: install-data-yes] Error 2
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/po'
> make[1]: *** [Makefile:413: install-recursive] Error 1
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_install: error: make -j8 install DESTDIR=/<<PKGBUILDDIR>>/debian/ap-utils AM_UPDATE_INFO_DIR=no returned exit code 2
> make: *** [debian/rules:18: binary] Error 25
> dpkg-buildpackage: error: fakeroot 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/ap-utils_1.5-5_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: