Re: Sarge kernels and Volatile
* Horms (horms@debian.org) [050801 11:43]:
> On Mon, Aug 01, 2005 at 09:28:37AM +0200, Andreas Barth wrote:
> > * Horms (horms@debian.org) [050801 08:23]:
> > > I am wondering if others thing that volatile is a good
> > > place for us to make uploads of updated 2.6.8 and 2.4.27 kerels for
> > > Sarge? This would allow us to remove these kernels from unstable/testing
> > > and still provide maintenence releases for users.
> > Well, my basic approach to that is that nobody of the volatile team can
> > really do security stuff (or otherwise debugging) for the kernels. So,
> > if the kernel team is able and willing to do that, we could go that way.
> > But anything that is in volatile needs to be security-supported till the
> > distribution is archived (and the security support won't be done by the
> > security-team).
> What I am really looking for is a way to allow the kernel-team (me?) to
> provide updates for sarge. Primarily security updates, but there are
> other important fixes too. The security team hasn't doene kernel updates
> for a long time now, I guess they are busy with other things. So I think
> it is valuable for the kernel team to provide updates.
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.
Cheers,
Andi
Reply to: