[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Proposed Kernel Updates for Sid: Round 1



Hi,

This has been a long time in the coming, but I'm happy
to report that we are slowly, but very surely making progress
towards being able to release a round of security updates for
Sarge.

These updates were actually prepared a little while ago,
but it has taken us a little while to work with the Security
team to get them into shape. Hopefully it won't take so long the
next time around, which will likely kick off as soon as this
round concludes.

The reason that I am writing is to solicit help in testing.
Some minor problems have been found, and mostly fixed,
but the more testing the merrier. 

What we are looking for is problems that have been _introduced_
by the security updates. Particularly problems like,
the system now fails to boot because vmlinuz is missing.

The status of the architectures is:

* Still needs fixing, should happen real soon now
  kernel-image-2.4.27-arm    wrong distribution, needs fix, random changes
  kernel-patch-2.4.27-mips   needs mipsel -> buildd, pending
* Recently fixed, in the most need of testing
  kernel-image-2.4.27-ia64
  kernel-image-2.4.27-alpha
  kernel-image-2.6.8-alpha
  kernel-patch-powerpc-2.6.8
* Not recently updated, already had some testing
  kernel-image-2.6.8-sparc
  kernel-image-2.4.27-sparc
  kernel-image-2.6.8-hppa
  kernel-image-2.6.8-i386
  kernel-image-2.4.27-i386
  kernel-image-2.6.8-m68k
  kernel-image-2.4.27-m68k
  kernel-image-2.4.27-s390
  kernel-patch-2.4.27-powerpc
  kernel-image-2.6.8-ia64
  kernel-image-2.6.8-s390
  kernel-image-2.6.8-amd64

You can find the images, and corresponding source in
http://kernel.debian.net/debian/pool/main/

And the archive is apt-gettable using:

deb http://kernel.debian.net/debian/ sarge-proposed-security-updates main
deb-src http://kernel.debian.net/debian/ sarge-proposed-security-updates main


If you know of new security bugs, and they aren't in 
http://svn.debian.org/wsvn/kernel/patch-tracking/?rev=0&sc=0
then send a note here, to the testing-security team, or
open a bug in the BTS.

-- 
Horms



Reply to: