Just for the record - a fix has been bin-NMU'ed but is not available for
automatic upgrade yet. See the URL in the attachment.
--
Marcin Owsiany <[EMAIL PROTECTED]> http://marcin.owsiany.pl/
GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216
--- Begin Message ---
On Mon, Jul 02, 2007 at 07:27:13PM +0200, Moritz Muehlenhoff wrote:
> Marcin Owsiany wrote:
> > > Why I haven't realized you're talking about my package up till now is a
> > > mystery to me. I'll check this ASAP.
> >
> > Indeed, it looks like I used wrong pbuilder tarball to build this one
> > :-(
> >
> > Security team: this just needs a rebuild, but how exactly should I fix
> > this? Can I do a bin-nmu so that other architectures don't need a
> > rebuild? Or should I just prepare 1:1.7~rc2-1etch2 as a new revision and
> > upload that?
>
> A binNMU has been done, a package is available at
> http://debian.netcologne.de/debian/pool/main/e/ekg/ekg_1.7~rc2-1etch1+b1_i386.deb
>
> It will also be part of the immediate stable point update.
As far as I can see, it has not been uploaded to etch-security, which
means it will only become available after the next point release. Can we
do anything to speed this up?
--
Marcin Owsiany <[EMAIL PROTECTED]> http://marcin.owsiany.pl/
GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216
signature.asc
Description: Digital signature
--- End Message ---
