"Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: >> On Tue, 27 Jan 2009, PJ Hyett wrote: >> >> > To expand further, here's the output from the command line when this happened. >> > >> > ~/Development/github(jetty)$ git push pjhyett jetty >> > fatal: bad object e13a86261c6e710af8fd4b5fb093b28b8583d820 >> > error: pack-objects died with strange error >> > error: failed to push some refs to 'git@xxxxxxxxxx:pjhyett/github.git' >> >> Hmm. The only thing I could think of is that the pack-objects used by >> your git-daemon is somehow not at the right version... > > No, that's pack-objects on the client. > > Its freaking weird. I don't know why a server side upgrade would > cause this on the client side. > > FWIW, in 1.6.1 the only mention of those bad object messages > is inside revision.c. I can't see why we'd get one of those > by itself. I would have expected messages from deeper down > too, like from sha1_file.c. As we do not know what version github used to run (or for that matter what custom code it adds to 1.6.1), I guessed that the previous one was 1.6.0.6 and did some comparison. The client side pack_object() learned to take alternates on the server side into account to avoid pushing objects that the target repository has through its alternates, so it is not totally unexpected the client side changes its behaviour depending on what the server does. -- 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
