Hi Thomas, hmm ... that might be fallout from the general move to fuse3. See MIR bug => https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1934510 And the links from there.
Ginggs did make an analysis back then if everything is ready to move: => https://lists.ubuntu.com/archives/ubuntu-devel/2021-July/041530.html I think almost all in that list was ready to move Your bug made me re-check things again from the POV of image builds. In the seeds we have: live-common:14:# * unionfs-fuse desktop-minimal:88: * (gvfs-fuse) # let non-GNOME apps see GVFS via fuse Not sure how that was missed in the past, probably the dependency checks were on reverse-depends, but not considering the seeds? Anyway, what we see now is a conflict between the seeds and some of the packaging changes that already happened (see the links from the link above - some paclages already switched - among others there is qemu and open-vm- tools). The latter (open-vm-tools) is usually seeded for usage as vmware guest. (Side-note: I see no useful use-case on a AWS image, and might be a separate improve-images discussion) #1 Package: gvfs-fuse Depends: fuse, gvfs (= 1.48.1-2ubuntu3), libc6 (>= 2.34), libfuse3-3 (>= 3.2.3), libglib2.0-0 (>= 2.65.1) #2 Package: unionfs-fuse Version: 1.0-1ubuntu2 Depends: libc6 (>= 2.7), libfuse2 (>= 2.8), fuse Continuing on those in the next comment ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
