Add an overlay that deselects commitizen's test_invalid_command regression test so the package builds against the Python 3.13.14 in nixos-26.05.
Why
commitizen 4.13.9 keeps per-Python-minor golden files for its CLI regression tests. The py_3_13 golden was captured against an early 3.13, whose argparse did not quote invalid choices. CPython later backported quoting into the 3.13.x line; nixos-26.05 now ships 3.13.14, so the committed golden no longer matches argparse output and checkPhase fails:
This failure blocks the whole home-manager closure (commitizen is a home.packages entry in home/git.nix). The package itself is unaffected — only its own stale test fixture is wrong.
Upgrading the interpreter is not a real fix: 3.14 also quotes and only passes because commitizen ships a matching py_3_14 golden. Getting there would mean either bumping the channel-wide python3 off its 3.13 pin or dragging a second full interpreter into the closure for one CLI tool. Deselecting one stale-golden test is the minimal correct change.
Verification
nixosConfigurations.emmathorpe-edaas.config.system.build.toplevel builds green
checks.x86_64-linux.{formatting,deadnix,statix} all pass
The overlay carries a comment to drop it once nixpkgs refreshes the fixture (or the upstream 3.13.x revert lands).
## What
Add an overlay that deselects commitizen's `test_invalid_command` regression test so the package builds against the Python 3.13.14 in `nixos-26.05`.
## Why
commitizen 4.13.9 keeps per-Python-minor golden files for its CLI regression tests. The `py_3_13` golden was captured against an early 3.13, whose argparse did **not** quote invalid choices. CPython later backported quoting into the 3.13.x line; `nixos-26.05` now ships 3.13.14, so the committed golden no longer matches argparse output and `checkPhase` fails:
```
-cz: error: ... invalid choice: 'x' (choose from init, commit, ...)
+cz: error: ... invalid choice: 'x' (choose from 'init', 'commit', ...)
```
This failure blocks the whole home-manager closure (commitizen is a `home.packages` entry in `home/git.nix`). The package itself is unaffected — only its own stale test fixture is wrong.
Upgrading the interpreter is not a real fix: 3.14 also quotes and only passes because commitizen ships a matching `py_3_14` golden. Getting there would mean either bumping the channel-wide `python3` off its 3.13 pin or dragging a second full interpreter into the closure for one CLI tool. Deselecting one stale-golden test is the minimal correct change.
## Verification
- `nixosConfigurations.emmathorpe-edaas.config.system.build.toplevel` builds green
- `checks.x86_64-linux.{formatting,deadnix,statix}` all pass
The overlay carries a comment to drop it once nixpkgs refreshes the fixture (or the upstream 3.13.x revert lands).
commitizen 4.13.9 ships per-Python-minor golden files for its CLI
regression tests. The py_3_13 golden was captured against an early 3.13
whose argparse did not quote invalid choices. CPython later backported
quoting into the 3.13.x line, and nixos-26.05 now ships 3.13.14, so the
golden no longer matches argparse's output:
-cz: error: ... invalid choice: 'x' (choose from init, commit, ...)
+cz: error: ... invalid choice: 'x' (choose from 'init', 'commit', ...)
This fails commitizen's checkPhase and breaks the home-manager closure.
The package itself is unaffected. Deselect just that test via an overlay
until nixpkgs updates the fixture (or the 3.13.x revert lands upstream).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
Add an overlay that deselects commitizen's
test_invalid_commandregression test so the package builds against the Python 3.13.14 innixos-26.05.Why
commitizen 4.13.9 keeps per-Python-minor golden files for its CLI regression tests. The
py_3_13golden was captured against an early 3.13, whose argparse did not quote invalid choices. CPython later backported quoting into the 3.13.x line;nixos-26.05now ships 3.13.14, so the committed golden no longer matches argparse output andcheckPhasefails:This failure blocks the whole home-manager closure (commitizen is a
home.packagesentry inhome/git.nix). The package itself is unaffected — only its own stale test fixture is wrong.Upgrading the interpreter is not a real fix: 3.14 also quotes and only passes because commitizen ships a matching
py_3_14golden. Getting there would mean either bumping the channel-widepython3off its 3.13 pin or dragging a second full interpreter into the closure for one CLI tool. Deselecting one stale-golden test is the minimal correct change.Verification
nixosConfigurations.emmathorpe-edaas.config.system.build.toplevelbuilds greenchecks.x86_64-linux.{formatting,deadnix,statix}all passThe overlay carries a comment to drop it once nixpkgs refreshes the fixture (or the upstream 3.13.x revert lands).