convirt depends on xen-utils and xen-hypervisor when not necessary

Bug #305326 reported by Tessa
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
convirt (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: convirt

Convirt can be used to manage remote Xen and KVM hosts via SSH. However, the package insists on installing the xen tools and hypervisor on the local system, converting it to a xen host even when unwanted. Those packages should be Recommends, not Depends in the convirt package, so that it can still be used as a remote management tool.

Revision history for this message
Jd (jd-jedi) wrote :

ConVirt requires Xen client library to talk to the remote xen.
xen-hypervisor is certainly not required. python-xen is required.

Revision history for this message
Tessa (unit3) wrote :

Ok, so python-xen-* and libxen3* are required, but not xen-utils-* (which tries to start xend at boot) or xen-hypervisor (which changes your boot setup). Is that about the sum of it?

Revision history for this message
Jd (jd-jedi) wrote :

Yes in theory.
I would see if some one can give it a try and confirm this practically.

Revision history for this message
Tessa (unit3) wrote :

Well, from the upstream source package (0.9.6), I can run it with just python-xen-3.3 and libxen3-3.3.0-1ubuntu7 installed (no xen-utils or xen-hypervisor), so it looks like that set of deps should be fine.

agent 8131 (agent-8131)
Changed in convirt (Ubuntu):
status: New → Confirmed
Revision history for this message
Tessa (unit3) wrote :

Their own Ubuntu/Debian packages available through their repo (http://www.convirture.com/repos/definitions/ubuntu/8.x/convirt.list) don't have this problem. Perhaps their packages just need to get merged into the distribution proper?

Revision history for this message
Tessa (unit3) wrote :

It looks like their packages now do have this problem. Can someone talk to upstream and get this fixed?

Revision history for this message
Tessa (unit3) wrote :

Actually, looks like my copy of apt was pulling in old deps. The upstream packages are fine, they still don't have this problem. Anyone know why the Ubuntu repo packages have different deps than the upstream ones? And how we can get the latest upstream packages into Ubuntu, instead of the old / buggy ones we have now?

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.