Discussion:
Bug#982717: udfclient: FTBFS: bmake[1]: no target to make.
Add Reply
Pali Rohár
2021-02-13 17:50:01 UTC
Reply
Permalink
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
debian/rules build
dh build --buildsystem=bmake
dh_update_autotools_config -O--buildsystem=bmake
install -d debian/.debhelper/bucket/files
cp -an --reflink=auto config.guess debian/.debhelper/bucket/files/420138cb266d63505ec54f169a34e1cc9aba80dc20a1eeac76b7bf5c9e5ff74e.tmp
mv debian/.debhelper/bucket/files/420138cb266d63505ec54f169a34e1cc9aba80dc20a1eeac76b7bf5c9e5ff74e.tmp debian/.debhelper/bucket/files/420138cb266d63505ec54f169a34e1cc9aba80dc20a1eeac76b7bf5c9e5ff74e
cp -f /usr/share/misc/config.guess ./config.guess
cp -an --reflink=auto config.sub debian/.debhelper/bucket/files/6585881331b69439aec3e94b9167983f9c3609b1b5dca9fa77d6941a3f79ccc2.tmp
mv debian/.debhelper/bucket/files/6585881331b69439aec3e94b9167983f9c3609b1b5dca9fa77d6941a3f79ccc2.tmp debian/.debhelper/bucket/files/6585881331b69439aec3e94b9167983f9c3609b1b5dca9fa77d6941a3f79ccc2
cp -f /usr/share/misc/config.sub ./config.sub
dh_autoreconf -O--buildsystem=bmake
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec md5sum {} + -o -type l -printf "symlink %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac
autoreconf -f -i
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec md5sum {} + -o -type l -printf "symlink %p
" > debian/autoreconf.after
dh_auto_configure -O--buildsystem=bmake
dh_auto_build -O--buildsystem=bmake
bmake
bmake[1]: no target to make.
bmake[1]: stopped in /<<PKGBUILDDIR>>
dh_auto_build: error: bmake returned exit code 2
Hello Lucas!

This looks like a bug in dh_auto_configure. dh_autoreconf correctly
started autoreconf but dh_auto_configure did not start ./configure.
So ./configure did not generated Makefile and bmake complained.
make: *** [debian/rules:8: build] Error 25
http://qa-logs.debian.net/2021/02/13/udfclient_0.8.11-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking 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 me
so that we can identify if something relevant changed in the meantime.
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--
Pali Rohár
***@gmail.com
Debian Bug Tracking System
2021-02-15 17:20:01 UTC
Reply
Permalink
tag -1 patch confirmed
Bug #982717 [src:udfclient] udfclient: FTBFS: bmake[1]: no target to make.
Added tag(s) patch and confirmed.
--
982717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982717
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Pali Rohár
2021-02-17 12:00:01 UTC
Reply
Permalink
The current bmake backend for debhelper no longer inherits from the
autoconf backend. The attached patch devises an override that
restores the old behaviour, and I've verified that it works.
Hello Dennis! Thank you for investigation and the patch. Will you update
also the package? Or should I do it? Note that I do not have Debian
Developer permissions so I can update new version of package only to
mentors server (which takes a long to appear in Debian archive...).
--
Pali Rohár
***@gmail.com
Debian Bug Tracking System
2021-02-22 11:10:01 UTC
Reply
Permalink
Your message dated Mon, 22 Feb 2021 11:03:45 +0000
with message-id <E1lE90D-000564-***@fasolo.debian.org>
and subject line Bug#982717: fixed in udfclient 0.8.11-2
has caused the Debian Bug report #982717,
regarding udfclient: FTBFS: bmake[1]: no target to make.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)
--
982717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982717
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Loading...