Le 11/04/2023 à 23:52, Florian Schlichting a écrit :
[…]I think we should take a step back and think about how a freshly installed mpd package should look like. I think it may actually be a feature that the system mpd.service is not enabled and started on a fresh install. On most desktop/laptop machines, leaving the system service off and enabling the user service is probably the better thing to do. How long has dh-installsystemd been disregarding our unit files? We may want to add --no-enable when we apply that patch.So I think in the case of mpd, perhaps nothing is severely broken currently and this bug doesn't require fixing for bookworm. Instead, it can perhaps be downgraded and fixed with the next regular upload, after the release?
I agree, this is the best thing to do.The package is not broken enough to require a fix, it's actually not really broken it's only not enabling/starting system unit which, I believe, is not the main use of MPD anyway.
In the mean time, I saved the patch (putting the unit files where systemd.pc says) in a dedicated branch on salsa. It's also forwarded/merged upstream as documented in patch header.
If nobody step in, I'll downgrade #1034236 to important by the end of next week. Please go ahead if you feel we should hurry.
cheers k.
signature.asc
Description: PGP signature
