Hi Santiago, On 26-09-2025 14:39, Santiago Vila wrote:
AFAIK, this was going to be RC for trixie, but in the last minute you requested to file remaining bugs as important, because there were more affected packages than expected and the release was close.
This issue is RC since since we announced it in [1] and I have seen multiple bug reports at severity serious. What we asked you to not do is to start a mass bug filing at severity serious so close to the trixie release for an issue we haven't done mass bug filing for before and for which at the time there was no practical impact on the reason why we made the issue RC. We were fearing too much maintainers would not understand that they shouldn't rush in a solution for that particular problem so close to the release if not bundled with other reasonable fixes. We see too often that people don't read or grasp the details and just trigger on RC bugs, even if the tagging says it doesn't need to be solved immediately in unstable.
For forky, I will try to report this category of bugs in a more consistent way (i.e. more often and not letting those issues to accumulate without reporting them).
Great, that way we avoid mass filings in the future.
If this is ok for you, I will proceed.
The devref recommends [2] to inform/discuss this on debian-devel@l.d.o. I recommend you follow the devref recommendation and state your intentions before doing such a new mass bug filing. I suggest to use some or all of the text from [1] in both the message to d-devel as well as in your bug reports; at the very least reference it. I'm slightly concerned about good communications here, because I believe this is delicate. For maintainers, the trivial way to avoid this RC issue is to no longer annotate Build-Depends with <!nocheck>, but we are also asking people to actively do that. Your mass bug filing should not lead to the wrong mindset.
Thank you for working on this. Paul [1] https://lists.debian.org/debian-devel-announce/2022/10/msg00004.html[2] https://www.debian.org/doc/manuals/developers-reference/beyond-pkging.html#reporting-lots-of-bugs-at-once-mass-bug-filing
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature