On Tue, 2026-02-10 at 10:43 +1100, Dmitry Smirnov wrote: > On Saturday, 7 February 2026 8:47:34 pm Australian Eastern Daylight > Time Adam D. Barratt wrote: > > I noticed that there's a zabbix upload in the stable-new queue for > > trixie, which appears to have been prepared by you. > > > > It's quite a large update (a gzip of the debdiff is 8MB and the > > diffstat "1995 files changed, 519537 insertions(+), 268166 > > deletions(- > > )"), but I can't see a p-u bug or any other discussion about the > > upload. > > Discussion happened in [email protected] primarily with Moritz > Mühlenhoff. Agreement was to treat Zabbix akin to "firefox-esr" > with direct upload to stable/proposed-updates because "zabbix" > package follows upstream "LTS" releases that are reasonably > conservative in regards to changes. (Large diff is partially due > to non-code changes in templates, etc.)
I'm afraid that you've misunderstood Moritz's comment. It's his opinion of how the update should be handled, not an OK to upload to p-u. > "README.Debian.security" [1] was added to package and approved > by Moritz. > > Who else should normally acknowledge change in approach to stable > uploads? (Please forgive my lack of familiarity with process -- it > is my very first package to be treated with exception.) > That would be the Release Team. We'll often make that decision with input from the maintainer and the Security Team, but for updates via p- u it's ultimately our decision. > > The version of the package is higher than the package in unstable, > > which is incorrect. > > Sorry about that. It is due to my lack of familiarity with uploading > to stable (which I did not do in years). I assumed that "dch -- > stable" would handle version like "dch --bpo" does, but apparently > manual change from "+deb13u1" to "~deb13u1" is required... Duly > noted. In general, you're correct, but that assumes that the base for your upload is the version currently in stable, whereas your base was a newer upload to unstable. > If I have to upload Zabbix to "trixie" in the future, should I > open a bug report to seek your pre-approval? It may not have to be pre-approval, if we have agreed a process specific to zabbix, but there should be a release.debian.org p-u bug, yes. > Are "firefox-esr" uploads to "stable" accompanied by bug reports? > What is the normal/expected procedure and where it is documented? > firefox-esr isn't uploaded to stable. It's uploaded to stable-security and then automatically copied over to p-u by the archive software. The normal process for stable uploads is documented at https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions There are some exceptions to that process, but those have been agreed after discussion of things such as upstream release processes, testing, regression rates and a positive history of handling update to stable over a longer period of time. Regards, Adam
