Private keys should work fine, if you have them set up correctly. You said that they work fine for straight-svn, but not for cap? What were the symptoms you were seeing?
- Jamis On Mar 14, 2007, at 9:54 AM, thabenksta wrote: > > Might anyone have a suggestion on ways to debug this? I've tried > everything I can think of. > > Thanks, > -Ben > > On 12 Mar, 22:09, "thabenksta" <[EMAIL PROTECTED]> wrote: >> Hmm, Let me see if I can explain this right. I had my environment >> working fine, but now it doesn't. >> >> I was forced to upgrade to Subversion 1.4, but now when I do a cap -a >> deploy, it asks for my password once and doesn't show it, then it >> will >> keep asking for my password again and again but showing it. Looks >> like this.... >> >> * executing task deploy >> * executing task update >> ** transaction: start >> * executing task update_code >> * querying latest revision... >> [EMAIL PROTECTED]'s password: >> [EMAIL PROTECTED]'s password: ******** >> [EMAIL PROTECTED]'s password: ******** >> [EMAIL PROTECTED]'s password: ******** >> [EMAIL PROTECTED]'s password: ******** >> [EMAIL PROTECTED]'s password: ******** >> [EMAIL PROTECTED]'s password: ******** >> [EMAIL PROTECTED]'s password: >> >> I can't even ^C out of it either. >> >> I updated Capistrano and Railsmachine, but still no cigar. >> >> I tried ssh keys, which works for regular svn commands, but not with >> cap. I've got other options, like cygwin, but I'd really like to get >> this to work as is. >> >> Has anyone come across this, and hopefully resolved it? > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
