tags:

views:

949

answers:

3

So I created a remote repo that's not bare (because I need redmine to be able to read it), and it's set to be shared with the group (so git init --shared=group). I was able to push to the remote repo and now I'm trying to clone it.

If I clone it over the net I get this:

remote: Counting objects: 4648, done.

remote: Compressing objects: 100% (2837/2837), done.

error: git-upload-pack: git-pack-objects died with error.B/s

fatal: git-upload-pack: aborting due to possible repository corruption on the remote side.

remote: aborting due to possible repository corruption on the remote side.

fatal: early EOF

fatal: index-pack failed

I'm able to clone it locally without a problem, and I ran "git fsck", which only reports some dangling trees/blobs, which I understand aren't a problem. What could be causing this? I'm still able to pull from it, just not clone. I should note the remote git version is 1.5.6.5 while local is 1.6.0.4

I tried cloning my local copy of the repo, stripping out the .git folder and pushing to a new repo, then cloning the new repo and I get the same error, which leads me to believe it may be a file in the repo that's causing git-upload-pack to fail...

Edit: I have a number of windows binaries in the repo, because I just built the python modules and then stuck them in there so everyone else didn't have to build them as well. If I remove the windows binaries and push to a new repo, I can clone again, perhaps that gives a clue. Trying to narrow down exactly what file is causing the problem now.

+1  A: 

Does "git gc" complain?

Yann Ramin
Nope, seems to work just fine.
gct
I don't know how, but running that command first fixed it for me.
Derek Dahmer
A: 

I'm getting the same error. Remote is 1.5.6.5, local is 1.6.6.1. Seems to only happen for my OSX, ol' cygwin's not having any trouble

A: 

Did you do by any chance make file name changes switching from upper to lowercase or vice versa? I have exactly the same problem on my Mac and I also can still clone the repo on for example another Linux machine. It's just Mac which causes the problem. The only thing which I've done in my last commit which was "different" do my normal usage was to change some file names from upper to lower case. In fact I had some troubles doing though due to the strange handling of filename which differ only in the case on Mac.

Did you manage to restore your repo? So far I haven't found a way to fix the error.

Hardy