Since nodejs 12.18.1 entered groovy-proposed, autopkgtests that rely on node-sha to compute SHA-1 hashes started failing reliably on ppc64el. This affects the following packages:
- node-sha - node-crypto-browserify - node-create-hash
Other architectures do not appear to be affected, and it's only the SHA-1 hashes that are incorrect, other hashing algorithm are not affected.
For reference, I'm attaching the full log for the last failed run of node-create-hash on ppc64el (see https://autopkgtest.ubuntu.com/packages/n/node-create-hash/groovy/ppc64el).
Upstream bug report: https://github.com/crypto-browserify/sha.js/issues/66
Since nodejs 12.18.1 entered groovy-proposed, autopkgtests that rely on node-sha to compute SHA-1 hashes started failing reliably on ppc64el. This affects the following packages:
- node-sha browserify
- node-crypto-
- node-create-hash
Other architectures do not appear to be affected, and it's only the SHA-1 hashes that are incorrect, other hashing algorithm are not affected.
For reference, I'm attaching the full log for the last failed run of node-create-hash on ppc64el (see https:/ /autopkgtest. ubuntu. com/packages/ n/node- create- hash/groovy/ ppc64el).
Upstream bug report: https:/ /github. com/crypto- browserify/ sha.js/ issues/ 66