From: Gustaf Hendeby Date: Wed, 13 May 2009 11:45:43 GMT Subject: Re: Preemptive EOF when pushing (using Msys git and PuTTY) Message-ID: <4A0AB2E7.8080707@isy.liu.se> In-Reply-To: <4A0A8529.9010009@gmail.com> Luben Manolov wrote: > Hi Gustaf, > > I had exactly the same problem, which you have described below. We are > using MsysGit 1.6.3 and plink on Windows. The solution in our case was > to start using OpenSSH (the version from msysgit) instead of PuTTY/plink. Thanks Luben! I will test that solution the next time the problem arises. Hopefully it solves the problem for people. /Gustaf > > Best regards, > > Luben > >> Hello everyone, and thanks for all your dedicated work with git. >> >> I have used git for quite some time now, mainly on different Linux >> platforms, without any problems. Recently we convert the office's pet >> project from svn to git. Many people at the office use Windows (Msys >> git 1.6.2 and plink), and I have stared to see (only from Windows >> people) problems when pushing similar to the following: >> >> Counting objects: 422, done. >> Compressing objects: 422, done. >> Writing objects: 100% (379/379), 77.77 KiB, done. >> Total 379 (delta 310), reused 371 (delta 303) >> fatal: early EOF >> error: unpack failed: index-pack abnormal exit >> To jkoehler serv-4100:/git/argos.git >> ![remote rejected] jk/ellipseFit -> jk/ellipseFit (n/a (unpacker error)) >> error: failed to push some refs to >> 'jkoehler serv-4100:/git/argos.git' >> >> There seems to be no problem with the repo, neither local nor remote, >> but for a specific setup the problem is reproducible on several Windows >> machines, but if I move the whole local repo to a Linux machine instead >> the problem is gone. >> >> I suspect the problem is that a ^Z EOF gets embedded in the pack to be >> transported, and that somehow interacts poorly with PuTTY, but that is >> just my guessing. And if so I don't know how to handle it. >> >> Has anyone experienced anything similar? If so, is there any simple fix >> to the problem? How would I go about to try to debug this? >> Unfortunately, this seems to happen on a regular basis and affects the >> git experience in a negative way, so I would be really happy to be able >> to resolve the problem. >> >> I'm thankful for any help that I can get. >