[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#831970: py-libmpdclient: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute



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.


Reply to: