MBF: packages shipping init scripts without corresponding systemd units

[Luca Boccassi]

Hi,

According to Lintian there are 314 packages shipping init scripts
without a corresponding systemd unit:

https://lintian.debian.org/tags/missing-systemd-service-for-init.d-script

They currently work because there is still a transitional unit
generator that creates a unit on-the-fly on boot. This was always
intended as a temporary stop-gap, and is technically vastly inferior to
a native unit, as for example it cannot tell the difference between a
one-shot and a long-running service, and cannot enable any hardening or
sandboxing options.

Now the generator is also on the way to be deprecated and removed. It's
been there for a decade, which is enough time to complete the
transition, and will likely be removed before Trixie ships.

Therefore I filed a bug against all affected packages, provided a patch
for policy:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039102

and a patch for Lintian to bump the severity from warning to error:

https://salsa.debian.org/lintian/lintian/-/merge_requests/407

It's possible that there will be a good chunk of false positives, as
often new units added don't have a name that matches exactly the old
init script name, in which case it's fine to add an override and close
the bug.

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20230625/68598002/attachment.sig>