On Mon, 2022-08-22 at 19:46 +0200, Jakub Ružička wrote: [...] > It's been fixed upstream in 3.1.3 release. > > I've marked the bug fixed in 3.1.3-2 by sending mail to > [email protected] - is that the recommended way? > > I'd prefer to reply to the bug with a magic syntax but also a human > readable explanation. The syntax I used with control server didn't > seem > to work in bug reply.
You can use "Control" pseudo-headers in the body of a mail to a bug. https://www.debian.org/Bugs/Reporting#additionalpseudoheaders has some examples. [...] > Next time, I'll be sure to file release.debian.org p-u bug before > uploading. > > There sure is a lot to learn about Debian processes, thanks for > clarification. Thanks. There's some more information about the workflow for updates to stable at https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions if that's of any help. Regards, Adam
