Hi Chris, On Fri, Apr 30, 2021 at 08:12:54PM +0000, Chris Knadle wrote: > Salvatore Bonaccorso: > > Hi Benedikt, > > > > On Thu, Apr 29, 2021 at 10:48:56AM +0200, Benedikt Tuchen wrote: > > > Hello > > > > > > Is this bug still observed? > > > > > > We would be very happy to see this problem solved for Buster as > > > well. > > > > That would be great. For a security team perspective this is marked as > > no-dsa, this means we think that it will not warrant a dedicated DSA, > > but fixing the issue in buster would be possible via one of the > > upcoming point releases. > > I also want to fix this but got lost in the documentation when I was last > doing the work. When I read the documentation in the Debian Developer's > Reference about how to do an upload to Stable, it wasn't immediately clear > to me which release to target and which upload queue to send the package to. > > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#upload-stable > > So now re-reading it, it seems the upload should target "buster" and the > upload I ship should likely be to the "proposed-updates-new" queue. > Probably? Somehow I find the wording a little difficult to be certain in its > parsing. If this is correct please let me know.
That is correct, and then one it hits there the NEW queue, a stable release mnager will decide if the upload should be accepted into the proposed-updates section. It should be accompanied with a respective release.debian.org bugreport accordingly as mentioned in the above rerference. Note there is as well this "improved" workflow: https://lists.debian.org/debian-devel-announce/2019/08/msg00000.html . Regards, Salvatore
