Git development
 help / color / mirror / Atom feed
From: Peter Bengtson <peter@peterbengtson.com>
To: git@vger.kernel.org
Subject: Submodule on Debian breaks
Date: Thu, 15 May 2008 14:29:54 +0200	[thread overview]
Message-ID: <06D015DD-6F3B-4D2E-8305-BDD062F149E6@peterbengtson.com> (raw)

We have problems cloning git repositories containing submodules on  
Debian. Cloning them locally, on Debian, or on Mac OS X, works without  
a hitch. Cloning them remotely from a Mac OS X repo server to a Mac OS  
X client computer also works as expected, as does cloning repos  
without submodules.

But as soon as a clone of a git repo containing a submodule on the  
Debian machine is attempted from another computer, this happens:

> error: git-upload-pack: git-pack-objects died with error.
> fatal: git-upload-pack: aborting due to possible repository  
> corruption on the remote side.
> remote: Generating pack...
> remote: Done counting 7 objects.
> remote: error: unable to find  
> 4d5436979e0afc1e9c03dceeeea3c2ddb9dbf211remote:
> remote: fatal: unable to get type of object  
> 4d5436979e0afc1e9c03dceeeea3c2ddb9dbf211
> remote: aborting due to possible repository corruption on the remote  
> side.
> fatal: early EOF
> fatal: index-pack failed

However, git fsck reports no errors.

The git version is the latest published one, 1.5.5.1, installed from  
source (not via apt-get), and configured only with ./configure -- 
prefix=/usr/local

Googling for info about git submodule and corrupted repos yields  
absolutely nothing.

Any ideas, anyone?

	/ Peter Bengtson

             reply	other threads:[~2008-05-15 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 12:29 Peter Bengtson [this message]
2008-05-15 12:55 ` Submodule on Debian breaks Johannes Schindelin

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=06D015DD-6F3B-4D2E-8305-BDD062F149E6@peterbengtson.com \
    --to=peter@peterbengtson.com \
    --cc=git@vger.kernel.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