I found a few things surprising about this bug too, but this might be due to my own ignorance about how these processes work:
- I was expecting the package to either be revoked, or to have a new `6.1.64-2` version being published with the previously good known state.
Maybe it wasn't done because it was not possible (mirrors being write-only, and maybe other complications in publishing a 6.1.64-2).
- I was expecting some guidelines to be published for affected machines. I've seen questions being asked [1], but no answers to them yet (so users are not sure if it would be safe to rollback to the previous kernel version (6.1.55-1) or not).
Maybe it's because the problem is not well understood yet, or maybe there are not enough people available to answer such questions on a weekend?
If someone can provide some context about "how these things work", it would be interesting to learn more about this.
[^1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843#33
- I was expecting the package to either be revoked, or to have a new `6.1.64-2` version being published with the previously good known state.
Maybe it wasn't done because it was not possible (mirrors being write-only, and maybe other complications in publishing a 6.1.64-2).
- I was expecting some guidelines to be published for affected machines. I've seen questions being asked [1], but no answers to them yet (so users are not sure if it would be safe to rollback to the previous kernel version (6.1.55-1) or not).
Maybe it's because the problem is not well understood yet, or maybe there are not enough people available to answer such questions on a weekend?
If someone can provide some context about "how these things work", it would be interesting to learn more about this.
[^1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843#33