Bug#601455: Steps towards a patch to document disabling a daemon upon installation

2017-12-26 Thread Andreas Henriksson
Hi, On Mon, Dec 25, 2017 at 06:27:21PM -0800, Russ Allbery wrote: > Ian Jackson writes: > > Sean Whitton writes: > > >> 2. Do we need to include any text saying *why* the /etc/default practice > >>is a bad idea? I couldn't come up with a succinct way to state it. > >>In general, I think

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

2017-12-26 Thread Debian Bug Tracking System
Processing control commands: > tags -1 = pending Bug #880992 [debian-policy] debian-policy should not recommend running editor using absolute path Added tag(s) pending; removed tag(s) patch. -- 880992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880992 Debian Bug Tracking System Contact o

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

2017-12-26 Thread Russ Allbery
Control: tags -1 = pending Sean Whitton writes: > On Mon, Dec 25 2017, Russ Allbery wrote: >>> not set, the commands "editor" and "pager" should be used, >>> respectively. These commands can be invoked explicitly (e.g. as >>> /usr/bin/editor), or through a $PATH search (e.g. as edit

Bug#682347: mark 'editor' virtual package name as obsolete

2017-12-26 Thread Holger Levsen
On Mon, Dec 25, 2017 at 05:02:01PM -0800, Russ Allbery wrote: > I think there are three options, and I'd love to get feedback on which of > those three options we should take. > > 1. Status quo: there is an undocumented editor virtual package, Policy >says that nothing has to provide or depend

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

2017-12-26 Thread Sean Whitton
Hello, On Mon, Dec 25 2017, Russ Allbery wrote: >> not set, the commands "editor" and "pager" should be used, >> respectively. These commands can be invoked explicitly (e.g. as >> /usr/bin/editor), or through a $PATH search (e.g. as editor). > >> ? > > This wording seems fine to m

Bug#876075: Anchors are non-unique in the single-HTML version

2017-12-26 Thread Sean Whitton
Hello, On Mon, Dec 25 2017, Russ Allbery wrote: > I'm not sure where we landed with this, but it feels like the > single-HTML output from Sphnix is kind of broken, and publishing that > on the web site has caused various problems. I'm not sure how to get > to the multi-page version on www.debian

Bug#688251: #688251: Built-Using description too aggressive

2017-12-26 Thread Sean Whitton
Hello, On Mon, Dec 25 2017, Russ Allbery wrote: > Seconded the above change and with or without the wording change > discussed in the other part of this thread. Thank you for your review. Here is the current diff awaiting a final second: diff --git a/policy/ch-relationships.rst b/policy/ch-rel

Bug#885219: /lib64 provision added in 9.1.1 prohibits multilib libc

2017-12-26 Thread Sean Whitton
Hello, On Mon, Dec 25 2017, Russ Allbery wrote: > commit e0759206c2960f3fd6427583f10c4f87b39b152e (HEAD -> > bug885219-rra) Author: Russ Allbery Date: Mon Dec 25 > 18:06:25 2017 > > Allow libc to install files in /lib64 > > diff --git a/policy/ch-opersys.rst b/policy/ch-opersys.rst index > 7

Bug#682347: mark 'editor' virtual package name as obsolete

2017-12-26 Thread Christoph Berg
Re: Russ Allbery 2017-12-26 <87wp1as3na@hope.eyrie.org> > 1. Status quo: there is an undocumented editor virtual package, Policy >says that nothing has to provide or depend on it, and some random >collection of editors provide it. I think this is a bad place to be, >so I would hope