Bug#404739: Processed: reassign 404739 to gss

[Simon Josefsson]

Russ Allbery <address@hidden> writes:

> Simon Josefsson <address@hidden> writes:
>
>> Sounds good to me.  I'm still curious about urgency level semantics.  Do
>> you know when urgency=medium is applicable?  The links I found earlier
>> where not that informative, and mostly said that urgency=high is for
>> security bugs.
>
> It's basically the maintainer's tradeoff between the urgency of updating
> testing and the desire to make sure the package is thoroughly tested in
> unstable.  I usually use urgency=medium for serious bugs that don't risk
> compromise or data loss, or for major bugs with risky fixes that need to
> be tested in unstable for a while.
>
> Since this is a minimal change that fixes an arguably RC bug and adds
> support for a major platform, urgency of high or medium is probably
> appropriate here, but I'm not sure that it matters a great deal.

Makes sense, thanks for explaining.

What's the next step now, do we wait for 5 days and then ask on
debian-release to push it into testing?

/Simon