iojs and exec-sync #1332

edwardsmarkf · 2015-04-03T01:06:00Z

hello - i just tried to install exec-sync after switching from node to io.js - and this package didnt want to install for me. any suggestions are appreciated!

npm -v

2.7.1

mkdir ./tester ; cd ./tester ; npm install exec-sync ;

npm WARN engine ffi@1.2.5: wanted: {"node":">=0.6.0"} (current: {"node":"1.5.2-nightly201503173c8ae2d934","npm":"2.7.1"})
\

ref@1.0.1 install /root/tester/node_modules/exec-sync/node_modules/ffi/node_modules/ref
node-gyp rebuild

gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: 404 status code downloading tarball
gyp ERR! stack at Request. (/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:1176: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:410:21)
gyp ERR! stack at HTTPParser.parserOnHeadersComplete (_http_common.js:88:23)
gyp ERR! stack at TLSSocket.socketOnData (_http_client.js:300:20)
gyp ERR! stack at emitOne (events.js:77:13)
gyp ERR! System Linux 2.6.32-504.8.1.el6.x86_64
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /root/tester/node_modules/exec-sync/node_modules/ffi/node_modules/ref
gyp ERR! node -v v1.5.2-nightly201503173c8ae2d934
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok
npm ERR! Linux 2.6.32-504.8.1.el6.x86_64
npm ERR! argv "/usr/local/bin/iojs" "/usr/local/bin/npm" "install" "exec-sync"
npm ERR! node v1.5.2-nightly201503173c8ae2d934
npm ERR! npm v2.7.1
npm ERR! code ELIFECYCLE

npm ERR! ref@1.0.1 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ref@1.0.1 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the ref 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 their info via:
npm ERR! npm owner ls ref
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /root/tester/npm-debug.log

The text was updated successfully, but these errors were encountered:

kenany · 2015-04-03T01:26:33Z

@edwardsmarkf Hmm, how was npm installed? I think you might not be using the version that has node-gyp patched for io.js support. Luckily npm@2.7.0 added the --node-gyp flag, you can try using pangyp instead:

$ npm install -g pangyp
$ npm install exec-sync --node-gyp=pangyp

edwardsmarkf · 2015-04-03T01:54:45Z

hello and thank you for the fast response. i also found sync-exec that
installed no problem so i believe i will go with that instead.

Thank you,

Mark Edwards

On Thu, Apr 2, 2015 at 6:27 PM, Kenan Yildirim notifications@github.com
wrote:

@edwardsmarkf https://github.com/edwardsmarkf Hmm, how was npm
installed? I think you might not be using the version that has node-gyp
patched for io.js support. Luckily npm@2.7.0
https://github.com/npm/npm/releases/tag/v2.7.0 added the --node-gyp
flag, you can try using pangyp https://github.com/rvagg/pangyp instead:

$ npm install -g pangyp
$ npm install exec-sync --node-gyp=pangyp

—
Reply to this email directly or view it on GitHub
#1332 (comment).

mscdex · 2015-04-03T02:12:37Z

It looks like you're using a nightly version. Did you try using a normal io.js release?

silverwind · 2015-04-03T14:07:06Z

I don't think this is worth investigating further. @edwardsmarkf is using a pretty outdated package, that also has a alternative in core, My guess for the cause would be @kenany's idea.

edwardsmarkf · 2015-04-03T15:16:02Z

for fun i ran: npm install -g npm ;

now using 2.7.5 and i still have same problem.

i also tried: npm install -g pangyp ; npm install exec-sync
--node-gyp=pangyp ;

again, same issue.

Thank you,

Mark Edwards

On Fri, Apr 3, 2015 at 7:07 AM, silverwind notifications@github.com wrote:

Closed #1332 #1332.

—
Reply to this email directly or view it on GitHub
#1332 (comment).

Fishrock123 · 2015-04-03T15:19:54Z

There are some floating patches to make npm work with io.js, so only the version of npm that io.js ships with will work. See: #1263

silverwind · 2015-04-03T15:21:02Z

I think you've hit #1263 there. Until that is resolved, it's probably best to only use a npm packaged with iojs itself. If you're updating npm through other channels, you're missing the floating patches. I hope we can soon resolve that situation.

kenany · 2015-04-03T16:53:49Z

@edwardsmarkf Hmm, that's odd. --node-gyp=pangyp should alleviate the need for the floating patches... it's what I myself have been doing :)

Are you sure it's the same 404 error? I just tried the command myself and it does fail at node-gyp rebuild but due to a bunch of CXX errors, not a 404.

edwardsmarkf · 2015-04-03T17:14:44Z

hi kenan - attached is the npm-debug.log

and in case i forget to mention it, this forum-group is awesome. thank you
all so much for showing patience with a technically-challenged newbie like
me.

n_pm install exec-sync --node-gyp=pangyp ;_

npm WARN engine ffi@1.2.5: wanted: {"node":">=0.6.0"} (current:

{"node":"1.5.2-nightly201503173c8ae2d934","npm":"2.7.5"})

ref@1.0.1 install
/root/tester/node_modules/exec-sync/node_modules/ffi/node_modules/ref
node-gyp rebuild

gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: 404 status code downloading tarball
gyp ERR! stack at Request.
(/usr/local/lib/node_modules/pangyp/lib/install.js:251: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/pangyp/node_modules/request/request.js:1255: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:410:21)
gyp ERR! stack at HTTPParser.parserOnHeadersComplete
(_http_common.js:88:23)
gyp ERR! stack at TLSSocket.socketOnData (_http_client.js:300:20)
gyp ERR! stack at emitOne (events.js:77:13)
gyp ERR! System Linux 2.6.32-504.8.1.el6.x86_64
gyp ERR! command "node" "/usr/local/bin/pangyp" "rebuild"
gyp ERR! cwd
/root/tester/node_modules/exec-sync/node_modules/ffi/node_modules/ref
gyp ERR! node -v v1.5.2-nightly201503173c8ae2d934
gyp ERR! pangyp -v v2.1.0
gyp ERR! not ok
npm ERR! Linux 2.6.32-504.8.1.el6.x86_64
npm ERR! argv "node" "/usr/local/bin/npm" "install" "exec-sync"
"--node-gyp=pangyp"
npm ERR! node v1.5.2-nightly201503173c8ae2d934
npm ERR! npm v2.7.5
npm ERR! code ELIFECYCLE

npm ERR! ref@1.0.1 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ref@1.0.1 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the ref 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 their info via:
npm ERR! npm owner ls ref
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /root/tester/npm-debug.log

Thank you,

Mark Edwards

On Fri, Apr 3, 2015 at 9:54 AM, Kenan Yildirim notifications@github.com
wrote:

@edwardsmarkf https://github.com/edwardsmarkf Hmm, that's odd.
--node-gyp=pangyp should alleviate the need for the floating patches...
it's what I myself have been doing :)

Are you sure it's the same 404 error? I just tried the command myself and
it does fail at node-gyp rebuild but due to a bunch of CXX errors, not a
404.

—
Reply to this email directly or view it on GitHub
#1332 (comment).

kenany · 2015-04-03T17:26:07Z

@edwardsmarkf Oh, actually I think I might get it now. pangyp (and patched node-gyp) will indeed get 404 errors since you are using a nightly version of io.js. These releases aren't in https://iojs.org/dist/ hence the 404.

silverwind · 2015-04-03T17:37:38Z

@kenany so the fix would be for pangyp to use https://iojs.org/download/nightly/ for nightly builds, right?

edwardsmarkf · 2015-04-03T23:33:14Z

for now, sync-exec is working perfectly. if and when i run into another
npm issue, i will try removing npm and (re)installing from the nightly.
honestly, i cant remember how npm was installed originally, but i probably
used the simplest way using 'yum'.

i have installed probably 15 npm packages in the past, and exec-sync is the
only one that ever gave me any trouble at all.

iojs has a fantastic forum. thank you all for being so kind (too bad the
stackexchange snobs are so difficult to work with -- NO please don't ding
my stackexchange reputation for this comment either)

Thank you,

Mark Edwards

On Fri, Apr 3, 2015 at 10:38 AM, silverwind notifications@github.com
wrote:

@kenany https://github.com/KenanY so the fix would be for pangyp to use
https://iojs.org/download/nightly/ for nightly builds, right?

—
Reply to this email directly or view it on GitHub
#1332 (comment).

mscdex added the npm Issues and PRs related to the npm client dependency or the npm registry. label Apr 3, 2015

silverwind closed this as completed Apr 3, 2015

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

iojs and exec-sync #1332

iojs and exec-sync #1332

edwardsmarkf commented Apr 3, 2015

kenany commented Apr 3, 2015

edwardsmarkf commented Apr 3, 2015

mscdex commented Apr 3, 2015

silverwind commented Apr 3, 2015

edwardsmarkf commented Apr 3, 2015

Fishrock123 commented Apr 3, 2015

silverwind commented Apr 3, 2015

kenany commented Apr 3, 2015

edwardsmarkf commented Apr 3, 2015

kenany commented Apr 3, 2015

silverwind commented Apr 3, 2015

edwardsmarkf commented Apr 3, 2015

iojs and exec-sync #1332

iojs and exec-sync #1332

Comments

edwardsmarkf commented Apr 3, 2015

kenany commented Apr 3, 2015

edwardsmarkf commented Apr 3, 2015

mscdex commented Apr 3, 2015

silverwind commented Apr 3, 2015

edwardsmarkf commented Apr 3, 2015

Fishrock123 commented Apr 3, 2015

silverwind commented Apr 3, 2015

kenany commented Apr 3, 2015

edwardsmarkf commented Apr 3, 2015

{"node":"1.5.2-nightly201503173c8ae2d934","npm":"2.7.5"})

kenany commented Apr 3, 2015

silverwind commented Apr 3, 2015

edwardsmarkf commented Apr 3, 2015