Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required

[Dmitry Bogatov <KAction@disroot.org>]

[2019-09-25 18:18] Ansgar <ansgar@43-1.org>
> Practically the project seems to have already
> decided that this is fine, even for packages that don't require
> systemd:
>
> +---
> | There are 1033 non-overridden instances of lintian detecting a
> | service unit without an init.d script [7].
> +---[ https://lists.debian.org/debian-devel-announce/2019/09/msg00001.html ]

I believe it partially my fault in this mis-representation.

Yes, problem exists (and it is severe), but not as severe like 1033 out
of 1300 daemons missing init.d scripts.

This lintian check have number of false-positives, like `foo@.service`
files triggering complains about missing `/etc/init.d/foo@` scripts, and
sometimes names plainly do not match (e.g bin:ifupdown).
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.