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

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

Your message dated Thu, 8 Jul 2021 16:14:44 +0200
with message-id <af0aa128-71cc-f505-d355-71e4594fce33@debian.org>
and subject line Re: Bug#990515: release.debian.org: buster->bullseye upgrade issue: sshfs is not upgraded due to fuse/fuse3
has caused the Debian Bug report #990515,
regarding release.debian.org: buster->bullseye upgrade issue: sshfs is not upgraded due to fuse/fuse3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
990515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990515
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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.

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


Andreas

--- End Message ---
--- Begin Message --- 
Hi,

On 06-07-2021 14:52, Andreas Beckmann wrote:
> On 01/07/2021 12.04, Andreas Beckmann wrote:
>> I'm just trying the attached patch which seems to solve the issue for
>> the kde metapackages with --install-recommends
>> kdeconnect is the one depending on sshfs, so it's a good candidate to
>> ensure we get fuse3 installed.
> 
> I've filed bugs against sshfs, kdeconnect and freedombox to add
>   Breaks: fuse (<< 3)
>   Depends: fuse3 (>= 3)
> which seems to be sufficient to solve all the cases where sshfs was not
> being upgraded.

These have been uploaded and I unblocked them.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: