git-blame icon indicating copy to clipboard operation
git-blame copied to clipboard

Can't update from 0.4.0 to 0.4.2

Open jelmerdemaat opened this issue 9 years ago • 10 comments

The update of git-blame (0.4.0 to 0.4.2) fails with this error:

\> [email protected] install C:\Users\username\AppData\Local\Temp\apm-install-dir-11541-7600-6asi0q\node_modules\git-blame\node_modules\pathwatcher\node_modules\runas
\> node-gyp rebuild


C:\Users\username\AppData\Local\Temp\apm-install-dir-11541-7600-6asi0q\node_modules\git-blame\node_modules\pathwatcher\node_modules\runas>node "C:\Users\username\AppData\Local\atom\app-0.196.0\resources\app\apm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild 

gypnpm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Users\\username\\AppData\\Local\\atom\\app-0.196.0\\resources\\app\\apm\\bin\\\\node.exe" "C:\\Users\\username\\AppData\\Local\\atom\\app-0.196.0\\resources\\app\\apm\\node_modules\\npm\\bin\\npm-cli.js" "--globalconfig" "C:\\Users\\username\\.atom\\.apm\\.apmrc" "--userconfig" "C:\\Users\\username\\.atom\\.apmrc" "install" "C:\\Users\\username\\AppData\\Local\\Temp\\d-11541-7600-jcsz2m\\package.tgz" "--target=0.22.0" "--arch=ia32"
npm ERR! node v0.10.35
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the runas 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 runas
npm ERR! There is likely additional logging output above.

Computer details: up-to-date Windows 7, Atom 0.196.0

U:\>apm -v
apm  0.164.0
npm  2.5.1
node 0.10.35
python
git 1.9.5.msysgit.0
visual studio

jelmerdemaat avatar May 01 '15 12:05 jelmerdemaat

Have you read through atom/node-runas#5? Might be related.

driskell avatar May 01 '15 17:05 driskell

Same for me :/

jakubhruby avatar May 05 '15 12:05 jakubhruby

Looks like you're on Windows? All other plugins are working fine?

alexcorre avatar May 07 '15 00:05 alexcorre

In my case it's Win 8.1 x64, all other plugins work fine.

jakubhruby avatar May 07 '15 07:05 jakubhruby

My case is indeed Windows 7, also x64, other plugins work fine.

Does https://github.com/atom/node-runas/issues/5 mean I have to installl Python myself to be able to update this plugin?

jelmerdemaat avatar May 07 '15 09:05 jelmerdemaat

I can +1 that I am also having this problem, running Windows 8.1 x64. Installing Python and Visual Studio is not an acceptable workaround. It looks like the issue @jelmerdemaat referenced is an atom bug... Should I be re-reporting this issue elsewhere?

shawmanz32na avatar May 07 '15 18:05 shawmanz32na

I also had this problem, and have seen similar problems caused by python 2.x vs python 3.x issues.

I have both installed, but python 3 is first in the path, which makes node-gyp choke.

So my solution was to run the following commands in an elevated command prompt:

C:\>SET PATH=C:\python27;%PATH%
C:\>apm update git-blame 

which successfully updated package from 0.4.0 to 0.4.3

vegar avatar May 21 '15 17:05 vegar

Installing Python locally should not be a requirement for an extension like this and is not an acceptable solution for me, unfortunately...

jelmerdemaat avatar May 22 '15 08:05 jelmerdemaat

Since atom is build on top of node and npm, I'm afraid you won't come far without, since many npm packages relay on python being available.

But of cause, it wouldn't hurt if it wasn't so.

vegar avatar May 22 '15 09:05 vegar

I'm hitting this problem on Ubuntu 15.04. However, running npm install -g runas works fine. apm -v outputs the following.

apm  1.4.0
npm  2.13.3
node 0.10.40
python 2.7.9
git 2.1.4

pkkid avatar Dec 08 '15 21:12 pkkid