tags 1109323 + patch thanks On Sun May 31, 2026 at 12:29 AM CEST, Serafeim (Serafi) Zanikolas wrote: > I see a bit of a discrepancy between the original request (which, judging by > the > link to [email protected], seems to be mostly about technical > details) and the ensued discussion (which is mostly about NMU/coordination > norms). > > Lucas, what exactly did you have in mind when you filed this bug? is there > anything in gannef's email that's not captured in dput/dcut manpages and > config > defaults that you think would be useful to include in devref?
Lucas, friendly ping.
> on coordination norms: section 5.13.1 ("When and how to do an NMU") seems to
> cover all aspects discussed in this bug (e.g. report a bug to BTS, use
> DELAYED)
> with the only exception being an explicit statement that it's okay to file a
> bug
> with a patch (or MR) and _at the same time_ upload to DELAYED so that one can
> fire and forget -- which does seem like a worthwhile addition.
everyone: please see attached patch.
thanks,
serafi
From f453783c581885230fee5d6ae1697816f73a2c24 Mon Sep 17 00:00:00 2001 From: "Serafeim (Serafi) Zanikolas" <[email protected]> Date: Sat, 13 Jun 2026 23:23:28 +0200 Subject: [PATCH] pkgs: recommend fire-and-forget DELAYED workflow and mention dcut(1). Closes #1109323. --- source/pkgs.rst | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/source/pkgs.rst b/source/pkgs.rst index 43339da..e23301a 100644 --- a/source/pkgs.rst +++ b/source/pkgs.rst @@ -446,10 +446,13 @@ making uploads that disrupt ongoing transitions. Delayed uploads -------------------------------------------------------------------------------------------------------------------------------- -It is sometimes useful to upload a package immediately, but to want this -package to arrive in the archive only a few days later. For example, -when preparing a :ref:`nmu`, you might want to -give the maintainer a few days to react. +It is sometimes useful to upload a package immediately, but to want this package +to arrive in the archive only a few days later. For example, when preparing a +:ref:`nmu`, you might want to give the maintainer a few days to react, while at +the same time having the certainty that your upload will eventually take effect +if the maintainer does not. A one-shot approach of (i) file bug with a patch (or +Merge Request) and (ii) at once upload to DELAYED, is much more efficient than +having to wait for days between the two steps. An upload to the delayed directory keeps the package in `the deferred uploads queue <https://ftp-master.debian.org/deferred.html>`__. When the @@ -462,6 +465,10 @@ multiple times per day to ``ftp.upload.debian.org``. With dput, you can use the ``--delayed`` *DELAY* parameter to put the package into one of the queues. +Sometimes you'll need to remove a previously uploaded package from the DELAYED +queue (e.g. because the package maintainer has asked you so). dcut(1) has +examples of how to do so. + .. _s5.6.4: Security uploads -- 2.47.3
signature.asc
Description: PGP signature
