First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 173710
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Joe Jezak <josejx@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Joe Jezak <josejx@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 173710 depends on: 173702 Show dependency tree
Bug 173710 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-04-07 22:29 0000
Hi everyone.  I've decided to pick up maintaining vanilla-sources.  To make my
life a bit easier, I would appreciate it if each arch could go through the list
below and let me know if they're okay, or if you want to keep another kernel.

From here, I'd like to keep the current kernel revision, two revisions back,
the 2.6.16 series latest and the _rc candidates.  If your arch has a problem
with that, please let me know. :)  Future stabilization requests will be made
in tandem with the gentoo-sources kernel of the same revision.

As for release candidates, should I use unstable keywords from the last kernel
and mask it?  Or would arches rather add their keywords as desired?  Another
option?

Here are the kernels, sorted by version, that I'd like to keep, along with the
keywords that would need to be added to do that, and any other questions I've
got:

== 2.4 Kernels ==
2.4.32 - For the x86 team if they want to keep it
2.4.34.2 - alpha, sparc, x86?

== 2.6.16 Kernels ==
2.6.16.46 - alpha amd64 arm ia64 ppc ppc64 s390 sparc x86

== 2.6.17 Kernels ==
I would like to remove all of these, but if arm can't move to a newer kernel:
2.6.17.14 - arm

== 2.6.18 Kernels ==
2.6.18.8 - alpha amd64 ~arm hppa ia64 ppc ppc64 s390 sparc x86

== 2.6.19 Kernels ==
2.6.19.7 - alpha amd64 ~arm hppa ia64 ppc ppc64 s390 sparc x86

== 2.6.20 Kernels ==
2.6.20.* - Stabilize with Gentoo Sources from the same patchset

I hope this makes sense and thanks! :)

------- Comment #1 From Joe Jezak 2007-04-07 22:31:55 0000 -------
*** Bug 165319 has been marked as a duplicate of this bug. ***

------- Comment #2 From SpanKY 2007-04-08 08:39:17 0000 -------
arm will have to stay with 2.6.17.x until i can verify newer things boot

------- Comment #3 From Markus Rothe 2007-04-08 13:10:24 0000 -------
that list is OK for ppc64.

although it would be OK for ppc64 to keep just the newest kernel versions.
there are no known regressions on this architecture. keeping those older
versions cannot hurt though.

------- Comment #4 From Christian Faulhammer 2007-04-08 13:30:59 0000 -------
(In reply to comment #0)
> == 2.4 Kernels ==
> 2.4.32 - For the x86 team if they want to keep it

 We don't want to keep it.

> 2.4.34.2 - alpha, sparc, x86?

 Tested and ok.

> == 2.6 Kernels ==
> 2.6.16.46 - alpha amd64 arm ia64 ppc ppc64 s390 sparc x86
> 2.6.18.8 - alpha amd64 ~arm hppa ia64 ppc ppc64 s390 sparc x86
> 2.6.19.7 - alpha amd64 ~arm hppa ia64 ppc ppc64 s390 sparc x86
> 2.6.20.* - Stabilize with Gentoo Sources from the same patchset

 All of above have been tested and are ok on x86.  All will go stable as soon
as all issues with gentoo-sources-2.6.20-r5 are sorted out.

------- Comment #5 From Gustavo Zacarias (RETIRED) 2007-04-09 12:16:55 0000 -------
Sparc needs/wants:
latest 2.4, latest 2.6.17, and latest 2.6.20.

------- Comment #6 From Jeroen Roovers 2007-04-11 03:48:04 0000 -------
To my knowledge, all of comment #13 on bug #150436 still applies.

------- Comment #7 From Christian Faulhammer 2007-04-18 14:20:55 0000 -------
x86 done

------- Comment #8 From Steve Dibb 2007-04-26 19:20:59 0000 -------
amd64 done

------- Comment #9 From Joe Jezak 2007-06-26 18:44:14 0000 -------
This is essentially done.

First Last Prev Next    No search results available      Search page      Enter new bug