[meta-virtualization][PATCHv2] libvirt: update from fuse2 to fuse3

[meta-virtualization][PATCHv2] libvirt: update from fuse2 to fuse3

[Markus Volk]

Using fuse2 and fuse3 in the same environment can be problematic. Most
projects I know of now support fuse3. ostree, flatpak, xdg-desktop-portal
and some other recipes in meta-openembedded are configured to use fuse3 and
libvirt is also able to do so.

This commit switches libvirt to fuse3 to reduce the number of recipes that still use
the old version.

Signed-off-by: Markus Volk <f_l_k@t-online.de>
---
 recipes-extended/libvirt/libvirt_9.2.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-extended/libvirt/libvirt_9.2.0.bb b/recipes-extended/libvirt/libvirt_9.2.0.bb
index 5e70470..9b5b2de 100644
--- a/recipes-extended/libvirt/libvirt_9.2.0.bb
+++ b/recipes-extended/libvirt/libvirt_9.2.0.bb
@@ -156,7 +156,7 @@ PACKAGECONFIG[selinux] = "-Dselinux=enabled,-Dselinux=disabled,libselinux,"
 PACKAGECONFIG[python] = ",,python3,"
 PACKAGECONFIG[sasl] = "-Dsasl=enabled,-Dsasl=disabled,cyrus-sasl,cyrus-sasl"
 PACKAGECONFIG[numactl] = "-Dnumactl=enabled,-Dnumactl=disabled,numactl,"
-PACKAGECONFIG[fuse] = "-Dfuse=enabled,-Dfuse=disabled,fuse,"
+PACKAGECONFIG[fuse] = "-Dfuse=enabled,-Dfuse=disabled,fuse3,"
 PACKAGECONFIG[audit] = "-Daudit=enabled,-Daudit=disabled,audit,"
 PACKAGECONFIG[libcap-ng] = "-Dcapng=enabled,-Dcapng=disabled,libcap-ng,"
 PACKAGECONFIG[wireshark] = "-Dwireshark_dissector=enabled,-Dwireshark_dissector=disabled,wireshark libwsutil,"
-- 
2.41.0

Re: [meta-virtualization][PATCHv2] libvirt: update from fuse2 to fuse3

[Bruce Ashfield]

In message: [meta-virtualization][PATCHv2] libvirt: update from fuse2 to fuse3
on 24/08/2023 Markus Volk wrote:

> Using fuse2 and fuse3 in the same environment can be problematic. Most
> projects I know of now support fuse3. ostree, flatpak, xdg-desktop-portal
> and some other recipes in meta-openembedded are configured to use fuse3 and
> libvirt is also able to do so.
> 
> This commit switches libvirt to fuse3 to reduce the number of recipes that still use
> the old version.
> 
> Signed-off-by: Markus Volk <f_l_k@t-online.de>
> ---
>  recipes-extended/libvirt/libvirt_9.2.0.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-extended/libvirt/libvirt_9.2.0.bb b/recipes-extended/libvirt/libvirt_9.2.0.bb
> index 5e70470..9b5b2de 100644
> --- a/recipes-extended/libvirt/libvirt_9.2.0.bb
> +++ b/recipes-extended/libvirt/libvirt_9.2.0.bb
> @@ -156,7 +156,7 @@ PACKAGECONFIG[selinux] = "-Dselinux=enabled,-Dselinux=disabled,libselinux,"
>  PACKAGECONFIG[python] = ",,python3,"
>  PACKAGECONFIG[sasl] = "-Dsasl=enabled,-Dsasl=disabled,cyrus-sasl,cyrus-sasl"
>  PACKAGECONFIG[numactl] = "-Dnumactl=enabled,-Dnumactl=disabled,numactl,"
> -PACKAGECONFIG[fuse] = "-Dfuse=enabled,-Dfuse=disabled,fuse,"
> +PACKAGECONFIG[fuse] = "-Dfuse=enabled,-Dfuse=disabled,fuse3,"
>  PACKAGECONFIG[audit] = "-Daudit=enabled,-Daudit=disabled,audit,"
>  PACKAGECONFIG[libcap-ng] = "-Dcapng=enabled,-Dcapng=disabled,libcap-ng,"
>  PACKAGECONFIG[wireshark] = "-Dwireshark_dissector=enabled,-Dwireshark_dissector=disabled,wireshark libwsutil,"
> -- 
> 2.41.0
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#8226): https://lists.yoctoproject.org/g/meta-virtualization/message/8226
> Mute This Topic: https://lists.yoctoproject.org/mt/100931588/1050810
> Group Owner: meta-virtualization+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 

Re: [meta-virtualization][PATCHv2] libvirt: update from fuse2 to fuse3

[Bruce Ashfield]

In message: [meta-virtualization][PATCHv2] libvirt: update from fuse2 to fuse3
on 24/08/2023 Markus Volk wrote:

> Using fuse2 and fuse3 in the same environment can be problematic. Most
> projects I know of now support fuse3. ostree, flatpak, xdg-desktop-portal
> and some other recipes in meta-openembedded are configured to use fuse3 and
> libvirt is also able to do so.
> 
> This commit switches libvirt to fuse3 to reduce the number of recipes that still use
> the old version.

I had previously updated libvirt to 9.6.0 in master-next,
so I tweaked the patch for that version and applied it to
that branch.

It is worth re-testing master-next and 9.6.0 to see if
everything still works as you expect.

I'll be merging master-next to master next week, once I'm
back from holidays.

Bruce

> 
> Signed-off-by: Markus Volk <f_l_k@t-online.de>
> ---
>  recipes-extended/libvirt/libvirt_9.2.0.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-extended/libvirt/libvirt_9.2.0.bb b/recipes-extended/libvirt/libvirt_9.2.0.bb
> index 5e70470..9b5b2de 100644
> --- a/recipes-extended/libvirt/libvirt_9.2.0.bb
> +++ b/recipes-extended/libvirt/libvirt_9.2.0.bb
> @@ -156,7 +156,7 @@ PACKAGECONFIG[selinux] = "-Dselinux=enabled,-Dselinux=disabled,libselinux,"
>  PACKAGECONFIG[python] = ",,python3,"
>  PACKAGECONFIG[sasl] = "-Dsasl=enabled,-Dsasl=disabled,cyrus-sasl,cyrus-sasl"
>  PACKAGECONFIG[numactl] = "-Dnumactl=enabled,-Dnumactl=disabled,numactl,"
> -PACKAGECONFIG[fuse] = "-Dfuse=enabled,-Dfuse=disabled,fuse,"
> +PACKAGECONFIG[fuse] = "-Dfuse=enabled,-Dfuse=disabled,fuse3,"
>  PACKAGECONFIG[audit] = "-Daudit=enabled,-Daudit=disabled,audit,"
>  PACKAGECONFIG[libcap-ng] = "-Dcapng=enabled,-Dcapng=disabled,libcap-ng,"
>  PACKAGECONFIG[wireshark] = "-Dwireshark_dissector=enabled,-Dwireshark_dissector=disabled,wireshark libwsutil,"
> -- 
> 2.41.0
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#8226): https://lists.yoctoproject.org/g/meta-virtualization/message/8226
> Mute This Topic: https://lists.yoctoproject.org/mt/100931588/1050810
> Group Owner: meta-virtualization+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 

Re: [meta-virtualization][PATCHv2] libvirt: update from fuse2 to fuse3

[Markus Volk]

[-- Attachment #1: Type: text/plain, Size: 620 bytes --]

On Sun, Aug 27 2023 at 01:30:22 PM +00:00:00, Bruce Ashfield 
<bruce.ashfield@gmail.com> wrote:
> It is worth re-testing master-next and 9.6.0 to see if
> everything still works as you expect.

Thanks, I will do the tests with the master-next branch.

One question about the other patch I sent. Do you have build issues 
with it or do you not want to support introspection at all?
I ask because the "gnome-boxes" recipe I recently sent to meta-gnome 
depends on vala bindings for libvirt-glib and cannot be built without 
the patch. For the latter case, it would be better to remove 
gnome-boxes from meta-gnome again.


[-- Attachment #2: Type: text/html, Size: 826 bytes --]

Re: [meta-virtualization][PATCHv2] libvirt: update from fuse2 to fuse3

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 932 bytes --]

On Sun, Aug 27, 2023, 11:43 PM Markus Volk <f_l_k@t-online.de> wrote:

> On Sun, Aug 27 2023 at 01:30:22 PM +00:00:00, Bruce Ashfield <
> bruce.ashfield@gmail.com> wrote:
>
> It is worth re-testing master-next and 9.6.0 to see if everything still
> works as you expect.
>
>
> Thanks, I will do the tests with the master-next branch.
>
> One question about the other patch I sent. Do you have build issues with
> it or do you not want to support introspection at all?
> I ask because the "gnome-boxes" recipe I recently sent to meta-gnome
> depends on vala bindings for libvirt-glib and cannot be built without the
> patch. For the latter case, it would be better to remove gnome-boxes from
> meta-gnome again.
>


I have no objections to introspection. I'm still out of the office, so I'm
only getting a few minutes here and there for email. Did I miss a patch ?
If so, feel free to point it out and I'll queue a build test!

Bruce

[-- Attachment #2: Type: text/html, Size: 1756 bytes --]

Re: [meta-virtualization][PATCHv2] libvirt: update from fuse2 to fuse3

[Markus Volk]

[-- Attachment #1: Type: text/plain, Size: 458 bytes --]

On Mon, Aug 28 2023 at 07:17:21 AM -03:00:00, Bruce Ashfield 
<bruce.ashfield@gmail.com> wrote:
> Did I miss a patch ? If so, feel free to point it out and I'll queue 
> a build test!

I didn't want to rush. I have sent 2 patches and the second was to fix 
build for introspection/vala for libvirt-glib. I sent it again and also 
pushed it here on github.

<https://github.com/MarkusVolk/meta-virtualization/commit/ce5f953c09fadba1f6e0014106adb4b23beef747>


[-- Attachment #2: Type: text/html, Size: 734 bytes --]

Re: [meta-virtualization][PATCHv2] libvirt: update from fuse2 to fuse3

[Bruce Ashfield]

On Mon, Aug 28, 2023 at 2:17 PM Markus Volk <f_l_k@t-online.de> wrote:
>
> On Mon, Aug 28 2023 at 07:17:21 AM -03:00:00, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
>
> Did I miss a patch ? If so, feel free to point it out and I'll queue a build test!
>
>
> I didn't want to rush. I have sent 2 patches and the second was to fix build for introspection/vala for libvirt-glib. I sent it again and also pushed it here on github.
>
> https://github.com/MarkusVolk/meta-virtualization/commit/ce5f953c09fadba1f6e0014106adb4b23beef747

Right. This is the patch that I was asking about how the documentation
was going to be used and packaged.

I didn't see a reply, did I miss that ?

Bruce

--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

Re: [meta-virtualization][PATCHv2] libvirt: update from fuse2 to fuse3

[Markus Volk]

[-- Attachment #1: Type: text/plain, Size: 409 bytes --]

On Mon, Aug 28 2023 at 09:49:36 PM -04:00:00, Bruce Ashfield 
<bruce.ashfield@gmail.com> wrote:
> Right. This is the patch that I was asking about how the documentation
> was going to be used and packaged.
> 
> I didn't see a reply, did I miss that ?

This was then a misunderstanding. I thought the libfuse patch was meant 
and had updated and replied to that

I've sent a v2 with an updated commit message


[-- Attachment #2: Type: text/html, Size: 593 bytes --]