-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 25.02.2009 um 05:24 schrieb Wesley Leggette:

>
>
>
>
> On 2/24/09 12:30, "Bastian Doetsch" <[email protected]> wrote:
>
>> I've pulled your changes, but now ssh doesn't work anymore. Please
>> have a look at it. I just my raw bitbucket repo as a test:
>>
>> ssh://bitbucket.org/bastiand/mercurialeclipse as URL and "hg" as
>> username. That used to work, but doesn't anymore. Only storing users/
>> passwords in .hgrc is not an option, so I guess your refactorings
>> broke the reading of user information from our text files and can't
>> cope with entering passwords manually.
>
> Are you getting this error:
>
> Process error, return code: 255, message: remote: ssh_askpass:
> exec(/usr/libexec/ssh-askpass): No such file or directory
> remote: Host key verification failed.
> abort: no suitable response from remote hg!
>
> I am getting this same error even before my changes (in  
> 1020:5223939f24d2).
>
> This is on Mac OS X, however, so that might just be my system.

Hey Wesley,

any news on this? I'd very much like to have the stuff you did  
integrated if the aforementioned bug is fixed :). The askpass error  
doesn't occur with my current version of MercurialEclipse where I  
never give bitbucket a username/password anymore as the ssh keys are  
working and the username is stored in our plug-in metadata directory.

Best regards,
Bastian


>
>
> Wesley
>
>
> >

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkmpIhwACgkQBqJW4lDO0YJMbgCfWIwGek+zq8ADCATbpds3a/8W
0oIAnR8CE6gQFJRPRIN0bV6CfTZQaAwu
=kYlD
-----END PGP SIGNATURE-----

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"MercurialEclipse" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/mercurialeclipse?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to