Source: dhcp-probe
Version: 1.3.0-10.1
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build
User: debian...@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 dhcp-probe
> dpkg-buildpackage: info: source version 1.3.0-10.1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Steve McIntyre <93...@debian.org>
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> dh_clean stamp-h*
> dh_clean: warning: Compatibility levels before 10 are deprecated (level 7 in 
> use)
> dh_auto_clean
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 7 in use)
>       make -j1 distclean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> Making distclean in lib
> make[2]: Entering directory '/<<PKGBUILDDIR>>/lib'
> test -z "libreplace.a" || rm -f libreplace.a
> rm -f *.o
> rm -f *.tab.c
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> rm -f .deps/inet_aton.Po
> rm -f .deps/my_null_proc.Po
> rm -f .deps/strerror.Po
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/lib'
> Making distclean in src
> make[2]: Entering directory '/<<PKGBUILDDIR>>/src'
> test -z "dhcp_probe" || rm -f dhcp_probe
> rm -f *.o
> rm -f *.tab.c
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> rm -f ./.deps/bootp.Po
> rm -f ./.deps/configfile.Po
> rm -f ./.deps/daemonize.Po
> rm -f ./.deps/dhcp_probe.Po
> rm -f ./.deps/get_myeaddr.Po
> rm -f ./.deps/get_myipaddr.Po
> rm -f ./.deps/open_max.Po
> rm -f ./.deps/report.Po
> rm -f ./.deps/utils.Po
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/src'
> Making distclean in doc
> make[2]: Entering directory '/<<PKGBUILDDIR>>/doc'
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f Makefile
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/doc'
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> test -z "" || rm -f 
> test . = "." || test -z "" || rm -f 
> rm -f config.h stamp-h1
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> rm -f cscope.out cscope.in.out cscope.po.out cscope.files
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> rm -f config.status config.cache config.log configure.lineno 
> config.status.lineno
> rm -f Makefile
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_autoreconf_clean
> dh_clean
> dh_clean: warning: Compatibility levels before 10 are deprecated (level 7 in 
> use)
>  debian/rules build
> make: *** No rule to make target 'configure', needed by 'config.status'.  
> Stop.
> dpkg-buildpackage: error: debian/rules build 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/dhcp-probe_1.3.0-10.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.

Reply via email to