Home-Manager not working as anticipated about nix-config HOT 8 CLOSED

Yeah, this is an error from impermanence, it's kinda of a pain they don't tell which mountpoint is conflicted haha.

Okay hm you can try commenting out every home.persistence block (or set persistent = false on your flake), check if it works, and then uncomment half of then and so on, until you know what is conflicting.

from nix-config.

Hey, that was a partial success. home-manager is working with persitance completly disabled. As soon as I enable it (wether or not something else is commented out or not) I get the described error.

Thank you so far. My system is usable now :)

from nix-config.

Thank you for your kind words! I'm really glad I could help out fellow nixers with my configs :D

Hmm, maybe you might have some kind of issue with the new nix profile? home-manager isn't very compatible with it.

I think you can switch back to nix-env by using rm /nix/var/nix/profiles/per-user/$USER/profile.

Let me know if it works!

from nix-config.

Thank you for the fast reply.

Removing of the per-user-profile had the effect, that the home-manager-configuration was build completely (my hopes where getting up). But after completion there is still nothing to be found with home-manager packages. I would really like to use home-manger especially for sway and the cli-config.

If it helps, my configuration is located at nix-config. Feel free to comment on my humble copy of your configuration (at the time I am using Gnome in the host-config as I have to get some things working).

Best Regards

Lutz

from nix-config.

Hey!

I'm hmm... Kinda out of ideas here. You're running something like (of course, with your own user and host) home-manager switch --flake .#misterio@atlas?

You can omit the URI fragment (part after #) if the user@host combination you're switching to is your current user and host (you can verify this with echo $USER@$(hostname).

Additionally (only if you already meet the previous requirement), you can omit the path (part before #) if your flake repository is located at (or symlinked to) ~/.config/nixpkgs.

Maybe try nix build .#[email protected], followed by ./result/activate.

from nix-config.

Thank you for your patience. The home-manager switch -b backup --flake .#lgo@flores was build as expected (I have to use -b backup because of the existing firefox-profile. After the build I got:

Starting Home Manager activation
Activating checkFilesChanged
Activating checkLinkTargets
Activating unmountPersistentStoragePaths
Activating createAndMountPersistentStoragePaths
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option

The same goes for the nix build-approach.

from nix-config.

Glad you got it working :)

Impermanence sure is a tough nut to crack. Enabling one at a time should help!

from nix-config.

Thank you for your patience. The home-manager switch -b backup --flake .#lgo@flores was build as expected (I have to use -b backup because of the existing firefox-profile. After the build I got:

Starting Home Manager activation
Activating checkFilesChanged
Activating checkLinkTargets
Activating unmountPersistentStoragePaths
Activating createAndMountPersistentStoragePaths
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option

The same goes for the nix build-approach.

Indeed, it's a bit annoying, there is no debugging option in the home-manager mode.

I think that during the home-manager switch phase, if an application writes to one of the impermanence mount folders, that impermanence (fuse) cannot mount the whole impermanence.

It's a shame, because the idea was good, but too restrictive, I deactivated it

from nix-config.