Re: unexpected EOF?

From: Tim O'Callaghan <timo@dspsrv.com>
Date: Dec 1, 2005, 13:49 UTC
Message-ID: <20051201134917.GH2188@ELSAMSW37164>
In-Reply-To: <E1EhohG-0001iZ-IB@jdl.com>

On Thu, Dec 01, 2005 at 07:42:02AM -0600, Jon Loeliger wrote:

Show 40 quoted lines

> 
> I thought I had imagined this last time, but now 
> that it has happened twice, I'm not so sure what
> is going on.  First pull attempt garners an
> unexpected EOF message; immediately pull again
> seems to work.
> 
> Some state:
> 
> jdl@ubuntu:/usr/src/git-core$ git --version
> git version 0.99.9j
> 
> jdl@ubuntu:/usr/src/git-core$ cat .git/remotes/origin
> URL: git://git.kernel.org/pub/scm/git/git.git/
> Pull: master:origin
> Pull: todo:todo
> Pull: maint:maint
> Pull: pu:pu
> 
> And the error capture:
> 
> jdl@ubuntu:/usr/src/git-core$ git pull origin
> fatal: unexpected EOF
> Fetch failure: git://git.kernel.org/pub/scm/git/git.git/
> jdl@ubuntu:/usr/src/git-core$ git pull origin
> Unpacking 17 objects
>  100% (17/17) done
> * committish: d175455acaaba6bd39dd2d5ec71961bf238f06d4
>   branch 'todo' of git://git.kernel.org/pub/scm/git/git
> * refs/heads/todo: same as branch 'todo' of git://git.kernel.org/pub/scm/git/git* committish: 93dcab2937624ebb97f91807576cddb242a55a46
>   branch 'maint' of git://git.kernel.org/pub/scm/git/git
> * refs/heads/maint: same as branch 'maint' of git://git.kernel.org/pub/scm/git/git
> * committish: b34403aa97047f90c0cdd5177e63a8e7530e3388
>   branch 'master' of git://git.kernel.org/pub/scm/git/git
> * refs/heads/origin: same as branch 'master' of git://git.kernel.org/pub/scm/git/git
> * committish: 6e35634a4d595d554423b04438bfa8b523414c54
>   branch 'pu' of git://git.kernel.org/pub/scm/git/git
> * refs/heads/pu: does not fast forward to branch 'pu' of git://git.kernel.org/pub/scm/git/git;
>   not updating.
> Already up-to-date.

I noticed this myself this morning. It happened twice, then after leaving it for a minute or two, it worked. Possibly traffic problems to kernel.org?

I should also report that if a spurious lockfile exists (under cygwin at least), git just dies with the cryptic "unable to create new cachefile".

Tim. "I've worked myself up from nothing to a state of supreme poverty." -- Groucho Marx