Git checking out problem [fatal: early EOFs]

Question

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.

score 6 · Answer 1 · edited May 23 '17 at 12:09

6

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

edited May 23 '17 at 12:09

Community

1
1

answered Mar 24 '10 at 06:43

VonC

1,262,500
529
4,410
5,250

1

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 Apr 07 '10 at 16:21
@Style: thank you for the feedback. I have update my answer to reflect the root cause you mention. – VonC Apr 07 '10 at 18:47
1

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 Apr 08 '10 at 02:22

score 4 · Answer 2 · edited Aug 12 '14 at 21:13

4

@rickb I found that running

git config --add core.compression -1

in the client (cygwin) repository fixed it.

edited Aug 12 '14 at 21:13

Druid

6,423
4
41
56

answered Nov 01 '10 at 23:48

Voket

331
2
2

Worked for me, Ubuntu 12.10, git 1.7.10.4 – WearyMonkey Dec 31 '12 at 22:43
Worked for me, MacOS X 10.8.4, git version 1.7.12.4 – Uygar Y Sep 12 '13 at 08:52

score 3 · Answer 3 · edited Aug 28 '13 at 20:38

3

git config --global --add core.compression -1

edited Aug 28 '13 at 20:38

Matt Bryant

4,841
4
31
46

answered Aug 28 '13 at 20:21

GermanF

51
4

score 1 · Answer 4 · answered Aug 17 '10 at 14:29

1

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

answered Aug 17 '10 at 14:29

Sverre

11
1

score 0 · Answer 5 · edited May 23 '17 at 12:30

0

Checkout this answer: https://stackoverflow.com/a/6849424

also you can try: git config --global core.compression 0 tp disable the compressions.

edited May 23 '17 at 12:30

Community

1
1

answered Nov 20 '16 at 09:49

Mohammad AlQanneh

3,227
1
16
14

score 0 · Answer 6 · answered Jan 25 '11 at 14:32

0

Try msysgit. I had the same issue with cygwin's git, and when I fetched the same repository using msysgit it worked first time.

See also this thread: http://cygwin.com/ml/cygwin/2010-09/msg00832.html

answered Jan 25 '11 at 14:32

Tim Abell

11,186
8
79
110

Git checking out problem [fatal: early EOFs]

6 Answers6

Linked