Description of problem: A significantly newer version of (fuse-)sshfs has been released. Version-Release number of selected component (if applicable): 2.8-5 Additional info: fuse-sshfs has received a reworking, and is on a 3.x release plan, 3.3.2 by now. The significant changes for 3.x are listed in the 3.0.0 release notes: https://github.com/libfuse/sshfs/releases/tag/sshfs-3.0.0 It requires fuse3, which is part of F27++. The step to sshfs 3.x could have long been done by including 3.3.x in the F28 release cycle, but *oh well*. Next chance with F29. (I have been using a self-built 3.3.1 of F27 successfully for some time.) This package doesn't seem to be linked to release-monitoring for some reason, though a Fedora mapping does exist on this page: https://release-monitoring.org/project/11058/
I have builds of fuse-sshfs-3.x in my personal copr: https://copr.fedorainfracloud.org/coprs/barsnick/fed-newer/package/fuse-sshfs/ The SPEC is updated with the newest dependencies, but somewhat convoluted, due to fallback support for systems without fuse3: http://copr-dist-git.fedorainfracloud.org/cgit/barsnick/fed-newer/fuse-sshfs.git/tree/fuse-sshfs.spec
@Peter, are you still maintaining this package? Would you like help?
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
(In reply to Michael Cronenworth from comment #2) > @Peter, are you still maintaining this package? Would you like help? Yes, please. I can't find a time to maintain this.
OK. I'll ship 2.10 in F27, F28 and look to ship 3.4.0 in F29+. I'm not taking ownership of the package, but I will do this one-time update.
3.4.0 is now in F29+.