password problem ...
Ken Watford
kwatford+hg at gmail.com
Wed Jul 13 14:03:10 UTC 2011
On Tue, Jul 12, 2011 at 5:19 PM, Lester Caine <lester at lsces.co.uk> wrote:
> I've worked my way through the maze, and have copies of my working projects
> mirrored on both the linux and windows machines, and mercurialeclipse is
> also working a lot better than it has in the past ... using the latest
> snapshot.
>
> Part of my problems were caused by both TortoiseHg and MercurialEclipse
> creating their own copies of hg on windows, and once I wiped any duplicates
> and switched back to a single identified copy as on Linux I started making
> progress. My windows machines use putty for ssh and it is this which the
> current windows git installs break, and the TortoiseHg install was
> bypassing. Having sorted the hgrc file, things are now working nicely ...
> except ...
>
> I've got my first 'superproject' with a .hgsub file and mercurialeclipse is
> displaying each subrepo nicely, but can't handle the top level
> synchronisation properly, so I've had to dropback to command line for that.
> The problem is that while I am (I think) using ssh authentication between
> machines, every cycle stops and asks for the password again. THIS is a
> problem I had with git on windows and was one of the main reasons for moving
> over to hg, but I am sure in this case I just have something configured
> incorrectly? I'm not quite sure HOW I should be linking between machines so
> that the various server copies are simply hg clones of the master?
Sadly, hg does not seem to cache login information that might be
shared between subrepos - for each subrepo, the server is contacted
and login requested.
The two main things you can do about this are to use the keyring
extension to save your credentials for that server, or (for an ssh
connection) make an ssh keypair for passwordless login.
For information on the keyring extension, see this:
http://mercurial.selenic.com/wiki/KeyringExtension
I believe TortoiseHg for Windows comes with it, but you probably have
to enable it, in addition to the other configuration details.
More information about the Mercurial
mailing list