Hi guys, There is a known bug in Versions, where if you have defined a custom schema in your ~/.subversion/config, it does not properly import your shell environment. So even if you simply uncomment the following line in ~/.subversion/config:
# ssh = $SVN_SSH ssh Versions will no longer be able to find ssh, if instead you write the line like this: ssh = $SVN_SSH /usr/bin/ssh everything will work just fine. So, while we work through our to-do list until this bug is fixed –it's alas a bit more complicated than it looks–, providing the full path to command line tools you've defined in the config file should resolve the problem for now.. Hoping this help, - Dirk Versions development team On Nov 5, 9:07 pm, Tim Gray <[EMAIL PROTECTED]> wrote: > I asked the EXACT same question a week ago and nobody responded. Let > me know if you fix it. I also emailed the developers but no reply. > > On Nov 5, 5:52 am, cvk <[EMAIL PROTECTED]> wrote: > > > Versions always gives me a subversion error when connecting to an svn > > +ssh repository: > > "Error in child process: exec of 'ssh' failed: No such file or > > directory" > > > Both ssh and svn are in /usr/bin. Checking out on terminal works fine, > > too. > > > Any suggestions? > > > Regards > > Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Versions" 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/versions?hl=en -~----------~----~----~----~------~----~------~--~---
