Bug#927221: gvfs-fuse version-specific depend on fuse (>= 2.8.4) blocks trans to fuse3

2019-04-16 Thread Simon McVittie
On Tue, 16 Apr 2019 at 09:22:53 -0500, Ron Lovell wrote: > Building a modified package locally is something I certainly need to > learn how to do, so I'll work on that. Then I know I can test fuse- > exfat, the existing sshfs 2, and set up a Samba server. For what it's worth, after patching

Bug#927221: gvfs-fuse version-specific depend on fuse (>= 2.8.4) blocks trans to fuse3

2019-04-16 Thread Ron Lovell
On Tue, 16 Apr 2019 14:24:21 +0100 Simon McVittie wrote: > Does fuse3 provide everything that's needed to mount and unmount older > FUSE filesystems that are still linked to libfuse2, like gvfs-fuse? > > If it does, then gvfs-fuse can depend on fuse (>= 2.8.4) | fuse3, or > just depend on plain

Bug#927221: gvfs-fuse version-specific depend on fuse (>= 2.8.4) blocks trans to fuse3

2019-04-16 Thread Simon McVittie
On Tue, 16 Apr 2019 at 07:27:51 -0500, Ron Lovell wrote: > Is the current dependency of gvfs-fuse on fuse (>=2.8.4) really > necessary? Would a dep on simply 'fuse' suffice? Does fuse3 provide everything that's needed to mount and unmount older FUSE filesystems that are still linked to libfuse2,

Bug#927221: gvfs-fuse version-specific depend on fuse (>= 2.8.4) blocks trans to fuse3

2019-04-16 Thread Ron Lovell
Package: gvfs-fuse Version: 1.38.1-3 Severity: important Dear Maintainer, Basically this regards the transition from fuse to fuse3, my primary motivation being to make the (Debian) world safe for a modern sshfs (3.5+). As others have pointed out (g.e. Bug #918984), trying to replace fuse with