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

installation fail :( #205

Open
imgntn opened this issue Aug 6, 2012 · 3 comments
Open

installation fail :( #205

imgntn opened this issue Aug 6, 2012 · 3 comments

Comments

@imgntn
Copy link

imgntn commented Aug 6, 2012

running ubuntu 12.04 LTS...


node-gyp configure build

gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: EACCES, stat '/root/.node-gyp/0.8.5'
gyp ERR! System Linux 3.2.0-27-virtual
gyp ERR! command "node" "/usr/lib/nodejs/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "build"
gyp ERR! cwd /home/ubuntu/foodpoisoning/backend/node_modules/now/node_modules/node-proxy
gyp ERR! node -v v0.8.5
gyp ERR! node-gyp -v v0.6.3
gyp ERR! not ok
npm ERR! [email protected] install: node-gyp configure build
npm ERR! sh "-c" "node-gyp configure build" failed with 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the node-proxy package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp configure build
npm ERR! You can get their info via:
npm ERR! npm owner ls node-proxy
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.2.0-27-virtual
npm ERR! command "nodejs" "/usr/bin/npm" "install" "now"
npm ERR! cwd /home/ubuntu/foodpoisoning/backend
npm ERR! node -v v0.8.5
npm ERR! npm -v 1.1.46
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/ubuntu/foodpoisoning/backend/npm-debug.log
npm ERR! not ok code 0

@flosse
Copy link

flosse commented Aug 17, 2012

...same problem with v0.8.7

@goldfire
Copy link

It looks like the problem might actually be with node-proxy, if the error messages are to be trusted.

@jhvst
Copy link

jhvst commented Aug 24, 2012

It surely seems so. Kind of pity that I can't deploy my applications either.

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

4 participants