The reason for this, is an issue with `rabbitmq-server`. The shipped configuration lacks some entries pointing to the plugin install dir, or the install dir doesn't exist. To reproduce: ```shell $ docker run -ti debian:trixie bash $ apt update ; apt install -y rabbitmq-server $ rabbitmq-plugins enable rabbitmq_stomp ``` The last command is what `koha-common.postinst` runs then the `koha-common` package is installed/upgraded. Hence the failure This is a `trixie` bug to keep an eye on.
Also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100165
*** This bug has been marked as a duplicate of bug 39314 ***
This isn't an upgrade from D12 (Rabbit 3.10) to D13 (Rabbit 4.0) so it shouldn't be a dupe of bug 39314. (In reply to Jonathan Druart from bug 39314 comment #7) > Is this still valid? > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104149#10 > "I wasn't able to reproduce, so probably it does work now?" So maybe Debian ticket 1104149 isn't related to the upgrade (reported didn't gave enough info) now that I see Tomas got the issue without upgrading. And maybe it's somehow solved 🤞
reported => the reporter The previous message is confusing: It seems I hit this issue. And when I wanted to reproduce I got bug 39314. The two tickets in koha seems like different things like the two tickets in Debian tracker seems different things. Because the reporter on Debian's 1104149 didn't mention an upgrade. And because Tomas here didn't got the issue via upgrading.