Jellyfin-Server Debian package helper scripts assume systemd being used

[PoC-dev]

After upgrading jellyfin from the Debian repos on https://repo.jellyfin.org/debian yesterday, I found that the jellyfin servers weren't (re)started. I presume this is because the Debian scripts assume Systemd to be used.

/var/lib/dpkg/info/jellyfin-server.postinst:    systemctl --system daemon-reload >/dev/null || true
/var/lib/dpkg/info/jellyfin-server.postrm:  systemctl --system daemon-reload >/dev/null || true
/var/lib/dpkg/info/jellyfin-server.postrm:	systemctl --system daemon-reload >/dev/null || true
/var/lib/dpkg/info/jellyfin-server.preinst:  systemctl --system daemon-reload >/dev/null || true

Because output is redirected to /dev/null there is no indication of failure.

Correct solution would be to use service instead of a direct call to systemctl. The manpage states:

service runs a System V init script or systemd unit […]

Note: I've provided a SysV-rc script myself. Feel free to ask if interested for incorporation into the Debian package. I refrained from touching the scripts, because they'll be overwritten with the next update anyway.

[joshuaboniface]

As noted, we only support systemd right now. I'd have no issue changing this to use service if a suitable initscript is provided, though I'm also not convinced that this is worthwhile as recent Debian and Ubuntu releases all functionally depend on systemd and as per the latest Debian project vote on the issue ~2 years ago, package maintainers are no longer required to provide/support SysV initscripts (meaning, not that I refuse to, but that Debian 13+ are highly likely to stop shipping these for many packages, cementing a systemd-only distro).

[PoC-dev]

Thank you for your kind offer. Please see attached my initscript jellyfin-server.txt.

Note that I had to rename it to txt to overcome local browser restrictions only.

I don't want to engage a debate on principles regarding Systemd. Arguments have been exchanged plentiful in other discussions with other people.

Please also note that the Debian project faced an intense, heated discussion prior to adopting Systemd as default (non mandatory, non singular) startup manager. This resulted in forking to Devuan, the subsequent department of manpower from the Debian project, and the new package orphan-sysvinit-scripts in Debian. I believe this is proof enough there actually is demand for SysV-init support.

I know that maintainers aren't required to support anything else but Systemd nowadays, but it clearly doesn't hurt to do so, especially for simple "start a daemon" scenarios. Please just recognize that there is actual demand for SysV-init support. And as long as the effort to work with SysV-init is little, why not carry along? Please support the freedom of choice which once was a compelling argument in the Linux community.

Please be aware that my PoV is solely that of a server sysadmin. I don't care about GUI requirements and ultra fast startup. Overall simplicity and comprehensibility even when operating under unfortunate conditions are what count for me first and foremost. I did a test-upgrade of a template server VM to Deb13 some weeks ago, and there was no indication about things breaking, expectably. I admit, that wasn't a thorough test, this is scheduled for next year, before Deb12 switches to LTS.

Thank you!