Quoting Dimitri John Ledkov (email@example.com):
> On 13 March 2014 15:56, Serge Hallyn <firstname.lastname@example.org> wrote:
> > Quoting Jamie Strandboge (email@example.com):
> >> On 03/12/2014 08:52 AM, Serge Hallyn wrote:
> >> > Quoting Jamie Strandboge (firstname.lastname@example.org):> Creating a symlink to
> >> /usr/bin/qemu-img from /usr/bin/kvm-img makes this error
> >> >> go away and things seem to work, but I've not reviewed/tested if this is the
> >> >> correct fix.
> >> > Ah. So the choice of kvm-img or qemu-img appears to be stored in
> >> > the qemu-driver. Can you restart libvirt and see if that fixes it
> >> > for you?
> >> It does.
> > Hm. So I'm not sure whether qemu should try to force a libvirt update...
> It's valid for e.g. qemu to declare "Breaks: libvirt (<< some
> version)" this way libvirt will be forced to upgrade and restart
> itself appropriately.
> And this way nothing happens if libvirt is not installed at all.
> (some version - being like the last one of libvirt uploaded into trusty)
Picking the right version would be tricky. Doesn't seem worth it to
push a no-build rebuild of libvirt just for this :)
Of course libvirt could be patched to re-do the check if it finds
that what it cached is no longer valid...
ubuntu-devel mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel