fix-libvirt-dependency : lp:~paelzer/uvtool : Git : Code : uvtool

Get this branch:: git clone -b fix-libvirt-dependency https://git.launchpad.net/~paelzer/uvtool

Only Christian Ehrhardt  can upload to this branch. If you are Christian Ehrhardt  please log in for upload directions.

Branch merges

Merged into uvtool:ubuntu/devel at revision 7996f7f8ccc0afad4010e9e5b8eaecfe8f1b55ef

Robie Basak: Pending requested 2017-05-30

Branch information

Name:: fix-libvirt-dependency

Repository:: lp:~paelzer/uvtool

Recent commits

7996f7f... by Christian Ehrhardt  on 2017-05-31

define alternatives for libvirt dependencies

To ease backporting make the old libvirt-bin an alternative
to the new packages.

Signed-off-by: Christian Ehrhardt <email address hidden>

f1009c7... by Christian Ehrhardt  on 2017-05-30

changelog: d/control: update libvirt dependency

Signed-off-by: Christian Ehrhardt <email address hidden>

49d5217... by Christian Ehrhardt  on 2017-05-30

d/control: update libvirt dependency

Post Xenial libvirt started to re-align with Debian packaging.
That affects the package names and content in those.
libvirt-bin in particular is only a transitional package which we want
to get rid of (LP: #1694159).

Currently uvtool-libvirt depended on it for two things:
1. to have a working libvirt service it can connect
2. to let users interact via virsh after uvt created a guest

Of these #1 is a real dependency - and while libvirt-daemon brings the
binaries it is only libvirt-daemon-system that does install it as a
service as people (and uvtool) expect it.

I first thought #2 would only be a recommends as most users want tools
like "virsh" to manage the uvtool created guests. But I realized that
while uvtool itself only connects via python-libvirt the maintainer
scripts of uvtool use virsh - therefore it has to be a dependency to
libvirt-clients as well.

Signed-off-by: Christian Ehrhardt <email address hidden>

a65795b... by Robie Basak on 2017-05-09