Why do some updates skip proposed? (launchpad bug 589163)

James Hogarth james.hogarth at gmail.com
Thu Jun 3 16:16:25 UTC 2010

Hey all,

Quick question for anyone that can give a quick answer...

The kernel released for lucid last night (2.6.32-22.35) broke kvm
guests - prevented them from starting.

The kernel that was in proposed (2.6.32-22.33) has no problems.

Looking at launchpad it looks like 2.6.32-22.35 never hit proposed and
went straight to updates/security:


Given that this broke KVM guests on an LTS release no less (and kvm is
pushed by Ubuntu as the virtualisation system to use) it presents a
reasonably serious problem.

How did this get straight to release with no testing in proposed?

What is the point of having proposed for bug testing if a released
package never goes through it - especially for something as critically
important to the core system as the kernel?

Hopefully the issue can be fixed soon so those of us who use KVM on
Lucid are able to use the latest kernel with any bug fixes again..

As it is anyone with this issue cannot get a fix from Ubuntu as a
vendor for the following CVE's as they are part of the update that
broke kvm:


And if they don't have the savvy (or are unwilling to run a 'proposed'
kernel) to obtain the 2.6.32-22.33 kernel directly from the launchpad
build page they will also be missing updates for launchpad bugs 526354
and 567016.

Any thoughts on this issue?



More information about the Ubuntu-devel-discuss mailing list