seeding a package that depends/recommends fuse3 causes livefs builds to fail

Bug #1916390 reported by Rik Mills
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fuse (Ubuntu)
Undecided
Unassigned
kio-fuse (Ubuntu)
Undecided
Unassigned
sshfs-fuse (Ubuntu)
Undecided
Unassigned

Bug Description

Seeding a package that depends/recommends fuse3 causes livefs builds to fail.

Examples:

kio-fuse: depends fuse3. Upstream KDE have requested/suggested that KDE distro add this to their default install.

sshfs-fuse: a dependency of kdeconnect, which is a default recommends in Kubuntu. Currently the version in Ubuntu is 3.6.0+repack+really2.10-0ubuntu1 as the real 3.x release from debian depends now on fuse3, and so breaks ISO builds.

Example build failure with seeded kio-fuse: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/hirsute/kubuntu/+build/261723

**** build log snip ****

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 fuse3 : Breaks: fuse
E: Unable to correct problems, you have held broken packages.
P: Begin unmounting filesystems...
P: Saving caches...
P: Begin unmounting filesystems...
P: Saving caches...
Build failed
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/lpbuildd/target/build_livefs.py", line 176, in run
    self.build()
  File "/usr/lib/python3/dist-packages/lpbuildd/target/build_livefs.py", line 167, in build
    self.run_build_command(["lb", "build"], env=base_lb_env)
  File "/usr/lib/python3/dist-packages/lpbuildd/target/build_livefs.py", line 90, in run_build_command
    return self.backend.run(args, cwd="/build", **kwargs)
  File "/usr/lib/python3/dist-packages/lpbuildd/target/lxd.py", line 537, in run
    subprocess.check_call(cmd, **kwargs)
  File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['lxc', 'exec', 'lp-hirsute-amd64', '--env', 'PROJECT=kubuntu', '--env', 'ARCH=amd64', '--', '/bin/sh', '-c', 'cd /build && linux64 lb build']' returned non-zero exit status 1.

Revision history for this message
Rik Mills (rikmills) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

The requirement for fuse comes from launchpad-buildd; because livefs builds happen inside a lxd container, fuse is required in order to be able to do mounts during the build. To support fuse3 we will need to arrange some sort of a migration.

Why is fuse3 provided as a separate source, instead of being version 3 of the fuse package? If we are going to move to supporting fuse version 3 (i.e. migrating to having it in main), the preferred method is to make the fuse package version 3 so that upgrades work correctly.

affects: ubuntu-cdimage → launchpad-buildd
Revision history for this message
Steve Langasek (vorlon) wrote :

Looking at this better, this is unrelated to launchpad-buildd's dependency on fuse (which sits outside the chroot) and instead comes via the platform live-common seed which depends on ntfs-3g, which has a pre-depends on fuse. (which is wrong, it should be a dependency not a pre-dependency.)

Reassigning this to fuse itself, since requiring parallel fuse and fuse3 daemons in the release should be addressed.

affects: launchpad-buildd → fuse (Ubuntu)
Revision history for this message
Rik Mills (rikmills) wrote :

Looks like Debian will be tackling the fuse -> fuse3 upgrade path in bookworm

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918984

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.