-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
bug: mkPackageOption has unexpected argument extraDescription #4119
Comments
That argument to At a glance I'd say your actual |
I just went insane.
I wasn't actually sure how to fix this because I don't know where channel data is stored or how Nix determines which user's channel to use when it's called... but I ended up nuking Nix and reinstalling from scratch. If a channel is owned by root how do you get it to be owned by your user on MacOS? Before nuking, I tried deleting all the channels with I tried chowning random directories to my user but that didn't work either. I wasn't sure what I was supposed to chown because there are a billion directories related to Nix. Is it somewhere in the nix store? Is it So I ended up doing a So, anyway, then I did
After I had installed Nix, adding the home-manager failed because of this bug: NixOS/nix#876 I... think another reboot fixed this. Can't remember. I had to reboot several times during the installation process to resolve issues. After getting channels to work I ran into this bug: #3734 Supposedly this is fixed in home-manager but I ran into it anyway. I fixed it by running After all that I got I'm not even sure how this broke, to be honest. None of my configuration changed. I'm thinking maybe I accidentally ran a Nix command with |
Sounds like a nightmare! Nix uses and manipulates channels for the user invoking it. So if you use I don't think there's anything in particular to be done on this issue, so I'm going to close it. Sorry you had such a bad experience! |
Are you following the right branch?
Is there an existing issue for this?
Issue description
MacOS home-manager seems to be broken for SSH:
This has been going on for, I dunno, a month.
Maintainer CC
No response
System information
The text was updated successfully, but these errors were encountered: