[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#592707: marked as done (kernel should be protected against old package kvm-source)

Your message dated Tue, 14 Dec 2010 05:05:22 +0000
with message-id <1292303122.3136.530.camel@localhost>
and subject line Re: kernel should be protected against old package kvm-source
has caused the Debian Bug report #592707,
regarding kernel should be protected against old package kvm-source
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
592707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592707
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: linux-2.6
Severity: minor

There was a package in Lenny, kvm-source, which contains
kernel module for kvm subsystem and is built from package
named kvm.

All modern kernels includes kvm modules.  Kvm package is
now transitional to qemu-kvm, which does not provide any
kernel modules or packages like kvm-source.

kvm-source package has been removed from squeeze.

When kvm-source package is installed, it replaces kvm
modules in current kernel with old, obsolete ones, so
that current kvm userspace does not work anymore.
But current kernel includes more recent kvm modules
which works correctly even with old userspace.

So kvm-source breaks current kernels.  It breaks even
lenny's kernel (2.6.26), which includes more recent
kvm modules than in kvm-source_72 (from lenny), and
even more - 2.6.26 received a few security fixes for
kvm modules which are not present in kvm-source.

The only solution to this I see is to include Conflicts:
into kernel against kvm-source (unversioned).

Note that it is not sufficient to add such conflicts:
to qemu-kvm (userspace component), because one may
have installed kvm-source without qemu-kvm, kvm-source
broke the kernel module (replacing it with older and
buggy one), and later qemu-kvm is installed on already
broken system.

Thanks!

/mjt

--- End Message ---
--- Begin Message --- 
On Thu, 2010-08-12 at 12:33 +0400, Michael Tokarev wrote:
[...]
> So kvm-source breaks current kernels.  It breaks even
> lenny's kernel (2.6.26), which includes more recent
> kvm modules than in kvm-source_72 (from lenny), and
> even more - 2.6.26 received a few security fixes for
> kvm modules which are not present in kvm-source.

It sounds like kvm-source should be removed from lenny.

> The only solution to this I see is to include Conflicts:
> into kernel against kvm-source (unversioned).
[...]

This is wrong, they do not conflict at all.  The problem is with the
modules, not the source.  But there are all kinds of old broken drivers
out there; should kernel image packages conflict with all such module
packages?  The answer is no.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: