Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required
Dmitry Bogatov writes:
> This lintian check have number of false-positives, like `foo@.service`
> files triggering complains about missing `/etc/init.d/foo@` scripts,
That's not a false positive according to current policy. See also
#911165.
> and sometimes names plainly do not match (e.g bin:ifupdown).
Neither is this.
As I said before, the current requirements in policy aren't that
helpful.
Ansgar
Reply to: