You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed this issue while trying to remove the ssh configs from a server I manage. The server has home-manager installed stand-alone.
Removing all the ssh configs does not remove the ssh_config file linked to the old generation. Somehow deploy-rs is inhibiting home-manager's cleanup functions.
I suspect it might have something to do with the fact that deploy-rs ends up creating two separate generations for every home-manager deployment but I haven't looked too deep into it. Will try to look into it further and update this issue.
The text was updated successfully, but these errors were encountered:
by default the profile name ended up being "home-manager" and this ended up squeezing the "activatable-home-manager-generation" into the home-manager generations and preventing the cleanup.
Could we perhaps document how to properly use home-manager standalone with deploy-rs in the README?
I noticed this issue while trying to remove the ssh configs from a server I manage. The server has home-manager installed stand-alone.
Removing all the ssh configs does not remove the ssh_config file linked to the old generation. Somehow deploy-rs is inhibiting home-manager's cleanup functions.
I suspect it might have something to do with the fact that deploy-rs ends up creating two separate generations for every home-manager deployment but I haven't looked too deep into it. Will try to look into it further and update this issue.
The text was updated successfully, but these errors were encountered: