I just checked out (not exported!) a fresh copy of my app from my svn server (using svnserve in daemon mode). Did a 'capify .' just be sure, even though I had done all of that before. I set :use_sudo to false, since I'm checking it out into my home directory. :user is set to me.
cap deploy:setup and deploy:check both did the right thing on my remote server. But when I do a cap deploy:update_code, I get the all- too-familiar: svn: Working copy '/<path-to-release>/releases/20100615155516' locked And then I get the bazillion lines as it tried to roll things back. Executing the 'svn checkout -q ....' command on the remote server works just fine, however, so there's nothing wrong with the command itself. Obviously I need to get this fixed, or I'll have to make all of my changes on the remote server. -- * You received this message because you are subscribed to the Google Groups "Capistrano" 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/capistrano?hl=en
