On Jun 18, 2010, at 11:35 AM, Nicolas Pitre wrote: > On Fri, 18 Jun 2010, Gavin Kistner wrote: > >> On Jun 16, 2010, at 1:34 PM, Nicolas Pitre wrote: >>> On Wed, 16 Jun 2010, Gavin Kistner wrote: >>>> 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? >> >> I ran into this problem again. I backed up both repositories in full, >> ran the command above in the remote repository, and it did not fix the >> problem. > > The error message changed a bit though, right? Yes, it failed in "index-pack" instead of "unpack-objects". Here's the new result: Counting objects: 116, done. Delta compression using up to 2 threads. Compressing objects: 100% (63/63), done. Writing objects: 100% (63/63), 11.19 KiB, done. Total 63 (delta 40), reused 0 (delta 0) error: unpack failed: index-pack 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' >> I deleted my local copy and cloned using ssh instead if git://, copied >> over the same changes and was able to push again. This looks to be my >> workaround. >> >> If anyone wants to dive deeper into this problem, please let me know >> and we can fight it using the snapshots I have. > > I would be interested in them. OK, I'll coordinate with you off-list. ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ----------------------------------------------------------------------------------- -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html