Bug#880992: debian-policy should not recommend running editor using absolute path

2017-11-08 Thread Sean Whitton
Hello Jonathan, On Wed, Nov 08 2017, Jonathan Nieder wrote: > I understand and agree, but that doesn't mean that packages should > invoke editor using an absolute path. > > Policy describes package behavior, not user behavior. Right. In this case, though, it describes package behaviour meant to

Bug#880920: Document Rules-Requires-Root field

2017-11-08 Thread Sean Whitton
Hello Ian, On Wed, Nov 08 2017, Ian Jackson wrote: > Sean Whitton writes ("Bug#880920: Document Rules-Requires-Root >field"): >> I wonder if we should just make Policy the new home of the spec that >> Niels and Guillem have already written? > > I certainly would rather not block incorporation of

Bug#880992: debian-policy should not recommend running editor using absolute path

2017-11-08 Thread Bill Allombert
On Wed, Nov 08, 2017 at 12:31:09PM -0800, Jonathan Nieder wrote: > Hi, > > Sean Whitton wrote: > > On Mon, Nov 06 2017, Jonathan Nieder wrote: > > >>Thus, every program that launches an editor or pager must use > >>the EDITOR or PAGER environment variable to determine the editor > >>o

Bug#880992: debian-policy should not recommend running editor using absolute path

2017-11-08 Thread Jonathan Nieder
Hi, Sean Whitton wrote: > On Mon, Nov 06 2017, Jonathan Nieder wrote: >> Thus, every program that launches an editor or pager must use >> the EDITOR or PAGER environment variable to determine the editor >> or pager the user wishes to use. If these variables are not set, >> the

Bug#881166: log files, postrotate example: start-stop-daemon or invoke-rc.d?

2017-11-08 Thread Russ Allbery
Daniel Pocock writes: > In the section on log files[1], the example uses start-stop-daemon: > postrotate > start-stop-daemon -K -p /var/run/foo.pid -s HUP -x /usr/sbin/foo -q > endscript > while elsewhere in the policy manual it is suggested to use invoke-rc.d > Inspecting my own system, I

Bug#880920: Document Rules-Requires-Root field

2017-11-08 Thread Russ Allbery
Ian Jackson writes: > Sean Whitton writes ("Bug#880920: Document Rules-Requires-Root field"): >> I wonder if we should just make Policy the new home of the spec that >> Niels and Guillem have already written? > I certainly would rather not block incorporation of this new spec into > Debian's off

Re: Bug#881166: log files, postrotate example: start-stop-daemon or invoke-rc.d?

2017-11-08 Thread Simon McVittie
On Wed, 08 Nov 2017 at 13:50:31 +0100, Daniel Pocock wrote: > Imagine the following scenario: > > - a package distributes an init script that runs the process with a PID file > > - later on, the package maintainer starts distributing a systemd unit > file as well, running the process in foregroun

Bug#880920: Document Rules-Requires-Root field

2017-11-08 Thread Ian Jackson
Sean Whitton writes ("Bug#880920: Document Rules-Requires-Root field"): > I wonder if we should just make Policy the new home of the spec that > Niels and Guillem have already written? I certainly would rather not block incorporation of this new spec into Debian's official document set, on the tas

Bug#881166: log files, postrotate example: start-stop-daemon or invoke-rc.d?

2017-11-08 Thread Daniel Pocock
Package: debian-policy Version: 4.1.1.1 In the section on log files[1], the example uses start-stop-daemon: postrotate start-stop-daemon -K -p /var/run/foo.pid -s HUP -x /usr/sbin/foo -q endscript while elsewhere in the policy manual it is suggested to use invoke-rc.d Inspecting my own syst