Repository navigation
Pin nixpkgs and haskell.nix exactly, and build with GHC 9.12.4 - #6
Merged
Merged
Conversation
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
1 participant
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.
All four repos were on floating nixpkgs refs, so
release-26.05locked to three different revs across rust, cpp and go — meaning three separate GHC 9.12.4 builds. Now pinned to exact commits:7993f34ee47e28a3d607a525aadc6c94b73be7281dde0b46d3daa5bf0ff3ea6332d579a1943b4a0cVerified all three dev shells now resolve to the same GHC store path,
/nix/store/vqb1g4ha3lak2wa28cfq6zbjq9y78vha-ghc-9.12.4, so it builds once.Resolver goes to
nightly-2026-04-19(GHC 9.12.4) where it was not already. haskell.nix had to move off its pinned commit because the old one predates the resolver —This version of stackage.nix does not know about the Stackage resolver nightly-2026-04-19.