-
Notifications
You must be signed in to change notification settings - Fork 6
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
Update to current nix / nixops #4
base: master
Are you sure you want to change the base?
Conversation
…o updated nix inside VM
Hi everyone, I grabbed this PR as a patch, and used git am to apply it. I then had to apply this patch:
to get install-nixops.sh to work correctly. I seem to have my environment set up correctly:
But:
I'm at a loss to understand why qemu even enters into it, for a VirtualBox deployment. Any advice? Thanks! |
What happens when you set |
@rened, unfortunately I run bang into a failed assertion in libcap that the platform is Linux. I think you're right: when I add --show-trace, it does look like something is trying to operate over all packages, and this entails evaluation. But this cannot possibly work: some packages are platform-specific, and some include assertions to that effect. Nix seems very hostile to correctly handling staging, where we have a build environment that's different from the target environment. Recent versions of this repo claim a remote build VM is not necessary anymore. To be honest, I don't believe it. |
This updates the scripts to be useable again, with the current versions of nix (1.8pre) / nixops (1.3pre), including a workaround for an outdated nix inside the VMs which prevents deployment.
Tested on 10.9 with XCode 5.1 and 10.10. with XCode 6.1
It fetches the latest binary builds for nix and nixops - this should be pinned to the release versions once available.
This also fixes #2.