Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
- To: Jeroen van Wolffelaar <jeroen@wolffelaar.nl>
- Cc: Sven Luther <luther@debian.org>, 328130-done@bugs.debian.org, debian-kernel@lists.debian.org, 323183@bugs.debian.org, debian-boot@lists.debian.org
- Subject: Re: Bug#328130: RM: please remove any remnant of 2.6.10 and 2.6.11 kernels from etch/sid
- From: Horms <horms@debian.org>
- Date: Wed, 14 Sep 2005 16:27:32 +0900
- Message-id: <[🔎] 20050914072730.GX27828@verge.net.au>
- Mail-followup-to: Jeroen van Wolffelaar <jeroen@wolffelaar.nl>, Sven Luther <luther@debian.org>, 328130-done@bugs.debian.org, debian-kernel@lists.debian.org, 323183@bugs.debian.org, debian-boot@lists.debian.org
- In-reply-to: <20050914025403.GK1646@A-Eskwadraat.nl>
- References: <20050913180111.GA21271@localhost.localdomain> <20050914025403.GK1646@A-Eskwadraat.nl>
On Wed, Sep 14, 2005 at 04:54:04AM +0200, Jeroen van Wolffelaar wrote:
> On Tue, Sep 13, 2005 at 08:01:11PM +0200, Sven Luther wrote:
> > Hi,
> >
> > I write this email to ask, now that linux-2.6 2.6.12-6 is in testing, there
> > isn't any reason to keep those 2.6.10 and 2.6.11 kernels around, A quick
> > glance listed those :
>
> (...)
>
> > Also, if there are 2.6.8 kernels in sid/etch still, these can be removed as
> > well.
>
> Please see #317079, #322697 and and #323183. This report is a duplicate from
> what's already in those three reports, so please followup to them where
> appropriate. I already see a duplicate discussion on whether 2.6.8 can be
> removed, so please coordinate in the -kernel team about this, I mailed -kernel
> about it before, and there's a bug on the kernel package (#323183) about it.
First up I'd like to applogise for the confusion and multiple bug
reports surrounding this. The simple truth is that the legacy
of the Sarge-era kernel packaging has left us with a mess, that
we are trying to sift through and slowly clean up. Its turning
out to be quite complicated, and thats not something that
you should have been asked to worry about.
I suggest that we just track this as 323183, rather than mucking around
with opening and merging existing bugs. Please let me know if you would
prefer a different approach.
I've just spent a bit of time looking through this and here
is a summary of where I beleive we are, others, please comment
if this is inaccurate or incomplete. If there are ammendments
I'll try and correlate them into an updated list.
Already removed:
kernel-image-2.6.11-s390 (done in Bug #317079)
kernel-image-2.6.11-sparc (done in Bug #317079)
kernel-patch-powerpc-2.6.11 (done in Bug #317079)
kernel-source-2.6.11 (done in Bug #317079)
kernel-image-2.6.10-alpha (done in Bug #322697)
kernel-image-2.6.10-hppa (done in Bug #322697)
kernel-image-2.6.10-sparc (done in Bug #322697)
kernel-source-2.6.10 (done in Bug #322697)
Ready for removal by ftpmasters
kernel-source-2.4.24
kernel-source-2.4.25
kernel-source-2.4.26
kernel-image-2.6.11-alpha
kernel-image-2.6.11-amd64
kernel-image-2.6.11-i386
kernel-image-2.6.11-ia64
kernel-patch-2.6.10-hppa
kernel-latest-2.6-amd64
fai-kernels (request from Holger Levsen)
mol-modules-2.6.11
Will be ready for removal once d-i moves from 2.6.8 to 2.6.12
kernel-image-2.6.8-alpha
kernel-image-2.6.8-amd64
kernel-image-2.6.8-hppa
kernel-image-2.6.8-i386
kernel-image-2.6.8-ia64
kernel-image-2.6.8-m68k
kernel-image-2.6.8-s390
kernel-image-2.6.8-sparc
kernel-patch-2.6.8-hppa
kernel-patch-2.6.8-m68k
kernel-patch-powerpc-2.6.8
kernel-source-2.6.8
kernel-latest-2.6-i386
kernel-latest-2.6-s390
kernel-latest-2.6-sparc
kernel-latest-2.6-hppa
Not ready for removal
kernel-latest-powerpc (needed for 2.4 and in turn d-i)
--
Horms
Reply to: