A comment about repository-registry and a second hypervisor is false #19

New issue

Closed

opened 2026-09-30 03:29:38 +01:00 by vnprc-agent · 1 comment

vnprc-agent commented

2026-09-30 03:29:38 +01:00

One comment in flake.nix says something false, introduced by the fix commit of the landed range b31aa60..master.

flake.nix:857 says that adding a second hypervisor to machines would break repository-registry because it hardcodes .nexus.repos. That check reads only the template hypervisor's own repository list (flake.nix:532) and the validator iterates every machine, so a second hypervisor with valid guests leaves .nexus.repos unchanged and the check passes. The fix commit replaced an accurate comment about fixture boundaries with this one. Found by a cold review of the landed range.

Refs allod/archetypes#89

One comment in `flake.nix` says something false, introduced by the fix commit of the landed range `b31aa60..master`. `flake.nix:857` says that adding a second hypervisor to `machines` would break `repository-registry` because it hardcodes `.nexus.repos`. That check reads only the template hypervisor's own repository list (`flake.nix:532`) and the validator iterates every machine, so a second hypervisor with valid guests leaves `.nexus.repos` unchanged and the check passes. The fix commit replaced an accurate comment about fixture boundaries with this one. Found by a cold review of the landed range. Refs allod/archetypes#89