Your message dated Tue, 27 Aug 2024 08:35:08 +0000
with message-id <e1sirfq-00a6z1...@fasolo.debian.org>
and subject line Bug#1077107: fixed in commit-patch 2.6.2-2
has caused the Debian Bug report #1077107,
regarding commit-patch: needs rebuild against dh-elpa >=2.1.5
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.)
--
1077107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: commit-patch
Severity: serious
Tags: patch
User: debian-emac...@lists.debian.org
Usertags: dh-elpa-2.1.5-rebuilds
Dear maintainer,
This package needs a no-change upload to rebuild it against dh-elpa
>=2.1.5. This is because binNMUs cannot be used to rebuild arch:all
packages.
The update is needed to resolve a problem for users upgrading between
stable releases. In some circumstances, old .elc files can be left
behind, and Emacs will try to load them. In the best case there will
be warnings that the .el file cannot be found, so the .eln file cannot
be produced. In the worst case the package could break.
This is an RC bug because it's a Policy violation to leave the files
behind upon removal of the old version.
Please do something like this:
% dch Rebuild against newer dh-elpa.
% dch -r
% git commit debian/changelog -mchangelog
and upload.
Thanks.
--
Sean Whitton
--- End Message ---
--- Begin Message ---
Source: commit-patch
Source-Version: 2.6.2-2
Done: David Caldwell <da...@porkrind.org>
We believe that the bug you reported is fixed in the latest version of
commit-patch, 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 1077...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
David Caldwell <da...@porkrind.org> (supplier of updated commit-patch 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, 26 Aug 2024 12:52:07 -0700
Source: commit-patch
Architecture: source
Version: 2.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: David Caldwell <da...@porkrind.org>
Changed-By: David Caldwell <da...@porkrind.org>
Closes: 1077107
Changes:
commit-patch (2.6.2-2) unstable; urgency=medium
.
* Rebuild against newer dh-elpa (Closes: #1077107).
Checksums-Sha1:
baa236ce06656feb5162e0e84df9bc5b559a317e 1904 commit-patch_2.6.2-2.dsc
6dd6d75fcf8fdfa5b0627c610b19e4839ef5096e 3320
commit-patch_2.6.2-2.debian.tar.xz
c3a55c428ef0b79bd6245d76fa175098ccc46075 8583
commit-patch_2.6.2-2_amd64.buildinfo
Checksums-Sha256:
06215d2a15988c938b6dd7e8937f0e1abc1b06da1548b97f342a9da5a5ef4f55 1904
commit-patch_2.6.2-2.dsc
1be5bd5487a0e4a648e298affbb3060dc7b179f1f5bcf721646989647a2bfbc1 3320
commit-patch_2.6.2-2.debian.tar.xz
38bd498af635b09f6d28c6a5a2169a82ef2854916f24317e4dcf98b772c1692e 8583
commit-patch_2.6.2-2_amd64.buildinfo
Files:
97bb3c3cb091eb698104972ac9aef452 1904 vcs optional commit-patch_2.6.2-2.dsc
0c2ccca680723c400b7b42861e2f9d00 3320 vcs optional
commit-patch_2.6.2-2.debian.tar.xz
ab287bff7f89bd893f70c455d635fe11 8583 vcs optional
commit-patch_2.6.2-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmbNgksACgkQrMfCzzCU
EYg3ZBAAn537mzAZvsR73jBLGNr3u0J3rh05faW7oFd7PfhzoGBqwZhue/ux27WY
K1/j07GbginrGt1l+wTo+Jg97SNioJtZQ69Yu0DqSiDgMR+IDsSyeRBI60sltKLZ
3rwCCwRE/1accEpiIPY7CGXBG71KSBqpwkFnXovatiTjIiU3zNAaavMyKuOT8ESG
CbblVd3QYBGCalZdv363tHfalkqrV2wg+vPrOHgU3fnXRHW8aClhqQh3ioMXARmX
pc3yO0nHuqPxw21JEO0lSqURxWbzisfa2jzIXraqFI+tEbQKPKBQUVcISjZO5pxf
vl9aJ6HddcZI0C43T3nXPLn5ngloo6/VdAqgs92T1qiVqV12duz1iyiw9GxpaQie
p/EG0hIY9nRTEA4NoWPcGBuoRDiwD8415E4LCMTxcFYm2vTd10RhU5BFUG8kFM9X
uGA9Q4mJ3XUL2wRC4lrreG/i3es6nYP8LBDPEtke5A/PUbXZgCyFgP0bYjaBBKAO
QxQuccmi18mpdufAaTN30oBvJooDaJZ7+vf1SEsldlAnUwSQKXLRkOicDesF/EDt
FXUEgees5KKGctHNeHsAr+tiJiQg4jwq5+aESEhkFRAo55Orw8UJSm71V/DI1IpM
Z5qvrZjrj/9tTpJp42ujo7o3de3xQR6R2jJgKa+KOcNkm2BZdpI=
=mjoh
-----END PGP SIGNATURE-----
pgppygwTO74gV.pgp
Description: PGP signature
--- End Message ---
