Bug#627490: debian-policy: Description field specification is ambiguous

2011-10-31 Thread Russ Allbery
Guillem Jover writes: > In any case I still think it might be a good idea to mention that the > two first line types must contain at least one non space character. > Compare it with the Changes, Files or Checksum field sections, where > that's explicitly mentioned. I've applied the following inf

Bug#627490: debian-policy: Description field specification is ambiguous

2011-05-21 Thread Guillem Jover
On Sat, 2011-05-21 at 10:53:13 +0200, Guillem Jover wrote: > dpkg errors out on empty lines inside a field value, but not blank > lines (those consisting only of spaces/tabs). Sorry, this was not clear. dpkg errors out when it expects only one stanza, otherwise an empty line (not a blank one) was

Bug#627490: debian-policy: Description field specification is ambiguous

2011-05-21 Thread Guillem Jover
On Sat, 2011-05-21 at 16:10:59 +0900, Charles Plessy wrote: > Le Sat, May 21, 2011 at 08:47:22AM +0200, Guillem Jover a écrit : > > > > The current specification for the Description field in §5.6.13 seems > > to be ambiguous regarding what can or cannot follow the initial > > characters. > > > >

Bug#627490: debian-policy: Description field specification is ambiguous

2011-05-21 Thread Charles Plessy
Le Sat, May 21, 2011 at 08:47:22AM +0200, Guillem Jover a écrit : > > The current specification for the Description field in §5.6.13 seems > to be ambiguous regarding what can or cannot follow the initial > characters. > > It specifies that a line can start with either “a single space” or > “two

Bug#627490: debian-policy: Description field specification is ambiguous

2011-05-20 Thread Guillem Jover
Package: debian-policy Version: 3.9.2.0 Severity: normal User: debian-pol...@packages.debian.org Usertag: issue Hi! The current specification for the Description field in §5.6.13 seems to be ambiguous regarding what can or cannot follow the initial characters. It specifies that a line can start