[needs-packaging] qemu-kvm-spice

Bug #878402 reported by Serge Hallyn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Fix Released
Wishlist
Unassigned

Bug Description

KVM is our primary virtualization solution in Ubuntu. It is well-support and exists in main.

We want to offer spice-enabled qemu-kvm. However, spice is currently in universe, while qemu-kvm is in main. So we'd like to offer a qemu-kvm-spice package, in universe, which provides spice-enabled binaries. The source code will be the same as qemu-kvm, but compiled with the --enable-spice flag configure flag.

URL: http://www.linux-kvm.org/page/Main_Page
License: GPLv2

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :
tags: added: needs-packaging
Revision history for this message
Brian Murray (brian-murray) wrote :

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist.

Changed in ubuntu:
importance: Undecided → Wishlist
Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for the proposed package. I don't really like the idea of having a duplicated qemu source. What is the reason to keep spice out of main? It it too much under development still?

Revision history for this message
Serge Hallyn (serge-hallyn) wrote : Re: [Bug 878402] Re: [needs-packaging] qemu-kvm-spice

Quoting Michael Vogt (<email address hidden>):
> Thanks for the proposed package. I don't really like the idea of having
> a duplicated qemu source. What is the reason to keep spice out of main?
> It it too much under development still?

It's simply very new. However we (server team) will certainly support
it in any case, so I will proceed this week or next with an MIR for the
spice libraries. If that MIR is accepted, then this package can be
deleted with a vengeance.

I do share your concern - it'd be easy for the source trees to get out of
sync and a security vulnerability (for instance) to get lost. However,
I will be maintaining both packages so while this could happen due to
my error (which is not unheard of), it at least shouldn't happen due to
lack of communication.

(With apologies - this package was uploaded yesterday. I'm sorry that
happened while you have concerns)

Revision history for this message
Alexey (alexey.u.m) wrote :
Changed in ubuntu:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.