Skip to content

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

Closed

Description

@wavded

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

Activity

  1. binarykitchen commented on May 11, 2015

    @binarykitchen

    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.

  2. rickdog commented on May 11, 2015

    @rickdog

    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

  3. added a commit that references this issue on May 12, 2015
  4. fengmk2 commented on May 12, 2015

    @fengmk2
    Contributor

    +1

  5. ottiker commented on May 12, 2015

    @ottiker

    +1

  6. binarykitchen commented on May 12, 2015

    @binarykitchen

    @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? ;)

  7. cfsghost commented on May 14, 2015

    @cfsghost

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

    https://github.com/rvagg/pangyp

  8. bryannaegele commented on May 19, 2015

    @bryannaegele

    +1

    still present in 2.0.2

  9. leecade commented on Jun 12, 2015

    @leecade

    +1
    still present in v2.2.1

  10. felipefdl commented on Jul 6, 2015

    @felipefdl

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

  11. message commented on Jul 9, 2015

    @message

    +1

  12. gabeio commented on Jul 11, 2015

    @gabeio

    👍 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 ❤️

  13. coderaiser commented on Jul 20, 2015

    @coderaiser

    Fixed in #669

  14. Fishrock123 commented on Aug 23, 2015

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions