Maybe this has something to do with it (from the Capistrano 2.1.0 changelog)[1]:
*2.1.0* October 14, 2007 ... cut ... * Use the --password switch for subversion by default, but add :scm_prefer_prompt variable (defaults to false) [Jamis Buck] [1]: http://svn.rubyonrails.org/rails/tags/capistrano_2-1-0/CHANGELOG Seems unlikely, but I guess you could try setting :scm_prefer_prompt to true... Brian On Apr 4, 4:14 pm, "Chris Petersen" <[EMAIL PROTECTED]> wrote: > Well, then I'm at a loss. I'm glad you found a work around! > > Chris > > On Fri, Apr 4, 2008 at 4:09 PM, Ken <[EMAIL PROTECTED]> wrote: > > > Hi Chris, > > > My deploy.rb looks pretty much like yours. The only difference is > > that I don't do a "set :group" and I don't "require 'mongrel_cluster/ > > recipes". Otherwise it's the same. Ditto on the important parts you > > have listed. > > > K > > > On Apr 4, 3:42 pm, "Chris Petersen" <[EMAIL PROTECTED]> > > wrote: > > > Would it be possible for your to include the important bits of your > > > deploy.rb file? (Scrubbed clean of anything incriminating of course). > > Mine > > > looks something like: > > > > require 'mongrel_cluster/recipes' > > > > set :application, "web" > > > > # Deployment Settings > > > set :repository, > > "svn+ssh://[EMAIL PROTECTED]/svnroot/trunk/projects/app > > " > > > set :deploy_to, "/mnt/apps/#{application}" # This is where your project > > will > > > be deployed. > > > > *set :domain, "my_deploy_server" * > > > role :app, domain > > > role :web, domain > > > role :db, domain, :primary => true > > > > # Set the Unix user and group that will actually perform each task > > > # on the remote server. The defaults are set to 'deploy' > > > set :user, "app" > > > set :group, "app" > > > > etc... > > > > the important parts being: > > > > 1. The repo_user is in the :repository variable > > > 2. There is no password set > > > 3. The ssh keys are setup for :[EMAIL PROTECTED] to ssh to > > > my_subversion_server without a password. > > > > Hope that helps, if you can include your deploy.rb it might help. > > > Chris > > > > On Fri, Apr 4, 2008 at 3:26 PM, Ken <[EMAIL PROTECTED]> wrote: > > > > > Interesting question. I do have ssh setup so that it doesn't ask for > > > > a password when it logs into subversion. However, on my desktop with > > > > 1.3 it does ask which matches your experience. On the laptop with > > > > Capistrano 2.2 it doesn't ask which also matches your experience. > > > > But... it dies with "Too many authentication failures" so I think > > > > it's screwed up some how but I'm not sure how. > > > > > Thanks, Ken > > > > > On Apr 4, 3:16 pm, "Chris Petersen" <[EMAIL PROTECTED]> > > > > wrote: > > > > > Do you have your ssh keys setup so ssh doesn't ask you for a > > password > > > > when > > > > > you log into your subversion server form your deployment server? I > > > > noticed > > > > > when upgraded from 1.3 to Capistrano 2 that it seemed to stop asking > > me > > > > for > > > > > my password and defaulted to using the keys. > > > > > > Chris > > > > > > On Fri, Apr 4, 2008 at 3:10 PM, Ken <[EMAIL PROTECTED]> wrote: > > > > > > > Hmmm... Well, here's the thing - I can still do Capistrano > > deploys > > > > > > from my desktop machine. It's just the laptop that won't work. I > > did > > > > > > do a SVN checkout on the laptop before moving on to the Capistrano > > > > > > step and the SVN checkout worked fine on the laptop. I would be > > the > > > > > > first to admit SVN and Capistrano aren't my strengths - :-) - but > > I'm > > > > > > unsure how the checkout on the server would help... Would I just > > > > > > check out into a random directory? Would I just delete that > > directory > > > > > > afterward? Sorry for my confusion... > > > > > > > Thanks for your help! Ken > > > > > > > On Apr 4, 2:59 pm, "Matt Aimonetti" <[EMAIL PROTECTED]> > > wrote: > > > > > > > it looks like a SVN checkout issue. login to your server and do > > a > > > > local > > > > > > > checkout of your repo. It shoudl cache your authentication and > > solve > > > > > > your > > > > > > > problem. > > > > > > > > -Matt > > > > > > > > On 4/4/08, Ken Hudson <[EMAIL PROTECTED]> wrote: > > > > > > > > > Hi All, > > > > > > > > > I have Capistrano 1.3.1 running on my desktop and all is > > working > > > > well > > > > > > and > > > > > > > > has been for almost a year. However, I just got a new laptop > > as a > > > > > > backup > > > > > > > > and I'm attempting to set up Capistrano 2.2 on Leopard and I'm > > > > having > > > > > > an > > > > > > > > issue with subversion. When I try to deploy I am receiving > > the > > > > > > following > > > > > > > > message: "Too many authentication failures for <username>" > > during > > > > the > > > > > > > > subversion checkout process. > > > > > > > > > Here's some additional information: > > > > > > > > > -- I have tried executing the command "ssh <userid> @ > > <website> > > > > and > > > > > > that > > > > > > > > works fine. > > > > > > > > -- I have tried executing the command "ssh -l <userid> > > <website> > > > > > > svnserve > > > > > > > > -t" and that works fine. > > > > > > > > -- I have tried executing the command "svn list > > > svn+ssh://<userid>@<website>.com/home/<directory>/svn/svn-repos/<directory> > > > > > > /trunk" > > > > > > > > and that works fine. > > > > > > > > -- However, I can't deploy my application with Capistrano. > > It > > > > always > > > > > > > > dies on the step that does the "svn checkout" with the error > > > > message > > > > > > "Too > > > > > > > > many authentication failures for <userid>". > > > > > > > > > Any help would be much appreciated. I've tried everything I > > can > > > > think > > > > > > of > > > > > > > > and I could really use some assistance or troubleshooting > > advice. > > > > > > > > > Regards, Ken --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
