Summary: | sys-kernel/genkernel-next-35 stable request | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
Component: | [OLD] Keywording and Stabilization | Assignee: | Fabio Erculiani (RETIRED) <lxnay> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | STABLEREQ |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 486636, 487674, 487676, 488046, 498446 | ||
Bug Blocks: |
Description
Pacho Ramos
2013-09-17 19:27:41 UTC
I don't see any problem with that. 24-r1 can go stable for me. Probably -27 will be a better candidate :/ Fabio, any problem with CCing arches for latest version? Looks like it includes interesting fixes over older version tagged for stabilization Thanks Feel free to go ahead amd64 stable See bug 488046 #comment #3. x86 stable Just seen bug 498446 will also be needed ;) + 18 Jan 2014; Pacho Ramos <pacho@gentoo.org> genkernel-next-35.ebuild: + ia64 stable, bug #485234 (thanks to Emeric Maschino for testing) + I can test only with a compilation. If it is enough I can mark stable (like I said for systemd) I would go ahead, I doubt it will add important regressions over old genkernel (for example, in the case of HPPA, looks like it was "as wrong" as old genkernel) Well, we already point in docs to systemd profiles, also explain the problems with old genkernel and also point to this alternative. Also the old genkernel is hardmasked in systemd profiles and, then, I guess people wanting to use genkernel on this arches will try to unmask genkernel-next and try it :| Keyworded on alpha. This bug is obsoleted by bug 506888 |