Hg clone on old SPARC

I’ve been trying to do hg clone using an Sun Ultra 80 (450MHz) running
Solaris 10. It fails after 60 seconds precisely. I think the CPU is too slow
to successfully clone the repo in time before some kind of connection
timeout occurs. It seems I’m not the only one having this problem (see link
below). Any chance I can get this timer extended (web master), or maybe some
other useful suggestions on how to resolve this issue? I’m new to Mercurial,
and when I tried to doing a clone to revision 100, then doing:

hg pull -r 500
hg pull -r 750
hg pull -r 1000

to get it in parts that don’t timeout, but I ended up with a bunch of heads
with the suggestion that I merge them (eventually telling me that I had to
to continue), and I’m not sure what do with that exactly.

http://kiln.stackexchange.com/questions/935/connection-ended-unexpectedly-when-cloning-a-large-repository

I’ve been trying to do hg clone using an Sun Ultra 80 (450MHz) running
Solaris 10. It fails after 60 seconds precisely.

I just increased Apache’s Timeout setting. Can you try again and see if
it’s fixed now?

Thanks,
–ryan.

And I was able to successfully clone on my old G4 iMac. :slight_smile:

Thanks!On Thu, Feb 17, 2011 at 8:22 AM, Ryan C. Gordon wrote:

I’ve been trying to do hg clone using an Sun Ultra 80 (450MHz) running

Solaris 10. It fails after 60 seconds precisely.

I just increased Apache’s Timeout setting. Can you try again and see if
it’s fixed now?

Thanks,
–ryan.


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org


-Sam Lantinga, Founder and CEO, Galaxy Gameworks

Yes, thanks much!On Thu, Feb 17, 2011 at 10:22 AM, Ryan C. Gordon wrote:

I’ve been trying to do hg clone using an Sun Ultra 80 (450MHz) running

Solaris 10. It fails after 60 seconds precisely.

I just increased Apache’s Timeout setting. Can you try again and see if
it’s fixed now?

Thanks,
–ryan.


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org