[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

Your message dated Tue, 21 Jan 2020 16:26:53 -0500
with message-id <CAOHcdNaWhGv=pHXuCikbKBOqLgOsvfMD09W0vmhaDyS3Rb8isw@mail.gmail.com>
and subject line Issue resolved in Policy
has caused the Debian Bug report #932704,
regarding debian-policy: Don't force sysvinit compatibility if e.g. alternate init required
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 owner@bugs.debian.org
immediately.)


-- 
932704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932704
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: debian-policy
Version: 4.4.0.1
Severity: normal

In section 9.11 (The Operating System/Alternate init systems), it is
stated that "...any package integrating with other init systems must
also be backwards-compatible with sysvinit by providing a SysV-style
init script...". There is a single exception for the alternate init
system implementation itself.

There are other exception conditions that we may want to consider
here. For instance, if a package has an explicit dependency on a
particular "alternate" init system, to, say, access the systemd D-Bus
interface, there is likely little value in providing sysv init
scripts.

I suggest that something like the following line be added to the end
of the second paragraph in that section:

"Also, SysV-style init scripts may be omitted for packages which have
an explicit dependency on an alternate init system."

-- 
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE

--- End Message ---
--- Begin Message --- 
The problem identified in the submission is resolved in Debian Policy
version 4.5.0.

--- End Message ---
Reply to: