Your message dated Sun, 25 Dec 2016 22:23:07 +0000 with message-id <e1clhc7-0002z5...@fasolo.debian.org> and subject line Bug#831930: fixed in spkproxy 1.4.8-4.4 has caused the Debian Bug report #831930, regarding spkproxy: 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.) -- 831930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: spkproxy Version: 1.4.8-4.3 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): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > for file in allwords bottomright.html CA.cert CA.pkey FileTemplate.xml > help.html index.html left.html notes.html passchecklist requestcache.html > scan_database.db server.cert server.pkey shortwords testpickle.pickle > titleframe.html topright.html words ; do \ > install -m644 $file > /<<PKGBUILDDIR>>/debian/spikeproxy//usr/share/spikeproxy/ ; \ > done > for file in daveutil.py requestandresponse.py spikeProxyUI.py spkproxy.py > testform.py testfunc.py testpickle.py versioncheck.py VulnXML.py > whiskerdbtovulnxml.py read_query.py timeoutsocket.py ; do \ > install -m755 $file > /<<PKGBUILDDIR>>/debian/spikeproxy//usr/share/spikeproxy/ ; \ > done > for dir in testVulnXml VulnXML ntlm ; do \ > cp -a $dir /<<PKGBUILDDIR>>/debian/spikeproxy///usr/share/spikeproxy/ ; > \ > done > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > install -m755 debian/spikeproxy-wrapper > `pwd`/debian/spikeproxy/usr/bin/spikeproxy > cd debian/spikeproxy/usr/share/spikeproxy/ && ln -s > ../../../var/cache/spikeproxy/ cache > dpkg-genchanges --build=all >../spkproxy_1.4.8-4.3_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/spkproxy_1.4.8-4.3_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: spkproxy Source-Version: 1.4.8-4.4 We believe that the bug you reported is fixed in the latest version of spkproxy, 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. Giovani Augusto Ferreira <giov...@riseup.net> (supplier of updated spkproxy 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: Sun, 25 Dec 2016 19:10:13 -0200 Source: spkproxy Binary: spikeproxy Architecture: source Version: 1.4.8-4.4 Distribution: unstable Urgency: medium Maintainer: Javier Fernandez-Sanguino Pen~a <j...@computer.org> Changed-By: Giovani Augusto Ferreira <giov...@riseup.net> Description: spikeproxy - Web application security testing proxy Closes: 831930 Changes: spkproxy (1.4.8-4.4) unstable; urgency=medium . * Non-maintainer upload. * Update DH level to 10. * debian/compat: updated to 10. * debian/control: - Bumped Standards-Version to 3.9.8. * debian/rules: - Fix FTBFS about a binary-indep target. Thanks to Santiago Vila for patch. (Closes: #831930) Checksums-Sha1: cb2c9027cabdf93030d443cc1b0ecd7891282290 1715 spkproxy_1.4.8-4.4.dsc e673e2c50d313e72613f4824d3633d241c6c66fa 10730 spkproxy_1.4.8-4.4.diff.gz Checksums-Sha256: 9b1fd26b089db9daaf293c2c96c2c5f99b608a0777e5115476137851aa21f782 1715 spkproxy_1.4.8-4.4.dsc a27d8125f6b88f2f8481912b0014b7a84a3670363da082b52ca5b2ab80ba3deb 10730 spkproxy_1.4.8-4.4.diff.gz Files: d12c7b4be55f841cee412bc51603747c 1715 net optional spkproxy_1.4.8-4.4.dsc 9f9c146906dc6d3e590d6693f0dbbdc2 10730 net optional spkproxy_1.4.8-4.4.diff.gz -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEs/UaJxJhnD7NdLjheElO9yN1pmwFAlhgPQYACgkQeElO9yN1 pmxfmw/+K0miGL6wjVgHfLLHjuASFG1jQk+5Ykx3xC9jCVnSpuK6mT3DeW+gmRmz qooU0VIBspnyQiFEWxYMTCRgp94uoMPtfx+LBJDiqksSulAr8wNYHJ6O5qPScv6k YtOcdxqfygQDCfYo4A+2dy1Jw9D6epfXCfHDF/zjMsXAz29vlZ/8JhU6R2hGnZmb 2l35SEGiINyhubKIi2dbxFWwGVQu/OsR8ARuLffZ+pYN+aRYq3Mlf0CppL1of61i aHPjGMPpqQ+UN0wGvf6ylRUO/iw9h5Pg41Riz0wii4YmdMl0bR7Fv5syeaGpm1ND r8KARq123qOagur/gplGFGV5ExSxEKJRTPFmjeJ8znui3WsWMfTywOZbWczSdWq1 NJ2QolsDM7Cf7FKqZ2HLZirqWk+20vXZ2owDLXb+PpLjJCTKZzBWQ0jzQrtLpJDN iwQvduS0WnSqey7Yng7jg4srn59I8wHibpyolZnj1iofgYkR6UTJk/utKClt6miM G/n35aPmtU5SC2yzbbl5IQgvu0uXxcTCMKHIOXUq6T/FIcBiOFSSmqVuADa0cDfC pER4BsFlnoEz980NslB1QrUlY3M0+N/LaKZjqfQGXjsH9sA/b47itNthNdpfw76k L3qBh+rAl8P5S/yuZI6fDKQLXUzhBek2AiLMSruv7jZ6UdAcxkg= =FyN8 -----END PGP SIGNATURE-----
--- End Message ---
