Your message dated Mon, 08 Jul 2024 18:05:03 +0000
with message-id <e1sqsjx-005lwg...@fasolo.debian.org>
and subject line Bug#1047276: fixed in mailfront 2.12-3
has caused the Debian Bug report #1047276,
regarding mailfront: Fails to build source after successful build
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.)
--
1047276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mailfront
Version: 2.12-2
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild
Hi,
This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).
This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.
More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild
Relevant part of the build log:
> cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env
> -us -uc -rfakeroot -S
> ------------------------------------------------------------------------------------------------------------------------
>
> dpkg-buildpackage: info: source package mailfront
> dpkg-buildpackage: info: source version 2.12-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Vagrant Cascadian
> <vagr...@reproducible-builds.org>
> dpkg-source --before-build .
> debian/rules clean
> dh clean
> dh_auto_clean
> make -j8 clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> rm -f `cat TARGETS`
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_clean
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: verifying ./mailfront_2.12.orig.tar.gz.asc
> gpgv: Signature made Thu Feb 12 14:10:37 2015 UTC
> gpgv: using RSA key 5151BDC9C14D3C67
> gpgv: Note: signatures using the SHA1 algorithm are rejected
> gpgv: Can't check signature: Bad public key
> dpkg-source: warning: cannot verify upstream tarball signature for
> ./mailfront_2.12.orig.tar.gz: no acceptable signature found
> dpkg-source: info: building mailfront using existing
> ./mailfront_2.12.orig.tar.gz
> dpkg-source: info: building mailfront using existing
> ./mailfront_2.12.orig.tar.gz.asc
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
> mailfront-2.12/conf-bgincs
> mailfront-2.12/conf-bglibs
> mailfront-2.12/conf-bin
> mailfront-2.12/conf-bin{orig}
> mailfront-2.12/conf-cc
> mailfront-2.12/conf-ccso
> mailfront-2.12/conf-ccso{orig}
> mailfront-2.12/conf-cc{orig}
> mailfront-2.12/conf-include
> mailfront-2.12/conf-include{orig}
> mailfront-2.12/conf-ld
> mailfront-2.12/conf-ld{orig}
> mailfront-2.12/conf-modules
> mailfront-2.12/conf-modules{orig}
> mailfront-2.12/conf-qmail
> mailfront-2.12/conf-qmail{orig}
> dpkg-source: error: aborting due to unexpected upstream changes, see
> /tmp/mailfront_2.12-2.diff.YhxZfb
> dpkg-source: info: Hint: make sure the version in debian/changelog matches
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
>
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage
> --sanitize-env -us -uc -rfakeroot -S' failed to run.
The full build log is available from:
http://qa-logs.debian.net/2023/08/13/mailfront_2.12-2_unstable.log
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: mailfront
Source-Version: 2.12-3
Done: Santiago Vila <sanv...@debian.org>
We believe that the bug you reported is fixed in the latest version of
mailfront, 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 1047...@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 mailfront 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: Mon, 08 Jul 2024 19:35:00 +0200
Source: mailfront
Architecture: source
Version: 2.12-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Santiago Vila <sanv...@debian.org>
Closes: 1047276
Changes:
mailfront (2.12-3) unstable; urgency=medium
.
* QA upload.
- debian/rules: Do not try to save the original conf-* files, as they
are created from scratch every time the package is built.
- debian/clean: Remove those files here instead.
* The above two changes will make the source package to be buildable
after a successful binary build. Closes: #1047276.
* debian/rules: Actually run the tests in dh_auto_test.
[ Daniel Lenharo de Souza ]
* Add fields Vcs-Git and Vcs-Browser.
Checksums-Sha1:
c6243938a4c37fa6a41e18f12c40f09c2cd83129 1747 mailfront_2.12-3.dsc
cd8ad9f403a43034abc489f4af0bee5f83bd7a24 30468 mailfront_2.12-3.debian.tar.xz
4c56dfdb59a94008b8bb417c18d3dd979d6b96fa 5554 mailfront_2.12-3_source.buildinfo
Checksums-Sha256:
666185aa632c750854ce1bd6dbe8b378810cf66a80f4397dc1404f7163172694 1747
mailfront_2.12-3.dsc
0d57855a951c1d8631dc860b85a30765d9288d23b7fb08b71c4706458f0f6cf4 30468
mailfront_2.12-3.debian.tar.xz
b922f944e8d2d348bba8eb0cafd342aa5c9071ff82da201557e259953bec1faf 5554
mailfront_2.12-3_source.buildinfo
Files:
11f1f45853a26ca92b2742fc6d866e3d 1747 mail optional mailfront_2.12-3.dsc
ad048a426485e623e1443998985cafb1 30468 mail optional
mailfront_2.12-3.debian.tar.xz
ce369f2ab295729e0a9593a3c53fc4d5 5554 mail optional
mailfront_2.12-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAmaMJHkACgkQQc5/C58b
izLtmQf7BO3gRCe9tZljRrtdZFWx+Vh3ubB9p42JjEVx5lQR90ZZQBhHtPaVymPp
BBSQILFwv7VaiQlaDLB78lxcaPL21zSyfFsqActH4GU8XwQ0zSTNvpnJ2WHtvHfl
171qYgN94i+bskVxuKbv7nF3/G1IOooLwGK/lV74OrdztrJMdvILcS9eqUX30XMu
mkjYvkEmDqKu+XSUuGNtjCenq9AGONTLIH20kvoj5h7eseFVp7qky+SrxetVJ46E
BhrXETYVcKBuxgfb9J5R7z9RNr5xs6//0BKoXEC+3lDYlaI78ypLByO/D17D7eYW
z3sW+SFQHFeqDHsueUwTeuXxJIVk3g==
=fMn3
-----END PGP SIGNATURE-----
pgpuzDrMq4DWc.pgp
Description: PGP signature
--- End Message ---
