Bug#944330: debian-policy: Hyphenation damage on plain text output

2019-11-07 Thread Russ Allbery
Guillem Jover writes: > The rendering to plain text contain many technical terms, program names, > email addresses, make rule names, etc., that have been cut at their > hypen at the end of line. This makes copy&paste more difficult, and it > reads confusingly. > I started collecting a list of th

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#944331: debian-policy: Spurious space after dash in plain text output

2019-11-07 Thread Guillem Jover
Package: debian-policy Version: 4.4.1 Severity: minor Hi! Noticed the following instances of spurious spaces after a dash, while skimming over the plain text policy document: - index, rendered as: ,--- * 7.8. Additional source packages used to build the binary - "Built- Using"

Bug#944332: debian-policy: Broken markup in policy source

2019-11-07 Thread Guillem Jover
Source: debian-policy Source-Version: 4.4.1.1 Severity: normal Hi! Found this markup issue while going over the policy: - chapter 4, footnote [6], rendered as: ,--- listed in the :ref:"`Maintainer" <#s-f-Maintainer` or "`Uploaders" ` control fields of the package), the first line

Bug#944330: debian-policy: Hyphenation damage on plain text output

2019-11-07 Thread Guillem Jover
Package: debian-policy Version: 4.4.1 Severity: minor Hi! The rendering to plain text contain many technical terms, program names, email addresses, make rule names, etc., that have been cut at their hypen at the end of line. This makes copy&paste more difficult, and it reads confusingly. I start

Bug#944329: debian-policy: Unclear text about password files modifications

2019-11-07 Thread Guillem Jover
Package: debian-policy Version: 4.4.1 Severity: normal Hi! There's this text in section §9.2.1: ,--- Packages other than "base-passwd" must not modify "/etc/passwd", "/etc/shadow", "/etc/group" or "/etc/gshadow". `--- It's not clear to me, whether this refers to the packaging or any pro

Bug#944325: please fix this unclear and obtuse phrasing in §7.8 (suggestion provided)

2019-11-07 Thread Nicholas D Steeves
Package: debian-policy Version: 4.4.1.1 Severity: normal The full sentence in question is "This field should not be added solely for purposes other than satisfying license or DFSG requirements to provide full source code". "solely for purposes other than satisfying" is the problematic constructio

Bug#944296: debian-policy: Source provenance requirement is WET

2019-11-07 Thread Guillem Jover
On Thu, 2019-11-07 at 09:00:29 -0800, Russ Allbery wrote: > Guillem Jover writes: > > This means that when using a debian/watch file one has to duplicate > > the information in two places, with the possibility of this getting > > out-of-sync, etc. > > > In addition the machine readable debian/cop

Bug#944296: debian-policy: Source provenance requirement is WET

2019-11-07 Thread Russ Allbery
Guillem Jover writes: > This means that when using a debian/watch file one has to duplicate > the information in two places, with the possibility of this getting > out-of-sync, etc. > In addition the machine readable debian/copyright format, specifies > the Source field as optional, which could

Bug#944296: debian-policy: Source provenance requirement is WET

2019-11-07 Thread Guillem Jover
Package: debian-policy Version: 4.4.1.1 Severity: wishlist Hi! We currently require (with a must) in section §12.5, to add to the debian/copyright, where the upstream source was obtained from: ,--- In addition, the copyright file must say where the upstream sources (if any) were obtained,