@Tim: I fixed it in update-manager so that it has a special upgrade
rule for people with the low-latency kernel (that needs to be released
noted as well). If you want to add a transitional package in the kernel
itself that is of course fine with me. I removed myself from the
assignies for this.
Doh! I misread your bug description. I'll assume this is fix released.
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: High = Medium
Status: In Progress = Fix Released
--
lowlatency kernel no longer available, dist-upgrade path unknown
https://bugs.launchpad.net/bugs/129458
Michael - its not 'Fix Committed' until it is in the official git
repository on kernel.ubuntu.com. Please send patches or pull requests to
[EMAIL PROTECTED]
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Fix Committed = In Progress
--
lowlatency kernel no longer available,
This is fixed in my local tree. It will automatically transition to
linux-image-generic
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Triaged = Fix Committed
--
lowlatency kernel no longer available, dist-upgrade path unknown
https://bugs.launchpad.net/bugs/129458
You received this
(local tree is the local update-manager repository)
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) = Michael Vogt
--
lowlatency kernel no longer available, dist-upgrade path unknown
https://bugs.launchpad.net/bugs/129458
You received this bug notification because you
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided = High
Status: New = Triaged
--
lowlatency kernel no longer available, dist-upgrade path unknown
https://bugs.launchpad.net/bugs/129458
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux-source-2.6.22 (Ubuntu)
Target: None = ubuntu-7.10-beta
--
lowlatency kernel no longer available, dist-upgrade path unknown
https://bugs.launchpad.net/bugs/129458
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
