On 8/8/06, <b class="gmail_sendername">Alex Efros</b> <<a href="mailto:powerman@...">powerman@...</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi!<br><br>On Mon, Aug 07, 2006 at 10:11:23PM +0200, Sune Kloppenborg Jeppesen wrote:<br>> - Unstable uses usually get the fix hours or even days before the GLSA is<br>> issued.<br><br>Why? I think security is important enough to force at least SOME admins to
<br>upgrade packet from current "stable, with security hole" to "unstable, without<br>security hole"... but for this admins must know about this security hole<br>as soon as fix for it become available, no matter in x86 or ~x86.
<br></blockquote></div><br>The maintainer provides a new ebuild, but (s)he is not allowed to stable of for any architecture, unless (s)he is a member of that architecture team. So often you have a fixed ebuild within the first day, but testing and stabling takes some time. (But sometime, you also have to wait weeks for a patch. But that is another story).
<br><br>If this is update is so important to admins, they are welcome to monitor our bugzilla activity to get 0-sec announcements of fixed ebuilds.<br>