# bcc control@bugs.d.o user release.debian....@packages.debian.org usertags 1054119 pu tags 1054119 bookworm moreinfo retitle 1054119 bookworm-pu: package qpdf/11.3.0-1 thanks
On Tue, 2023-10-17 at 07:32 -0400, Jay Berkenbilt wrote: > The attached patch to qpdf 11.3.0 fixes a bug that could potentially > result in loss of data. I'd like permission from the release team to > upload this to stable. I've been a debian developer since 2005, but > it's been years since I've last prepared a release to the stable > distribution. As far as I can tell, the current procedure is to > upload with the target distribution as "stable" and upload to ftp- > master. This will direct the package the proposed-updates queue. Is > this correct? > Close, but a few rough edges. :-) In relation to your query above, suite codenames - i.e. "bookworm" in this case - are preferred over designations such as "stable", as they're more self-documenting over time. Technically, such uploads enter the "stable-new" queue, from where we can accept them (or not) into p-u, but that's an implementation detail. In terms of the patch, the diff we would need for review is a source debdiff of an appropriately-versioned package that you've built and tested against stable, not just the patch to the source code. I'd suggest reviewing https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions as a more general primer on the process. As noted in the dev-ref section, please use "reportbug release.debian.org" for p-u requests, or set equivalent metadata. That helps ensure that the request ends up in the correct section of our BTS web view, where uncategorised bugs may get overlooked for some time. I've fixed up the relevant bits for this request (see the start of my reply). Regards, Adam
