diff options
| author | Adam Joseph <adam@westernsemico.com> | 2022-04-25 18:07:10 -0700 |
|---|---|---|
| committer | Bjørn Forsman <bjorn.forsman@gmail.com> | 2022-04-26 10:31:08 +0200 |
| commit | 0c922b4ea680ff2fa2d7c120c0eaea32694f7eb0 (patch) | |
| tree | 5b7246c3b17fc2dad939cebe9d747ffa2e749c22 /pkgs/development/python-modules/rangehttpserver | |
| parent | 8e4696eabe550c0d20d5e53e584200fecfb71087 (diff) | |
evtest: update sha256 hash
Commit 6df37c9aab85fb1494e2a106b5491a3fc1f7f278 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.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions