I just bought Versions, and I am having problems with svn+ssh. I have
it all set up for command line access: I defined a tunnel for svn 'a2'
with the custom port (-p), my username (-l) on the remote server, and
my keyfile (-i), and it's working:
$ svn list
Hi Bob,
Welcome to the group.
Your hunch is correct, there's a known issue with Versions resolving
paths through the environment for anything listed in the .subversion/
config file. If you put the full path to the ssh executable (/usr/bin/
ssh) in there it should work as expected.
Let me know
Noah Campbell noahcampb...@gmail.com wrote (Fri, 2 Oct 2009 15:43:56 -0700):
Anyone...it's rendering Versions unusable and messing with my
workflow :P
On Oct 2, 9:50 am, Noah Campbell noahcampb...@gmail.com wrote:
I upgraded and I think something broke, but I can't get the last
version of
Fortunately I don't have any problems with 1.0.6 but I do agree that
older Versions (how funny) should be available:-)
Enjoy your weekend,
- Marijn
On Oct 4, 2009, at 1:55 AM, Tobias Jung wrote:
Noah Campbell noahcampb...@gmail.com wrote (Fri, 2 Oct 2009
15:43:56 -0700):
I upgraded and I think something broke, but I can't get the last
version of Versions to confirm.
Can someone point me to the archive of older Versions, specifically
1.0.5?
Thank you,
-Noah
--~--~-~--~~~---~--~~
You received this message because you are subscribed
Anyone...it's rendering Versions unusable and messing with my
workflow :P
On Oct 2, 9:50 am, Noah Campbell noahcampb...@gmail.com wrote:
I upgraded and I think something broke, but I can't get the last
version of Versions to confirm.
Can someone point me to the archive of older Versions,
I keep getting the following on Mac 10.6.1 when trying to access my
repo Error in child process: exec of 'ssh' failed: No such file or
directory
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Versions group.
To
I was having similar issue and worked out the solution, which involved
extending Dirk's solution.
Dirk talks about giving full path to ssh but, in the same line of the
config file, you might also have to give full path to your key file.
Example:
ssh = $SVN_SSH /usr/bin/ssh -i /Users/[your