CODEWITHSUNDEEP
gitolitetortoisegitgit-pull
arnie
arnie

Reputation: 85

Pull not working - TortoiseGIT / Windows 7 / GIT on Debian + gitolite

i have a weird issue. Im using TortoiseGIT (Win7) and my repositories are placed on a vritual server (Debian), where im using gitolite and SSH keys.

I can clone the repository to my PC, i can run Fetch, Push, Commit, Sync .. everything, but when trying to Pull the changes from server Pushed by other contributor, the following error appears:

git.exe pull -v --progress      "origin"
fatal: 'pull' appears to be a git command, but we were not
able to execute it. Maybe git-pull is broken?
git did not exit cleanly (exit code 128)

I don't understand, why just the pull command is not working .. thanks for any help.

I can make a clone of the repository, with the contributed changes .. but can not Pull the changes to created repository on my PC.

Upvotes: 8

Views: 5966

Answers (4)

CW0lf
CW0lf

Reputation: 29

I see that you're able to run "git fetch". If you can also run "git merge", running the sequence "git fetch" followed by "git merge" will accomplish the same thing as "git pull".

Source: http://git-scm.com/docs/git-pull

Upvotes: 0

Peter
Peter

Reputation: 1715

I encountered this same issue after changing the git Bash executable sh.exe to be always run as administrator (to get round another problem). It then left git unable to access it under certain scenarios and caused various "Maybe git-* is broken?" errors. Perhaps this might help someone...

Upvotes: 13

Steven
Steven

Reputation: 3250

Uninstalling old Git and reinstalling the latest build fixed this issue for me.

Here's a link to the installers Link to get installers

My exact error message was 

C:\Program Files (x86)\Git/libexec/git-core\git-pull: line 304: exec: git-merge: not found
fatal: 'pull' appears to be a git command, but we were not
able to execute it. Maybe git-pull is broken?

Upvotes: 2

VonC
VonC

Reputation: 1328912

The error message is very much linked to Git, and comes from help.c:

static const char bad_interpreter_advice[] =
  N_("'%s' appears to be a git command, but we were not\n"
  "able to execute it. Maybe git-%s is broken?");

That is similar to issue 40 (of another GUI, here terminal-ide).

In that case, it was due to the remote Git installation, which was incomplete

(Comments 3 of issue 19)

git-merge was also missing from install, can be fixed with

$> ln -s git git-merge

in system/bin/

The resolution might not be exactly the same in your case, but it could be related to a faulty Git installation.

Upvotes: 1

Related Questions