-
Notifications
You must be signed in to change notification settings - Fork 107
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
FYI nix unstable is broken right now, avoid updating #296
Comments
Workaround (untested):
source: NixOS/nixpkgs#124215 (comment) |
Workaround isn't working placing that nix setting here, but this is probably the wrong place: ❯ git diff lib/devos/mkHosts.nix
diff --git a/lib/devos/mkHosts.nix b/lib/devos/mkHosts.nix
index 8e2a799..ee2abb2 100644
--- a/lib/devos/mkHosts.nix
+++ b/lib/devos/mkHosts.nix
@@ -33,6 +33,7 @@ let
hardware.enableRedistributableFirmware = lib.mkDefault true;
+ nix.sandboxPaths = [ "/bin/sh" ];
nix.nixPath = [
"nixpkgs=${nixos}"
"nixos-config=${self}/lib/compat/nixos"
devos2 big-mass-of-changes 「↪ 𝚫 ✔ 📁 」 ⎔ on (us-east-1)
❯ nix-shell --pure --run "nix show-config | grep sandbox-paths"
warning: Git tree '/home/cody/devos2' is dirty
sandbox-paths = |
I got around it by doing the other fix suggested in that thread: ❯ git diff lib/devos/mkHosts.nix
diff --git a/lib/devos/mkHosts.nix b/lib/devos/mkHosts.nix
index 8e2a799..5ffa4f9 100644
--- a/lib/devos/mkHosts.nix
+++ b/lib/devos/mkHosts.nix
@@ -38,6 +38,7 @@ let
"nixos-config=${self}/lib/compat/nixos"
"home-manager=${inputs.home}"
];
+ documentation.info.enable = lib.mkForce false; Then sandboxPaths was fixed and I could switch to the newest nix unstable that fixes this issue (I think, we'll see). |
Thanks for your report and links to upstream! At this moment, is there anything left for us to track here? |
Nope, things are all good for me now and I assume the windows for others to encounter this is closed now. |
Just tested with flk core to rule out it being my config:
People are working on it, this is the related issue: NixOS/nixpkgs#124215
The text was updated successfully, but these errors were encountered: