Add-ons can't be installed with Node.js v6.0.0-rc.3

[fivdi]

• Version: v6.0.0-rc.3
• Platform: Linux raspberrypi 4.1.19-v7+ Debugger: current multi clients system is unuseful #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux
• Subsystem: build

This issue is similar to #6237. When installing add-ons with Node.js v6.0.0-rc.3 an attempt is made to download node-v6.0.0-rc.3-headers.tar.gz from https://iojs.org/download/rc/v6.0.0-rc.3/node-v6.0.0-rc.3-headers.tar.gz (which doesn't exist) rather than from https://nodejs.org/download/rc/v6.0.0-rc.3/node-v6.0.0-rc.3-headers.tar.gz (which does exist.)

Here's an example:

pi@raspberrypi:~ $ npm install i2c-bus

> i2c-bus@1.0.2 install /home/pi/node_modules/i2c-bus
> node-gyp rebuild

gyp WARN install got an error, rolling back install
gyp ERR! configure error 
gyp ERR! stack Error: 404 response downloading https://iojs.org/download/rc/v6.0.0-rc.3/node-v6.0.0-rc.3-headers.tar.gz
gyp ERR! stack     at Request.<anonymous> (/home/pi/opt/node-v6.0.0-rc.3-linux-armv7l/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:210:14)
gyp ERR! stack     at emitOne (events.js:101:20)
gyp ERR! stack     at Request.emit (events.js:188:7)
gyp ERR! stack     at Request.onRequestResponse (/home/pi/opt/node-v6.0.0-rc.3-linux-armv7l/lib/node_modules/npm/node_modules/request/request.js:952:10)
gyp ERR! stack     at emitOne (events.js:96:13)
gyp ERR! stack     at ClientRequest.emit (events.js:188:7)
gyp ERR! stack     at HTTPParser.parserOnIncomingClient (_http_client.js:469:21)
gyp ERR! stack     at HTTPParser.parserOnHeadersComplete (_http_common.js:105:23)
gyp ERR! stack     at TLSSocket.socketOnData (_http_client.js:359:20)
gyp ERR! stack     at emitOne (events.js:96:13)
gyp ERR! System Linux 4.1.19-v7+
gyp ERR! command "/home/pi/opt/node-v6.0.0-rc.3-linux-armv7l/bin/node" "/home/pi/opt/node-v6.0.0-rc.3-linux-armv7l/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/pi/node_modules/i2c-bus
gyp ERR! node -v v6.0.0-rc.3
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok 
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.
npm WARN You are using a pre-release version of node and things may not work as expected
npm ERR! Linux 4.1.19-v7+
npm ERR! argv "/home/pi/opt/node-v6.0.0-rc.3-linux-armv7l/bin/node" "/home/pi/opt/node-v6.0.0-rc.3-linux-armv7l/bin/npm" "install" "i2c-bus"
npm ERR! node v6.0.0-rc.3
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE

npm ERR! i2c-bus@1.0.2 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the i2c-bus@1.0.2 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the i2c-bus package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs i2c-bus
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls i2c-bus
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/npm-debug.log
pi@raspberrypi:~ $ 

It's possible to work around the issue by manually downloading and decmpressing node-v6.0.0-rc.3-headers.tar.gz before the install:

pi@raspberrypi:~ $ wget https://nodejs.org/download/rc/v6.0.0-rc.3/node-v6.0.0-rc.3-headers.tar.gz
pi@raspberrypi:~ $ tar -zxf node-v6.0.0-rc.3-headers.tar.gz
pi@raspberrypi:~ $ npm install i2c-bus --nodedir=/home/pi/node-v6.0.0-rc.3

> i2c-bus@1.0.2 install /home/pi/node_modules/i2c-bus
> node-gyp rebuild

make: Entering directory '/home/pi/node_modules/i2c-bus/build'
  CXX(target) Release/obj.target/i2c/src/i2c.o
  SOLINK_MODULE(target) Release/obj.target/i2c.node
  COPY Release/i2c.node
make: Leaving directory '/home/pi/node_modules/i2c-bus/build'
/home/pi
└─┬ i2c-bus@1.0.2 
  ├── bindings@1.2.1 
  └── nan@2.2.1 

npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.
npm WARN You are using a pre-release version of node and things may not work as expected
pi@raspberrypi:~ $ 

[jasnell]

argh... looks like I made the wrong selection again :-( ... will rebuild the artifacts

[jasnell]

Rebuild starting now, it'll take a short while then should be good to go again.

[fivdi]

Everything has been rebuilt now. The armv7l build, which was the one being used above, is now functioning correctly. Thanks :)

[jasnell]

Awesome. Eventually I'll actually be able to make the right selection when building the RC ;-)

[MylesBorins]

in reality we should not have to select that box... there is no instance where you would do a custom build and not want the headers hosted in "rc"... I'll make an issue on build

edit: nodejs/build#393

[jasnell]

Usability FTW!

[fivdi]

I'm not sure if it's important, but this issue and #6237 are slightly different. In #6237 release should have been rc. In the case described by this issue iojs.org should have been nodejs.org.

[MylesBorins]

@fivdi fwiw it is pretty much the same issue. There is a drop down box to select the release stream for the headers... pick the wrong option and it doesn't work. I've done this a few times... pretty annoying. Hopefully that issue I started on build will stop this from happening ever again!

[jasnell]

Yeah, to be honest, the io.js url options should just be removed at this point.