Your message dated Mon, 08 Sep 2014 13:47:05 +0000 with message-id <e1xqzhd-0007bl...@franck.debian.org> and subject line Bug#753184: fixed in foremost 1.5.7-5~deb7u1 has caused the Debian Bug report #753184, regarding foremost: FTBFS: dpkg-source: error: expected ^--- in line 3 of diff `foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch' 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.) -- 753184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: foremost Version: 1.5.7-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140628 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Unpack source > ───────────── > > gpgv: keyblock resource `/sbuild-nonexistent/.gnupg/trustedkeys.gpg': file > open error > gpgv: Signature made Fri Jul 20 14:05:33 2012 UTC using RSA key ID EED3BC0D > gpgv: Can't check signature: public key not found > dpkg-source: warning: failed to verify signature on ./foremost_1.5.7-4.dsc > dpkg-source: info: extracting foremost in foremost-1.5.7 > dpkg-source: info: unpacking foremost_1.5.7.orig.tar.gz > dpkg-source: info: unpacking foremost_1.5.7-4.debian.tar.gz > dpkg-source: info: applying fix-config-file-path.patch > dpkg-source: error: expected ^--- in line 3 of diff > `foremost-1.5.7/debian/patches/fix-lintian-hardening-warnings.patch' > dpkg-source: info: applying fix-lintian-hardening-warnings.patch > dpkg-source: info: fuzz is not allowed when applying patches > dpkg-source: info: if patch 'fix-lintian-hardening-warnings.patch' is > correctly applied by quilt, use 'quilt refresh' to update it > FAILED [dpkg-source died] The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/28/foremost_1.5.7-4_unstable.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: foremost Source-Version: 1.5.7-5~deb7u1 We believe that the bug you reported is fixed in the latest version of foremost, 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 753...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raúl Benencia <r...@kalgan.cc> (supplier of updated foremost 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: Fri, 25 Jul 2014 12:00:45 -0300 Source: foremost Binary: foremost Architecture: source amd64 Version: 1.5.7-5~deb7u1 Distribution: wheezy Urgency: medium Maintainer: Raúl Benencia <r...@kalgan.cc> Changed-By: Raúl Benencia <r...@kalgan.cc> Description: foremost - forensic program to recover lost files Closes: 753184 Changes: foremost (1.5.7-5~deb7u1) wheezy; urgency=medium . * Update maintainer email address. * Include new VCS control fields. * Fix FTBFS caused by a regression in dpkg 1.16.15, which was uploaded as security update. The problem is caused by the way in which dpkg parses a patch's headers. In order to solve this, a newline character was needed between the last DEP-3 header and the beginning of the patch. Thanks Juhani Numminen. (Closes: #753184) * Bump standards version to 3.9.5, no changes. Checksums-Sha1: 8dbac4ed225b925b5d339de1cf2f63ce92f2ce01 1822 foremost_1.5.7-5~deb7u1.dsc 2b410103b74e00009b01edd958888619b52894d8 7396 foremost_1.5.7-5~deb7u1.debian.tar.gz 6f019caa0562dc2b4d4998e990eccc4034dc8785 46068 foremost_1.5.7-5~deb7u1_amd64.deb Checksums-Sha256: 5c64a89752fc67847a6ee2b1a99558503376d3eda83f8a2e441f36f789761a72 1822 foremost_1.5.7-5~deb7u1.dsc 4949ff010a87da10931659a5e8f39811b64fc428387f53cbcd8d16226cef11d5 7396 foremost_1.5.7-5~deb7u1.debian.tar.gz 7781d928d1d4af8339ce8a2cd702d2896a48930a697bf25dcbb52f200d10975b 46068 foremost_1.5.7-5~deb7u1_amd64.deb Files: 07ef9c640e9f7f698e04a96b4709dee6 1822 admin optional foremost_1.5.7-5~deb7u1.dsc 0372a8a9d01f7ceb31485066c0711074 7396 admin optional foremost_1.5.7-5~deb7u1.debian.tar.gz b76e0a306e3ad2c30290b90b34596e7c 46068 admin optional foremost_1.5.7-5~deb7u1_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUC8TzAAoJELlyvz6krlejIAEP/iy1WbUOAOBbTncjk69FQFZ0 QGTQUXP63V1S5PzSgLIBnzh3km8s8Ai4+I+2kgZj0ItAhCXlmoqVsEa8bcVYBLRS Cfj9Kzpv8aAwmE3KVyiLGp3tF6QDGTryigvHa1ZisLehDfQYbcF9WN6XrGtjm5K8 vz0U21tQg5huZ9GsCr9N/8Q6qBnx0POngeHde2IU2umCp/Gec65CcTAVZdcUjbVS keHlzUPRE9ke8ymCZJTWuOttbFa8J8Pc+t4+8Fk2JIrs5Z1+oYIAWL4WvMJ2dM0y yrr53GSt6DZz0BTfUflhFd6fVpTAxBjQ8cam9XwgxIXUsL9IOTvLEm5cbUXIKxPT MhaE84EPJKimjH1xOLM4UbYCmqa8O7DLJiK7VFIMptDqId+DUrTBSXY13ReXYNDF wHBURggYrC1XkPkafYw+6XJE9mMnSSUlRW+SKdyvE0acgwrhnkPtAnKKlcmZkRr+ KgFT/I2ZyicbXbR+4PjnueboXb3L3CfkxSPXygNPzZ7DOrHen9wQ937aU+ap6huB gtDhZdhBPJbo0pra9tUsLl7BwJqRFe1Fvm977mr6NN35y2RB4M+PXcD4rKAM8RuE KtapP6pfIfTjry9dKIkxoRxWHGTSxviZekSMCR5S78wmZA5lHziPdZsK2ysYf1Jz itDM9JdMDjmwcStqHlS5 =GJ6D -----END PGP SIGNATURE-----
--- End Message ---
