Your message dated Tue, 24 Mar 2020 13:41:44 +0000 with message-id <0473ec0e-2b45-4944-a1ea-1803fceb8f02@sloti26t01> and subject line Re: lintian: probably shouldn't emit package-supports-alternative-init-but-no-init.d-script for instanced systemd services (foo@.service) has caused the Debian Bug report #934805, regarding lintian: probably shouldn't emit package-supports-alternative-init-but-no-init.d-script for instanced systemd services (foo@.service) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 934805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: lintian Version: 2.18.0 Severity: minor Some packages contain "instanced" systemd units named like foo@.service, which represent a family of possible systemd units foo@bar.service for arbitrary values of bar. For example, quake2-server in contrib is one of these: you can run any number of servers on different ports by creating more than one configuration file and enabling multiple instances of the unit. This is not a feature that exists in LSB init scripts, so I don't think maintainers can be expected to provide it. I can see two possible improvements here: - do not emit package-supports-alternative-init-but-no-init.d-script for foo@.service at all, on the basis that the feature does not exist in LSB init, so feature parity is not implementable - do not emit package-supports-alternative-init-but-no-init.d-script for foo@.service if /etc/init.d/foo exists, on the assumption that /etc/init.d/foo is equivalent to one of the instances of foo@.service If a package contains /etc/init.d/foo and foo@.service, then it should likely also either contain foo.service (e.g. quake2-server follows this pattern), or "mask" foo.service by making it a symlink to /dev/null to avoid both /etc/init.d/foo and instances of foo@.service being invoked under systemd. Thanks, smcv
--- End Message ---
--- Begin Message ---Version: 2.25.0 Hi, > lintian: probably shouldn't emit package-supports-alternative-init- > but-no-init.d-script for instanced systemd services (foo@.service) I believe this was fixed in: https://salsa.debian.org/lintian/lintian/commit/705488630772c04fa8c474fd01791b0ef5edd516 Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
--- End Message ---
