On Sat, Apr 13, 2013 at 12:03:15PM +0100, João Joyce wrote:
> I have tried to remove and recreate my git folder and remove some
> files to get more logs. Here they are:
Your output looks quite odd.
> packet: push< 0000000000000000000000000000000000000000 capabilities^{}\0 report-status delete-refs side-band-64k quiet ofs-delta
> packet: push< 0000
So this is the server advertising its refs. It doesn't have any, so it
just gives a blank capabilities string, followed by a flush. OK.
> packet: push> 0000000000000000000000000000000000000000 17c420b8bd99856aee6da9c1743f6df0ec18a9ca refs/heads/master\0report-status side-band-64k
> packet: push> 0000
And we want to push up one ref, so we send it, along its old and new
sha1s, its name, and our own capabilities list. And then we flush. OK.
> packet: push< 20b8bd99856aee6da9c1743f6df0ec18a9cac28267338c198573ad59e89d0acc445a62b3d127
> acf853d0a30287d9455dbe1707edeb16cc3e9b22
Now what the heck is this? We should be sending the packfile next,
and the server should send us back the ref status. It would look
something like:
packet: push< 0000000000000000000000000000000000000000 capabilities^{}\0 report-status delete-refs side-band-64k quiet ofs-delta
packet: push< 0000
packet: push> 0000000000000000000000000000000000000000 662bbff2308c7e72f417d3419f4984222faf7ef8 refs/heads/master\0 report-status side-band-64k
packet: push> 0000
packet: push< \1000eunpack ok0019ok refs/heads/master0000
packet: push< 0000
packet: push< unpack ok
packet: push< ok refs/heads/master
packet: push< 0000
What is generating that output on the server? Do you have any hooks on
the server repository that might generate output (we _should_ be
channeling their output over the sideband, but we might have missed a
case). What transport are you using (git-over-ssh, git-over-http, etc)?
-Peff
--
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