I just did a gem update and it broke my rails application. I had to
go back to 2.0.2, because 2.0.2.9129 produces this error on Mac OS X
Leopard:
/Users/nicholas/RubyDev/dummy/config/environment.rb:38: undefined
method `time_zone=' for #<Rails::Configuration:0x12c9f24>
(NoMethodError)
from /Library/Ruby/Gems/1.8/gems/rails-2.0.2/lib/initializer.rb:47:in
`run'
from /Users/nicholas/RubyDev/dummy/config/environment.rb:13
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/
ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/
ruby/1.8/rubygems/custom_require.rb:27:in `require'
from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/
active_support/dependencies.rb:496:in `require'
from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/
active_support/dependencies.rb:342:in `new_constants_in'
from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/
active_support/dependencies.rb:496:in `require'
from /Library/Ruby/Gems/1.8/gems/mongrel-1.1.4/bin/../lib/mongrel/
rails.rb:147:in `rails'
... 20 levels...
from /Library/Ruby/Gems/1.8/gems/rails-2.0.2/lib/commands/server.rb:
39
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/
ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/
ruby/1.8/rubygems/custom_require.rb:27:in `require'
from script/server:3
Guys... gem sources -r http://gems.rubyonrails.org/. Some wonky
tutorial or something prolly [accidentally] permanently added that
repo to yr gem sources. As it contains "developer" gems [which are
essentially Edge Rails snapshots], you prolly don't want that. Just
remove that source as I suggested and remove those gem rails ending in
the revision numbers and you will be fine. Rails is not broken. All is
well in the kingdom.
Ok thanks first, despite the message I got in IRC is a bit rude, you
do indeed point out the issue correctly and now the problem is fixed.
So- can explain a bit if I should remove the gem source from
rubyonrails.org, or thats just a intermittent issue so I just keep my
gems not update for a while and it should be ok?