Using svn+ssh with TortoisePlink.exe
1,003 views
Skip to first unread message
Atle Ræstad
Jan 9, 2014, 2:05:12 PM1/9/14
to us...@tortoisesvn.tigris.org
Hi
When I set TortoiseSVN->Settings->Network->SSH client or environment variable SVN_SSH to use plink.exe or TortoisePlink.exe -i myPrivateKey it works as expected. I can access repositories on our Linux hosts. Great!
However there is an annoying behaviour. If some of my login files on Linux (for example .cshrc) contains printouts it will stop TortoiseSVN to support svn+ssh and TortoiseSVN returns with the error message:
Unable to connect to a repository at URL ...
To better debug SSH connection problems, remove the -q option from ...
Using plink outside TortoiseSVN works fine even when the .cshrc file contains some printouts.
I guess that the printouts causes TortoiseSVN to be confused when it shall parse the answer. But I'm wondering if this behaviour is expected? Or perhaps it should be made more robust and ignore the login printouts?
/Atle
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3071405
To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].
When I set TortoiseSVN->Settings->Network->SSH client or environment variable SVN_SSH to use plink.exe or TortoisePlink.exe -i myPrivateKey it works as expected. I can access repositories on our Linux hosts. Great!
However there is an annoying behaviour. If some of my login files on Linux (for example .cshrc) contains printouts it will stop TortoiseSVN to support svn+ssh and TortoiseSVN returns with the error message:
Unable to connect to a repository at URL ...
To better debug SSH connection problems, remove the -q option from ...
Using plink outside TortoiseSVN works fine even when the .cshrc file contains some printouts.
I guess that the printouts causes TortoiseSVN to be confused when it shall parse the answer. But I'm wondering if this behaviour is expected? Or perhaps it should be made more robust and ignore the login printouts?
/Atle
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3071405
To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].
Simon Large
Jan 9, 2014, 4:26:17 PM1/9/14
to us...@tortoisesvn.tigris.org
On 9 January 2014 19:05, Atle Ræstad <atle....@gmail.com> wrote:
> Hi
>
> When I set TortoiseSVN->Settings->Network->SSH client or environment variable SVN_SSH to use plink.exe or TortoisePlink.exe -i myPrivateKey it works as expected. I can access repositories on our Linux hosts. Great!
>
> However there is an annoying behaviour. If some of my login files on Linux (for example .cshrc) contains printouts it will stop TortoiseSVN to support svn+ssh and TortoiseSVN returns with the error message:
> Unable to connect to a repository at URL ...
> To better debug SSH connection problems, remove the -q option from ...
>
> Using plink outside TortoiseSVN works fine even when the .cshrc file contains some printouts.
>
> I guess that the printouts causes TortoiseSVN to be confused when it shall parse the answer. But I'm wondering if this behaviour is expected? Or perhaps it should be made more robust and ignore the login printouts?
TortoisePlink is just a windowless version of plink. So which version
> Hi
>
> When I set TortoiseSVN->Settings->Network->SSH client or environment variable SVN_SSH to use plink.exe or TortoisePlink.exe -i myPrivateKey it works as expected. I can access repositories on our Linux hosts. Great!
>
> However there is an annoying behaviour. If some of my login files on Linux (for example .cshrc) contains printouts it will stop TortoiseSVN to support svn+ssh and TortoiseSVN returns with the error message:
> Unable to connect to a repository at URL ...
> To better debug SSH connection problems, remove the -q option from ...
>
> Using plink outside TortoiseSVN works fine even when the .cshrc file contains some printouts.
>
> I guess that the printouts causes TortoiseSVN to be confused when it shall parse the answer. But I'm wondering if this behaviour is expected? Or perhaps it should be made more robust and ignore the login printouts?
of plink are you using that works?
Simon
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3071408
Atle Ræstad
Jan 10, 2014, 5:09:46 AM1/10/14
to us...@tortoisesvn.tigris.org
There is no difference in using plink and TortoisePlink (except for some window popup when using plink).
However I found out what caused this behaviour. One of the files I reference was printing normal output to stderr! (A script using >&2). I changed the script to print normal output to stdout and errors to stderr. And now TortoiseSVN behaves as expected.
To summarize TortoiseSVN supports login shells with printouts to stdout and not stderr. Which is correct behaviour, sorry for the question.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3071435
However I found out what caused this behaviour. One of the files I reference was printing normal output to stderr! (A script using >&2). I changed the script to print normal output to stdout and errors to stderr. And now TortoiseSVN behaves as expected.
To summarize TortoiseSVN supports login shells with printouts to stdout and not stderr. Which is correct behaviour, sorry for the question.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3071435
Reply all
Reply to author
Forward
0 new messages