Hi Horms, On Monday, 01 Aug 2005, Horms ([EMAIL PROTECTED]) wrote: > On Mon, Aug 01, 2005 at 11:52:48AM +0200, Andreas Barth wrote: > > * Horms ([EMAIL PROTECTED]) [050801 11:43]: > > > On Mon, Aug 01, 2005 at 09:28:37AM +0200, Andreas Barth wrote: > > > > * Horms ([EMAIL PROTECTED]) [050801 08:23]: > > > > Ok. Which updates do you have at hand currently that you want to push > > in? > > > > > > Also, you might consider if the current approach to rebuild the kernels > > > > is the best one (but that's of course up to you as long as you do the > > > > work :). > > > > > I am not sure what you are getting at there. > > > > > > The current build process is a mess. We are tying to sort that > > > out with single-source, which is what you can see for 2.6.12. > > > If we can get this working, and convince ourselves that > > > moving sarge from 2.6.8 to 2.6.12 is possible, then yes, we > > > should do that. But for now, I'm really looking for a way > > > to do maintenance on 2.4.27 and 2.6.8. > > > > Yes, that was about my intention as well. So, yes, please move forward > > with 2.4.27 and 2.6.8 and send a list of recommended updates. > > I need to go through the BTS and see what else could go in. > But what I have right now is listed at in the following Changelogs. > > http://svn.debian.org/wsvn/kernel/trunk/kernel/source/kernel-source-2.6.8-2.6.8/debian/changelog?op=file&rev=0&sc=0 > http://svn.debian.org/wsvn/kernel/trunk/kernel/i386/kernel-image-2.6.8-i386-2.6.8/debian/changelog?op=file&rev=0&sc=0 > > http://svn.debian.org/wsvn/kernel/trunk/kernel-2.4/source/kernel-source-2.4.27-2.4.27/debian/changelog?op=file&rev=0&sc=0 > http://svn.debian.org/wsvn/kernel/trunk/kernel-2.4/i386/kernel-image-2.4.27-i386-2.4.27/debian/changelog?op=file&rev=0&sc=0
IMHO this changes should go via security.debian.org. Nearly every changelog entry lists a CVE ID. Joey (and the rest of the security team), what is needed to get this via security.d.o? Martin -- Martin Zobel-Helas debian-volatile team member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
