npm install duo shasum check failed

[samuelreh]

Hi,

I keep getting this error when running npm install -g duo

npm install -g duo
npm ERR! Error: shasum check failed for /var/folders/r4/1mwxmq4x0mb9wk24ch994bf40000gn/T/npm-29342-pVmd9zj6/registry.npmjs.org/duo/-/duo-0.5.0.tgz
npm ERR! Expected: 1dd9b2f7ea1289ba94cef63c34956c3f972da507
npm ERR! Actual:   823f078359e8d1c96b8d69b0bf18b6f17c7c375c
npm ERR!     at /Users/samuelreh/.nvm/v0.11.13/lib/node_modules/npm/node_modules/sha/index.js:38:8
npm ERR!     at ReadStream.<anonymous> (/Users/samuelreh/.nvm/v0.11.13/lib/node_modules/npm/node_modules/sha/index.js:85:7)
npm ERR!     at ReadStream.EventEmitter.emit (events.js:129:20)
npm ERR!     at _stream_readable.js:898:16
npm ERR!     at process._tickCallback (node.js:343:11)
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.3.0
npm ERR! command "node" "/Users/samuelreh/.nvm/v0.11.13/bin/npm" "install" "-g" "duo"
npm ERR! cwd /Users/samuelreh/Development/Attr/attribution/analytics.js-integrations
npm ERR! node -v v0.11.13
npm ERR! npm -v 1.4.23
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/samuelreh/Development/Attr/attribution/analytics.js-integrations/npm-debug.log
npm ERR! not ok code 0

Any ideas?

[wryk]

Duo install works fine for me with npm@1.4.9 and duo@0.5.4

[stephenmathieson]

duo isn't quite ready yet, so you probably shouldn't be installing it yet :p

for what it's worth, i can install it fine:

$ npm --version
1.4.14
stephenmathieson at MBP in ~/repos/tmp/foo
$ npm install duo
npm WARN package.json better-assert@1.0.0 No repository field.
npm WARN package.json component-builder@0.6.5 No repository field.
npm WARN package.json express@0.14.0 No repository field.
npm WARN package.json stdin@0.0.1 No repository field.
npm WARN engine koa@0.8.2: wanted: {"node":">= 0.11.9"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine koa-ratelimit@1.0.3: wanted: {"node":"> 0.11.4"} (current: {"node":"v0.10.29","npm":"1.4.14"})
duo@0.5.4 ../../../node_modules/duo
├── co@3.1.0
├── unyield@0.0.1
├── co-exists@0.0.1
├── debug@0.8.1
├── stream-log@0.1.0
├── bytes@1.0.0
├── thunkify@2.1.2
├── delegates@0.0.3
├── win-fork@1.1.1
├── batch@0.5.1
├── extend.js@0.0.1
├── step.js@2.0.1
├── commander@2.3.0
├── archy@0.0.2
├── json-mask@0.3.1
├── atomic-json@0.0.3 (enqueue@0.0.3)
├── co-parallel@1.0.0 (co-thread@0.0.1)
├── duo-string-to-js@0.0.4 (string-to-js@0.0.1)
├── file-deps@0.0.5 (mini-tokenizer@0.1.2)
├── mkdirp@0.5.0 (minimist@0.0.8)
├── co-fs@1.2.0 (thunkify@0.0.1, co-from-stream@0.0.0)
├── component-clone@0.2.2 (component-type@1.0.0)
├── duo-pack@1.0.2 (combine-source-map@0.3.0)
├── duo-package@0.4.2 (thunkify@0.0.1, enstore@0.0.2, node-netrc@0.0.1, semver@2.3.2, gh-resolve@3.0.1, request@2.39.0, tar-fs@0.4.1)
├── duo-main@0.0.3 (component-type@1.0.0, mocha@1.21.3)
├── duo-test@0.2.4 (co-exec@1.1.0, buffer-events@0.0.2, wd-browser@0.1.1, open@0.0.5, queue-component@1.0.6, koa-route@1.1.4, debug@1.0.4, koa-common@1.2.0, koa-static@1.4.6, koa@0.8.2, to-pascal-case@0.0.2, localtunnel@1.3.0, mocha@1.21.3, wd@0.3.4)
├── max-component@1.0.0 (to-function@2.0.5)
└── gnode@0.0.8 (regenerator@0.4.12)

[kenany]

@samuelreh Node.js 0.11.x has a bug in its shasum implementation (joyent/node#7365). Maybe that's why you're getting a different shasum than expected?

[jonathanong]

lol why is this here? @MatthewMueller can you make the duo repos public? i don't think it'll spam your followers or anything

[matthewmueller]

haha no idea why this is here, but @KenanY is right. I was publishing using 0.11.x. The latest duo was published using node 0.10.x so it should install.

@samuelreh thanks for playing around with an early version of duo! duo will be open sourced very soon, but until then please find me on #duo.js or shoot me an email (address in my profile). this is not the right place for these kinds of issues.