Grrr. To be honest, I'm _this_ close to ditching windows support altogether. I don't use windows, and I don't like to use windows, and I don't plan to troubleshoot these myself anymore.
Patches to improve windows support will be accepted, as long as they don't do evil things to the code, but I'm really, really frustrated with windows at the moment and do not relish the thought of dealing with more mountains of these bug reports. It's a losing battle. So, windows users: if you want capistrano, you'll need to figure this out on your own. :( - Jamis On Sun, Dec 7, 2008 at 8:52 AM, Larry <[EMAIL PROTECTED]> wrote: > > Hi Jamis, > > There was a problem with an "undefined method close?" for us Windows > users (I know, I know... sorry!) using PuTTY/Pageant: > > ====== > C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/net-ssh-2.0.4/lib/net/ssh/ > service/forward.rb:218:in `prepare_client': undefined method `closed?' > for #<Net::SSH::Authentication::Pageant::Socket:0x33b26dc> > (NoMethodError) > ====== > > Here is what you said in the thread about this issue for 2.5.2: > > ====== > This is caused when you are using ssh agent forwarding with capistrano > on windows. It should be fixed in the next release of capistrano, but > in the meantime you can explicitly disable agent forwarding in your > deploy.rb: ssh_options[:forward_agent] = false > ====== > > Here is what happened when I upgraded to Cap 2.5.3 (and along with it > net-ssh-2.0.6): > > ====== > ** [deploy:update_code] exception while rolling back: TypeError, can't > convert Net::SSH::Authentication::Pageant::Socket into IO > :/Programs/ruby-1.8.6/lib/ruby/gems/1.8/gems/capistrano-2.5.3/lib/ > capistrano/processable.rb:25:in `select': can't convert > Net::SSH::Authentication::Pageant::Socket into IO (TypeError) > from C:/Programs/ruby-1.8.6/lib/ruby/gems/1.8/gems/ > capistrano-2.5.3/lib/capistrano/processable.rb:25:in > `process_iteration' > from C:/Programs/ruby-1.8.6/lib/ruby/gems/1.8/gems/ > capistrano-2.5.3/lib/capistrano/command.rb:163:in `process!' > from C:/Programs/ruby-1.8.6/lib/ruby/gems/1.8/gems/ > capistrano-2.5.3/lib/capistrano/command.rb:162:in `loop' > from C:/Programs/ruby-1.8.6/lib/ruby/gems/1.8/gems/ > capistrano-2.5.3/lib/capistrano/command.rb:162:in `process!' > from C:/Programs/ruby-1.8.6/lib/ruby/gems/1.8/gems/ > capistrano-2.5.3/lib/capistrano/command.rb:133:in `process' > from C:/Programs/ruby-1.8.6/lib/ruby/gems/1.8/gems/ > capistrano-2.5.3/lib/capistrano/configuration/actions/invocation.rb: > 81:in `run_tree' > from C:/Programs/ruby-1.8.6/lib/ruby/gems/1.8/gems/ > capistrano-2.5.3/lib/capistrano/configuration/connections.rb:170:in > `execute_on_servers' > from C:/Programs/ruby-1.8.6/lib/ruby/site_ruby/1.8/rubygems/ > custom_require.rb:31:in `each_slice' > ... 40 levels... > from C:/Programs/ruby-1.8.6/lib/ruby/gems/1.8/gems/ > capistrano-2.5.3/lib/capistrano/cli/execute.rb:14:in `execute' > from C:/Programs/ruby-1.8.6/lib/ruby/gems/1.8/gems/ > capistrano-2.5.3/bin/cap:4 > from C:/Programs/ruby-1.8.6/bin/cap:19:in `load' > from C:/Programs/ruby-1.8.6/bin/cap:19 > ====== > > Sorry to be a pain, but any ideas of what is going wrong and how to > fix it? > > Thanks, > Larry > > > On 6 Dec, 23:58, "Jamis Buck" <[EMAIL PROTECTED]> wrote: >> Just a quick note to announce Capistrano 2.5.3. You can read the full >> release announcement here: >> >> http://capify.org/2008/12/7/capistrano-2-5-3 >> >> The most notable fix is the lingering issue with deploying from a git >> repository, where you'd get "Unable to resolve revision" errors. Those >> are hopefully laid to rest, now. >> >> Cheers, >> >> Jamis > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
