git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Tom Sgouros <tomfool@as220.org>, git@vger.kernel.org
Subject: Re: mysterious error message
Date: Fri, 26 Sep 2008 07:26:48 -0700	[thread overview]
Message-ID: <20080926142648.GV3669@spearce.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0809261400400.13830@pacific.mpi-cbg.de.mpi-cbg.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Thu, 25 Sep 2008, Tom Sgouros wrote:
> 
> > I receive the following error message when I try to do a 'git push':
> > 
> >   tomfool@toms-box:hpl$ git push
> >   updating 'refs/heads/master'
> >     from ad4ae7925d3dd23798e7c5b733d2d8f930f7410f
> >     to   5b5f5fae014a4f3535fa10b0f6e28b4bf3225dc3
> >    Also local refs/remotes/origin/master
> >   Generating pack...
> >   Done counting 10 objects.
> >   Deltifying 10 objects...
> >   error: pack-objects died with strange error
> >   unpack eof before pack header was fully read
> >   ng refs/heads/master n/a (unpacker error)
> >   error: failed to push to 'ssh://tomfool@as220.org/home/tomfool/hpl.git'
> >   tomfool@toms-box:hpl$
> 
> I got this message when I tried to push a project with submodules to a 
> server which had submodule-ignorant git installed.  Maybe it's that?

Almost.

I think its that there are submodules in the local side and they are
being pushed to the remote peer, but the git binary on the client
that is being used to execute git-push doesn't know about submodules.

"error: pack-objects died with strange error":

This was pack-objects aborting when it saw a subtree entry and it
couldn't trace down that path in order to include it into the pack.

"unpack eof before pack header was fully read":

This is the server side aborting because its gotten the command
set from the git-push client, but pack-objects never even got to
create the pack header, since it couldn't generate the full list
of objects it needed to include.

Tom, try upgrading to a Git implementation on the client.  It seems
to me that this repository must have been moved here by means outside
of Git (NFS mount?), or the client got downgraded (wrong $PATH?)

-- 
Shawn.

  reply	other threads:[~2008-09-26 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-25 21:33 mysterious error message Tom Sgouros
2008-09-26  8:20 ` Uwe Kleine-König
2008-09-26 14:29   ` tom sgouros
2008-09-26 12:01 ` Johannes Schindelin
2008-09-26 14:26   ` Shawn O. Pearce [this message]
2008-09-26 14:32   ` tom sgouros
2008-09-26 14:37     ` Shawn O. Pearce
2008-09-28 15:18       ` tom sgouros

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080926142648.GV3669@spearce.org \
    --to=spearce@spearce.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=tomfool@as220.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).