Debian Bug report logs - #831927
log4cpp-doc: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@debian.org>

To: submit@bugs.debian.org

Subject: log4cpp-doc: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute

Date: Wed, 20 Jul 2016 21:06:51 +0200

Source: log4cpp-doc
Version: 1.0-1
Severity: important
Tags: stretch sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.


The specific error below usually happens there is a binary-indep target in
debian/rules which is either empty or does not do anything useful.

If all the arch-independent packages are dummy transitional packages released
with jessie, the easy fix is to drop them now. If not, debian/rules should be
modified so that the binary-indep target generates the architecture independent
packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
>  fakeroot debian/rules binary-indep
> make: Nothing to be done for 'binary-indep'.
>  dpkg-genchanges --build=all >../log4cpp-doc_1.0-1_all.changes
> dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/07/20/log4cpp-doc_1.0-1_unstable_archallonly.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!

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.

Message #10 received at 831927@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Lucas Nussbaum <lucas@debian.org>

Cc: 831927@bugs.debian.org, Debian BTS <control@bugs.debian.org>

Subject: Re: log4cpp-doc: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute

Date: Thu, 21 Jul 2016 21:37:29 +0200 (CEST)

[Message part 1 (text/plain, inline)]

tags 831927 + patch
thanks

Swapped binary-* targets.

Trivial patch attached.

[log4cpp-doc.patch.txt (text/plain, attachment)]

Message #19 received at 831927-close@bugs.debian.org (full text, mbox, reply):

From: Fathi Boudra <fabo@debian.org>

To: 831927-close@bugs.debian.org

Subject: Bug#831927: fixed in log4cpp-doc 1.0-2

Date: Thu, 22 Dec 2016 09:33:34 +0000

Source: log4cpp-doc
Source-Version: 1.0-2

We believe that the bug you reported is fixed in the latest version of
log4cpp-doc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 831927@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Fathi Boudra <fabo@debian.org> (supplier of updated log4cpp-doc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 22 Dec 2016 10:31:52 +0200
Source: log4cpp-doc
Binary: liblog4cpp-doc
Architecture: source all
Version: 1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Fathi Boudra <fabo@debian.org>
Changed-By: Fathi Boudra <fabo@debian.org>
Description:
 liblog4cpp-doc - C++ library for flexible logging (documentation)
Closes: 615324 831927
Changes:
 log4cpp-doc (1.0-2) unstable; urgency=medium
 .
   * Switch to dh (Closes: #831927)
   * Add Homepage field to point to upstream homepage (Closes: #615324)
Checksums-Sha1:
 e07bcc9699c04cfecd65e353367df9b1e9cf6c38 1721 log4cpp-doc_1.0-2.dsc
 ed0d5a88b8bf2e5beeb8708abd9ae866a23ea5ea 2172 log4cpp-doc_1.0-2.debian.tar.xz
 f09ced1fe41b43b26abea18b2e52cddf85675294 2427940 liblog4cpp-doc_1.0-2_all.deb
 9c301cab24fccc238f9ac47679f6ea1da8a8d473 5290 log4cpp-doc_1.0-2_amd64.buildinfo
Checksums-Sha256:
 9fc5f4fde5873a04a0891bfcf390f0ddaec5392693c58afe4577ae1ffb940628 1721 log4cpp-doc_1.0-2.dsc
 66c04ea3e85f2b20315efda8ec0a02fec749d4c383c458eae4a2b4cb94f7c06d 2172 log4cpp-doc_1.0-2.debian.tar.xz
 350b959d71d64f4cb5ffbcb739bb07ac308f25b509eb699d59e7ceda2930d994 2427940 liblog4cpp-doc_1.0-2_all.deb
 a81d03a5beabe100141015a0815159aebe5806333ecb4fb55812888233beb30b 5290 log4cpp-doc_1.0-2_amd64.buildinfo
Files:
 8877df4dc765c289a9740741d38193ce 1721 doc optional log4cpp-doc_1.0-2.dsc
 97738beb889b5e8003d0ae7741578346 2172 doc optional log4cpp-doc_1.0-2.debian.tar.xz
 511f783478c9a4aeaee73fd52db7c847 2427940 doc optional liblog4cpp-doc_1.0-2_all.deb
 41dbbb4db9eafa4eec08aa0de598f633 5290 doc optional log4cpp-doc_1.0-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEErgXg8j6f/HimcCpY/zQ5qUgYqYwFAlhbmNoACgkQ/zQ5qUgY
qYxZ1RAAp6w01KlHDloDqId1rG3N2fb0HRHfVXl64Qyx6ZGP3nplkDRjYWV31Y6d
leMpyDg/K3mMTXmlS3badO6pBG+71MMmhRmb19vAuZFdKG+dI/GNZRu7L2baM1xr
yPqTXwpeme9YdbntZZBSwcxlrBHP/KhfA7zEYI1K7WBUEB/lYFypKR/NQupx/e3x
00B2wfaBbb6QTEK7SIRubJ3Z+wkDxd/EedDbcWMwNgTtwgwVae7YziwVYCoSuId9
ib6Ol1JMwCERTetyXihVcdeFKliFr6nevXrpNrX9cO/jYTZcUj7p6gnBYMjxZaQj
ExnCX8M3cN+Azdxa9o6PPtnPourdoCxRHe06QqEvnc5ofQO36IJvuIchaU1BgFG7
i8p6MMGGJb6C7siR2nYykyajL2kGxGyetOnJK7BMujELMShhWQTQpEtoW4TqngCz
sMFXZZD//OPHWR0+0Ljms+Y7LcVZrXd9HD9paE/6yYi1uawLxeObPoYcjsXI74Kd
5zG/8XXRotbEDyOQMAM42k6rvcRXldEA7jbrdJCLgxglX9z/wlK3yly+3tyTshdx
C3gDQKCwzY7wIETiHPqi3+s1wLcFS64hgmYQGfRIoFZBjCxL5yBsoDsfbqYM2zPQ
8XrscvD8YqJO/WzCzo8n/8UHiyD51DOyVOJzisSwiAXmGTZ8V/8=
=EKP6
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.