Bug#941198: initscripts: packages should ship systemd units

2019-11-07 Thread Ansgar
Russ Allbery writes: > --- a/policy/ch-opersys.rst > +++ b/policy/ch-opersys.rst > @@ -388,11 +388,14 @@ argument ``stop``. > Writing the scripts > ~~~ > > -Packages that include daemons for system services should place scripts > -in ``/etc/init.d`` to start or stop services at

Bug#941198: initscripts: packages should ship systemd units

2019-11-06 Thread Sean Whitton
Hello, On Sun 03 Nov 2019 at 01:04PM -08, Russ Allbery wrote: > --- a/policy/ch-opersys.rst > +++ b/policy/ch-opersys.rst > @@ -388,11 +388,14 @@ argument ``stop``. > Writing the scripts > ~~~ > > -Packages that include daemons for system services should place scripts > -in

Bug#941198: initscripts: packages should ship systemd units

2019-11-04 Thread Holger Levsen
On Fri, Nov 01, 2019 at 11:20:59AM -0700, Russ Allbery wrote: > > I think there is already a lintian warning: > > > > https://lintian.debian.org/tags/missing-systemd-service-for-init.d-script.html > Oh! I should have checked rather than assuming. It would ideally be nice > to make it a

Bug#941198: initscripts: packages should ship systemd units

2019-11-03 Thread Russ Allbery
Ansgar writes: > Sean Whitton writes: >>> +Packages that include system services should include ``systemd`` units >>> +to start or stop services. >>> + >>> Packages that include daemons for system services should place scripts >>> in ``/etc/init.d`` to start or stop services at boot time or

Bug#941198: initscripts: packages should ship systemd units

2019-11-01 Thread Russ Allbery
Ansgar writes: > Russ Allbery writes: >> Ansgar writes: >> I think we can proceed to add a Policy "should" for including a systemd >> unit file unless someone raises objections pretty soon here. So far, I >> haven't seen any objections to the basic idea. > Okay. Anything further I should do

Bug#941198: initscripts: packages should ship systemd units

2019-11-01 Thread Ansgar
Russ Allbery writes: > Ansgar writes: >> How to proceed with this? Do you still require any wording changes? > > I think we can proceed to add a Policy "should" for including a systemd > unit file unless someone raises objections pretty soon here. So far, I > haven't seen any objections to the

Bug#941198: initscripts: packages should ship systemd units

2019-11-01 Thread Russ Allbery
Ansgar writes: > How to proceed with this? Do you still require any wording changes? I think we can proceed to add a Policy "should" for including a systemd unit file unless someone raises objections pretty soon here. So far, I haven't seen any objections to the basic idea. > Or should we

Bug#941198: initscripts: packages should ship systemd units

2019-11-01 Thread Simon McVittie
On Fri, 01 Nov 2019 at 12:21:43 +0100, Ansgar wrote: > Dmitry Bogatov writes: > > Does it mean that lack of systemd unit file is RC-critical bug? Or I > > will be able to waive it with "you are welcome to contribute a patch" > > response? I think in general the answer is that it should be a

Bug#941198: initscripts: packages should ship systemd units

2019-11-01 Thread Ansgar
Dmitry Bogatov writes: > [2019-09-28 18:02] Russ Allbery >> I agree. This seems entirely reasonable to me. Both the behavior and the >> inherent documentation are better with unit files, and systemd is the >> default init system so that's an advantage for a lot of our users. >> >> That said, if

Bug#941198: initscripts: packages should ship systemd units

2019-10-01 Thread Russ Allbery
Dmitry Bogatov writes: > Does it mean that lack of systemd unit file is RC-critical bug? No, it would be a should. So just a regular bug. -- Russ Allbery (r...@debian.org)

Bug#941198: initscripts: packages should ship systemd units

2019-10-01 Thread Dmitry Bogatov
[2019-09-28 18:02] Russ Allbery > Sean Whitton writes: > > > I don't currently have any reason to doubt we have a project consensus > > that systemd unit files should be included in packages in addition to > > sysvinit scripts, so I hope we can make this change. > > I agree. This seems

Bug#941198: initscripts: packages should ship systemd units

2019-09-30 Thread Bill Allombert
On Sun, Sep 29, 2019 at 03:19:43PM +0100, Josh Triplett wrote: > On Sun, 29 Sep 2019 12:03:11 +0200 Bill Allombert wrote: > > On Sat, Sep 28, 2019 at 06:02:52PM -0700, Russ Allbery wrote: > > > Sean Whitton writes: > > > > > > > I don't currently have any reason to doubt we have a project

Bug#941198: initscripts: packages should ship systemd units

2019-09-29 Thread Russ Allbery
Bill Allombert writes: > On Sat, Sep 28, 2019 at 06:02:52PM -0700, Russ Allbery wrote: >> I agree. This seems entirely reasonable to me. Both the behavior and >> the inherent documentation are better with unit files, and systemd is >> the default init system so that's an advantage for a lot of

Bug#941198: initscripts: packages should ship systemd units

2019-09-29 Thread Josh Triplett
On Sun, 29 Sep 2019 12:03:11 +0200 Bill Allombert wrote: > On Sat, Sep 28, 2019 at 06:02:52PM -0700, Russ Allbery wrote: > > Sean Whitton writes: > > > > > I don't currently have any reason to doubt we have a project consensus > > > that systemd unit files should be included in packages in

Bug#941198: initscripts: packages should ship systemd units

2019-09-29 Thread Bill Allombert
On Sat, Sep 28, 2019 at 06:02:52PM -0700, Russ Allbery wrote: > Sean Whitton writes: > > > I don't currently have any reason to doubt we have a project consensus > > that systemd unit files should be included in packages in addition to > > sysvinit scripts, so I hope we can make this change. >

Bug#941198: initscripts: packages should ship systemd units

2019-09-28 Thread Russ Allbery
Sean Whitton writes: > I don't currently have any reason to doubt we have a project consensus > that systemd unit files should be included in packages in addition to > sysvinit scripts, so I hope we can make this change. I agree. This seems entirely reasonable to me. Both the behavior and the

Bug#941198: initscripts: packages should ship systemd units

2019-09-28 Thread Sean Whitton
Hello, On Fri 27 Sep 2019 at 09:26AM +02, Ansgar wrote: > Sean Whitton writes: >>> +Packages that include system services should include ``systemd`` units >>> +to start or stop services. >>> + >>> Packages that include daemons for system services should place scripts >>> in ``/etc/init.d`` to

Bug#941198: initscripts: packages should ship systemd units

2019-09-27 Thread Ansgar
Sean Whitton writes: >> +Packages that include system services should include ``systemd`` units >> +to start or stop services. >> + >> Packages that include daemons for system services should place scripts >> in ``/etc/init.d`` to start or stop services at boot time or during a >> change of

Bug#941198: initscripts: packages should ship systemd units

2019-09-26 Thread Sean Whitton
Hello, On Thu 26 Sep 2019 at 09:59AM +02, Ansgar wrote: > Package: debian-policy > Version: 4.4.0.1 > Severity: normal > > Packages should ship systemd units as this provides a better > experience to users. (In particular the systemd-sysv-generator has to > make some assumptions that are not

Bug#941198: initscripts: packages should ship systemd units

2019-09-26 Thread Ansgar
Package: debian-policy Version: 4.4.0.1 Severity: normal Packages should ship systemd units as this provides a better experience to users. (In particular the systemd-sysv-generator has to make some assumptions that are not always correct; it is better to explicitly tell systemd what to do.)