HTTP trees trailing GIT trees

HTTP trees trailing GIT trees

[Panagiotis Issaris]

Hi all,

A few days ago I started noticing that my GIT tree cloned through http was
always trailing the one which was clone using the git protocol.

When pulling both clones to the lastest version I got this:

* Last one when accessed through http:
commit dedc2982f2f845357f28dff401fe5df8510c6a8f
Author: benoit <benoit <at> 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b>
Date:   Tue May 22 08:28:32 2007 +0000

* Last one when accessed through git:
commit 55d4b9a1d0bb75a085462d4f885301507d8fd082
Author: takis <takis <at> 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b>
Date:   Wed May 23 09:07:57 2007 +0000


I reported this to the person who had setup the repository:
http://article.gmane.org/gmane.comp.video.ffmpeg.devel/51151

But unfortunately, the problem seems to remain.

Is this a known problem, or might this be a bug or misconfiguration?

I am using git version 1.5.2.35.ga334 when using http and git version 1.5.1.3
when using the git protocol.

The repository is available through http as:
http://git.mplayerhq.hu/ffmpeg

Through the git protocol:
git://git.mplayerhq.hu/ffmpeg

And through gitweb:
http://git.mplayerhq.hu/


With friendly regards,
Takis

Re: HTTP trees trailing GIT trees

[Petr Baudis]

  Hi,

On Wed, May 23, 2007 at 04:01:33PM CEST, Panagiotis Issaris wrote:
> I reported this to the person who had setup the repository:
> http://article.gmane.org/gmane.comp.video.ffmpeg.devel/51151
> 
> But unfortunately, the problem seems to remain.
> 
> Is this a known problem, or might this be a bug or misconfiguration?

  did any push happenned since the post-update hook was enabled? It
takes effect only after the next push. So far,

	http://git.mplayerhq.hu/ffmpeg/info/refs

and

	http://git.mplayerhq.hu/ffmpeg/refs/heads/master

is still out-of-sync (keeping this in sync is what is the job of the
post-update hook, or git-update-server-info respectively).

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Ever try. Ever fail. No matter. // Try again. Fail again. Fail better.
		-- Samuel Beckett

Re: HTTP trees trailing GIT trees

[Panagiotis Issaris]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Petr Baudis wrote:
>   Hi,
> 
> On Wed, May 23, 2007 at 04:01:33PM CEST, Panagiotis Issaris wrote:
>> I reported this to the person who had setup the repository:
>> http://article.gmane.org/gmane.comp.video.ffmpeg.devel/51151
>>
>> But unfortunately, the problem seems to remain.
>>
>> Is this a known problem, or might this be a bug or misconfiguration?
> 
>   did any push happenned since the post-update hook was enabled? It
> takes effect only after the next push. So far,
> 
> 	http://git.mplayerhq.hu/ffmpeg/info/refs
> 
> and
> 
> 	http://git.mplayerhq.hu/ffmpeg/refs/heads/master
> 
> is still out-of-sync (keeping this in sync is what is the job of the
> post-update hook, or git-update-server-info respectively).

Yes, I'd think so, as Måns stated that he had enabled the hook on
2007-05-22 20:43:27. The last commit shown on http://git.mplayerhq.hu/
through gitweb occurred 25 minutes ago ("Wed, 23 May 2007 13:46:11 +0000").

Thanks for your fast reply.

With friendly regards,
Takis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGVEuA9kOxLuzz4CkRAkXTAJ9xqbkUO6qF88HwV7GSYnVkV+VRNgCfSr/D
ZPPYBfeD9RpqbXNKwmukObc=
=wkyo
-----END PGP SIGNATURE-----

Re: HTTP trees trailing GIT trees

[Panagiotis Issaris]

Hi,

Petr Baudis <pasky <at> suse.cz> writes:
> 
>   Hi,
> 
> On Wed, May 23, 2007 at 04:01:33PM CEST, Panagiotis Issaris wrote:
> > I reported this to the person who had setup the repository:
> > http://article.gmane.org/gmane.comp.video.ffmpeg.devel/51151
> > 
> > But unfortunately, the problem seems to remain.
> > 
> > Is this a known problem, or might this be a bug or misconfiguration?
> 
>   did any push happenned since the post-update hook was enabled? It
> takes effect only after the next push. So far,
> 
> 	http://git.mplayerhq.hu/ffmpeg/info/refs
> 
> and
> 
> 	http://git.mplayerhq.hu/ffmpeg/refs/heads/master
> 
> is still out-of-sync (keeping this in sync is what is the job of the
> post-update hook, or git-update-server-info respectively).
> 

Yes, I'd think so, as Måns stated that he had enabled the hook on
2007-05-22 20:43:27. The last commit shown on http://git.mplayerhq.hu/
through gitweb occurred 25 minutes ago ("Wed, 23 May 2007 13:46:11 +0000").

Thanks for your fast reply.

With friendly regards,
Takis

Re: HTTP trees trailing GIT trees

[Panagiotis Issaris]

Hi,

Panagiotis Issaris <takis.issaris <at> uhasselt.be> writes:
> Petr Baudis <pasky <at> suse.cz> writes:
> > On Wed, May 23, 2007 at 04:01:33PM CEST, Panagiotis Issaris wrote:
> > > I reported this to the person who had setup the repository:
> > > http://article.gmane.org/gmane.comp.video.ffmpeg.devel/51151
> > > 
> > > But unfortunately, the problem seems to remain.
> > > 
> > > Is this a known problem, or might this be a bug or misconfiguration?
> > 
> >   did any push happenned since the post-update hook was enabled? It
> > takes effect only after the next push. So far,
> > 
> > 	http://git.mplayerhq.hu/ffmpeg/info/refs
> > 
> > and
> > 
> > 	http://git.mplayerhq.hu/ffmpeg/refs/heads/master
> > 
> > is still out-of-sync (keeping this in sync is what is the job of the
> > post-update hook, or git-update-server-info respectively).
> > 
> 
> Yes, I'd think so, as Måns stated that he had enabled the hook on
> 2007-05-22 20:43:27. The last commit shown on http://git.mplayerhq.hu/
> through gitweb occurred 25 minutes ago ("Wed, 23 May 2007 13:46:11 +0000").
> 
> Thanks for your fast reply.

I've checked both protocols from the same network now, unfortunately
without any improvements.

Furthermore, I've also started tracing, hoping to figure out what
the problem might be (or getting a hint from someone regarding
the possible cause).

The host which is involved:
nslookup 213.144.138.186
186.138.144.213.in-addr.arpa    name = natsuki.mplayerhq.hu

Parts of the trace -f:
...
connect(4, {sa_family=AF_INET, sin_port=htons(80),
sin_addr=inet_addr("213.144.138.186")}, 16) = -1 EINPROGRESS 
(Operation now in progress)
...
send(4, "GET /ffmpeg/info/refs HTTP/1.1\r\n
User-Agent: curl/7.15.5
(i486-pc-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8c zlib/1.2.3
libidn/0.6.5\r\n
Host: git.mplayerhq         .hu\r\nAccept: */*\r\nPragma:
no-cache\r\n\r\n", 188, MSG_NOSIGNAL) = 188
...
recv(4, "HTTP/1.1 200 OK\r\nDate: Thu, 24 May 2007 12:27:05 GMT\r\n
Server: Apache/2.2.3 (Debian) mod_python/3.2.10 Python/2.4.4\r\n
Last-Modified:  Thu, 24 May 2007          04:25:50 GMT\r\n
ETag: \"2c01f-79-ad720f80\"\r\nAccept-Ranges:
bytes\r\nContent-Length: 121\r\nContent-Type:
text/plain\r\n\r\nc30fa83981290671ed972835297fbe93ef9d1e58\t
refs/heads/master\nc30fa83981290671ed972835297fbe93ef9d1e58\t
refs/remotes/git-svn\n",
16384, MSG_NOSIGNAL) = 381


So, we're asking for /ffmpeg/info/refs, and the server is 
returning c30fa8391812..., but, using GitWeb one can see 
that c30fa839812... is  not the last commit, this one is:
http://git.mplayerhq.hu/?p=ffmpeg;a=commit;
h=47d7dcb5a7d89f413064e7ef1b54d77e59fb8375


When using the git protocol, the trace shows this:
...
connect(3, {sa_family=AF_INET, sin_port=htons(9418),
sin_addr=inet_addr("213.144.138.186")}, 16) = 0
dup(3)                            = 4
write(4, "0032git-upload-pack /ffmpeg\0host=git.mplayerhq.hu\0",
50) = 50
read(3, "007c", 4)                = 4
read(3, "47d7dcb5a7d89f413064e7ef1b54d77e59fb8375 HEAD\0multi_ack
thin-pack side-band side-band-64k ofs-delta shallow no-progress\n",
120) = 120
read(3, "003f", 4)                = 4
read(3, "47d7dcb5a7d89f413064e7ef1b54d77e59fb8375 
refs/heads/master\n", 59) 
= 59
read(3, "0042", 4)                = 4
read(3, "47d7dcb5a7d89f413064e7ef1b54d77e59fb8375 
refs/remotes/git-svn\n", 62) 
= 62
read(3, "0000", 4)                = 4
...

So, here, I'd guess it's also asking for the latest revision and 
apparantly receiving 47d7dcb5a... as the hash, which is correct (and 
the same as GitWeb shows).
 
And hints? Any other info I can provide?

I've upgrade GIT hoping it solve the problem, but it doesn't. Some 
versions, I've tried are git version 1.5.2.35.ga334 and git 
version 1.5.2.

With friendly regards,
Takis

 

Re: HTTP trees trailing GIT trees

[Johannes Schindelin]

Hi,

On Thu, 24 May 2007, Panagiotis Issaris wrote:

> So, we're asking for /ffmpeg/info/refs, and the server is returning 
> c30fa8391812..., but, using GitWeb one can see that c30fa839812... is 
> not the last commit, this one is: 
> http://git.mplayerhq.hu/?p=ffmpeg;a=commit; 
> h=47d7dcb5a7d89f413064e7ef1b54d77e59fb8375

So, info/refs is still old. This file should have been updated by 
git-update-server-info. I am not sure how this repo is updated, but I 
suspect that the wrong hook contains the call to update-server-info, or 
that the correct hook is not activated, or it does not have write 
permission.

Ciao,
Dscho

Re: HTTP trees trailing GIT trees

[Panagiotis Issaris]

Hi Dscho,

Johannes Schindelin <Johannes.Schindelin <at> gmx.de> writes:
> Hi,
> 
> On Thu, 24 May 2007, Panagiotis Issaris wrote:
> 
> > So, we're asking for /ffmpeg/info/refs, and the server is returning 
> > c30fa8391812..., but, using GitWeb one can see that c30fa839812... is 
> > not the last commit, this one is: 
> > http://git.mplayerhq.hu/?p=ffmpeg;a=commit; 
> > h=47d7dcb5a7d89f413064e7ef1b54d77e59fb8375
> 
> So, info/refs is still old. This file should have been updated by 
> git-update-server-info. I am not sure how this repo is updated, but I 
> suspect that the wrong hook contains the call to update-server-info, or 
> that the correct hook is not activated, or it does not have write 
> permission.

Thanks! I've just reported this on the ffmpeg mailinglist.

Thanks again for your fast reply,
With friendly regards,
Takis

Re: HTTP trees trailing GIT trees

[Jakub Narebski]

Johannes Schindelin wrote:

> Hi,
> 
> On Thu, 24 May 2007, Panagiotis Issaris wrote:
> 
>> So, we're asking for /ffmpeg/info/refs, and the server is returning 
>> c30fa8391812..., but, using GitWeb one can see that c30fa839812... is 
>> not the last commit, this one is: 
>> http://git.mplayerhq.hu/?p=ffmpeg;a=commit; 
>> h=47d7dcb5a7d89f413064e7ef1b54d77e59fb8375
> 
> So, info/refs is still old. This file should have been updated by 
> git-update-server-info. I am not sure how this repo is updated, but I 
> suspect that the wrong hook contains the call to update-server-info, or 
> that the correct hook is not activated, or it does not have write 
> permission.

If you push to repository (it is the usual setup for public
repositories), it would be enough to simply enable default 
'post-update' hook (make it executable).

If you however for example commit to this public repository directly,
you would need to put call to git-update-server-info in the 'post-commit'
hook.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

Re: HTTP trees trailing GIT trees

[Johannes Schindelin]

Hi,

On Fri, 25 May 2007, Jakub Narebski wrote:

> Johannes Schindelin wrote:
> 
> > Hi,
> > 
> > On Thu, 24 May 2007, Panagiotis Issaris wrote:
> > 
> >> So, we're asking for /ffmpeg/info/refs, and the server is returning 
> >> c30fa8391812..., but, using GitWeb one can see that c30fa839812... is 
> >> not the last commit, this one is: 
> >> http://git.mplayerhq.hu/?p=ffmpeg;a=commit; 
> >> h=47d7dcb5a7d89f413064e7ef1b54d77e59fb8375
> > 
> > So, info/refs is still old. This file should have been updated by 
> > git-update-server-info. I am not sure how this repo is updated, but I 
> > suspect that the wrong hook contains the call to update-server-info, or 
> > that the correct hook is not activated, or it does not have write 
> > permission.
> 
> If you push to repository (it is the usual setup for public
> repositories), it would be enough to simply enable default 
> 'post-update' hook (make it executable).
> 
> If you however for example commit to this public repository directly,
> you would need to put call to git-update-server-info in the 'post-commit'
> hook.

I have the slight suspicion that this repo is only updated via git-svn. 
And I am still new enough to git-svn to not know which hook it executes, 
if any.

Ciao,
Dscho