Skip to content
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

installing karma from the npm repository causes a 404 #840

Closed
elachys opened this issue Nov 27, 2013 · 15 comments
Closed

installing karma from the npm repository causes a 404 #840

elachys opened this issue Nov 27, 2013 · 15 comments

Comments

@elachys
Copy link

elachys commented Nov 27, 2013

$ npm install karma
npm http GET https://registry.npmjs.org/karma
npm http 200 https://registry.npmjs.org/karma
npm http GET https://registry.npmjs.org/karma/-/karma-0.10.6.tgz
npm http 404 https://registry.npmjs.org/karma/-/karma-0.10.6.tgz
npm ERR! fetch failed https://registry.npmjs.org/karma/-/karma-0.10.6.tgz
npm ERR! Error: 404 Not Found
npm ERR!     at WriteStream.<anonymous> (/usr/local/Cellar/node/0.10.18/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/Cellar/node/0.10.18/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!     <https://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

npm ERR! System Darwin 13.0.0
npm ERR! command "/usr/local/Cellar/node/0.10.18/bin/node" "/usr/local/bin/npm" "install" "karma"
npm ERR! cwd /Users/XXXX
npm ERR! node -v v0.10.18
npm ERR! npm -v 1.3.8
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/XXXX/npm-debug.log
npm ERR! not ok code 0
@ncancelliere
Copy link

I get the same issue.

$ npm -g install karma
npm http GET https://registry.npmjs.org/karma
npm http 304 https://registry.npmjs.org/karma
npm http GET https://registry.npmjs.org/karma/-/karma-0.10.6.tgz
npm http 404 https://registry.npmjs.org/karma/-/karma-0.10.6.tgz
npm ERR! fetch failed https://registry.npmjs.org/karma/-/karma-0.10.6.tgz
npm ERR! Error: 404 Not Found
...
npm ERR! System Darwin 13.0.0
npm ERR! command "/usr/local/Cellar/node/0.10.22/bin/node" "/usr/local/bin/npm" "install" "-g" "karma" "--registry" "http://registry.npmjs.org"
npm ERR! cwd /Users/nicholas
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14

@dstevenson
Copy link

Same here. Appears the tarball is missing on npmjs.

GET https://registry.npmjs.org/karma/-/karma-0.10.6.tgz

{"error":"not_found","reason":"Document is missing attachment"}

@ncancelliere
Copy link

Hmm, even trying to go back a bit: npm install -g [email protected] (same with 0.10.4, even @canary)

I get the following missing tar balls:

npm http 404 https://registry.npmjs.org/karma-phantomjs-launcher/-/karma-phantomjs-launcher-0.1.1.tgz
npm http 404 https://registry.npmjs.org/karma-firefox-launcher/-/karma-firefox-launcher-0.1.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/karma-phantomjs-launcher/-/karma-phantomjs-launcher-0.1.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/karma-firefox-launcher/-/karma-firefox-launcher-0.1.1.tgz

@mhart
Copy link

mhart commented Nov 27, 2013

Yeah - because karma has just specified all of its dependencies as * it will always try to get the latest versions... which is bad.

Can karma's dependencies be updated so that they're not * - this would at least allow people to rollback to previous versions successfully.

@jkintscher
Copy link

Getting the exact same error and output as above that prevents me from installing my package with "karma": "~0.11". It worked just a few hours ago.

@ObadahFahmy
Copy link

Same error here.

$ npm install -g karma
npm http GET http://registry.npmjs.org/karma
npm http 304 http://registry.npmjs.org/karma
npm http GET http://registry.npmjs.org/karma/-/karma-0.10.6.tgz
npm http 404 http://registry.npmjs.org/karma/-/karma-0.10.6.tgz
npm ERR! fetch failed http://registry.npmjs.org/karma/-/karma-0.10.6.tgz
npm ERR! Error: 404 Not Found
npm ERR!     at WriteStream.<anonymous> (C:\Program Files\nodejs\node_modules\np
m\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 C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-f
s\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!     <https://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

npm ERR! System Windows_NT 6.1.7600
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nod
ejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "karma"
npm ERR! cwd C:\Users\Ob
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\Users\Ob\npm-debug.log
npm ERR! not ok code 0```

@jkintscher
Copy link

It just worked for me. Try again and see if it’s revolved for you guys as well. Probably some glitch of npmjs.org, eh?

@dstevenson
Copy link

Looks good now for me too.

@mhart
Copy link

mhart commented Nov 27, 2013

Yep, good for me too now as well 👍

@vojtajina
Copy link
Contributor

Guys, I'm sorry, but this is just NPM being retarded (see https://github.com/isaacs/npm/issues/4205). I have no idea what happend. I force pushed it again and it's good now.

Instead of specifying versions, we gonna remove the peerDeps, see #767.

@mhart
Copy link

mhart commented Nov 27, 2013

@vojtajina I'd say your original publish must have only half-succeeded (npm has been wobbly of late) - hence the tarball not being attached.

Being able to safely rollback for users in cases like this would be reeeeeally helpful, so removing any * dependencies would be great!

@ncancelliere
Copy link

Thank you for resolving this so quickly. I too can confirm it's working. I think mhart has some good points though about avoiding * dependencies, so users can use older versions confidently.

@vojtajina
Copy link
Contributor

@mhart Yep, I'm gonna remove the "peerDependencies" in 0.12 see #767.

@victorliun
Copy link

Hi Guy.

I just changed the registry to http version by

npm config set registry http://registry.npmjs.org/
That works for me. Hope can help someone.

@dm89
Copy link

dm89 commented Feb 3, 2016

I am having this issue now. Any suggestions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants