Upgrading to Activesupport 1.2.2 from 1.2.1 breaks rails. See below. The 1.2.1 ebuild seems to have been removed from portage. I don't know the reason for this deletion, but it makes running rails a bit tricky atm... /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require__': no such file to load -- initializer (LoadError) from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require' from ./script/../config/boot.rb:14 from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in `require' from script/server:2 Reproducible: Always Steps to Reproduce: 1. 2. 3.
Sorry, that's the wrong output. Can't find the proper one anymore (rails is now officially borked on my system), but rails really wanted 1.2.1 and didn't like 1.2.2 very much.
Did you upgrade rails and all of the other ones as well?
I copied rails-0.14.1 to 0.14.2 and upgraded, which brought upgrades to dev-ruby/actionpack, dev-ruby/actionmailer and dev-ruby/actionwebservice (probably could have done this manually, but rails still needs activesupport-1.2.1, it literally says so). After this upgrade, all seems to work again. However, rails-0.14.2 is not yet in portage.
sorry ,forgot to commit it from my local tree. merged now.
.
