Hg update problems

Hg update problems

[Eliot Blennerhassett]

Hi Takashi,

Wierd, I can see your checkin in a browser at 
http://hg.alsa-project.org/alsa-driver/  

14 hours ago:  	asihpi version 3.09.09
changeset 3506: 	e600ecb8fbd7
tag:	tip
author: 	tiwai

Also I see it in a clean clone of the repo.

but hg pull on my original repo still gets nothing same as before, head is out 
of date - details:
eliot@zaphod:~/src/alsahg/alsa-driver$ hg -v --debug heads
changeset:   3507:86adcd0d6d849d5f8d41448d3cd4d1a8660d6214
tag:         tip
description:
Added tag v1.0.16rc2 for changeset 1dc44ca35555


Tracing (strace) further I see that Hg queries the repository like this
http://hg.alsa-project.org/alsa-driver/?cmd=heads
and gets back
86adcd0d6d849d5f8d41448d3cd4d1a8660d6214
So the remote repo is telling me that my local is up to date, even though the 
web interface shows more recent tip.

Very wierd...

Anyone else see this or shed any light on it?
--
Eliot

Re: Hg update problems

[Tobin Davis]

Whatever the problem is, it is affecting the rss feed as well.  My
hda-sch patch was added today:

        changeset: 5794:9c896b0ea558 
        user: tiwai 
        date: Wed Jan 30 08:13:55 2008 +0100 
        summary: HDA-Intel - Add support for Intel SCH

But has failed to show up on my RSS feed reader (updated every 30
minutes).   My hg pull uses http://hg.alsa-project.org/alsa-kernel and
the RSS feed is 
http://hg.alsa-project.org/alsa-kernel?cl=tip;style=rss


Tobin

On Thu, 2008-01-31 at 11:33 +1300, Eliot Blennerhassett wrote:

> Hi Takashi,
> 
> Wierd, I can see your checkin in a browser at 
> http://hg.alsa-project.org/alsa-driver/  
> 
> 14 hours ago:  	asihpi version 3.09.09
> changeset 3506: 	e600ecb8fbd7
> tag:	tip
> author: 	tiwai
> 
> Also I see it in a clean clone of the repo.
> 
> but hg pull on my original repo still gets nothing same as before, head is out 
> of date - details:
> eliot@zaphod:~/src/alsahg/alsa-driver$ hg -v --debug heads
> changeset:   3507:86adcd0d6d849d5f8d41448d3cd4d1a8660d6214
> tag:         tip
> description:
> Added tag v1.0.16rc2 for changeset 1dc44ca35555
> 
> 
> Tracing (strace) further I see that Hg queries the repository like this
> http://hg.alsa-project.org/alsa-driver/?cmd=heads
> and gets back
> 86adcd0d6d849d5f8d41448d3cd4d1a8660d6214
> So the remote repo is telling me that my local is up to date, even though the 
> web interface shows more recent tip.
> 
> Very wierd...
> 
> Anyone else see this or shed any light on it?
> --
> Eliot
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

-- 
Tobin Davis 


"Consequences, Schmonsequences, as long as I'm rich."
		-- "Ali Baba Bunny" [1957, Chuck Jones]

Re: Hg update problems

[Jaroslav Kysela]

On Thu, 31 Jan 2008, Eliot Blennerhassett wrote:

> Hi Takashi,
> 
> Wierd, I can see your checkin in a browser at 
> http://hg.alsa-project.org/alsa-driver/  
> 
> 14 hours ago:  	asihpi version 3.09.09
> changeset 3506: 	e600ecb8fbd7
> tag:	tip
> author: 	tiwai
> 
> Also I see it in a clean clone of the repo.
> 
> but hg pull on my original repo still gets nothing same as before, head is out 
> of date - details:
> eliot@zaphod:~/src/alsahg/alsa-driver$ hg -v --debug heads
> changeset:   3507:86adcd0d6d849d5f8d41448d3cd4d1a8660d6214
> tag:         tip
> description:
> Added tag v1.0.16rc2 for changeset 1dc44ca35555
> 
> 
> Tracing (strace) further I see that Hg queries the repository like this
> http://hg.alsa-project.org/alsa-driver/?cmd=heads
> and gets back
> 86adcd0d6d849d5f8d41448d3cd4d1a8660d6214
> So the remote repo is telling me that my local is up to date, even though the 
> web interface shows more recent tip.

I get e600ecb8fbd75433610a8c5cdc6335c939940302 here.
Do you have a HTTP cache or proxy server between our server and your side?

						Jaroslav

-----
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project, Red Hat, Inc.

Re: Hg update problems

[Eliot Blennerhassett]

Hi Jaroslav,

On Thursday 31 January 2008 20:34:10 Jaroslav Kysela wrote:

> I get e600ecb8fbd75433610a8c5cdc6335c939940302 here.
> Do you have a HTTP cache or proxy server between our server and your side?

No. (Well, not AFAIK anyway)

I have been away for a few days...
Today my "hg pull -u" brings me up to date with hg head as seen via the web 
interface.  I.e. its OK again now. 

However, that head is over 30 hours old, I will be interested to see what 
happens after the next checkin.

regards

--
Eliot Blennerhassett
www.audioscience.com