New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build 3.0.20 failed and is breaking packages dependent on event-stream #46

Closed
themasterchef opened this Issue Dec 11, 2013 · 10 comments

Comments

Projects
None yet
7 participants
@themasterchef

themasterchef commented Dec 11, 2013

Just tried to run npm update this morning on a barebones project containing browserify, debowerify, and connect. Browserify errored out when npm tried to grab it, so I looked deeper and got the following error:

npm http 404 https://registry.npmjs.org/event-stream/-/event-stream-3.0.20.tgz
npm ERR! fetch failed https://registry.npmjs.org/event-stream/-/event-stream-3.0.20.tgz
npm ERR! Error: 404 Not Found
npm ERR!     at WriteStream.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/fetch.js:57:12)
npm ERR!     at WriteStream.EventEmitter.emit (events.js:117:20)
npm ERR!     at fs.js:1596:14
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:103:5
npm ERR!     at Object.oncomplete (fs.js:107:15)
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 Linux 3.11.0-14-generic
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "update"
npm ERR! cwd /home/[path to node project directory]
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14

The CI server also indicates event-stream v3.0.20 fails across all browsers.

@mathieucivel

This comment has been minimized.

mathieucivel commented Dec 11, 2013

Same issue here, I had to specify a previous version of grunt-coffeelint in order to install it.

@dominictarr

This comment has been minimized.

Owner

dominictarr commented Dec 11, 2013

oh, this is because of npm publish being broken, i think.
I'm unpublishing event-stream@3.0.20 ... I'm trying to at least,
okay, it worked. go back to event-stream@3.0.19 until npm publish is working reliably again.

@mathieucivel

This comment has been minimized.

mathieucivel commented Dec 11, 2013

It solved the problem for grunt-coffeelint@0.0.8, it installed 3.0.18 though.

npm http GET https://registry.npmjs.org/event-stream/-/event-stream-3.0.18.tgz
npm http 200 https://registry.npmjs.org/event-stream/-/event-stream-3.0.18.tgz
@dominictarr

This comment has been minimized.

Owner

dominictarr commented Dec 11, 2013

okay, I've published 3.0.20 successfully.
can you check if it's working?
hmm, maybe we skipped 3.0.19 some how, no matter.

@lo1tuma

This comment has been minimized.

lo1tuma commented Dec 11, 2013

It is not working because stream-combiner is required in version 0.0.3 but the latest version is 0.0.2.

See: travis-ci build output.

@sreuter

This comment has been minimized.

sreuter commented Dec 11, 2013

Just ran into the same problem :-(

It is not working because stream-combiner is required in version 0.0.3 but the latest version is 0.0.2.

@tj

This comment has been minimized.

tj commented Dec 11, 2013

derp, got this too for segment

@timoxley

This comment has been minimized.

timoxley commented Dec 19, 2013

@dominictarr I believe you can close this, appears fixed.

@themasterchef

This comment has been minimized.

themasterchef commented Dec 19, 2013

Yeah, it appears fixed from here as well.

@dominictarr

This comment has been minimized.

Owner

dominictarr commented Dec 20, 2013

cool, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment