It seems the correct fix to this error is to add
$ENV{GIT_EXEC_PATH} = "/usr/libexec/git-core";
to your .gitolite.rc file.
More Related Contents:
- gitosis vs gitolite? [closed]
- Specify an SSH key for git push for a given domain
- gitolite push error -> remote: ENV GL_RC not set
- How to sparsely checkout only one single file from a git repository?
- Can Git hook scripts be managed along with the repository?
- Having a hard time understanding git-fetch
- How can I view a git log of just one user’s commits?
- How to configure Git post commit hook
- Can I make git recognize a UTF-16 file as text?
- What’s the difference between Git Revert, Checkout and Reset?
- Making ‘git log’ ignore changes for certain paths
- Configuring diff tool with .gitconfig
- Windows git “warning: LF will be replaced by CRLF”, is that warning tail backward?
- How to undo “git commit –amend” done instead of “git commit”
- Undo git update-index –assume-unchanged
- How do I fetch only one branch of a remote Git repository?
- Git excludesfile for a branch
- Git push doesnt do anything over HTTPS
- Git – Checkout a remote tag when two remotes have the same tag name
- In git, is there a way to show untracked stashed files without applying the stash?
- How to move a git repository into another directory and make that directory a git repository?
- How do I update my bare repo?
- Fatal error “unsafe repository (‘/home/repon’ is owned by someone else)”
- How to attribute a single commit to multiple developers?
- What’s the use of the staging area in Git?
- Is “git push –mirror” sufficient for backing up my repository?
- Git pull fails with bad pack header error
- Error in git push heroku master through ssh behind proxy
- How do I fix “remote: fatal error in commit_refs” errors trying to push with Git?
- Git push error: RPC failed; result=56, HTTP code = 200 fatal: The remote end hung up unexpectedly fatal