Re: Debugging strange "corrupt pack" errors on SuSE 9

[Nicolas Pitre <nico@cam.org>]

On Wed, 20 Jun 2007, Martin Langhoff wrote:

> On 6/20/07, Nicolas Pitre <nico@cam.org> wrote:
> > Maybe the client machine runs git version < 1.4.2.2, in which case it is
> > possible that your push created a pack containing delta objects with
> > offset to base which git versions prior 1.4.2.2 do not understand.
> 
> Ouch. We weren't supposed to have non-backwards compatible changes...

Well... to be fair, we should say that your setup is a bit non 
conventional.

> > If this is the problem you are facing (the error message should confirm
> > this) then the easiest solution is to upgrade git on the client.
> 
> Ha ha. Not particularly easy, unfortunately.
> 
> > A quick fix for the client is to set repack.usedeltabaseoffset to
> > false on the machine where you have git 1.5 installed, then run "git
> > repack -a -d", and finally copy the pack over to the client repository.
> 
> That'll be a bit easier -- it's a fix we can do on the transfer repo
> ourselves.
> 
> Thanks! I do wonder though -- isn't a backwards-incompatible change
> like this worthy of don't we bump core.repositoryformatversion?

The repository hasn't really changed, and even such a version bump 
wouldn't help you anyway.

I also note that you're using cogito.  And from what I can deduce, it 
seems that cogito is simply copying the pack(s) over without further 
sanity checks.  This only serves to muddy things even further.

If your client machine is so important then you should consider 
upgrading to a later git version, and stop using cogito.  It will solve 
this pack problem, and you'll get added pack sanity checks as a bonus.


Nicolas