Hi Bernd, I'm glad to heard that as we were not sure it would work well with fuse3. As a reminder, the libs are co-installable it is "bin:fuse" vs "bin:fuse3" that are conflicting. So when you change that remember to also change fuse->fuse3.
In the meantime it was found that unionfs-fuse isn't seeded (anymore) - it is only a comment in the Ubuntu seeds nowadays. So it will be great to move it to fuse3, but not resolve the issue discussed here. That must have been due to one of the other dependencies in the image. Anyone looking at this - please coordinate with ginggs, trevinho, paride on #ubuntu-devel for the timing of related Ubuntu uploads if they are seeded (or even in general). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: Invalid Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: New Status in open-vm-tools package in Ubuntu: Incomplete Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
