similar to: [PATCH] run: Don't fail on missing LIBGUESTFS_PATH if --disable-appliance

The previous behavior caused the build to abort when trying to build the sysprep documentation -- without much of a hint of what went wrong. --- run.in | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/run.in b/run.in index 7545f0b..9f92306 100755 --- a/run.in +++ b/run.in @@ -66,9 +66,10 @@ chcon --reference=/tmp tmp 2>/dev/null ||: if [ "x at

Here are some of the patches that I have maintained in the patch queue of my packages that I maintain within the Debian distribution (http://packages.qa.debian.org/libg/libguestfs.html). All of them address FTBFS (fail to build from source) errors that happened with the particular configuration that is used for building the Debian package. Cheers, -Hilko

$ libguestfs-test-tool ... libguestfs: launch: version=1.42.0fedora=33,release=5.fc33,libvirt ... libguestfs: build appliance libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/lib/guestfs) ... It appears that this configure test is now failing:

They will fail anyway in that case, so run them only when the FUSE support is built in. --- fish/Makefile.am | 6 +++++- sysprep/Makefile.am | 6 +++++- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/fish/Makefile.am b/fish/Makefile.am index fc7c729..5ffa0f1 100644 --- a/fish/Makefile.am +++ b/fish/Makefile.am @@ -297,7 +297,6 @@ TESTS += \ test-find0.sh \ test-inspect.sh

Hi, all. I've set up an LXC container for various Openstack admin chores, and now I'm being asked to have it used for importing qcow2 images -- on which we want to run utilities like virt-sparsify and virt-sysprep, first. Sadly, when I do that, it dies horribly, e.g., root@openstack-cli:/tmp# virt-sysprep -a cloud-image.qcow2 Examining the guest ... libguestfs: warning:

Move the "FIXED APPLIANCE" section from libguestfs-make-fixed-appliance(1) to the general guestfs(3), so it's more visible and less hidden in the documentation of a rarely-used tool. Expand the FAQ question about libguestfs without supermin, mentioning the build options needed and pointing to the aforementioned new section. --- appliance/libguestfs-make-fixed-appliance.pod | 28

Here are three patches that fix issues with out-of-tree building and one that uses Ruby's own autoconf stuff for determining how Ruby bindings should be built. Cheers, -Hilko

On Fri, Apr 28, 2017 at 05:03:58PM +0300, Pavel Butsykin wrote: > On 27.04.2017 18:28, Richard W.M. Jones wrote: > > > >On Thu, Apr 27, 2017 at 03:55:10PM +0300, Pavel Butsykin wrote: > >>The flag determines the behavior of working with the appliance, and specifically > >>the choice to use the build supermin appliance or the fixed appliance. If the >

On Monday, 18 September 2017 18:39:40 CEST Richard W.M. Jones wrote: > dib/output_format_docker.mli | 19 + > dib/output_format_qcow2.mli | 19 + > dib/output_format_raw.mli | 19 + > dib/output_format_squashfs.mli | 19 + > dib/output_format_tar.mli | 19 + >

This change allows the run scripts of virt-v2v and libguestfs to be chained. --- run.in | 16 +++++++++++++--- 1 files changed, 13 insertions(+), 3 deletions(-) diff --git a/run.in b/run.in index 9388398..7cef715 100755 --- a/run.in +++ b/run.in @@ -37,9 +37,19 @@ b=@abs_builddir@ export TMPDIR="$b" # Set local environment relative to this script. -export

On Tue, Apr 25, 2017 at 03:58:45PM +0300, Pavel Butsykin wrote: > On 25.04.2017 15:11, Richard W.M. Jones wrote: > >On Tue, Apr 25, 2017 at 02:35:26PM +0300, Pavel Butsykin wrote: > >>The patch changes the order of the steps to search for fixed/supermin > >>appliance in accordance with documentation: > >> > >>"If the fixed appliance is found,

This works reliably for me ... Rich.

I believe this patch has now been superseded by Hilko's commit here: https://github.com/libguestfs/libguestfs/commit/f75142c577255b30f2a8e1d27baa5fd185594197 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#)

I download libguestfs from github and fetch to the *origin master*. I tried to build libguestfs in my own linux distro and I followd the http://libguestfs.org/guestfs-building.1.html#using-a-prebuilt-binary-appliance to replace with supermin I download the appliance-1.30.1.tar.xz and appliance-1.30.1.tar.xz.sig and extract the tarball to /home/user/appliance and export

In case the appliance is disabled at configure, then all the phony guests will not be built during the 'make check' time. Since the tests already handle an empty windows.vmdk fine (in case ntfs-3g is not available), then just create it empty in this case. Reported by: Martin Kletzander. --- v2v/Makefile.am | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/v2v/Makefile.am

--- format/Makefile.am | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/format/Makefile.am b/format/Makefile.am index 0d1b28e..1dc8f14 100644 --- a/format/Makefile.am +++ b/format/Makefile.am @@ -74,4 +74,6 @@ TESTS_ENVIRONMENT = \ MALLOC_PERTURB_=$(random_val) \ $(top_builddir)/run +if ENABLE_APPLIANCE TESTS = test-virt-format.sh +endif ENABLE_APPLIANCE -- 1.7.9

On Tue, Apr 25, 2017 at 06:13:37PM +0300, Pavel Butsykin wrote: > On 25.04.2017 16:04, Richard W.M. Jones wrote: > >Can you see what: > > > > guestfish get-path > > /usr/lib64/guestfs > > >prints? Are you setting LIBGUESTFS_PATH at all? > > > > No. > > # ls /usr/lib64/guestfs > initrd kernel README.fixed root supermin.d > >

Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> --- align/Makefile.am | 2 +- builder/Makefile.am | 2 +- builder/website/Makefile.am | 2 +- cat/Makefile.am | 4 ++-- common-rules.mk | 8 ++++---- customize/Makefile.am | 2 +- df/Makefile.am | 4 ++-- diff/Makefile.am | 2 +-

On Wed, Jun 10, 2015 at 06:47:44PM +0200, Pino Toscano wrote: > index e2ee1b5..eebab53 100644 > --- a/src/guestfs.pod > +++ b/src/guestfs.pod > @@ -3540,6 +3540,30 @@ Finally, the child process sends asynchronous messages back to the > main program, such as kernel log messages. You can register a > callback to receive these messages. > > +=head1 FIXED APPLIANCE > +

Simplifies the build a bit. This is on top of the previous SELinux relabelling patch set, although not related to it. Rich.