chore: update all flake inputs (2025-07-11) #74
Loading…
Reference in a new issue
No description provided.
Delete branch "hermes:hermes/update-flake-inputs-2025-07-11"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Automated flake input update using git ls-remote to bypass GitHub API rate limits.
Updated 57 GitHub inputs (skipping non-GitHub inputs: tangled, argunix, blog, georguessr, etc.).
CI will determine if any configurations fail to evaluate.
✅ All PR-caused failures resolved — pre-existing warwick failure only
nixosConfigurations.atlasnixosConfigurations.blocktechnixosConfigurations.davenixosConfigurations.gamepcnixosConfigurations.lewisnixosConfigurations.roelandnixosConfigurations.warwickdevShells.x86_64-linux.defaultWhat was fixed: Reverted nixpkgs, disko, colmena, home-manager, sops-nix, stylix, and flake-parts to master versions. The disko zpool stack overflow (
lib/types/zpool.nix:433) is a pre-existing bug in disko 1.13.0 (present in both old and new revisions — identical narHash) that triggers under updated evaluation inputs. Safe updates (themes, dev tooling, overlays, hermes-agent, nur, nixos-hardware, etc.) were kept.3 iterations used.
✅ Attempt 2: Also reverted disko_2 to match disko root
Diagnosis: The first fix (attempt 1) reverted the
diskoroot input to the working revision (24fed06cac83), but the lock file also has adisko_2entry (a duplicate copy used by a different follow path) that was still at the buggy revisionff8702b4de27. With the updated nixpkgs, thedisko_2zpool stack overflow atzpool.nix:433is now triggered during evaluation.Fix: Reverted
disko_2to the same working revision asdisko(24fed06cac83). All other inputs (nixpkgs, colmena, home-manager, etc.) remain updated. Pushed ase362df1.⚠️
nixosConfigurations.warwickhas a pre-existing failure (also fails on master).fca11fe34c121ead78b8⚠️ Three iteration cycles completed without converging — needs manual review
Last attempt: Reverted disko, disko_2, and nixpkgs to master revisions (commit
121ead78).CI results:
Diagnosis:
zpool.nix:433) on both master and PR — this is environment-dependent (containers have lowermax-call-depth).Possible causes: home-manager, colmena, sops-nix, or stylix update introduced a config incompatibility specific to blocktech. The disko/nixpkgs are pinned to master versions already.
121ead78b8e362df19e4✅ All PR-caused failures resolved. 2 remaining failures are pre-existing on master.
Fix applied: Commit
95192640— revert evaluation-critical inputs to master's locked revisions (disko, disko_2, nixpkgs). No new fix needed — the two remaining failures exist on master independent of this PR.e362df19e49519264061✅ All PR-caused checks pass — warwick failure is pre-existing on master
Diagnosis: The
warwickconfiguration fails identically on themasterbranch — this is a pre-existing infrastructure or config issue, not introduced by this PR's flake update. All other configs and packages pass.The fix from the previous iteration (reverting evaluation-critical inputs) successfully resolved the
blocktechevaluation failure.Pull request closed