evtest: update sha256 hash #170349
Merged
evtest: update sha256 hash #170349
Conversation
This file contains 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
Commit 6df37c9 bumped the version of evtest but failed to update the hash. As a result, hosts which already have evtest-1.33 source present will build the old version but label it as evtest-1.34. Hosts which lack the older source code will fail their builds. This commit corrects the issue. We should think about a way to get Hydra to catch issues like this. Maybe require that if two FODs have different hashes then they must have different `${pname}-${version}`s? Only for FODs, of course.
ghost
mentioned this pull request
ofborg
bot
added
10.rebuild-darwin: 0
bjornfor
approved these changes
Apr 26, 2022
1 task
|
Successfully created backport PR #170388 for |
|
The process '/usr/bin/git' failed with exit code 1 |
ghost
deleted the
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.
Description of changes
Commit 6df37c9 bumped the version of
evtest but failed to update the hash. As a result, hosts which
already have evtest-1.33 source present will build the old version but
label it as evtest-1.34. Hosts which lack the older source code will
fail their builds. This commit corrects the issue.
We should think about a way to get Hydra to catch issues like this.
Maybe require that if two FODs have different hashes then they must
have different
${pname}-${version}s? Only for FODs, of course.Things done
sandbox = trueset innix.conf? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)nixos/doc/manual/md-to-db.shto update generated release notes