On Tue, Mar 10, 2020 at 02:16:28PM +0100, Pino Toscano wrote: > On Tuesday, 10 March 2020 14:07:41 CET Richard W.M. Jones wrote: > > Should we do this yet? It would of course only be for upstream. > > Not sure why it should be "upstream only".
I meant only that we would just put it in git, and not try to backport it (so it wouldn't affect people using current tarballs). > In any case, the big issue in this case is that you cannot build > virt-v2v with libguestfs from git. So until that is done, bumping > the version requirements means that almost noone (unless they install > libguestfs) can work on virt-v2v... I guess because virt-v2v and libguestfs are more intimately connected than other dependencies, it's worth trying to make this work. I thought we could do it already using ‘../libguestfs/run’, so I uninstalled libguestfs from my laptop and tried it, but: $ ../libguestfs/run ./autogen.sh [other stuff] && make checking for LIBGUESTFS... no configure: error: Package requirements (libguestfs >= 1.40) were not met: Well how hard can it be ... I'll see if I can fix this. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top _______________________________________________ Libguestfs mailing list [email protected] https://www.redhat.com/mailman/listinfo/libguestfs
