Can i ask what is the policy for old bugs aganist release-notes? Currently the page has several that relate to bookworm (and some before): should anything relating to bookworm or earlier be closed? is it still desirable/possible to amend the bookworm release-notes?
these bugs look like valid things which could have been in bookworm release-notes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037144 - Please add bug #1037142 in the "5.4 Known severe bugs" section for bookworm the Debian - that bug is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037142 which is now closed - is some issue specific to a particular graphics card - if bookworm wasnt released it would be worth doing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038151 - document rename of the "ssh" group to "_ssh" in bookworm as people might have relied on 'ssh' eg with 'AllowGroups to "root ssh"' - if bookworm wasnt released it would be worth doing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037116 - says that debian-edu bookworm was not ready -- this is, i assume, valid, but anyone affected has presumably worked close? - if bookworm wasnt released it would be worth doing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037203 - aide is broken by the upgrade. The proposed text says what the workaround is - if bookworm wasnt released it would be worth doing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037430 - exim upgrade now fails if tainted data is used - if bookworm wasnt released it would be worth doing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055027 - links to https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/201 - if bookworm wasnt released it would be worth doing And these ones i think could be closed as "too late"/too minor/other reasons: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030119 is tagged trixie, but is about the annoying 'pam_env(sshd:session): deprecated reading of user environment enabled' messages which you get in bookworm. However the ssh maintainer has fixed this for trixie: no need to document that in trixie, so suggest closing this? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012174 -- is about mentioning https in apt lines: I think this is fixed, so close? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035065 - states that "the sssd cache becomes invalid on the upgrade to Bookworm due to a new format", - no new info provided on what this means since request in May 2023 - suggest closing as it doenst seem to have been an issue in practice and there is nothing actionable in it https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036876 - states that "debian was previously able to boot from lvm volume groups that were not complete while running in the initramfs and that bookworm will no longer support this" - porbably valid, but not a usual setup -- close? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037121 - The salt-stack was removed from bookworm. there is proposed text, and i assume valid, but im not sure it's high-profile enough to warrent inclusion now? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050833 - changes to network naming: it is not clear to me if this was actually a change in bookworm or an old change. i think this is the user not reading previous release-notes correctly - close? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070258 - user did not follow the instrcutions to remove non-debian software. close? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987068 - says cgroup2 support is incomplete for containers in bullseye. - no response from submitter since 2021. close? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987069 - another cgroup2-related thing from 2021. last message says it's too long for release-notes. close? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991809 - says new instalations of nis should follow a nis-howto document, but upgrades work - no response to "what do users upgrading need to know", seems out of scope for release-notes. close? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036907 - something to do with dash. unclear to me... doesnt seem to have been an issue. close? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927679 - is about docbook syntax. release-notes now use markdown. close? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930318 - unclear - i think they are suggesting to rename i386 to "PC". i dont think that is actually any clearer, "PC" would have made sense in the 1990s, but i dont think people really use it any more. close?
