This is very likely due to a bug that I just fixed; "type -p" is not  
available on the vanilla POSIX shell, but is what cap 1.99.2 uses to  
determine whether a command exists in the path. I committed a change  
that uses "which" instead, which should be more portable. If you open
capistrano/recipes/deploy/remote_dependency.rb and change line 26 to  
use "which" instead of "type -p", does that work any better for you?

- Jamis

On Jun 17, 2007, at 8:37 PM, Claudio Poli wrote:

>
> hi,
> I'm trying out the new capistrano release, however:
>
> # cap deploy:setup
> works fine,it can connect and set up the appropriate directories
> # cap -q deploy:check
> The following dependencies failed. Please check them and try again:
> --> `/usr/bin/svn' could not be found in the path (www.domain.com)
>
> in deploy.rb:
>
> set :scm, :subversion
> set :scm_command, "/usr/bin/svn" # ubuntu feisty
> set :local_scm_command, "/usr/local/bin/svn" # mac osx
>
> obiouvsly the svn command is present on the remote machine, and can be
> accessed through the user which capistrano is connecting.
>
> what can be wrong?
> thanks.
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to