-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 on Darwin broken #1468
Comments
@lukeadams we have prepared a fix for this, can you test:
This uses the upcoming Nix 1.11.13 /cc @grahamc |
I can test it later today on a clean VM, but re-running it on my Sierra VM with nix already installed prints this where I assume it would have asked for y/n: |
Hello, in installed this on a clean Sierra machine. Installation worked perfectly as far as i can confirm. Strangely some installed binarys are not working compared to my older El Capitan machine. If i build fish shell via nix it will only open in a debug-mode stating that: <W> fish: Could not set up terminal.
<W> fish: TERM environment variable set to 'xterm-256color'.
<W> fish: Check that this terminal type is supported on this system.
<W> fish: Using fallback terminal type 'ansi'.
<W> fish: Could not set up terminal using the fallback terminal type 'ansi'.
<W> fish: Using fallback terminal type 'dumb'.
<W> fish: Could not set up terminal using the fallback terminal type 'dumb'. Thought this would be my fault, fixed and double-checked terminfo. I assume my issue with htop is about the same:
Spent some hours on this without any success or more informations. maybe someone here has an idea? |
Hi, @dieideeistgut
It's a bug in nix 1.11.12, I think. |
Wow - Didn't know that - Thanks alot! I even tried this before so i must have had a combination of corrupted macos terminfo files and this issue here. Thanks again! |
For what it is worth, 1.11.13 is now released. The TERMINFO is a problem with Nixpkgs, not Nix. The issue has been patched in Nixpkgs already, however the nixpkgs-unstable channel hasn't updated to contain the fix yet. |
The installscript errors on a fresh macOS Sierra VM (full output):
The issue seems to be with the multiuser [y/n] prompts taking piped input from curl, causing it to default to n for all prompts.
Running
allows installation to proceed with no issues.
The text was updated successfully, but these errors were encountered: