Bug#831970: marked as done (py-libmpdclient: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)
Your message dated Fri, 22 Jul 2016 16:38:39 +0000
with message-id <E1bQdTD-0002JM-LO@franck.debian.org>
and subject line Bug#831970: fixed in py-libmpdclient 0.11.1-5
has caused the Debian Bug report #831970,
regarding py-libmpdclient: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute
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 owner@bugs.debian.org
immediately.)
--
831970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831970
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: py-libmpdclient
Version: 0.11.1-4
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
> dh_testdir
> dh_testroot
> dh_clean -k
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_installdirs
> python setup.py install --no-compile --prefix /<<PKGBUILDDIR>>/debian/python-mpdclient/usr
> running install
> running build
> running build_py
> creating build
> creating build/lib.linux-x86_64-2.7
> copying mpdclient2.py -> build/lib.linux-x86_64-2.7
> running install_lib
> creating /<<PKGBUILDDIR>>/debian/python-mpdclient/usr
> creating /<<PKGBUILDDIR>>/debian/python-mpdclient/usr/lib
> creating /<<PKGBUILDDIR>>/debian/python-mpdclient/usr/lib/python2.7
> creating /<<PKGBUILDDIR>>/debian/python-mpdclient/usr/lib/python2.7/site-packages
> copying build/lib.linux-x86_64-2.7/mpdclient2.py -> /<<PKGBUILDDIR>>/debian/python-mpdclient/usr/lib/python2.7/site-packages
> running install_egg_info
> Writing /<<PKGBUILDDIR>>/debian/python-mpdclient/usr/lib/python2.7/site-packages/py_libmpdclient-0.11.1-py2.7.egg-info
> dpkg-genchanges --build=all >../py-libmpdclient_0.11.1-4_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/py-libmpdclient_0.11.1-4_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.
--- End Message ---
--- Begin Message ---
Source: py-libmpdclient
Source-Version: 0.11.1-5
We believe that the bug you reported is fixed in the latest version of
py-libmpdclient, 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 831970@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Santiago Vila <sanvila@debian.org> (supplier of updated py-libmpdclient 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: Fri, 22 Jul 2016 16:07:48 +0200
Source: py-libmpdclient
Binary: python-mpdclient
Architecture: source
Version: 0.11.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Santiago Vila <sanvila@debian.org>
Description:
python-mpdclient - Python interface to MPD
Closes: 831970
Changes:
py-libmpdclient (0.11.1-5) unstable; urgency=medium
.
* QA upload.
* Switch to dh, "dpkg-buildpackage -A" should now work. Closes: #831970.
* Switch to "3.0 (quilt)" source format.
Checksums-Sha1:
6296d877de36a32c3304f5a6627db0a3004247d2 1393 py-libmpdclient_0.11.1-5.dsc
fb5012bf74616d6702c44376d940121c5c6f1a2f 1784 py-libmpdclient_0.11.1-5.debian.tar.xz
Checksums-Sha256:
6cdb076be3ca299640af71e9eb949109bc512b9011f66a02599b669ce3925d10 1393 py-libmpdclient_0.11.1-5.dsc
26d8a6d0fb1c54a3b1b985760e2a8fa033a4c176e81cd36e1bf0fb3705c4ab34 1784 py-libmpdclient_0.11.1-5.debian.tar.xz
Files:
43c2b8d1aaa53e283c2f497dd8a70706 1393 python extra py-libmpdclient_0.11.1-5.dsc
e42a063b0ac643e6d94a2686950f28cb 1784 python extra py-libmpdclient_0.11.1-5.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCAAGBQJXkikyAAoJEEHOfwufG4sykH8H/0jLApyVjkpPlxNv64NBmv/I
oGmJy2P914JDvLZ2qr1mlYqtfQslwMeCuNWHJ9ljqC+BuD6bjCgGOtgM4ggRWT4A
oUtX311vcroacAGyf5zvdsFvQbxff8Q2aIeGUUXqaklAJBqHnxOmGtV2Yv/En+V/
ZMl4flgZJrdVn95/O6ErpuZ8db9Itw6P5eNVnWy6KWEAiAJbLSth3LrpbzJf57zz
F1c1QYb4cVH7gK0qSQwmuFwrFEEE7cXJ8PXvDLm0mbMtAbu9LajECnDZPpzgWyRo
SHvFU/aRWGGNwg0MM5n9i4jBM9298jeZrvFX8qjk0mioUBDJsw4dm3g0SfoNjY8=
=b4N+
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: