Paul Gevers
2025-04-05 06:50:01 UTC
Reply
PermalinkDuring the preparation phase of bookworm, I was running an awareness
campagne on RC bugs [1] in package in the key package set [2]. As those
packages are exempted from being auto-removed, their RC bugs are
ironically less exposed. Ideally we should get the number of RC bugs in
trixie down to zero.
We're now in the middle of the first freeze. Currently we have 183 RC
bugs in key packages affecting trixie of which 133 are unresolved in
unstable or experimental, aren't pending and don't have a patch. Here
are 5 RC bugs in key packages to draw attention to this class of bugs.
Remember, resolving these bugs is a collective effort.
#994274 syslinux
FTBFS with gnu-efi 3.0.13
https://bugs.debian.org/994274
#1064712 node-public-encrypt
FTBFS: TypeError: RSA_PKCS1_PADDING is no longer supported for private
decryption, this can be reverted with --security-revert=CVE-2023-46809
https://bugs.debian.org/1064712
#1065666 mesa
Upgrading to mesa from testing breaks compiz
https://bugs.debian.org/1065666
#1069553 xsd
FTBFS on armel: dh_auto_test: error: make -j4 test returned exit code 2
https://bugs.debian.org/1069553
#1071316 infinipath-psm
FTBFS: ips_proto_dump.c:142:15: error: static declaration of
âÂÂstrlcatâ follows non-static declaration
https://bugs.debian.org/1069553
I am asking for help with investigating RC bug reports, judging
severity, reproducing the issue, clarifying the problem, i.e. bug
triaging of all RC bugs that haven't seen activity for a while and that
are still affecting trixie. Of course ideally the bug gets fixed.
Remember, if you really think a bug shouldn't be RC (particularly if you
are the maintainer), downgrade it with an explanation. If in doubt,
leave your note in the bug report, that's already a great help.
Paul
[1] https://udd.debian.org/dev/cgi-bin/rcblog7.cgi
[2] https://release.debian.org/key-packages.html