-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
ipfs update not working #2460
Comments
That error message is fixed in an updated version of go-ipfs; it now directs the user to ipfs-update. (Is this a catch 22?---unable to update because an update is required to know how to update.) |
Sadly that requires me to manually install ipfs-update, but no problem. However, I tried to install v0.4.0-dev, which yails then with the following mesage:
|
@sexybiggetje I couldnt reproduce the issue youre having. It appears from the log output that your source tree for fs-repo-migrations might be dirty. Could you try removing |
Well that got me a step further, but I now get the strangest error :).
But I think that's a message from go itself? |
Yeah, thats kinda really weird. I'll look into that... |
what happens if you run |
It gives a similar result.
I think I should figure this one out seperately from this issue, it should be go related. I'm able to do a simple hello world with go, but somehow the paths are not playing nice. I'll completely remove go and try again on a fresh installation. |
@sexybiggetje cool, let me know how it goes. |
@sexybiggetje can this be closed? |
I used the installer as linked on the ipfs.io install page. This is the OS X v0.3.11 package (http://dist.ipfs.io/go-ipfs/v0.3.11/go-ipfs_v0.3.11_darwin-amd64.tar.gz).
After install I like to check if I'm up to date, so we issue ipfs update:
I'm now left curious as to what wasn't installed, and how to properly fix this. I do have go 1.6 installed and not 1.5, but that shouldn't be too much of a difference for this operation.
The text was updated successfully, but these errors were encountered: