Description of problem: fuse-sshfs 2.5 is out. Any reason not to update to it? Noticed as I was about to do a build for EPEL7.
Version 2.5 is out there: http://sourceforge.net/projects/fuse/files/sshfs-fuse/2.5/ The list of changes is pretty short: * Add -o disable_hardlink option (debian bug #670926). Reported by Louis-David Mitterrand * Optimize readdir by sending multiple requests in parallel. Add -o sync_readdir to restore old behavior. Patch by Alexander Neumann * Map SSH2_FX_FAILURE to ENOTEMPTY for rmdir. Reported by Ross Lagerwall * When checking root directory use LSTAT not STAT. This prevents I/O error being returned after a successful mount if a symlink is mounted. Reported by Bart Friederichs Seemed minor, so I updated it in the epel7 branch.
I built 2.5 locally on Fedora 20 (x86_64) and it works fine - it does indeed fix the mounting symlink corner case.
Still waiting for this. I have built it here, successfully: http://copr.fedoraproject.org/coprs/barsnick/fed-newer/build/25447/ Repo info: http://copr.fedoraproject.org/coprs/barsnick/fed-newer/ To enable: $ dnf copr enable barsnick/fed-newer (requires dnf-plugins-core)
This is a reminder according to https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers Please respond ASAP why this package should not be updated, allow others to update it or orphan it so a new maintainer can pick it up.
fuse-sshfs-2.5-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/fuse-sshfs-2.5-1.fc21
Package fuse-sshfs-2.5-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fuse-sshfs-2.5-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-16988/fuse-sshfs-2.5-1.fc21 then log in and leave karma (feedback).
fuse-sshfs-2.5-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.