Your message dated Fri, 05 Aug 2016 23:57:13 +0000 with message-id <e1bvozj-0000ti...@franck.debian.org> and subject line Bug#831957: fixed in adzapper 20090301.dfsg.2-1 has caused the Debian Bug report #831957, regarding adzapper: 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 ow...@bugs.debian.org immediately.) -- 831957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: adzapper Version: 20090301.dfsg.1-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_clean -k > dh_clean: dh_clean -k is deprecated; use dh_prep instead > dh_installdirs > # Add here commands to install the package into debian/adzapper. > install -m 755 scripts/squid_redirect debian/adzapper/usr/bin/adzapper > install -m 755 debian/adzapper.wrapper debian/adzapper/usr/bin > install -m 755 debian/adzapper2konq debian/adzapper/usr/bin > install -m 755 debian/adzapper2ab debian/adzapper/usr/bin > install -m 644 debian/adzapper.conf debian/adzapper/etc/ > dpkg-genchanges --build=all >../adzapper_20090301.dfsg.1-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/adzapper_20090301.dfsg.1-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.
--- End Message ---
--- Begin Message ---Source: adzapper Source-Version: 20090301.dfsg.2-1 We believe that the bug you reported is fixed in the latest version of adzapper, 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 831...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Santiago Vila <sanv...@debian.org> (supplier of updated adzapper 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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sat, 06 Aug 2016 00:27:06 +0200 Source: adzapper Binary: adzapper Architecture: source Version: 20090301.dfsg.2-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group <packa...@qa.debian.org> Changed-By: Santiago Vila <sanv...@debian.org> Description: adzapper - proxy advertisement zapper add-on Closes: 831957 Changes: adzapper (20090301.dfsg.2-1) unstable; urgency=medium . * QA upload. * Package is orphaned (Bug #722717). Set maintainer to "Debian QA Group". * Repackage source tarball again. Old tarball had modified files and a populated debian directory. * Package is "Arch: all". Move things from binary-arch to binary-indep. Package should now build with "dpkg-buildpackage -A". Closes: #831957. * Raise debhelper compat level to 9. * Simplify debian/rules. * Standards-Version: 3.9.8. Checksums-Sha1: 886d5204ec5c5d178a9336f656ce0f9d6e8c51b9 1416 adzapper_20090301.dfsg.2-1.dsc e12b4872152d302aa30b9cb4d3bf417b39547d1c 109556 adzapper_20090301.dfsg.2.orig.tar.xz 2535c5824ecd51cab1c974cf8564fffb5b0e0800 11380 adzapper_20090301.dfsg.2-1.debian.tar.xz Checksums-Sha256: 12cc0fc17c8887f0c89f361b7fa7b155822889b2960ca531231336f9510bc6ee 1416 adzapper_20090301.dfsg.2-1.dsc 51a5770bb2358275ad3705fc11eeaf2171b97579d69f48ba8ebdb93d89c994dd 109556 adzapper_20090301.dfsg.2.orig.tar.xz 0c6a06daa890cacbcd69b3e156aadb6ec36b27b21081fbbde684a374acb2ef6c 11380 adzapper_20090301.dfsg.2-1.debian.tar.xz Files: 27a82cc278aa60fa9476ba8e8a00bb75 1416 web optional adzapper_20090301.dfsg.2-1.dsc 4c20b9ee0c710ca91e8333ad8467f5b0 109556 web optional adzapper_20090301.dfsg.2.orig.tar.xz 50a622bdf55461b4398adcf6e6136b9a 11380 web optional adzapper_20090301.dfsg.2-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXpRXmAAoJEEHOfwufG4syewYH/juvgaXqAK4yYqfk3VtwfGsW GA4zgC7ck1HEG4LDXddexnZN8jz0hLgydojlt97EUPzzrATrZFuaSnJz+k1x7Gcp Oe7B5PHwyaUvF3yPddUz4Iv/q6TqFCpPG9iQ0sJRi5Dev+vgnbqcYjp7uMzv62Fr KAUE3qJB3HtNciYWHU66Mb0HG+YkNaHzFkDfkHlG5uPAarKBONuQ/rMFvuZzUpTz 3cA+1WWm2stYJWtun9hDh0eYPJtiWeEIfejxTh+HpJcFtuvRiBu8jSNBw7RYpy7g Bq4pzOvJJ+5ivVekX71DQLutTZVAMeGi/98a8DHIvrVuXLs8UnJNe+YV6o2fj7g= =FDDg -----END PGP SIGNATURE-----
--- End Message ---
