Your message dated Wed, 18 Jun 2025 13:49:15 +0000
with message-id <[email protected]>
and subject line Bug#1107552: fixed in dgit 13.3
has caused the Debian Bug report #1107552,
regarding git-debpush's changed suite check
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 [email protected]
immediately.)
--
1107552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107552
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-debpush
Version: 13.13
git-debpush notices if your suite has changed since the last upload
and complains. I'm not sure this complaint is warranted. If it *is*
warranted, maybe dgit should have it too.
Background - the no-good UNRELEASED changelog convention:
The possibility of this mistake arises because of the (IMO broken)
"UNREELASED" convention in changelogs. Using UNRELEASED this way,
(rather than an unfinalised changelog entry) deletes the target suite
information from the changelog. Then dch must restore it but it
doesn't have all the information.
I think UNRELEASED was invented because some tool(s) didn't understand
unfinalised changelogs, so someone invented the same thing again but
worse. UNRELEASED's sole advantage is that it can be parsed by bad
changelog parsers. (The date in it is often a hindrance.)
Unfortunatley the UNRELEASED convention is widespread (and not all
tooling supports unfinalised chagnelogs very well). But, I think the
right answer to this possible source of human error is to use
unfinlised changelogs instead (and play whack-a-mole with tooling).
(Or to put something like UNRELEASED-unstable into the changelog.)
I use unfinalised changelogs, so that's what we've been doing in the
dgit team. With our workflow, this mistake cannot arise, so there is
never any need to confirm a change of suite. A change of suite in the
changelog was always done deliberately, by changing the suite in
changelog from one real suite into another.
git-debpush pickiness:
git-debpush can easily do this check because it's digging into history
anyway to try to find out which quilt mode to use. dgit would maybe
have to do something similar if we wanted it to check this.
But git-debpush is trying to be less picky than dgit. I think this
includes not just trying to avoid conversion failures at the t2u
service, but also being picky about things that can be detected
synchronously.
It seems odd that we have put a check in git-debpush which mitigates a
risk that existing upload tooling also fails to mitigate, and for
which there are other mitigations, at least some of which can be
adopted immediately.
Compaarison with dgit:
dgit has a --new option which seems to do the same thing, but is
actually for something different. dgit insisting on --new won't stop
you accidentally uploading the experimental branch to sid. I think
dgit's --new is wrong and have filed #1107551 about that.
Tenative conclusion:
This check should be simply removed from git-debpush.
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 13.3
Done: Sean Whitton <[email protected]>
We believe that the bug you reported is fixed in the latest version of
dgit, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sean Whitton <[email protected]> (supplier of updated dgit 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 18 Jun 2025 13:55:28 +0100
Source: dgit
Architecture: source
Version: 13.3
Distribution: experimental
Urgency: medium
Maintainer: Debian tag2upload Delegates <[email protected]>
Changed-By: Sean Whitton <[email protected]>
Closes: 1107552 1107897
Changes:
dgit (13.3) experimental; urgency=medium
.
git-debpush behavioural improvements:
* Read a whole line when prompting. Closes: #1107897.
* Drop changed-suite check. Closes: #1107552.
* Exit immediately if overriding a check denied by user.
.
git-debpush fix:
* Fix parsing --batch command line option.
.
Documentation [Ian Jackson]:
* tag2upload(5): New "SEMANTICS" section.
Checksums-Sha1:
f8c05eb47965d92dcd3bbd184e0730789009ad5e 2413 dgit_13.3.dsc
0ec931eabc1360b643c2f58b48209e95aabae61d 762900 dgit_13.3.tar.gz
Checksums-Sha256:
e4c4395266812d94719078799277fae0b24259427be40d04c41125c111581d16 2413
dgit_13.3.dsc
8c85b286e78bad03320d68b4a15f457866eb604339a82ac686f2841d856a536b 762900
dgit_13.3.tar.gz
Files:
6574f6600fb2574baaabfe909faf2e6e 2413 devel optional dgit_13.3.dsc
06502bbb4cc2eabcaa962b8b76805879 762900 devel optional dgit_13.3.tar.gz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmhSwIsACgkQaVt65L8G
YkBf6RAApJMuV+vngl6yl2TCx6rH0EtxXVcx2GAbKxbrDHJ5SLaDolQbMDWLxKwa
4/qBpipus7aulbMtct9mD43KldXSEtHJK34F7GM8bqeyaC8nn7q5rK63Vb6jEHTN
9KVx1SaofTeQIoBGlZ9yV3CB1N8nhRUIM8N4I1m7WhEuSqUSmFWmHr6m8bK0uY1q
16WalMexWlWcKSQ5N0BzEtwOfsrxhq0XoiMzLKdigldtw5kAAAdP/a9vBanTVzgB
Vm1/2ToTko+r/p07qBTti8EiSLijy1aqBVSvpcp+U5dBohIUUFTVOp+npOWTkwNh
S9SJZn3wm1y/yP9+FB/J4hHyA2PHaD4+d0B9YjYNY+ozt3jRvzNfaQC78iG2yp4m
5EHJk35fnlNH/LdBZuHBTPxYQk6gdMbhvDc8YYuWjB8Uck1jvyaHsVCr6LVvxhE2
z+wouBcRbNNk9UvRzQ7hBSTfH4GZYc6ZmYN9s6mCTahzXYXoWnny/uglYQgIAy3N
Ht2WIrH/MIe1RbhH7o06xXhZ/iD8O5CHEQAhIZkh5R7ogUtV/Lzvt+8V2SlfMGYj
7W8UhgmnwCS9LG3kYBp+YRqntWF3++iF9iZtLQEXDW78Z0qrLaT6uZC12ViaX7tO
uxTVt+mNUq+Z9CcDaMxM3CIWHxDOTeeimjyi4fmcN45VxKTSbMo=
=qP80
-----END PGP SIGNATURE-----
pgpNVVTEdWzFg.pgp
Description: PGP signature
--- End Message ---
