We get a strange behavior, when deploying the same application from different platforms : - Fedora 7 (64 bits) - Suse 10 (64 bits)
We use the last release of Capistrano. On Fedora all is ok, on Suse it fails. The code is in a Subversion repository reachable via http:// The deployment server is a Linux Debian, in our DMZ : My colleague (Suse) and I (Fedora) have pushed our public DSA keyz on the server, without passcode we easily connect to the server without prompt password. The error my colleague get on Suse is the following.... * executing `deploy' * executing `deploy:update' ** transaction: start * executing `deploy:update_code' * executing "svn checkout -q -r54 http://sharails.svn.beanstalkapp.com/repos/trunk /var/www/sharails/ releases/20080423153756 && (echo 54 > /var/www/sharails/releases/ 20080423153756/REVISION)" servers: ["192.168.30.22"] *** [deploy:update_code] rolling back * executing "rm -rf /var/www/sharails/releases/20080423153756; true" servers: ["192.168.30.22"] ** [deploy:update_code] exception while rolling back: Capistrano::ConnectionError, connection failed for: 192.168.30.22 (ArgumentError: wrong number of arguments (0 for 1)) connection failed for: 192.168.30.22 (ArgumentError: wrong number of arguments (0 for 1)) I guess there is a problem with SSH connection opened by our deploy capistrano task. What i haven't compared , is the release of the SSH client on the Suse box. Thanks for your answer Laurent Suse 9 , 64 bits --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
