sha version mismatch on npm
zenitraM opened this issue · 4 comments
Hey,
It seems the just published 0.4.2 has been uploaded to npm with a wrong sha1, causing it to fail npm install and breaking tests running and deploys everywhere:
➜ vizz npm install srs
npm http GET https://registry.npmjs.org/srs
npm http 304 https://registry.npmjs.org/srs
npm http GET https://registry.npmjs.org/srs/-/srs-0.4.2.tgz
npm http 200 https://registry.npmjs.org/srs/-/srs-0.4.2.tgz
npm ERR! Error: shasum check failed for /var/folders/tn/t28x6xb571gfgm6yz4dfjqd00000gn/T/npm-17813-HsXs4kp4/1403263846990-0.5543835323769599/tmp.tgz
npm ERR! Expected: 6bc4df3beb3e89d75024a2a9e8930451df67758f
npm ERR! Actual: 5c72ff8172e0b9d4703578bb3b18ecc5f4c49002
npm ERR! From: https://registry.npmjs.org/srs/-/srs-0.4.2.tgz
npm ERR! at /usr/local/Cellar/node/0.10.26/lib/node_modules/npm/node_modules/sha/index.js:38:8
npm ERR! at ReadStream.<anonymous> (/usr/local/Cellar/node/0.10.26/lib/node_modules/npm/node_modules/sha/index.js:85:7)
npm ERR! at ReadStream.EventEmitter.emit (events.js:117:20)
npm ERR! at _stream_readable.js:920:16
npm ERR! at process._tickCallback (node.js:415: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>
npm ERR! System Darwin 13.1.0
npm ERR! command "/usr/local/Cellar/node/0.10.26/bin/node" "/usr/local/bin/npm" "install" "srs"
npm ERR! cwd /Users/zenitram/code/vizz
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/zenitram/code/vizz/npm-debug.log
npm ERR! not ok code 0
This could be a bug related with publishing using node 0.11:
https://twitter.com/npm_support/status/467873731931828224
We're going to force 0.4.1 for the time being, although you probably want to fix this
Thanks for reporting. I have been seeing this too in multiple modules I published last night. But I was not publishing using node v0.11.x and the shasum problems seemed random at the time - usually only occurring on travis. But, with fresh eyes I'll try to get to the bottom of it today.
also npm/npm#5515
try again now? srs@0.4.3 has been published that should fix.