Repository navigation
fix: allow Python 3.13.12 environment glue - #263
Merged
Merged
Conversation
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Allow the generated
-python3-3.13.12-env.drvalongside the existing Python 3.13.13 environment marker in the shared maintenance policy.sctmes/dotfiles #68 inherits Codex Base
.18from #260, but follows its own nixpkgs. Its failed gate completed both policy evaluations and both dry runs, then rejected exactly one new derivation:k481qj768y8riix6j2s098iy0pgzbbg6-python3-3.13.12-env.drv. The previous fix covered only 3.13.13.Native derivation inspection confirms that this exact output assembles existing Python 3.13.12 and Pillow 12.2.0 paths with the standard Perl buildEnv linker and binary wrappers. It declares
preferLocalBuild=true,allowSubstitutes=false, and no build inputs; it does not compile Python or Pillow. The change adds one exact environment marker to the shared base, with no downstream exception or gate-script change.Validation: evaluated the actual exported policy and replayed the downstream gate's existing classification functions against its retained base/head logs and policies. The original replay reproduced the exact CI blocked list (one new blocked derivation, zero new direct fetches). With the added marker, both deltas are empty. Only Python 3.13.12 environment entries change classification; other blocked derivations remain.
git diff --checkpassed. The replay was offline; formal upstream CI remains pending.After this merges, refresh #68's
upstreamlock and let its maintenance gate validate the consumer before rebuilding host 116.