I recently upgraded rails from 3.0.7 to 3.0.9. Rails app rojects keep a list of all gems used, and if you intend to use the system's gem rather than bundling gems internally in the app, you have to update the project whenever your system's gems are updated so that the two match. Rails projects are updated from within the project root using: rake update:rails When I try to do that I get the following: Could not find rake-0.9.2 in any of the sources Run `bundle install` to install missing gems. As I understand it, the "bundle install" is not the preferred Gentoo method of managing gems since they are not installed system-wide, and bypass the build packaging system. Reproducible: Always
dev-ruby/railties depends on rake >=0.8.7 so my guess is that some other gem in you Gemfile requires rake 0.9.0. You can check the Gemfile.lock to see which one.
The Gemfile.lock does list rake (>= 0.8.7) for railities, but then further down lists rake-0.9.2 by itself. I'm not sure why it is in there because it was not available before upgrading rails to 3.0.7. All the other gem dependencies are still listing the previous version since I haven't been able to get it to update. I tried to create a new rails project to see what the Gemfile.lock would contain from the newer rails-3.0.9, but that fails as well: $ rails new dummy /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require': no such file to load -- rails/cli (LoadError) from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `require' from /usr/lib64/ruby/gems/1.8/gems/rails-3.0.9/bin/rails:8 from /usr/bin/rails:8:in `load' from /usr/bin/rails:8
Created attachment 279253 [details] rails-3.0.7 Gemfile.lock attaching Gemfile.lock
As far as I know nothing in the Gentoo tree currently depends on rake 0.9, and I can create a new rails app with rails 3.0.9 without problems. Since you are using bundler, it might have dumped gems in the gem directory in your home directory, and that may be where rake 0.9 is being picked up.
I used bundler to see what it would download that it thinks is missing, but afterwards I removed the ~/.gem directory. Does it drop files anywhere else that I need to remove?
Not quite sure what the problem was, but emerging rdoc seemed to fix the issue with rails not starting up. After that I could delete the Gemfile.lock and rake would build a new one.
(In reply to comment #6) > Not quite sure what the problem was, but emerging rdoc seemed to fix the issue > with rails not starting up. Ah right, that's the same problem we had with Rails 2.3.12. One of the task files requires an rdoc task file that is only available in the rdoc gem. I've added this dependency now. > After that I could delete the Gemfile.lock and rake would build a new one. Ok, so does that mean that your original problem is solved?
Yes, problem seems to be solved. It would seem that messing with bundler caused the newer version of rake to be added to the gem lock file, and the missing rdoc prevented me from generating an updated gem lock file.
