npm install on clean tree produces ominous error messages

[jrgm]

And actually, I think this gets cleaned up since postinstall.js gets run again and the second time automation-tests npm install is ok. But I don't want to ship train-2013.03.29 with this splat.

> node ./scripts/postinstall.js

>>> Installing automation-tests dependencies
*** Generating ephemeral keys used for testing ***
npm http GET http://127.0.0.1:49428/vows/0.6.4
npm http GET http://127.0.0.1:49428/request/2.12.0
npm http GET http://127.0.0.1:49428/optimist/0.3.5
npm http GET http://127.0.0.1:49428/underscore/1.4.2
npm http GET http://127.0.0.1:49428/minimatch/0.2.6
npm http GET http://127.0.0.1:49428/q/0.8.10
npm http GET http://127.0.0.1:49428/mkdirp/0.3.4
npm http 404 http://127.0.0.1:49428/request/2.12.0
npm ERR! registry error parsing json
npm http 404 http://127.0.0.1:49428/vows/0.6.4
npm ERR! registry error parsing json
npm http 404 http://127.0.0.1:49428/optimist/0.3.5
npm ERR! registry error parsing json
npm ERR! SyntaxError: Unexpected token p
npm ERR! package installation disallowed by lockdown
npm ERR!     at Object.parse (native)
npm ERR!     at RegClient.<anonymous> (/usr/local/node-0.8.17/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:226:23)
npm ERR!     at Request.init.self.callback (/usr/local/node-0.8.17/lib/node_modules/npm/node_modules/request/main.js:120:22)
npm ERR!     at Request.EventEmitter.emit (events.js:99:17)
npm ERR!     at Request.<anonymous> (/usr/local/node-0.8.17/lib/node_modules/npm/node_modules/request/main.js:648:16)
npm ERR!     at Request.EventEmitter.emit (events.js:126:20)
npm ERR!     at IncomingMessage.Request.start.self.req.self.httpModule.request.buffer (/usr/local/node-0.8.17/lib/node_modules/npm/node_modules/request/main.js:610:14)
npm ERR!     at IncomingMessage.EventEmitter.emit (events.js:126:20)
npm ERR!     at IncomingMessage._emitEnd (http.js:366:10)
npm ERR!     at HTTPParser.parserOnMessageComplete [as onMessageComplete] (http.js:149:23)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Darwin 11.4.2
npm ERR! command "/usr/local/node-0.8.17/bin/node" "/usr/local/node-0.8.17/bin/npm" "install"
npm ERR! cwd /Users/jmorrison/tmp/build-it/browserid/automation-tests
npm ERR! node -v v0.8.17
npm ERR! npm -v 1.2.0
npm ERR! type unexpected_token
npm http 404 http://127.0.0.1:49428/minimatch/0.2.6
npm ERR! registry error parsing json
npm http 404 http://127.0.0.1:49428/underscore/1.4.2
npm ERR! registry error parsing json
npm http 200 http://127.0.0.1:49428/mkdirp/0.3.4
npm http GET http://127.0.0.1:49428/mkdirp/-/mkdirp-0.3.4.tgz
npm http 404 http://127.0.0.1:49428/q/0.8.10
npm ERR! registry error parsing json
npm http 200 http://127.0.0.1:49428/mkdirp/-/mkdirp-0.3.4.tgz
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/jmorrison/tmp/build-it/browserid/automation-tests/npm-debug.log
npm ERR! not ok code 0

[jaredhirsch]

#3164 was a no-go, bug still open. we could just merge the fix over from the train, but it'd be nice to fix the automation-tests problems for reals.

[jbonacci]

OK. I see other issues now (see separate email), but not these specific errors on a clean, first-time install.
I will leave it for @jrgm to Verify.

[jrgm]

verified for train-2013.04.12 and dev branches.