On Thu, Jun 2, 2011 at 3:34 PM, Ryan Johnson wrote: > On 02/06/2011 9:05 AM, Chris Sutcliffe wrote: >> >> On 2 June 2011 08:27, Christopher Faylor wrote: >>> >>> Could you provide the actual steps needed to duplicate the problem, >>> assuming that anyone doing testing will not be familiar with mercurial? >> >> It seems to be an issue with using mercurial over ssh versus mercurial >> over http. For example, cloning the Emerge Desktop repository over >> http (read only) works fine: >> >> hg clone http://emerge.hg.sourceforge.net:8000/hgroot/emerge/emerge >> >> However, when I clone over ssh (for read/write) using my public key: >> >> hg clone ssh://ir0nh...@emerge.hg.sourceforge.net/hgroot/emerge/emerge >> >> The command appears to hang after the operation completes. >> >> Unfortunately I don't know of an anonymous mercurial repository that >> you can clone over ssh to recreate the issue. > > Assuming cygwin sshd is running locally, couldn't you just create an empty > repo and then try to ssh-clone it? > > mkdir ~/test-repo > cd ~/test-repo > hg init > hg clone ssh://localhost/test-repo tr2 > > Ryan >
in that case you can also test with rsync through ssh to check if it is a more general ssh issue and it is not related to mercurial. Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
