# Rake gems broken when using capistrano-ext in rails 2.2.x **URL:** \ **Category:** Rails\ **Created:** [December 4, 2008, 5:09am UTC](https://www.ruby-forum.com/t/rake-gems-broken-when-using-capistrano-ext-in-rails-2-2-x/154812 "2008-12-04T05:09:09Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Freddy\_A](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/6de8d8/32.png) [@Freddy\_A](https://www.ruby-forum.com/u/Freddy_A)\ **Post date:** [December 4, 2008, 5:09am UTC](https://www.ruby-forum.com/t/rake-gems-broken-when-using-capistrano-ext-in-rails-2-2-x/154812/1 "2008-12-04T05:09:09Z")
Just tested the rails bort setup and got an error when running rake gems: - [F] capistrano-ext rake aborted! You have a nil object when you didn’t expect it! The error occurred while evaluating nil.dependencies If I change to rails 2.1.2 it works fine but any of the rails 2.2.x versions gives the same nil… The problem line is =\> config.gem “capistrano-ext”, :lib =\> “capistrano” Anyone else seen this? Here is the full trace: - [F] capistrano-ext rake aborted! You have a nil object when you didn’t expect it! The error occurred while evaluating nil.dependencies /opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/ gem\_dependency.rb:77:in `dependencies' /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in`to\_proc’ /opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/ gem\_dependency.rb:80:in `map' /opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/ gem_dependency.rb:80:in`dependencies’ /opt/local/lib/ruby/site\_ruby/1.8/rubygems/custom\_require.rb:31:in `to_proc' /opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/ gem_dependency.rb:80:in`map’ /opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/ gem\_dependency.rb:80:in `dependencies' /opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/tasks/gems.rake: 15:in`print\_gem\_status’ /opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/tasks/gems.rake:4 /opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/tasks/gems.rake:3:in `each' /opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/tasks/gems.rake:3 /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:617:in`call’ /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:617:in `execute' /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:612:in`each’ /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:612:in `execute' /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:578:in`invoke\_with\_call\_chain’ /opt/local/lib/ruby/1.8/monitor.rb:242:in `synchronize' /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:571:in`invoke\_with\_call\_chain’ /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:564:in `invoke' /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:2019:in`invoke\_task’ /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `top_level' /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in`each’ /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `top_level' /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:2036:in`standard\_exception\_handling’ /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:1991:in `top_level' /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:1970:in`run’ /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:2036:in `standard_exception_handling' /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:1967:in`run’ /Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/bin/rake:31 /usr/bin/rake:19:in `load’ /usr/bin/rake:19 ---
**Author:** ![Freddy\_A](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/6de8d8/32.png) [@Freddy\_A](https://www.ruby-forum.com/u/Freddy_A)\ **Post date:** [December 4, 2008, 5:22am UTC](https://www.ruby-forum.com/t/rake-gems-broken-when-using-capistrano-ext-in-rails-2-2-x/154812/2 "2008-12-04T05:22:03Z")
Found it… There was a bug that was found and will be fixed in Rails 2.2.3… The patch at lighthouse is here: [http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1464](http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1464)