Build e2fsprogs against fuse3. The last release of fuse2 was in Jan 2019 and it no longer gets security updates. Fuse3 was released in 2016. It seems that there has been some level of fuse3 support since 1.45.3
(In reply to Peter Robinson from comment #0) > Build e2fsprogs against fuse3. The last release of fuse2 was in Jan 2019 and > it no longer gets security updates. Fuse3 was released in 2016. It seems > that there has been some level of fuse3 support since 1.45.3 Hello Peter, thanks for the request. I'd like to know what the motivation behind your request is. Is it just the fact that the newer package (fuse3) is available and fuse2 is no longer updated, or do you have a usability issue or a use case you'd like to solve ? -Lukas
> thanks for the request. I'd like to know what the motivation behind your > request is. Is it just the fact that the newer package (fuse3) is available > and fuse2 is no longer updated, or do you have a usability issue or a use > case you'd like to solve ? Looking at reductions and de-duplications for the RHEL for Edge initiative, we currently have both fuse2 and fuse3 with the general move towards fuse3 as you'd expect, there's currently this and 2 others that still depend on the old fuse.
(In reply to Peter Robinson from comment #2) > Looking at reductions and de-duplications for the RHEL for Edge initiative, > we currently have both fuse2 and fuse3 with the general move towards fuse3 > as you'd expect, there's currently this and 2 others that still depend on > the old fuse. Thanks for the clarification. I think it should be as easy as changing the dependencies, but it'll require some testing. -Lukas
For reference there's some details here: https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0
What's the status here, would be good to get this done in time for el10 branching.