user debian-pol...@packages.debian.org usertags 666726 normative proposal thanks
Le Wed, Jun 20, 2012 at 12:10:35PM +0200, Ansgar Burchardt a écrit : > > I agree this could be clarified in policy. In pratice we already > disallow empty package relations (besides apt choking on them there is > also an explicit check in dak for this). Hello everybody, In summary, checkinstall has been corrected, apt and dak refuse packages with empty control fields, and I think that dpkg's tolerance is not a problem as local packages do not need to follow the Policy, and Debian's package go through dak and therefore do not have empty control fields. How about the attached patch, that adds "Its value must not be empty." after "The field ends at the end of the line or at the end of the last continuation line". -- Charles Plessy Tsurumi, Kanagawa, Japan
>From 3a686f7d4f15604df43fc806df97fd4ddaa92b9f Mon Sep 17 00:00:00 2001 From: Charles Plessy <ple...@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> -- 1.7.10
