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.



Andy
-- 
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail.com
-

[ message continues ]

Bad voodoo.  What does 'git fetch -k' do?  It uses slightly
different code for handling the deltas...

-- 
Shawn.
-

[ message continues ]

Happened to me yesterday or so pulling the vanilla kernel (big push shortly
before 2.6.20-rc1). Trying again somewhat later went through flawlessly.
Might have been git running out of memory.
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                    Fono: +56 32 2654431
Universidad Tecnica Federico Santa Maria             +56 32 2654239
Casilla 110-V, Valparaiso, Chile               Fax:  +56 32 2797513

-

[ message continues ]

This is a very possible cause, especially if both processes 
(pack-objects and unpack-objects) are running at the same time on the 
same machine.


Nicolas
-

[ message continues ]

Andy, which version of git do you run (I presume they are the
same version, as you are doing the local fetching), and which
version of git was the "slightly out of date" repository
prepared with?

I think this is the second time I've seen a report of unpacker
barfing on the mailing list.  Nico, anything rings a bell?


-

[ message continues ]

One of them is switched off and in another place at the moment, so this is 
from memory:

The initial repository was made with origin/master from a few days ago, that's 
the one I've been calling "out-of-date".  I cloned that to another computer 
and continued adding patches using "1.4.4.1.g3ece-dirty" (the dirt is just my 
colour branch patch on top of ba988a83).  The fetch is being done back on the 
original system which has the newer git but older repository.

I hadn't realised it was quite a serious as these responses are making it 
sound.  I'll gather more precise data upon my return home.

On the up-to-date computer I've just made a fresh repository, set .git/config 
to point locally at the full repository and ran git-fetch.  Interestingly, 
that has worked perfectly.

Clearly it is version-specific.  I'll do a bit of bisection later and see if I 
can nail the problem down.


Andy

-- 
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com
-

[ message continues ]

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


Nicolas
-

[ message continues ]