Debian Bug report logs - #831912
mrename: 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: mrename: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute

Date: Wed, 20 Jul 2016 21:07:02 +0200

Source: mrename
Version: 1.2-12
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):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> install mcpmv  /<<PKGBUILDDIR>>/debian/mrename/usr/bin
> install mrename /<<PKGBUILDDIR>>/debian/mrename/usr/bin
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>  dpkg-genchanges --build=all >../mrename_1.2-12_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/mrename_1.2-12_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 831912@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Lucas Nussbaum <lucas@debian.org>

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

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

Date: Thu, 21 Jul 2016 21:27:20 +0200 (CEST)

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

tags 831912 + patch
thanks

Swapped binary-* targets.

Trivial patch attached.

[mrename.patch.txt (text/plain, attachment)]

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

From: Kevin Coyner <kcoyner@debian.org>

To: 831912-close@bugs.debian.org

Subject: Bug#831912: fixed in mrename 1.2-13

Date: Wed, 12 Oct 2016 04:55:23 +0000

Source: mrename
Source-Version: 1.2-13

We believe that the bug you reported is fixed in the latest version of
mrename, 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 831912@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kevin Coyner <kcoyner@debian.org> (supplier of updated mrename 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: Tue, 11 Oct 2016 23:18:57 -0400
Source: mrename
Binary: mrename
Architecture: source all
Version: 1.2-13
Distribution: unstable
Urgency: medium
Maintainer: Kevin Coyner <kcoyner@debian.org>
Changed-By: Kevin Coyner <kcoyner@debian.org>
Description:
 mrename    - tool for easy and automatic renaming of many files
Closes: 615254 670187 831912
Changes:
 mrename (1.2-13) unstable; urgency=medium
 .
   * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
     Thanks to Jari Aalto <jari.aalto@cante.net>. Closes: #670187.
   * Update to Standards-Version to 3.9.8 and debhelper to 9.
   * Add build-indep target; use dh_prep in rules file. Closes: #831912.
   * Patch 05 is new; in-line changes to original sources.
   * Fix description-contains-homepage by adding homepage field.
     Closes: #615254.
   * Fix description-synopsis-starts-with-article.
   * Fix copyright-with-old-dh-make-debian-copyright.
   * Fix copyright-refers-to-versionless-license-file.
Checksums-Sha1:
 579c369b3e8d3f2ec8f879b69fcbc36a742f4452 1332 mrename_1.2-13.dsc
 1f0c9ed405e04047093a430eb3732e1269e02f0d 4812 mrename_1.2-13.debian.tar.xz
 d4afed3e445155eba2bd76e25798c299e33af33e 6410 mrename_1.2-13_all.deb
Checksums-Sha256:
 e7d0b69f95bc9046a7acbf2f69bda9dc338556a2a0b64d95cbc3717fff6ab690 1332 mrename_1.2-13.dsc
 61850013b51fb4822583b22c88e7ea3ab3b398d9cb9d0140b1009480ace99b84 4812 mrename_1.2-13.debian.tar.xz
 2e32cd94c9c2d53b184cf2204185a9c0a01df00e600b62961d0c4a1e55bcc8d8 6410 mrename_1.2-13_all.deb
Files:
 d229016cab2ddf92494bc76e4c56a9e2 1332 utils optional mrename_1.2-13.dsc
 c55061cbacd1b690e96efbed9cd394af 4812 utils optional mrename_1.2-13.debian.tar.xz
 9720c032fbf7ad00ffecaa6a18084f94 6410 utils optional mrename_1.2-13_all.deb

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

iQEcBAEBCAAGBQJX/bDsAAoJEOuzGmLIXY9xkIYH+wQkw7qMU2+E7ZK88lI9t7AQ
U0wcDHDSbWMdX0MBZ6JFhYg98dcsgAUxTKr/8Xg7+zwlyn6URLSPvmdlJh+SbISG
fqpaCiKnDXw2snIO1nvQajwZhGhOjeK5vdVCLrsVb6vpDp5jbDGzomO4XR5UBJnm
UD/EdPJJeHNdstJx7sybrk/a5jfpMHgCqft9hMzD43h+qeK2bPYDj1mLk+tXlq/7
+vtzXeLY0xAwjx++rtrSQVO03wZsvV3FVDNmOun/N///04281c+QM02dE0oJi9XF
8IaOJ+UVNNbk70/3Jpw6D/UnZAK5AfedaKlc8cjB6V7BVXbaT2RxQkUm1dOfcoo=
=tBI8
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.