views:

424

answers:

4

Dear all,

I'm running a Ubuntu (9.10) server with Git (latest from Ubuntu package manager) installed. Access to the Git is via SSH. On windows machines, I'm using Cygwin to push/pull code.

I can push my project code onto the server but when I do a clone or pull, it returns a [fatal: early EOFs] error at about 75-80%.

Upon further investigation, it seems like textual data has no issue when pulled/cloned but when the jar files and images are pulled from Git, the error will occur.

Any suggestion/advice that can help to resolve this issue?

Thanks in advance.

+3  A: 

What is the Git version are you using (Ubuntu 9.10 packages mentions 1.6.3)

A recent thread reported a similar issue with Git1.7.1, although it was from a Cygwin environment.

$ git clone git:/repo/git/acl acl.test
  Initialized empty Git repository in /c/tmp/acl.test/.git/
  remote: Counting objects: 9205, done.
  remote: Compressing objects: 100% (3300/3300), done.
  fatal: The remote end hung up unexpectedly
  fatal: early EOFs:  62% (5708/9205)
  fatal: index-pack failed

Did you try downgrade your Git (on the server side and/or the client side) and see if the problem persists?


As the OP Style reports in the comments, the message can also be trigger by an incorrect protocol:

git+ssh://

instead of just:

ssh:// + git command

VonC
Sorry to reply so late, the solution seems to be due to how I log into the repository. Previously I was using "git+ssh://". When I changed to log in using "ssh://" followed by git command, the error is gone :)
Style
@Style: thank you for the feedback. I have update my answer to reflect the root cause you mention.
VonC
@VonC: most welcome :) I want to mark your answer as useful but not enough reputation points >< But I'm really amazed and loving the community here. Nice to meet you! Stack overflow rocks, Git too ;)
Style
@Style: You are welcome :) According to http://stackoverflow.com/faq, you can mark an answer as accepted, you just cannot yet upvote it (not until you reach 15 reputation points)
VonC
A: 

For some reason, the problem went away after I enabled Compression in the ~/.ssh/config file. God knows why.

Sverre
A: 

Sorry, this isn't an answer but a question - on which side did you enable the compression? Ubuntu or Win/cygwin?

I'm having the same problems - version 1.7.2.3 on cygwin, 1.7.3.1 on Mac OS X

rickb