Ubuntu
fuse3 package

  1. Bug #1956949
  2. Comment #3

Comment 3 for bug 1956949

Revision history for this message
Colin Watson (cjwatson) wrote :

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.