Summary: | stabilise suspend2-sources-2.6.17 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Iain Buchanan <iaindb> |
Component: | New packages | Assignee: | Christian Heim (RETIRED) <phreak> |
Status: | RESOLVED CANTFIX | ||
Severity: | enhancement | CC: | 8an, askwar, Jochen.Trumpf, juergennagel, mail, me, pacho, ticho, x86, zlin |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | output from emerge --info |
Description
Iain Buchanan
2006-09-04 17:12:46 UTC
Created attachment 96019 [details]
output from emerge --info
Still need to wait a bit, till I finished fixing/stabilizing hibernate-script-1.93 (that's needed/recommended with >=2.6.17). Currently I'm working on getting bug 146352 resolved, but its a bit hard since I can't reproduce it. (In reply to comment #2) > Still need to wait a bit, till I finished fixing/stabilizing > hibernate-script-1.93 (that's needed/recommended with >=2.6.17). Currently I'm > working on getting bug 146352 resolved, but its a bit hard since I can't > reproduce it. OK, that helped. Just need to stabilize hibernate-script-1.93 before suspend2-sources-2.6.17 will go stable too! (that means 30 days from today) *** Bug 146352 has been marked as a duplicate of this bug. *** Removing the DEPEND on 146352, as its fixed in the current patch tarball. UPSTREAM agrees with me, that removing the dash-feature of hibernate-script is the best solveable way. Any chance of stabilizing 2.6.18 instead? I'd love to be able to use the in-kernel ieee80211 stack (and no, I won't run unstable sources ... ;-). (In reply to comment #6) > Any chance of stabilizing 2.6.18 instead? I'd love to be able to use the > in-kernel ieee80211 stack (and no, I won't run unstable sources ... ;-). > You can try this "testing" version. You don't need to remove your old kernel and I am using 2.6.18 sources without problems (and latest hibernate-script ;-) also) (In reply to comment #6) > Any chance of stabilizing 2.6.18 instead? I'd love to be able to use the > in-kernel ieee80211 stack (and no, I won't run unstable sources ... ;-). let's leave 2.6.18 to it's own trial period! from the suspend2 list, there are still various problems with it :) What's the current status concerning the stabilization? 2006-10-26 had been the target date according to comment #3. :) (In reply to comment #9) > What's the current status concerning the stabilization? > 2006-10-26 had been the target date according to comment #3. :) Yup, I'm a slacker :) Adding x86 for stabilization. Closing, as the new target for stabilization is 2.6.18. New bug is 157584. |