Greetings.
I'll to try to incorporate the upstream .service file if possible.b
The issue I keep running into with .service files with mumble-server is
that I'm not able to get the daemon to start with systemd with most of
the .service files I've seen and tried for it so far. Had worked out a
working
.service file for mumble-server many moons ago as part of another bug
report, but I haven't been able to find that work I did again in order to
incorporate that.
Lack of being able to work out a working .service file is also what has
led to delay in releasing Mumble 1.5.517 which I've had a package mostly
ready for release since February. :-(
Thanks for finding the upstream mumble 1.3.4 service file, I hope that
will work in the test VM I have for it.
-- Chris
On 11/12/23 07:59, Chris Hofstaedtler wrote:
Control: reassign -1 mumble-server
Hi,
* [email protected] <[email protected]>:
Package: mumble
Severity: important
Usertags: missing-systemd-service
[..]
mumble has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because a transitional
sysv-init-to-unit generator was shipped by systemd. This is in the
process of being deprecated and will be removed by the time Trixie
ships, so the remaining packages that ship init scripts without
systemd units will stop working.
Upstream actually includes a .service file in the source tree, as
can be seen here:
https://sources.debian.org/src/mumble/1.3.4-4/scripts/murmur.service/
It seems like installing it with a small patch for the Debian path
derivation should hopefully do the job.
Best,
Chris
