Your message dated Fri, 13 Jan 2017 16:18:55 +0000 with message-id <e1cs4z5-000bbo...@fasolo.debian.org> and subject line Bug#831954: fixed in libsnmp-mib-compiler-perl 0.06-2.2 has caused the Debian Bug report #831954, regarding libsnmp-mib-compiler-perl: 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.) -- 831954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: libsnmp-mib-compiler-perl Version: 0.06-2.1 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>>' > Manifying 2 pod documents > Installing > /<<PKGBUILDDIR>>/debian/libsnmp-mib-compiler-perl/usr/share/perl5/Bundle/SNMP/MIB/Compiler.pm > Installing > /<<PKGBUILDDIR>>/debian/libsnmp-mib-compiler-perl/usr/share/perl5/SNMP/MIB/Compiler.pm > Installing > /<<PKGBUILDDIR>>/debian/libsnmp-mib-compiler-perl/usr/share/man/man3/Bundle::SNMP::MIB::Compiler.3pm > Installing > /<<PKGBUILDDIR>>/debian/libsnmp-mib-compiler-perl/usr/share/man/man3/SNMP::MIB::Compiler.3pm > Installing > /<<PKGBUILDDIR>>/debian/libsnmp-mib-compiler-perl/usr/bin/mibbrowser > Installing > /<<PKGBUILDDIR>>/debian/libsnmp-mib-compiler-perl/usr/bin/mibcompiler > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > chmod a-x > /<<PKGBUILDDIR>>/debian/libsnmp-mib-compiler-perl/usr/share/perl5/SNMP/MIB/Compiler.pm > touch install-stamp > dh_testdir > touch arrange-stamp > dh_testdir > touch binary-indep-stamp > dpkg-genchanges --build=all > >../libsnmp-mib-compiler-perl_0.06-2.1_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/libsnmp-mib-compiler-perl_0.06-2.1_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: libsnmp-mib-compiler-perl Source-Version: 0.06-2.2 We believe that the bug you reported is fixed in the latest version of libsnmp-mib-compiler-perl, 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. Adrian Bunk <b...@debian.org> (supplier of updated libsnmp-mib-compiler-perl 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: SHA512 Format: 1.8 Date: Fri, 13 Jan 2017 17:58:36 +0200 Source: libsnmp-mib-compiler-perl Binary: libsnmp-mib-compiler-perl Architecture: source Version: 0.06-2.2 Distribution: unstable Urgency: medium Maintainer: Deepak Tripathi <apenguinli...@gmail.com> Changed-By: Adrian Bunk <b...@debian.org> Description: libsnmp-mib-compiler-perl - a MIB Compiler supporting SMIv1 and SMIv2 Closes: 831954 Changes: libsnmp-mib-compiler-perl (0.06-2.2) unstable; urgency=medium . * Non-maintainer upload. * Apply patch from Santiago Vila to fix "dpkg-buildpackage -A". (Closes: #831954) Checksums-Sha1: c0f7de9c916720e7f6a9a771e4e7543f8fce12f9 1870 libsnmp-mib-compiler-perl_0.06-2.2.dsc 7e0f72e18781439be4b140d4ccae245f30cc04f3 2606 libsnmp-mib-compiler-perl_0.06-2.2.diff.gz Checksums-Sha256: 68f83011574aac5b7cf1153275f2ff765a5d1e64ffc81f67fe60058e95813512 1870 libsnmp-mib-compiler-perl_0.06-2.2.dsc d9ae1aa6fdc61758365d491eed9d33a7a90c143fc18d84a19337a14dd01c3646 2606 libsnmp-mib-compiler-perl_0.06-2.2.diff.gz Files: 7dac8902606473564186bb0ed63c3bb7 1870 perl optional libsnmp-mib-compiler-perl_0.06-2.2.dsc c0ebd8645df5e0c29e95a592aa9247fd 2606 perl optional libsnmp-mib-compiler-perl_0.06-2.2.diff.gz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlh4+Z0ACgkQiNJCh6LY mLEMNQ/8D2B3mc917FVwQhAxTk5dML4lszLRrIQ/hyW9mIb/mHKMaoTsUvHhMVPh 86qC+BvJkoMfMj5baUJDRrawIK5tYyTlebQduG6Tz3Xzb20I2nls/5ibfARVm/JO 4y03gsY1W7G/+6y/d1nKSJJgHRuRDEKQ05PDxudzLpSGICJyDVv6rzg+SBNUZ24T j3BqvYKRZM4Rjs/rspCnbweBM1obh0MRYE62lj0j3ns0+s2jcN5meUhAhe7Ae6XJ 8C99Y+RtRclA3Qk5RNC4mCg0o8vsedf5zV5xInZf35mCnpu6LLEncwx7bLSQ1P2E VsQIwniQBiK/Q5GBTt/C2su8FkR1rwdK+q44K0lEpMwETaTuZwaw43H3MOrIeMoL m73uUgKzswj081E1avh6gAXoubX48NW4FbsoLHk9MeuPxW0qVup2ue57A38g8Try MPd38fKYGA141Xx5VsK6qsMEtfvPPBMmH1LCTK66PRQmCFVgWhi33BF8YwD2e9BD m9TvEG5ioM0E01eYmNieFz4vwo1ooTMY4Rd1A6R8iO9nGFEnZNDzSLmHjFH5U+XV GPZzMAmeZBjDTuoUsrPwP7DVKEiBe57NR7G5z7ZXO2Ci154mP9hnay3uS21rSCEw kMtPwPEZ1vqdv9ZUkBuojVipHhsmkpQP587eYZML8LbLrlM3ZFc= =BmYe -----END PGP SIGNATURE-----
--- End Message ---
