Fix dependency checksum error during initial setup #86
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.
The provided URL for
mips-gcc-egcs-2.91.66-linux.tar.gz
within./shell.nix
points to thelatest
release of that repository.However, that repository recently saw new releases, so a different file now gets downloaded and the provided checksum for that file no longer matches.
This PR pins the release of that dependency to its version 0.2, which matches the provided sha256 checksum.
As an alternative to this PR, if an update to a newer version of the dependency is being considered, I recommend both updating the sha256 to the current up-to-date version of 0.4, as well as pinning the dependency to said version.
For reference, see https://github.com/decompals/mips-gcc-egcs-2.91.66/releases