Your message dated Mon, 7 Jul 2014 13:32:22 +0200
with message-id <[email protected]>
and subject line Re: Bug#754070: include urgency in DSAs
has caused the Debian Bug report #754070,
regarding include urgency in DSAs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
754070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754070
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: security.debian.org
severity: wishlist

Hi,

assuming not all DSAs are of urgency=high, I think it would be nice to include 
the urgency in the DSA text directly, so one can learn about the urgency 
before applying these updates. Does this seem like a reasonable idea?

Background: support contracts which allow immediate deployment of urgent + 
critical updates. With those it's very useful to know the urgency 
easily+early.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
--- Begin Message ---
Hi Salvatore,

On Montag, 7. Juli 2014, Salvatore Bonaccorso wrote:
> Do you mean the urgency=high in debian/changelog?

yes.
 
> Historically urgency=high should always be set in debian/changelog for
> security-uploads[1], and there should be no DSA with urgency not high
> (I know this is not the case). This had previously probably also some
> technical background on archive/buildd side, but has no "real" meaning
> for the update itself.

thanks. So I guess this is quite bogus and the bug should be closed (and those 
support contracts should be reworded...), doing so, thanks for your feedback!

Reopening is also easy if I got this wrong. (Or things have changed as the 
word "historically" might imply?)


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to