Re: report on current state of sarge security

To: debian-release@lists.debian.org, secure-testing-team@lists.alioth.debian.org
Subject: Re: report on current state of sarge security
From: Martin Schulze <joey@infodrom.org>
Date: Sat, 27 Nov 2004 11:33:41 +0100
Message-id: <[🔎] 20041127103341.GX7329@finlandia.infodrom.north.de>
In-reply-to: <[🔎] 20041127100821.GG25412@mauritius.dodds.net>
References: <[🔎] 20041123201517.GA21860@kitenet.net> <[🔎] 20041127100821.GG25412@mauritius.dodds.net>

Steve Langasek wrote:
> > perl 5.8.4-4 needed, have 5.8.4-3 for CAN-2004-0976
> > 	FTBFS on mipsel due to test suite failures.
> > 	Note that this happened for -3 also, and yet it somehow got built
> > 	and into sarge anyway. How?
> 
> Probably a hand-build outside the autobuilders. <sigh>

Looks like:

./2004/10/31/perl_5.8.4-3_mipsel.changes    Good signature from "Matthias Klose <doko@debian.org>" (0x0F932C9C)

Regards,

	Joey

-- 
A mathematician is a machine for converting coffee into theorems.   Paul Erdös

Reply to:

References:
- report on current state of sarge security
  - From: Joey Hess <joeyh@debian.org>
- Re: report on current state of sarge security
  - From: Steve Langasek <vorlon@debian.org>

Prev by Date: Re: Bug#282276: bigloo: FTBFS in sarge: skribe is missing.
Next by Date: Re: report on current state of sarge security
Previous by thread: Re: report on current state of sarge security
Next by thread: Re: report on current state of sarge security
Index(es):
- Date
- Thread