Closed bigethan closed 9 years ago
Same here with npmjs.org:
npm ERR! Error: shasum check failed for /tmp/tmp/npm-44-gpP24ZzY/registry.npmjs.org/buster-test/-/buster-test-0.7.9.tgz
npm ERR! Expected: 627ef9f9a22e199424f743e80a949d27d3858597
npm ERR! Actual: d36a411d4feb97bee19020ca1e3527798006a3a8
npm ERR! From: http://registry.npmjs.org/buster-test/-/buster-test-0.7.9.tgz
npm ERR! at /usr/local/lib/node_modules/npm/node_modules/sha/index.js:38:8
npm ERR! at ReadStream.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/sha/index.js:85:7)
npm ERR! at ReadStream.emit (events.js:117:20)
npm ERR! at _stream_readable.js:929:16
npm ERR! at process._tickCallback (node.js:419:13)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR! <http://github.com/npm/npm/issues>
And manual check produced same results
vs
$ shasum buster-test-0.7.9.tgz
d36a411d4feb97bee19020ca1e3527798006a3a8 buster-test-0.7.9.tgz
PS. While you at it, would be nice to fix bugs field as well, since there is no issue page for buster-test
.
Thank you.
This is a bug in npm itself, I'd say. https://github.com/npm/npm/issues/6541
Got this once myself in the morning, then it went away. A colleague mentioned he had success with EU mirror of npm.
I think republishing the package might fix the issue, since recorded checksum looks wrong.
Npm no longer allows publishing over something. I'd wait for official response from their team.
Simple bump in patch version will do :)
Does the issue still exist for you? Installing buster-test is ok for me, on windows and on linux. If i shasum the downloaded tgz file, i get 627ef9f9a22e199424f743e80a949d27d3858597, the value that is expected.
Looks like https://github.com/npm/npm/issues/6541 is closed off by now, although https://github.com/npm/npm/issues/6451 isn't
@bigethan, @alexindigo, because i got no answer, i assume the issue also doesn't exist for you anymore.