@Bernd "not being seeded" means that unionfs-fuse isn't in the set of packages that define what goes into the Ubuntu 'main' component. In summary this is done by choosing some "seed" packages and computing their (build-)dependency tree, see [1,2] if you want to know more.
Automatic syncing of unionfs-fuse from Debian won't happen at the moment because the package in Ubuntu has Ubuntu specific changes. By looking at the package changelog these are: * No change rebuild to pick up -fPIE compiler default * Merge from Debian unstable (LP: #1476699). Remaining changes: - debian/control: Add Multi-Arch: foreign. Of course only the second one is a "real" change. If you can add Multi-Arch: foreign to d/control in Debian then we can make unionfs-fuse auto-sync again to Ubuntu. See [3,4] for more details in Multi-Arch. [1] https://wiki.ubuntu.com/SeedManagement [2] https://wiki.ubuntu.com/Germinate [3] https://wiki.debian.org/MultiArch/Hints [4] https://wiki.ubuntu.com/MultiarchSpec -- 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: Fix Released 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
