Bill,Could you post your deploy.rb? Or, if you'd rather not post it here, could you email it to me directly?
The deprecation warning is almost certainly going to be due to something like deprec being loaded, maybe in ~/.caprc. Deprec is currently not compatible with cap2. If it isn't deprec, then it's going to be some other 3rd party extension that you're loading, which is not cap2-compatible.
- Jamis On Dec 18, 2007, at 4:50 PM, Bill Kocik wrote:
You're correct, I'm using subversion, and now that I look at it I see it's that connection that's failing. The session goes like this: $ cap deploy [DEPRECATION] Capistrano.configuration is deprecated. Use Capistrano::Configuration.instance instead * executing `deploy' * executing `deploy:update' ** transaction: start * executing `deploy:update_code' [EMAIL PROTECTED]'s password: At this point I hit ^c, because there is no "[EMAIL PROTECTED]", so all the passwords in the world aren't going to work. I have 'set :user, "the-right-username"' in my deploy.rb, but it still insists on ssh'ing as bkocik (which is my locally logged-in username on my OS X box). I then get this: svn: Connection closed unexpectedly *** [deploy:update_code] rolling back . . . I have no idea what that deprecation notice is about. So I put this in my deploy.rb file, near the top: set :scm_username, 'bill' Alas, the session works exactly as it did above - it tries to connect to the SVN host as 'bkocik'. I'm sure I'm doing something dumb somewhere, but I'll be darned if I can figure out what it is. -Bill On Dec 18, 6:36 pm, Jamis Buck <[EMAIL PROTECTED]> wrote:Bill, Can you post the specific error you're getting? Is it the ssh connection from capistrano that is complaining, or the ssh connection for subversion? (I assume you're using subversion.) - Jamis On Dec 18, 2007, at 4:08 PM, Bill Kocik wrote:Check, check, and check. I wish it were something simple, but it doesn't look like it will be. I have no idea how to debug this, either.Thanks again for your attempts.-BillOn Dec 18, 6:06 pm, tr <[EMAIL PROTECTED]> wrote:Bill,The only other things I can think of to check are; ensure your Capfile is in RAILS_ROOT, that it has the line:load 'config/deploy'in it, that your deploy.rb is in the correct location, and that you are running 'cap' from the RAILS_ROOT of your application.TROn Dec 18, 3:45 pm, Bill Kocik <[EMAIL PROTECTED]> wrote:No, that was just a placeholder for my groups post. I have the actual username in deploy.rb. I'm also using 2.1.0 (which I should have mentioned in the first place), though I tried temporarily downgradingto 1.4.0 to see if that would help. It didn't, of course. I have noidea why that setting is being ignored. But thanks . . .-Billsmime.p7s 3KDownload--~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
smime.p7s
Description: S/MIME cryptographic signature
