[Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"

[Colin Watson]

That installation by launchpad-buildd happens in the container that
livecd-rootfs runs in, not in the chroot that livecd-rootfs is busy
building.  If you look more closely at the build log you can see it
succeeding earlier on.  We may indeed have to update launchpad-buildd to
use fuse3, but it's not what's breaking the build here.

The more immediate problem is:

  Package: fuse
  Task: standard, server-minimal

  Package: fuse3
  Task: cloud-image, server, ubuntu-server-raspi

This in turn is because open-vm-tools 2:11.3.5-1 switched to fuse3, so
fuse3 ends up in the expanded server seed
(https://people.canonical.com/~ubuntu-archive/germinate-
output/ubuntu.jammy/rdepends/ALL/fuse3), while loads of other things
still depend on fuse and so fuse ends up in the expanded server-minimal
seed (https://people.canonical.com/~ubuntu-archive/germinate-
output/ubuntu.jammy/rdepends/ALL/fuse).

This is a distribution inconsistency problem, not a launchpad-buildd
problem.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to fuse3 in Ubuntu.
https://bugs.launchpad.net/bugs/1956949

Title:
  CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"

Status in launchpad-buildd:
  New
Status in fuse3 package in Ubuntu:
  Invalid

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