[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#990515: release.debian.org: buster->bullseye upgrade issue: sshfs is not upgraded due to fuse/fuse3



Am 01.07.21 um 09:32 schrieb Paul Gevers:
Hi Andreas, Laszlo,

On 01-07-2021 08:27, Andreas Beckmann wrote:
Package: release.debian.org
Severity: normal

let's start a discussion here and once we found a package to upgrade,
turn this into an unblock request.

And let's add the fuse and fuse3 maintainer to the discussion.

sshfs is sometimes kept at the buster version because of some dependency
mess of fuse/fuse3.
This usually shows up in large metapackages like freedombox or kde-full
with --install-recommends enabled. Probably because there are additional
dependency paths on fuse.

* sshfs/buster depends on fuse
* sshfs/bullseye depends on fuse3
* fuse still exists in bullseye as a real package
* fuse3/bullseye has Conflicts/Replaces: fuse and a
versioned Provides: fuse (= ${source:Version})
Upgrading would require kicking out fuse and installing fuse3 but apt
does not do that, as so often.

This isn't solved by a followup distupgrade either.

I haven't found a solution adding more Breaks: fuse to various packages
to solve this cleanly. Naturally I would have suggested to add a
transitional fuse binary package to src:fuse3 which just
Depends: fuse3 (= ${binary:Version}) and adjust the Breaks/Replaces in
fuse3 to fuse (<< 3). src:fuse then should drop its fuse package (or
rename it to fuse2 while adding a '2' to all filenames).

I'm also not convinced that fuse3 is a real replacement for fuse: it has
symlinks foo -> foo3 for all binaries and manpages. But the initramfs
hook only does 'copy_exec /sbin/mount.fuse3 /sbin', it does not care
about /sbin/mount.fuse

If fuse3 is a full replacement, then it should take over the fuse binary package name (and not use a versioned Provides). If it's not a full replacement, then the versioned Provides should be removed.


Laszlo, what do you think?

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


Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: