Hi,
There's very little I can do for Debian about this problem. Indeed,
upstream doesn't even support 3.10 to 3.13 upgrade, so upgrading
Bookworm to 3.13, or uploading 3.13 to bookworm-backports will not solve
the issue.
Heavy RabbitMQ users that cannot reset their /var/lib/rabbitmq/mnesia
database could maybe use upstream docker image to attempt a rolling
upgrade. Otherwise, users are advised to simply drain all queues and
make clients point to a new cluster if that's possible. This really
depends a lot on the application, and it's hard to describe a solution
that would work for everyone.
Please note that there's already some release notes about this:
https://salsa.debian.org/ddp-team/release-notes/-/commit/d1185415d5fb044c7802410bf9c7ef8d751ba7f1
that are pointing to this bug. I would therefore, advise anyone to
document workaround in this bug entry.
I'm then lowering this bug severity to important, knowing that I
probably wont be able to fix it.
Cheers,
Thomas Goirand (zigo)
