search

FredrikNoren / ungit

The easiest way to use git. On any platform. Anywhere.
MIT License
10.44k stars 640 forks source link

Error installation ungit #584

Open Gagi33 opened 9 years ago

Gagi33 commented 9 years ago

When I tried to install ungit, i have these errors :

npm WARN engine forever-monitor@1.1.0: wanted: {"node":"0.8.x"} (current: {"node":"0.12.5","npm":"2.11.2"})

typechecker@2.0.8 preinstall /usr/local/lib/node_modules/ungit/node_modules/getmac/node_modules/extract-opts/node_modules/typechecker node ./cyclic.js

npm WARN engine hawk@0.10.2: wanted: {"node":"0.8.x"} (current: {"node":"0.12.5","npm":"2.11.2"}) npm WARN engine hoek@0.7.6: wanted: {"node":"0.8.x"} (current: {"node":"0.12.5","npm":"2.11.2"}) npm WARN engine sntp@0.1.4: wanted: {"node":"0.8.x"} (current: {"node":"0.12.5","npm":"2.11.2"}) npm WARN engine cryptiles@0.1.3: wanted: {"node":"0.8.x"} (current: {"node":"0.12.5","npm":"2.11.2"})

npm WARN engine boom@0.3.8: wanted: {"node":"0.8.x"} (current: {"node":"0.12.5","npm":"2.11.2"})

ws@0.4.32 install /usr/local/lib/node_modules/ungit/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws

(node-gyp rebuild 2> builderror.log) || (exit 0)

And the installation stop. What can i do ?

Thank you for helping.

FredrikNoren commented 9 years ago

@Gagi33 can you give some more details about which system you are on, and which node and npm versions you are using? It looks like socket.io fails to install for some reason

nicolaiskogheim commented 9 years ago

I got all the same errors (err, warnings) just now when installing the latest version through npm. ungit works like a charm none the less.

ungit 0.9.3 osx 10.9.5 node 0.12.7

beeAzul commented 8 years ago

Hi @FredrikNoren, I have the same error than @Gagi33 , my version of npm is 3.3.7, I have ugraded it today, I don't have found any solution to resolve my problem, please help me and this error : image

FredrikNoren commented 8 years ago

@beeAzul Which version of git is that?

jung-kim commented 8 years ago

@beeAzul Error displayed seems to be different then this issue, should it be separate issue?

@FredrikNoren Maybe we should ignore this particular error for git log op as it isn't an error from ungits point of view

beeAzul commented 8 years ago

I have installed the last version of git. When I have wached your video where you explain how ungit work, you don't have any error, but me, "after my npm install -g ungit" I always have this error.

Do you have an idea?

beeAzul commented 8 years ago

So, can you tell me what is this command, and why it does'nt work, if this command can't be use in windwos, maybe i have to to edit the code which is used to run this comand

Ajedi32 commented 8 years ago

@beeAzul The error in the screenshot you posted seems to be caused by Ungit trying to run git log in an empty repository with no commits. Seems like a separate problem from the one in this issue though.

beeAzul commented 8 years ago

Hi, I bring the subject up because I have'nt found a solution to my problem. I have understood that the problem come from ungit which can't run some command like "-c color.ui=false".

I think Ungit don't work correctly with windows, I have the last version of node.js and the last version of npm. Maybe it was working before with some version of npm and node.js.

when I installed GIt (last version) I configured it with option for windows

Ajedi32 commented 8 years ago

-c color.ui=false isn't a command, it's just one of the options being passed to git. The actual command being run is just git log, which is erroring out because there are no commits in your repository (as the error message says).

As a temporary work-around you should open a command line and make the first commit manually. After that ungit should work.

The long term fix is to patch ungit so that particular error isn't treated as an error anymore. But that's a separate issue from the one posted by the OP here.