Re: renaming linux-kernel source package
Andres Salomon wrote:
> >> >> * Older kernels get removed; no need to ask for manual removal of
> >> >> linux-kernel-2.6.12 after 2.6.13 becomes available for all archs.
> >> >> However, we lose the ability to have multiple 2.6's in a release,
> >> >> which sounds like a win to me; we shouldn't be doing multiple 2.6
> >> >> releases anymore anyways, the security team has made it clear they
> >> >> don't want to support multiple kernels, and it would be extra pressure
> >> >> for all archs to keep up.
> >> >
> >> > This makes it unlikely to ever get working mips/mipsel kernels in the
> >> > single source package.
> >> Perhaps you could give a reason why this is the case?
> > Because I'm currently at 2.5 of ~8 subarchitectures working for 2.6.12,
> > and I hear already talk about 2.6.13.
> I wasn't aware that you worked on mips/mipsel stuff for older kernels in
> the archive anyways, except for the case when we decide to stabilize on a
> certain version for a release. In any case, now that experimental is
> autobuilt, we can upload a new kernel to it and stabilize architectures,
> while simultaneously updating the older version in sid
Does this mean to maintain two separate tracks then? Moving the
experimental package to unstable could never be done when it is