-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mounting fails: Could not find fusermount binary #51
Comments
Do you have FUSE installed? If not, there should be a package available in
|
There is another package called
But I think I already installed that as part of the TMSU Go dependencies. The main problem here seems to be that it looks for |
Hi, sorry, yes, did not notice that as I was reading it on my phone. You are indeed correct in that looking wrong. I shall take a look a little later on today. Thanks for reporting this issue. |
Thanks! I think I found the source of the problem, and it's an "upstream bug" in this file, it looks for "/bin/fusermount" in the PATH, which it can't find (I don't have "/usr" in my PATH). It was introduced only recently, and should be fixed if I use the latest stable version instead. I'll raise the issue in the go-fuse project and come back here to close this as soon as I have tested it with the stable version of go-fuse. |
Great. Many thanks for investigating and letting me know.
|
Okay, while there is no stable version of go-fuse, checking out an older state of the repo worked, TMSU compiles and passes the tests now. |
Great, thanks. |
Hello,
since the current stable release does not work for me, I wanted to confirm the error by compiling it myself before creating an issue for it. Unfortunately, I can't seem to get that to work either. While it compiles fine, it gives an error during the unit tests (and also when using
tmsu mount
):Output of
whereis fusermount
:I believe that it is a problem with my system / environment or with Go (I have never worked with or compiled anything with Go before).
printenv
does not show anything pointing to/bin/bin
, though. Does Go use a different environment variable with a strange default value or something? The problem exists on both the master branch and the v0.5 branch. My apologies if this is not actually a TMSU error but an error on my system, feel free to close the issue if that is the case.Thanks in advance.
Edit:
go env
output:go version
:go version go1.4.2 linux/amd64
The text was updated successfully, but these errors were encountered: