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

Home Manager on Darwin activation failure (Existing file... ) #710

Closed
khaneliman opened this issue Jan 13, 2025 · 2 comments
Closed

Home Manager on Darwin activation failure (Existing file... ) #710

khaneliman opened this issue Jan 13, 2025 · 2 comments

Comments

@khaneliman
Copy link

Been getting this for a while, not sure when it started, yet. It prevents the home-manager configuration changes from being applied until I manually remove the sops-nix plist file and then run my flake switch again. Happens with every activation. Just wondering if others have seen it, too.

Activating checkFilesChanged
Activating checkKittyTheme
Activating checkLaunchAgents
Existing file '/Users/khaneliman/Library/LaunchAgents/org.nix-community.home.sops-nix.plist' is in the way of '/nix/store/1mi0iig898yyqk23gzkng4yg4dqpqzw7-home-manager-agents/org.nix-community.home.sops-nix.plist'
removed '/Users/khaneliman/.local/state/home-manager/gcroots/new-home'
@khaneliman khaneliman changed the title Sops-nix home-manager on Darwin activation failure Home Manager on Darwin activation failure (Existing file... ) Jan 13, 2025
@Mic92
Copy link
Owner

Mic92 commented Jan 14, 2025

Maybe report this in the home-manager repository. sops-nix is just using it's interface.

@khaneliman
Copy link
Author

Sorry, thought it was something unique to sops-nix implementation of the activation logic. Tried git bisecting sops-nix and couldn't find a trigger reason for it. After a bunch of flake updates with all my inputs I haven't been seeing it as consistently anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants