Skip to content

asahi: HM takeover of existing /home/da — backups, stale hm-v3 state, substituter shadowing #64

Description

@cernoh

ASAHI's da home was previously managed by standalone hm-v3 (home-manager switch as user service). After the dendritic switch, HM activation moves in-tree via home-manager-da.service. Expect and remediate:

  • Dotfile churn: home-manager.backupFileExtension = "hm-backup" will rename any pre-existing file the new config also manages. Sweep after first switch:
    find /home/da -name '*.hm-backup' -not -path '*/.cache/*'
    Diff each against its replacement; delete or port customizations back through this repo.
  • Old hm-v3 generations linger in da's user profile (home-manager generations). They still activate on demand and can confuse rollbacks. Once the new path is stable:
    home-manager expire-generations "1 day ago"
    (run as da; do NOT run the old hm-v3 checkout's switch again afterwards)
  • User-level nix conf shadowing: hm-v3 may have left/generated ~/.config/nix/nix.conf. A stale one overrides system substituters/trusted settings for that user (documented failure mode: cache.nixos.org silently dropped → massive source builds). Check content after switch; if it exists, either empty it or let the flake's HM layer own it.
  • Session env deltas: EDITOR/VISUAL now pinned to nvim via programming module; zellij default_shell=fish; tmux direnv update-environment list changed. Nothing to fix — just re-login rather than reusing pre-switch shells when verifying.

Related: #63 (pre-switch gate), #62.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions