-
Notifications
You must be signed in to change notification settings - Fork 42
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
404 Not Found - for migration on OpenBSD #100
Comments
Downloading this repo, and running the migration manually seems to work fine:
So, perhaps we just need to add the openbsd GOOS binary here? |
We distribute through https://github.com/ipfs/distributions which doesn't appear to support OpenBSD. I'll look into adding support now. |
Fixed and released. Note: I've also uploaded OpenBSD binary builds to dist.ipfs.io. |
tested and confirmed from my end. thanks! |
strange...it was working...now I'm getting a 404 again. :( |
What architecture? Could also just be DNS issues.
|
OpenBSD amd64
|
Ah... I forgot. go-ipfs hard-codes the dist URL so we can't really fix this without a release. Options:
Given that you're shipping a port, option 4 is probably the best. |
makes sense to me. i just verified #3 works. i'll work to add a patch to the code locally when building for OpenBSD (#4). thank you. |
I'm in the process of updating the ipfs package/port for OpenBSD, and have noticed fs-migrations fail.
The current package/port builds ipfs-0.4.22, and when attempting to run the ipfs-0.5.1 binary (easily built with
make build
), I see the following error:I'd like for this to work so updating a the go-ipfs package from the older (0.4.22) version to the newer (0.5.1 and beyond) will "just work".
I suspect some work needs to be done to remove the $GOOS ("openbsd" here) details from the filename...how different can these be between linux and openbsd?
The text was updated successfully, but these errors were encountered: