Bug#666726: debian-policy: Clarify if empty control fields are ollowed or not

[Bill Allombert <ballombe@debian.org>]

> From: Charles Plessy <plessy@debian.org>
> Date: Sat, 4 Aug 2012 11:16:50 +0900
> Subject: [PATCH] Disallow empty fields in control files, as apt and dak
>  reject them already.
> 
> Closes: 666726
> ---
>  policy.sgml |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/policy.sgml b/policy.sgml
> index 52dbb26..c59604e 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -2514,10 +2514,10 @@ endif
>  
>  	<p>
>  	  The field ends at the end of the line or at the end of the last
> -	  continuation line (see below).  Horizontal whitespace (spaces
> -	  and tabs) may occur immediately before or after the value and is
> -	  ignored there; it is conventional to put a single space after
> -	  the colon.  For example, a field might be:
> +	  continuation line (see below).  Its value must not be empty.
> +	  Horizontal whitespace (spaces and tabs) may occur immediately before
> +	  or after the value and is ignored there; it is conventional to put a
> +	  single space after the colon.  For example, a field might be:
>  	  <example compact="compact">
>  Package: libc6
>  	  </example>

As I understand, your patch change section 5.1 "Syntax of control files".
This is not correct since empty fields need to be allowed in section
5.2. Source package control files -- `debian/control'

So maybe this must be moved to section 5.3 
5.3. Binary package control files -- `DEBIAN/control'
(and maybe 5.4 and 5.5, I am not sure).

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here.