On Wed, Sep 22, 2010 at 12:59:02AM +0300, Jonathan Nieder wrote:
> Hi,
> 
> The Anarcat wrote:
> 
> > Seems to me this is a regression from the last security upgrade.
> [...]
> > What am I missing here?
> 
> Rather than a security advisory, it's from a stable point release,
> unfortunately.

I understand that, but how does that keep us from issuing another
update on security.debian.org?

> volatile and s-p-u are the only ways I know of to quickly address
> errata like this.

People running stable are not necessarily running volatile and s-p-u. I
don't object to uploading to s-p-u at first, but keeping there seems
non-sensical: Debian, that stable distribution we all hold so dear has
now a broken git package that cannot do *anything* anymore. I find that
is a shame and should be fixed ASAP.

volatile, proposed-updates and backports are not enough.

A.

-- 
Antoine Beaupré
Réseau Koumbit Networks
+1.514.387.6262

Attachment: signature.asc
Description: Digital signature

Reply via email to