qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v1 20/34] tests/docker: add libfuse3 development headers


From: Daniel P . Berrangé
Subject: Re: [PATCH v1 20/34] tests/docker: add libfuse3 development headers
Date: Wed, 5 Jan 2022 14:50:44 +0000
User-agent: Mutt/2.1.3 (2021-09-10)

On Wed, Jan 05, 2022 at 02:26:55PM +0000, Richard W.M. Jones wrote:
> On Wed, Jan 05, 2022 at 01:49:55PM +0000, Alex Bennée wrote:
> > From: Stefan Hajnoczi <stefanha@redhat.com>
> > 
> > The FUSE exports feature is not built because most container images do
> > not have libfuse3 development headers installed. Add the necessary
> > packages to the Dockerfiles.
> > 
> > Cc: Hanna Reitz <hreitz@redhat.com>
> > Cc: Richard W.M. Jones <rjones@redhat.com>
> > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > Acked-by: Richard W.M. Jones <rjones@redhat.com>
> > Reviewed-by: Beraldo Leal <bleal@redhat.com>
> > Tested-by: Beraldo Leal <bleal@redhat.com>
> > Message-Id: <20211207160025.52466-1-stefanha@redhat.com>
> > [AJB: migrate to lcitool qemu.yml and regenerate]
> > Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> 
> 
> I checked all the package names and they look good, so:

FYI, the libvirt-ci  CI pipelines validate that all package
names are correct by creating a job for each distro and
checking that every package known to libvirt-ci can be
installed. This catches issues where distros rename or
drop packages. These are some of the reasons why we'll
benefit from using libvirt-ci / lcitool for auto-generating
these dockerfiles in QEMU.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|




reply via email to

[Prev in Thread] Current Thread [Next in Thread]