Error: Could not locate git binary #425

Closed
jitendravyas opened this Issue Feb 7, 2013 · 4 comments

Comments

Projects
None yet
3 participants
@jitendravyas

I'm getting this error when I install HTML5 boilerplate with grunt option.

My os is windows 8 - 64bit
npm version - 1.2.10
node.js version - 0.8.19
Docpad version - 6.21.10

info: Installing the HTML5 Boilerplate with Grunt skeleton into E:\myblog
error: An error occured:
Error: Could not locate git binary
at balUtilModules.getGitPath (C:\Users\jitendra\AppData\Roaming\npm\node_mod
ules\docpad\node_modules\bal-util\out\lib\modules.js:294:23)
at _Class.next (C:\Users\jitendra\AppData\Roaming\npm\node_modules\docpad\no
de_modules\bal-util\out\lib\modules.js:180:16)
at _Class.balUtilFlow.Group._Class.exit (C:\Users\jitendra\AppData\Roaming\n
pm\node_modules\docpad\node_modules\bal-util\out\lib\flow.js:479:14)
at _Class.balUtilFlow.Group._Class.complete (C:\Users\jitendra\AppData\Roami
ng\npm\node_modules\docpad\node_modules\bal-util\out\lib\flow.js:438:18)
at balUtilFlow.Group._Class.completer (C:\Users\jitendra\AppData\Roaming\npm
\node_modules\docpad\node_modules\bal-util\out\lib\flow.js:450:31)
at balUtilModules.determineExecPath (C:\Users\jitendra\AppData\Roaming\npm\n
ode_modules\docpad\node_modules\bal-util\out\lib\modules.js:194:22)
at balUtilPaths.exists (C:\Users\jitendra\AppData\Roaming\npm\node_modules\d
ocpad\node_modules\bal-util\out\lib\paths.js:140:18)
at Object.fs.exists as oncomplete

E:\myblog>

@SteveMcArthur

This comment has been minimized.

Show comment
Hide comment
@SteveMcArthur

SteveMcArthur Apr 7, 2013

Contributor

This seems to occur when you try to install the template on a drive other than C:. I got the same error when trying to run it on my D:\ drive but it worked fine on the C:\

Contributor

SteveMcArthur commented Apr 7, 2013

This seems to occur when you try to install the template on a drive other than C:. I got the same error when trying to run it on my D:\ drive but it worked fine on the C:\

@SteveMcArthur

This comment has been minimized.

Show comment
Hide comment
@SteveMcArthur

SteveMcArthur Apr 7, 2013

Contributor

Seems to be fixed by adding the path to the git binary (probably: C:\Program Files\Git\bin) to the "Path" environment variable

Contributor

SteveMcArthur commented Apr 7, 2013

Seems to be fixed by adding the path to the git binary (probably: C:\Program Files\Git\bin) to the "Path" environment variable

@balupton

This comment has been minimized.

Show comment
Hide comment
@balupton

balupton Apr 7, 2013

Member

Yeah, adding it to your path is the recommended way of resolving this, as seen by our node.js installation instructions. In the error message should we add a link to an article where people can read up on this? Perhaps even this issue?

Member

balupton commented Apr 7, 2013

Yeah, adding it to your path is the recommended way of resolving this, as seen by our node.js installation instructions. In the error message should we add a link to an article where people can read up on this? Perhaps even this issue?

@balupton balupton closed this Apr 7, 2013

@balupton

This comment has been minimized.

Show comment
Hide comment
@balupton

balupton Apr 8, 2013

Member

Added a reference to this issue in the troubleshooting guide.

Member

balupton commented Apr 8, 2013

Added a reference to this issue in the troubleshooting guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment