It seems that the snapd package in Jammy already has the `libfuse-dev | libfuse3-dev` Build-Dep, however we may still have an issue. That build-dep *allows* snapd to be built using libfuse3-dev, but by default the first declared dependency will be used by the resolver, which means that by default snapd will still build against libfuse-dev on Jammy. This will block demoting fuse2 to universe.
OTOH inverting the order (`libfuse3-dev | libfuse-dev`) will cause snapd to be build against libfuse3-dev on pre-Jammy releases (AIUI you want to use a common packaging across several releases).
A way out could be using a versioned dependency:
libfuse3-dev (>= 3.10.5-1) | libfuse-dev
so libfuse3-dev will only be used on Jammy, and libfuse-dev on the older releases. I didn't test this, but it should work.
Hi Alberto,
It seems that the snapd package in Jammy already has the `libfuse-dev | libfuse3-dev` Build-Dep, however we may still have an issue. That build-dep *allows* snapd to be built using libfuse3-dev, but by default the first declared dependency will be used by the resolver, which means that by default snapd will still build against libfuse-dev on Jammy. This will block demoting fuse2 to universe.
OTOH inverting the order (`libfuse3-dev | libfuse-dev`) will cause snapd to be build against libfuse3-dev on pre-Jammy releases (AIUI you want to use a common packaging across several releases).
A way out could be using a versioned dependency:
libfuse3-dev (>= 3.10.5-1) | libfuse-dev
so libfuse3-dev will only be used on Jammy, and libfuse-dev on the older releases. I didn't test this, but it should work.