Skip to content
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

After macOs 15.1 update nix get nuked, the installer fails at reinstalling it #11805

Closed
1 of 3 tasks
boborbt opened this issue Nov 4, 2024 · 3 comments
Closed
1 of 3 tasks

Comments

@boborbt
Copy link

boborbt commented Nov 4, 2024

Platform

  • Linux:
  • macOS
  • WSL

Additional information

As mentioned in the subject, macOs 15.1 update nukes the nixos installation. Trying reinstalling nix fails.

Output

Please see the stderr and stdout outputs in the attached files.
stderr.log
stdout.log

@cole-h
Copy link
Member

cole-h commented Nov 4, 2024

How do you mean "nix get nuked"? It's no longer available on your PATH? If so, you may want to take a look at this issue: #3616

This happens because macOS updates overwrite the various profile files that we write the "please add Nix tools to the PATH" snippet to.

@boborbt
Copy link
Author

boborbt commented Nov 5, 2024

How do you mean "nix get nuked"? It's no longer available on your PATH? If so, you may want to take a look at this issue: #3616

Unfortunately I’m not able to be very specific since I removed and reinstalled nix to workaround the problem. From what I remember the whole /nix directory appeared to be empty, but I learnt that during one of the first checks I did and I’m now afraid I missed something less dramatic like the issue you are mentioning.

I’ll report more information here in case I’ll encounter the problem again.

@abathur
Copy link
Member

abathur commented Nov 5, 2024

Since it doesn't sound like we have anything actionable here for now, I'm going to tentatively close this specific issue.

If you do run into this again and open a new issue, can you include a single copy of the output of the process in your terminal instead of the split stderr/out files? (I didn't see anything obvious in the stderr log here, but it's generally more helpful to see any error messages in context rather than separate.)

@abathur abathur closed this as not planned Won't fix, can't repro, duplicate, stale Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants