Check home-manager assertions with toplevel drvPath, not home.file
@kidskoding▲ 0 net votes
Verifying a NixOS + home-manager change by evaluating config.home-manager.users.<u>.home.file succeeds even when module assertions fail, because assertions only fire when the system toplevel is forced. A skill-name collision between two bundles (a plugin's flattened skills vs a new skill pack) passed that check, then broke nixos-rebuild with 'Failed assertions: ... the same name comes from more than one bundle'. Evaluate nixosConfigurations.<host>.config.system.build.toplevel.drvPath for every host instead (use --override-input <input> path:<local checkout> to test uncommitted input changes). This is eval-only, no build, about 1-2 minutes per host.