Re: unpacker error on push

From: Nicolas Pitre <nico@fluxnic.net>
Date: Jun 16, 2010, 19:34 UTC
Message-ID: <alpine.LFD.2.00.1006161520480.13427@xanadu.home>
In-Reply-To: <0B32FF97-4B20-4B9A-BA45-08EF9485F3A1@nvidia.com>

On Wed, 16 Jun 2010, Gavin Kistner wrote:

> (my apologies if you receive this twice; I sent it once before I was 
> authenticated on the mailing list)

This list doesn't require you to be subscribed for you to post messages.

Show 18 quoted lines

> Local: OS X 10.6.3, git 1.7.1
> Remote: Ubuntu Lucid, git 1.7.0.4
> 
> How can I fix whatever is broken so that I can push again, and—more 
> importantly—get the important changes I made last night over to the 
> remote, by hook or by crook?> -_-_-_-_-_-_-_-_-_-_ On the local 
> machine -_-_-_-_-_-_-_-_-_-_
> 
> Slim2:bugbot3 phrogz$ git push
> Counting objects: 70, done.
> Delta compression using up to 2 threads.
> Compressing objects: 100% (31/31), done.
> Writing objects: 100% (40/40), 26.91 KiB, done.
> Total 40 (delta 11), reused 37 (delta 8)
> error: unpack failed: unpack-objects abnormal exit
> To git://10.20.16.110/bugbot3.git
> ! [remote rejected] planning -> planning (n/a (unpacker error))
> error: failed to push some refs to 'git://10.20.16.110/bugbot3.git'

Could you try doing "git config receive.unpackLimit 1" on the _remote_ machine in the receiving repository?

Note this is not a proper fix but rather an attempt to isolate the issue. Please make a backup of the entire repository both on the local and the remote machine if you can, so the failure can be reproduced again after restoring them to the current state in case this would "fix" the issue.

Nicolas