From: Yuval L. <sf...@sf...> - 2011-02-11 13:19:51
|
On February 10, 2011 09:44:58 am Jim Watters wrote: > Sorry for the missinformation before my apology (I guess I am getting more 'Canadian' every day) for the confusion as well, and for not being very prompt in my replies (time is short at the moment). We'll get this sorted out. > The Hugin one worked and the panotools one did not. Can you try the panotools again with http://panotools.hg.sourceforge.net:8000/hgroot/panotools/libpano it is now exactly the same set up as Hugin, unless I missed something (e.g. permissioning). > I want to eliminate SSH as a cause of the problem Understand. From my experience, SSH is easier than HTTP. As part of my current day-job I implemented an Hg install; and while at it, alarmed by the SF brak-in problems, I also implemented an Hg "mirror" of Hugin on my own web server. Accessing my mirror with SSH works painless, out of the box. WWW access was a pain and I am still bumping into issues. The ultimate goal of the "mirror" is to set up a "federation" of mutually trusting repos pushing and pulling from each other to make the project completely independent of any central hosting, but it is very premature to discuss this and completely off topic. It's something like github functionality without the dependency on the hub. > Except it got everything in the hugin and not just the doc sub folder! :( That's "normal". You can't check out just a sub folder of a repository yet. I know development is moving in that direction, but is not there yet. Also, it is not as critical as in SVN. In SVN every single check in/out is a net operation. Bandwidth, latency, connection are critical. In Hg, once you have a clone of the *whole* repository, all check in/out operations are just local disk access. Only push/pull are bandwidth, latency, connection dependent. The Hugin repo is quite large, although by today's standards, at about 63MB, a drop in the ocean with respect to hard disk size. The initial cloning is the only operation that really suffers from this. > Maybe anonymous has not been enabled with the panotools hg repository? anonymous does not really need to be enabled. If you can see it in the web browser, it should work. > I tried again with SSH and it worked this time. good! as I stated, SSH is easier. But now you will have to change the URL since I have moved the location of the repo. Sorry for that. In a text editor, open .hg/hgrc and change [paths] default = ssh://US...@pa.../hgroot/panotools/panotools/libpano to read [paths] default = ssh://US...@pa.../hgroot/panotools/libpano Yuv |