-
-
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
Error: HOME is set to "/Users/xxx" but we expect "/var/empty" #4026
Comments
You should probably set your |
Hmm, it seems like Home Manager's |
Wow, It works after setting |
Ouch. I'm not sure what the correct way to use nix-darwin is in this case. It seems you are expected to explicitly set the home directory? There doesn't seem to be an @LnL7 The default home directory of a user in nix-darwin seems to be set to We recently introduced a check in the Home Manager activation script that verifies that the user that the script is built for matches the user running the activation. This check led to this issue since @sxyazi had missed to set the home directory in the nix-darwin configuration. The home directory option was originally introduced in LnL7/nix-darwin@b8713d5 and as far as I can tell it is mostly unchanged since then. Perhaps nix-darwin could have something similar to NixOS's |
Thanks for the clear elaboration, so far it looks like setting If so I will file an issue for nix-darwin and ask them to add the |
@sxyazi I had the same problem after updating flakes just now. For now I used the |
Signed-off-by: Spencer Heywood <l.spencer.heywood@protonmail.com>
See nix-community/home-manager#4026 for more details.
Apparently there's some bug here that isn't solved: Conversation about hotfix: nix-community/home-manager#4026 Ticket about realfix: LnL7/nix-darwin#682
Are you following the right branch?
Is there an existing issue for this?
Issue description
I encountered the error when I rebuilt after updating.
It's supposed to be caused by 6a19225. I'm on the Darwin system.
Maintainer CC
@rycee
System information
The text was updated successfully, but these errors were encountered: