-
Notifications
You must be signed in to change notification settings - Fork 0
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
Installation fails on Pirateship for Pi #1
Comments
are you installing using the root user? |
@treehouse-su @mafintosh Yup, installing as root.
^ This line seems to be like an obvious issue, but then it changes dir and that seems ok.
^ This line I think is the most telling. My guess is that |
|
@rjsteinert try running it with |
Trying... |
Running it on a Pi-1b which takes some time. Will boot a Pi-2b in parallel. |
Same story on Pi-2b.
|
Ok :( we are setting up prebuilds for leveldown for Raspberry Pi tomorrow. That should fix this going forward. I'll ping you in this thread when they are online. |
Thanks @mafintosh - builds of leveldown would certainly speed things up. I'm now going to attempt to update some things in the Pirateship for Pi environment and run again.
|
Similar looking error. We haven't ruled out this being an issue specific to Pirateship for Pi yet so I'm going to try the above commands on a stock Raspbian image.
|
Tried ^ and received segmentation fault. With help from @treehouse-su (dogi) he explained how some debs for node work for Pi-1b and some work for Pi-2b. I now have the following running on an Pi-1b on top of latest Raspbian.
The next step is running the Pi-2b script on a Raspbian build. |
Here is output for Pi-1b on Raspbian using the script above for getting node 0.12.6 from herokuapp.
|
@mafintosh Perhaps we move this issue to the |
|
And then this worked... getting closer.
|
Note, on Pirateship for Pi, there is a |
In conclusion (without testing on R-Pi 2), the key here was setting node to 0.12.x and using the |
*In conclusion (without testing on R-Pi 2), the key here was setting node to 0.12.x (with the right deb for the corresponding R-Pi version) and using the --unsafe-perm flag when installing dat. |
with
it worked also for R-PI 2b on pirateship image what I am about to release |
Good team work everyone @mafintosh @treehouse-su! Todo before closing this:
|
Manually running
npm install dat-g
on Pirateship for Pi results in a fail.The text was updated successfully, but these errors were encountered: