Fix index-sha256 bit rot
#2390
Merged
Fix index-sha256 bit rot
#2390
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
If an new package is deployed to `hackage.haskell.org`, to use it before it is captured by the `hackage.nix` update add the following to the project arguments: ```nix index-state="2025-06-16T00:00:00Z"; # Use current time here # This hash in not valid, the error message will give the correct hash index-sha256="sha256-NS28jJYko/tNUKVhncntu/mV8tsQmTA52T000000000="; ``` This change PR fixes some "bit rot" issues: * A warning about `--index-state` argument being out of range is now an error. * The sha256 might now be in base16 or base32.
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.
If an new package is deployed to
hackage.haskell.org, to use it before it is captured by thehackage.nixupdate add the following to the project arguments:This change PR fixes some "bit rot" issues:
--index-stateargument being out of range is now an error.