Source: gpsim-doc Version: 0.22.0-2 Severity: important Tags: stretch sid User: debian...@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_prep > rm -f debian/gpsim-doc.substvars > rm -f debian/gpsim-doc.*.debhelper > rm -rf debian/gpsim-doc/ > dh_installdirs > install -d debian/gpsim-doc > install -d debian/gpsim-doc/usr/share/doc/gpsim-doc > dpkg-genchanges --build=all >../gpsim-doc_0.22.0-2_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/gpsim-doc_0.22.0-2_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.
