-
Notifications
You must be signed in to change notification settings - Fork 2
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
fails to build on NixOS #10
Comments
Did you solve this issue? I'm also getting the following warning when running
I am using Arch Linux as host. I am wondering if this is also has anything to do with the " |
@mhuesch can you try again? At that moment the dependencies for this repo were being upgraded, and this one hadn't been yet. @jrhamilton I'm curious... The warning |
I believe I was running out of space after /nix build after using nix-shell which may have been causing the I chose to move the /nix onto a different partition. For the curious, I completely removed Nix from my machine by using the following advice: https://github.com/NixOS/nix/issues/1402 I then re-installed: Before running ATTENTION, SCARY PROCEDURE INCOMING!
Then proceed with As for the Useful links for the above process: |
thanks @guillemcordoba. I am able to build it now, as of
when I run the UI, I am able to execute
if this isn't relevant to other users feel free to ignore - it's ok if I'm not able to build the repo as I've mostly done my learning at this point, just by looking at the code. but if it's useful I'm happy to keep digging and try to get it working. |
hi!
I was looking through this repo as an example Holochain project to help me understand good structuring / practices. it has been helpful in that way - thanks 🙂
when I follow the steps in the README, I encounter an error in
npm install
(technically, inside ofnpm run build-holochain
):I wondered if this had something to do with changes in the
profiles
andinvitations
zones, which were set to track a branch, not a fixed git SHA. but I fixed them with the below patch and still get the same error.The text was updated successfully, but these errors were encountered: