Bug 39868 - koha-common fails to install on trixie
Summary: koha-common fails to install on trixie
Status: RESOLVED DUPLICATE of bug 39314
Alias: None
Product: Koha
Classification: Unclassified
Component: Packaging (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL: https://bugs.debian.org/cgi-bin/bugre...
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-09 13:13 UTC by Tomás Cohen Arazi (tcohen)
Modified: 2025-12-15 00:49 UTC (History)
4 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomás Cohen Arazi (tcohen) 2025-05-09 13:13:25 UTC
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.
Comment 1 Jonathan Druart 2025-05-12 07:34:40 UTC
Also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100165
Comment 2 Jonathan Druart 2025-05-12 07:35:34 UTC

*** This bug has been marked as a duplicate of bug 39314 ***
Comment 3 Victor Grousset/tuxayo 2025-12-12 00:40:26 UTC
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 🤞
Comment 4 Victor Grousset/tuxayo 2025-12-15 00:49:55 UTC
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.