Bug 226398 - sysutils/fusefs-sshfs: failed to mount file system
Summary: sysutils/fusefs-sshfs: failed to mount file system
Status: Closed Unable to Reproduce
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Many People
Assignee: Muhammad Moinur Rahman
URL:
Keywords: patch, regression
Depends on:
Blocks:
 
Reported: 2018-03-06 19:33 UTC by nielsensanders@gmail.com
Modified: 2018-12-31 18:35 UTC (History)
7 users (show)

See Also:
bugzilla: maintainer-feedback? (bofh)


Attachments
Additional port sysutils/fusefs-ssfs2 (3.06 KB, text/plain)
2018-04-03 17:40 UTC, Harald Schmalzbauer
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description nielsensanders@gmail.com 2018-03-06 19:33:09 UTC
anders@kontorbsd:~ % sshfs anders@127.0.0.1:/ fisk
mount_fusefs: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ on /usr/home/anders/fisk: No such file or directory
fuse: failed to mount file system: No error: 0


happens at the latest build and sems to be happening from the upgrade to 3.3 (r453084) 

last working version is (r442599) i read the man pages and cant see anything happening so i am reporting this as a bug.

this happens on various FreeBSD-current builds and trueos.
Comment 1 strangeqargo 2018-03-09 21:06:39 UTC
(In reply to nielsensanders@gmail.com from comment #0)
can confirm, 12-CURRENT
Comment 2 Mateusz Piotrowski freebsd_committer freebsd_triage 2018-03-10 01:51:49 UTC
Same here. FreeBSD 12.0-CURRENT r330529 amd64, fusefs-sshfs: 3.3.1.
Comment 3 Muhammad Moinur Rahman freebsd_committer freebsd_triage 2018-03-22 13:44:19 UTC
(In reply to Mateusz Piotrowski from comment #2)
After upgrading to fusefs library 3 this bug has occurred. Can anyone confirm with 2?
Comment 4 Daniel Kolesa 2018-04-02 23:52:34 UTC
Confirmed broken here as well. I will try with fusefs libs 2...
Comment 5 Harald Schmalzbauer 2018-04-03 08:27:52 UTC
I can't even compile sysutils/fusefs-sshfs due to (python)USES madness, which seems to hit a version dependency race.
It's easy reproducable (meson seems to need python3, while 'rst2man', defined as build dependency in fusefs-sshfs Makefile installs py27-docutils-0.14_1 – meson won't build afterwards).
Since Makefiles are more or less empty these days, it's very hard for part-time porters to follow such "simple" dependency failures.
Here's the build machine:
pkg info     
cpdup-1.18                     Comprehensive filesystem mirroring and backup program
dialog4ports-0.1.6             Console Interface to configure ports
gettext-runtime-0.19.8.1_1     GNU gettext runtime libraries and programs
gettext-tools-0.19.8.1         GNU gettext development and translation tools
gmake-4.2.1_2                  GNU version of 'make' utility
indexinfo-0.3.1                Utility to regenerate the GNU info page index
libffi-3.2.1_2                 Foreign Function Interface
liblz4-1.8.1.2,1               LZ4 compression library, lossless and very fast
pkg-1.10.5                     Package manager
pkgconf-1.4.2,1                Utility to help to configure compiler and linker flags
readline-7.0.3_1               Library for editing command lines as they are typed
rsync-3.1.3                    Network file distribution/synchronization utility

/usr/ports/sysutils/fusefs-sshfs/#: make

===>  License GPLv2 accepted by the user
===>   fusefs-sshfs-3.3.1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by fusefs-sshfs-3.3.1 for building
===>  Extracting for fusefs-sshfs-3.3.1
=> SHA256 Checksum OK for libfuse-sshfs-sshfs-3.3.1_GH0.tar.gz.
===>  Patching for fusefs-sshfs-3.3.1
===>  Applying FreeBSD patches for fusefs-sshfs-3.3.1
===>   fusefs-sshfs-3.3.1 depends on executable: rst2man - not found
===>  License BSD2CLAUSE GPLv3+ PD PSFL accepted by the user
===>   py27-docutils-0.14_1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by py27-docutils-0.14_1 for building
===>  Extracting for py27-docutils-0.14_1
=> SHA256 Checksum OK for docutils-0.14.tar.gz.
===>  Patching for py27-docutils-0.14_1
===>   py27-docutils-0.14_1 depends on package: py27-setuptools>0 - not found
===>  License MIT accepted by the user
===>   py27-setuptools-39.0.1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by py27-setuptools-39.0.1 for building
===>  Extracting for py27-setuptools-39.0.1
=> SHA256 Checksum OK for python/setuptools-39.0.1.zip.
===>  Patching for py27-setuptools-39.0.1
===>   py27-setuptools-39.0.1 depends on file: /usr/local/bin/python2.7 - not found
===>  License PSFL accepted by the user
===>   python27-2.7.14_1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by python27-2.7.14_1 for building
===>  Extracting for python27-2.7.14_1
=> SHA256 Checksum OK for python/Python-2.7.14.tar.xz.
===>  Patching for python27-2.7.14_1
===>  Applying FreeBSD patches for python27-2.7.14_1
===>   python27-2.7.14_1 depends on package: pkgconf>=1.3.0_1 - found
===>   python27-2.7.14_1 depends on executable: msgfmt - found
===>   python27-2.7.14_1 depends on shared library: libffi.so - found (/usr/local/lib/libffi.so)
===>   python27-2.7.14_1 depends on shared library: libreadline.so.7 - found (/usr/local/lib/libreadline.so.7)
===>   python27-2.7.14_1 depends on shared library: libintl.so - found (/usr/local/lib/libintl.so)
===>  Configuring for python27-2.7.14_1
configure: loading site script /usr/ports/Templates/config.site
checking build system type... amd64-portbld-freebsd11.1
checking host system type... amd64-portbld-freebsd11.1
checking for python2.7... no
checking for python3... no
checking for python... no
checking for --enable-universalsdk... no
...
Move: bin/rstpep2html --> bin/rstpep2html-2.7
Link: @bin/rstpep2html --> bin/rstpep2html-2.7
====> Compressing man pages (compress-man)
===>  Installing for py27-docutils-0.14_1
===>  Checking if py27-docutils already installed
===>   Registering installation for py27-docutils-0.14_1 as automatic
Installing py27-docutils-0.14_1...
===>   fusefs-sshfs-3.3.1 depends on executable: rst2man - found
===>   Returning to build of fusefs-sshfs-3.3.1
===>   fusefs-sshfs-3.3.1 depends on executable: msgfmt - found
===>   fusefs-sshfs-3.3.1 depends on executable: meson - not found
===>  License APACHE20 accepted by the user
===>   meson-0.45.1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by meson-0.45.1 for building
===>  Extracting for meson-0.45.1
=> SHA256 Checksum OK for meson-0.45.1.tar.gz.
===>  Patching for meson-0.45.1
===>  Applying FreeBSD patches for meson-0.45.1
===>   meson-0.45.1 depends on package: py36-setuptools>0 - not found
===>   meson-0.45.1 depends on package: py36-setuptools>0 - not found
*** Error code 1                        

Stop.
make[1]: stopped in /usr/ports/devel/meson
*** Error code 1

Stop.
make: stopped in /usr/ports/sysutils/fusefs-sshfs

Who's responsible? ports/Mk? devel/python? devel/meson? sysutils/fusesshfs?

IMHO, ports/Mk needs to be freezed (development in trunk and merged after beeing tested/approved).  A decade ago, I almost never had a problem with any port to compile.  These days, almost every time I try, I get make[1]: stopped in /usr/ports/... as result.
And so many packages depend on build(-only) tools – python on foremost front.
meson seems to be a new make-everything-unfixable tool :-(
IMHO, since fusefs-sshfs has nothing to do with GNOME, compiling it on FreeBSD shouldn't lock it to GNOME!  I'm happy if I can provide patches to fix things, but I can't go through all that GNOME-build stuff.  This dependency locking is a big time consuming monster – instead of writing one 5 lines more in a Makefile...
So to get to the point where one can analyze what/how USES=fuse:3 broke fusefs-sshfs, one must waste time analyzing/fixing the GNOME build infrastructure first – there's something wrong IMHO.

-harry
Comment 6 Daniel Kolesa 2018-04-03 15:10:05 UTC
I modified the fusefs-sshfs to build the 2.10 version and I can confirm that the 2.10 version works, unlike any of the 3.* ones based on new libfuse. It's hard to tell whether it's a libfuse problem or sshfs, considering sshfs 3.x can only use libfuse 3.x and sshfs 2.x uses libfuse 2.x.
Comment 7 Harald Schmalzbauer 2018-04-03 17:40:11 UTC
Created attachment 192175 [details]
Additional port sysutils/fusefs-ssfs2

Thanks for testing, Daniel.
Since e.g. fusefs-ntfs still depends on sysutils/fusefs-libs (not sysutils/fusefs-libs3) I can imagine people want the 2-version as alternative port.
Attached is a shell archvie for such a port which is named fusefs-sshfs2.
I'd prefere the other way, current sysutils/fusefs-ssfs becomes sysutils/fusefs-ssfs3!!!
But for anyone stumbling across this report and needs a working version, please find attached.
GPG signature verified (against the different tarball (which the signature is for) from GH but I verified that the extractet content of both tarballs is equal, so the tarball our port can be considered valid with the distinfo in the shar).
Comment 8 Dmitry Afanasiev 2018-05-10 14:33:41 UTC
sysutils/fusefs-ssfs2 from attachment works fine, thanks You!
Comment 9 Daniel Kolesa 2018-05-10 14:56:40 UTC
sure, older sshfs works, but we should probably figure out why the newer one is broken... but yeah, for now having a workaround is good.
Comment 10 Roman Bogorodskiy freebsd_committer freebsd_triage 2018-11-14 15:40:51 UTC
Could you try sshfs with the recent update of sysutils/fusefs-libs3: https://docs.freebsd.org/cgi/getmsg.cgi?fetch=1152083+0+current/svn-ports-all ?
Comment 11 Muhammad Moinur Rahman freebsd_committer freebsd_triage 2018-11-30 10:41:52 UTC
I have updated fusefs-sshfs to 3.5.0. Can anyone please share some feedback?
Comment 12 Muhammad Moinur Rahman freebsd_committer freebsd_triage 2018-12-31 18:31:32 UTC
As of Version 3.5.0 I am unable to reproduce the scenario on HEAD aka 13.
Comment 13 Daniel Kolesa 2018-12-31 18:35:18 UTC
works for me now