Bug#1068504: mumble-server: wrong path for systemd-sysusers file

[Chris Hofstaedtler]

Hi,

On Thu, Jan 09, 2025 at 06:42:00PM -0500, Chris Knadle wrote:
> On 1/9/25 12:55, Michael Biebl wrote:
> > Am 08.01.25 um 19:44 schrieb Chris Knadle:
> > > Hello, Michael.
> > > 
> > > I'm emailing again because I've tried again to follow the
> > > suggestions that were made for this bug, and it is not working.
> > > 
> > > On 11/22/24 06:09, Michael Biebl wrote:
> > > > Again, I don't understand why you try to fiddle with
> > > > debian/rules and variables in .install files (don't do that)
> > > The directive here is to avoid using variables in the .install file.
> > > > You install systemd-dev (including systemd.pc), the build system
> > > > picks up the paths from systemd.pc via pkgconf and installs the
> > > > files into the correct paths. All you need to do in .install is
> > > > reference the now correct paths.
> > > 
> > > Then the directive here is to reference a "correct path" in the
> > > .install file, which presumably is in a variable. (?) Or, whatever
> > > the "correct path" is meant to mean, I don't know what that is and
> > > cannot interpret it.
> > 
> > No, all you are supposed to do in your .install files is to use the
> > correct paths
> 
> There's several ways to do things in .install files, I don't think "supposed
> to" fits here. It seems like you're expecting this issue to be handled a
> certain way and for someone else to do what you expect.

Yes, we expect Debian package maintainers to implement the simple thing.
For a limited while, for a limited subset of packages, we expected
them to do something more complicated, and when that applied, we
sent patches. However this time is over, and packages should do the
simple thing of directly using the path *in* /usr.

> > /usr/lib/systemd/system/foo.service
> > /usr/lib/sysusers.d/foo.conf
> > /usr/lib/tmpfile.d/foo.conf
> 
> I tried this after adding systemd-dev as a build dependency none of that
> works.

This is where Michael pointed out that the upstream build system is
buggy.

Using pkg-config to read the correct values from systemd.pc is well
in the upstream domain, and the ecosystem expects that upstream
maintainers can do that. Worst case, upstream can copy the runes
from one of the thousands of other projects using the same build
system.

mumble is probably the last package that can't figure this out one
way or another, and it's getting a bit tiring. Especially when
people are trying to help, but clearly the messages don't come
across.

Best,
Chris