Hi Nicolas, On 21-10-2021 02:17, Nicholas D Steeves wrote: > I will of course credit you for identifying this issue and taking the > initiative to fix it, and will upload without delay once I receive your > ACK (please CC me).
Thanks you, but as I detect these issues in an automatic way without much manual labor, I don't need the credits :). And I uploaded to DELAYED exactly to give others the opportunity to fix it before me, so uploading to DELAYED in my opinion *always* has that ACK implied. > For future reference, if there was an NMUdiff, I would incorporate it > into the -4 release along with my change, but then, what is the best > practise? I have pasted the diff below, but for such a no change NMU, I'd just ignore it if I were you. It's not interesting especially if you beat the upload anyways. > Ask for the NMU submitter to cancel the delayed upload, > upload -4 which will presumably cause -3.1 to be rejected when the > delayed timer fires, or cancel the delayed upload myself? I can (and will try) to cancel my upload, but it's rather harmless if I fail because it will indeed be rejected if there is already an newer version in the suite and you'll only get a reject e-mail about it (which can still be annoying, so I'll try and cancel). Paul paul@mulciber /tmp/python-volatile $ git diff HEAD~ diff --git a/debian/changelog b/debian/changelog index dacf399..8fcaf23 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +python-volatile (2.1.0-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * source only upload to enable migration (Closes: #996722) + + -- Paul Gevers <elb...@debian.org> Sun, 17 Oct 2021 20:58:04 +0200 + python-volatile (2.1.0-3) unstable; urgency=medium [ Debian Janitor ]
OpenPGP_signature
Description: OpenPGP digital signature
