Bug 212361 – vanilla-sources cleanup

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Raúl Porcel (RETIRED) 2008-03-05 09:49:13 UTC]

So, there we go

Link: http://packages.gentoo.org/package/vanilla-sources?arches=all

2.6.23.17: amd64,arm,hppa,ppc,ppc64
2.6.22.19: arm,ppc,ppc64 (amd64 is maybe interested?)
2.6.16.60: amd64,arm,ppc,ppc64,s390

I guess everything between .17 and .22 can be removed.

[Comment 1 Jeroen Roovers (RETIRED) 2008-03-06 16:52:42 UTC]

(In reply to comment #0)
> I guess everything between .17 and .22 can be removed.

If you meant everything >=sys-kernel/vanilla-sources-2.6.17 and <sys-kernel/vanilla-sources-2.6.22, then that's OK for HPPA. Else, re-CC us.

[Comment 2 Raúl Porcel (RETIRED) 2008-03-06 17:02:35 UTC]

(In reply to comment #1)
> Else, re-CC us.
> 

Well, you need to stabilize 2.6.23.17 :) You have .23.16 stable

And if wasn't clear enough, with this:
2.6.23.17: amd64,arm,hppa,ppc,ppc64
2.6.22.19: arm,ppc,ppc64 (amd64 is maybe interested?)
2.6.16.60: amd64,arm,ppc,ppc64,s390

i meant, stabilize those exact versions since you have an older stable

[Comment 3 Jeroen Roovers (RETIRED) 2008-03-11 05:13:54 UTC]

HPPA is done now, then.
Marked 2.6.23.17 stable.

[Comment 4 Markus Rothe (RETIRED) 2008-03-12 09:35:28 UTC]

ppc64 done

[Comment 5 Joe Jezak (RETIRED) 2008-03-22 15:50:59 UTC]

PPC is done, thanks for cleaning these up!

[Comment 6 SpanKY 2008-03-24 11:54:15 UTC]

how many times do i need to tell people that 2.6.16.x needs to hang around for s390 ?  it isnt any maintenance burden on you, so leave it be

[Comment 7 Raúl Porcel (RETIRED) 2008-03-24 12:30:37 UTC]

vapier, 2.6.16.x is not going to be removed, i'm just asking you to stabilize 2.6.16.60 since you have .16.46 stable, nothing else.

Same for arm, but for arm it would be cool if you stabilize .23.17 and .22.19 along with .16.60.

I need .16.x for sparc, so i'm going to make sure it doesn't gets removed

[Comment 8 Peter Volkov (RETIRED) 2008-05-24 13:28:21 UTC]

2.6.16.60 does not build on amd64. Should we apply fix:
https://www.x86-64.org/pipermail/patches/2006-September/003434.html
or drop stable amd64 keyword for 2.6.16?

[Comment 9 Raúl Porcel (RETIRED) 2008-05-24 15:06:34 UTC]

Applying a patch for vanilla-sources? No way :P Does current stable build? If not, then drop the keyword.

Thanks

[Comment 10 Peter Volkov (RETIRED) 2008-05-26 11:21:22 UTC]

amd64 done. 2.6.16 dropped stable.

[Comment 11 Jochen 2008-08-26 15:26:25 UTC]

Howdy,

given the current process of kernel development wouldn't it be much nicer if the newest stable kernel would be automatically marked stable as it may contain security fixes? Accordingly all release candidates should be masked.

Cheers
punraz

[Comment 12 Kelly Price 2008-10-13 14:54:12 UTC]

I can safely say these vanilla kernels have no problems for me:

2.6.26.2 amd64
2.6.25.4 x86

I'm going to push to 2.6.27.0 today and do a week-long test there.

[Comment 13 Kelly Price 2008-10-25 16:31:56 UTC]

2.6.27.0's been stable on x86 and amd64 for me now.  Pushing to 2.6.27.3 on my setups.