git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-fetch fails with error code 128
Date: Thu, 14 Dec 2006 21:25:06 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0612142120260.18171@xanadu.home> (raw)
In-Reply-To: <200612142308.45376.andyparkins@gmail.com>

On Thu, 14 Dec 2006, Andy Parkins wrote:

> Hello,
> 
> This is with my big "every linux patch" repository that I talked about in 
> another thread.  To bring you up to speed:
> 
>  1. Made repository
>  2. Made a zip of the .git directory
>  3. Copied the zip elsewhere
>  4. Extracted it into a temporary directory
>  5. Went to an out-of-date version of this repository
>  6. Used git-fetch to update it.
> 
> This gave me the following output:
> 
> $ git fetch
> remote: Generating pack...
> remote: Done counting 189146 objects.
> remote: Result has 186566 objects.
> remote: Deltifying 186566 objects.
> remote:  100% (186566/186566) done
> Unpacking 186566 objects
> fatal: failed to apply delta
> fatal: unpack-objects died with error code 128
> Fetch failure: /home/andyp/projects/temp/.git
> 
> What does that mean?  I ran fsck --full on the source repository, but it's 
> made no difference.

Could you please instrument patch-delta.c to determine which of the
"return NULL" is executed?



      parent reply	other threads:[~2006-12-15  2:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14 23:08 git-fetch fails with error code 128 Andy Parkins
2006-12-14 23:19 ` Shawn Pearce
2006-12-14 23:25 ` Horst H. von Brand
2006-12-15  2:31   ` Nicolas Pitre
2006-12-15  0:02 ` Junio C Hamano
2006-12-15  9:46   ` Andy Parkins
2006-12-15 21:55     ` Junio C Hamano
2006-12-15 22:13       ` Nicolas Pitre
2006-12-16  0:37         ` Junio C Hamano
2006-12-16 13:29         ` Andy Parkins
2006-12-16 22:12       ` Andy Parkins
2006-12-15  2:25 ` Nicolas Pitre [this message]

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=Pine.LNX.4.64.0612142120260.18171@xanadu.home \
    --to=nico@cam.org \
    --cc=andyparkins@gmail.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;
as well as URLs for NNTP newsgroup(s).