| Summary: | Please keyword sys-kernel/gentoo-sources-2.6.15-r1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Daniel Drake (RETIRED) <dsd> |
| Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | dertobi123, wolf31o2 |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 111968, 113203, 116667, 116916, 117680, 117834, 118005, 118111, 118395 | ||
| Bug Blocks: | 119737 | ||
|
Description
Daniel Drake (RETIRED)
2006-01-11 08:16:23 UTC
Can we skip making 2.6.15 stable and wait for 2.6.16? The PPC mess is HORRIBLE in 2.6.15. Just ask JoseJX. 2.6.16 has already hit rc1 so it's not far off. 2.6.16 is about 1 1/2 months off, so no, we can't wait. But you don't have to mark it stable on ppc if you don't want :) I added bug #119203 to the depends list, this needs to be taken care of before we can even think about marking 2.6.15 stable on ppc. Removing dep on bug 119203 since ppc won't be marking 2.6.15 stable amd64, x86, arm: Please mark gentoo-sources-2.6.15-r1 as stable. alpha, ppc64, ia64: Does 2.6.15 run OK for you? If so, please add a testing keyword to gentoo-sources-2.6.15-r1. Oops, think I forgot to click the "Add Archs" button. Let me try again. amd64, x86, arm: Please mark gentoo-sources-2.6.15-r1 as stable. alpha, ppc64, ia64: Does 2.6.15 run OK for you? If so, please add a testing keyword to gentoo-sources-2.6.15-r1. looks good on amd64. Marked Stable ~alpha done. x86 is done... feel free to blame Halcy0n if something breaks... :P well.. I'm on ppc64 and 2.6.15 (vanilla) runs just fine, but I cannot install it using portage due to bug #113203. (unpacking manual works just fine!) So no go on ppc64 for the moment. :-( 2.6.15-r1 changes the init behavior of network devices vs 2.6.14-r5. If you have firewire ports it automatically inserts the FW Ethernet driver and makes it eth0. This makes it the default ethernet device which messes up your net.eth0 configuration. This has happened to me on both the X86 and X86_64 platforms. Sorry if this is the wrong place to post this, but it's kind of batty. Who uses firewire as their default network device? hansmi has marked this ppc stable since we've fixed bug #119203. stable on ppc64 ia64 is good arm: ping :) (please mark -r3 stable at this time) all done |