[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#412634: 5.6.17 (Urgency) should list emergency, maybe a normative list?



Russ Allbery <rra@debian.org> writes:

> Here is a proposed patch to put a normative list of supported Urgency
> values into Policy and to reconcile the two different informative lists
> currently there by removing the footnote in the changelog section and
> having that section simply defer to the Urgency control field definition
> as it does for other data that goes into control fields.
>
> The supported Urgency values are set by the dak configuration (and by
> the britney configuration), so they're not set in stone, but I think a
> normative list is a reasonable thing to put into Policy.  In practice,
> they're rather unlikely to change, and Debian maintainers need to know
> what the supported values are in order to create packages that dak will
> accept.

I haven't received any feedback on this patch, but I think it's obviously
correct.  I'm therefore committing it.  If anyone has any objections, say
so now.

> --- orig/policy.sgml
> +++ mod/policy.sgml
> @@ -1516,14 +1516,7 @@
>  	  <tt><var>keyword</var>=<var>value</var></tt> settings in the
>  	  <prgn>dpkg</prgn> changelog format (though there is
>  	  currently only one useful <var>keyword</var>,
> -	  <tt>urgency</tt>).<footnote>
> -	      Recognized urgency values are <tt>low</tt>,
> -	      <tt>medium</tt>, <tt>high</tt> and <tt>emergency</tt>.
> -	      They have an effect on how quickly a package will be
> -	      considered for inclusion into the <tt>testing</tt>
> -	      distribution, and give an indication of the importance
> -	      of any fixes included in this upload.
> -	  </footnote>
> +	  <tt>urgency</tt>).
>  	</p>
>  
>  	<p>
> @@ -2950,10 +2943,19 @@
>  	  <p>
>  	    This is a description of how important it is to upgrade to
>  	    this version from previous ones.  It consists of a single
> -	    keyword usually taking one of the values <tt>low</tt>,
> -	    <tt>medium</tt> or <tt>high</tt> (not case-sensitive)
> -	    followed by an optional commentary (separated by a space)
> -	    which is usually in parentheses.  For example:
> +	    keyword taking one of the values <tt>low</tt>,
> +	    <tt>medium</tt>, <tt>high</tt>, <tt>emergency</tt>, or
> +	    <tt>critical</tt><footnote>
> +	      Other urgency values are supported with configuration
> +	      changes in the archive software but are not used in Debian.
> +	      The urgency affects how quickly a package will be considered
> +	      for inclusion into the <tt>testing</tt> distribution and
> +	      gives an indication of the importance of any fixes included
> +	      in the upload.  <tt>Emergency</tt> and <tt>critical</tt> are
> +	      treated as synonymous.
> +            </footnote> (not case-sensitive) followed by an optional
> +	    commentary (separated by a space) which is usually in
> +	    parentheses.  For example:
>  
>  	    <example>
>    Urgency: low (HIGH for users of diversions)

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>




Reply to: