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

io.js 2.0.1 -- Error: 404 status code downloading tarball #623

Closed
wavded opened this issue May 11, 2015 · 13 comments
Closed

io.js 2.0.1 -- Error: 404 status code downloading tarball #623

wavded opened this issue May 11, 2015 · 13 comments
Labels

Comments

@wavded
Copy link

wavded commented May 11, 2015

All addons currently are failing due to:

> microtime@1.4.1 install /Users/wavded/Projects/golfhits/modules/mail/node_modules/mailer/node_modules/graygelf/node_modules/microtime
> node-gyp rebuild

gyp ERR! configure error
gyp ERR! stack Error: 404 status code downloading tarball
gyp ERR! stack     at Request.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:246:14)
gyp ERR! stack     at emitOne (events.js:82:20)
gyp ERR! stack     at Request.emit (events.js:166:7)
gyp ERR! stack     at Request.onRequestResponse (/usr/local/lib/node_modules/npm/node_modules/request/request.js:1156:10)
gyp ERR! stack     at emitOne (events.js:77:13)
gyp ERR! stack     at ClientRequest.emit (events.js:166:7)
gyp ERR! stack     at HTTPParser.parserOnIncomingClient (_http_client.js:414:21)
gyp ERR! stack     at HTTPParser.parserOnHeadersComplete (_http_common.js:88:23)
gyp ERR! stack     at Socket.socketOnData (_http_client.js:304:20)
gyp ERR! stack     at emitOne (events.js:77:13)
gyp ERR! System Darwin 14.3.0
gyp ERR! command "/usr/local/bin/iojs" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/wavded/Projects/golfhits/modules/logger/node_modules/graylog/node_modules/graygelf/node_modules/microtime
gyp ERR! node -v v2.0.1
gyp ERR! node-gyp -v v1.0.3
gyp ERR! not ok
@binarykitchen
Copy link

Indeed, this is worrying and breaking the app we are developing here.

Would be extremely helpful if the error message also showed what URL it is trying to download the tarball from.

@rickdog
Copy link

rickdog commented May 11, 2015

I posted this 4 days ago, there's been no response, I suspect the author is not much interested in supporting iojs.

node-gyp.js needs to be modified to handle iojs.
It looks for files in the wrong directories.
The x64 files are found at https://iojs.org/dist/v1.0.1/win-x64/, not https://iojs.org/dist/v1.0.1/x64/

$ node "c:\Program Files\iojs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild
gyp info it worked if it ends with ok
gyp info using node-gyp@1.0.2
gyp info using node@1.0.1 | win32 | x64
gyp http GET https://iojs.org/dist/v1.0.1/iojs-v1.0.1.tar.gz
gyp http 200 https://iojs.org/dist/v1.0.1/iojs-v1.0.1.tar.gz
gyp http GET https://iojs.org/dist/v1.0.1/SHASUMS256.txt
gyp http GET https://iojs.org/dist/v1.0.1/x64/node.lib
gyp http GET https://iojs.org/dist/v1.0.1/node.lib
gyp http 404 https://iojs.org/dist/v1.0.1/x64/node.lib
gyp WARN install got an error, rolling back install
gyp http 200 https://iojs.org/dist/v1.0.1/SHASUMS256.txt
gyp http 404 https://iojs.org/dist/v1.0.1/node.lib
gyp ERR! configure error
gyp ERR! stack Error: 404 status code downloading 64-bit node.lib

dcposch added a commit to dcposch/node-gyp that referenced this issue May 12, 2015
This makes issues like nodejs#623 easier to debug
@fengmk2
Copy link
Contributor

fengmk2 commented May 12, 2015

+1

1 similar comment
@ottiker
Copy link

ottiker commented May 12, 2015

+1

@binarykitchen
Copy link

@rickdog thanks but i think you cannot imply without facts that the author isn't interested to support iojs. if that were true, i could make a similar assumption that the author isn't interested to support windows. how you'd feel about that? ;)

@cfsghost
Copy link

I found a fork which has no this issues for io.js. is it possible to merge?

https://github.com/rvagg/pangyp

@bryannaegele
Copy link

+1

still present in 2.0.2

@leecade
Copy link

leecade commented Jun 12, 2015

+1
still present in v2.2.1

@felipefdl
Copy link

+1
iojs - v2.3.3
that happen only when use the last version of npm.

@message
Copy link

message commented Jul 9, 2015

+1

@gabeio
Copy link

gabeio commented Jul 11, 2015

👍 side note to anyone who knows this library better (than I do at least) the author seems to be accepting pull requests frequently; so if someone could make a pull request rather than complain wait it'd probably save everyone a lot of trouble ❤️

@coderaiser
Copy link

Fixed in #669

@Fishrock123
Copy link
Contributor

#701

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

No branches or pull requests