Ruby on Rails updated to 2.1.0
We’ve updated the default version of Ruby on Rails on our servers to version 2.1.0.
If you use Rails and you haven’t explicitly chosen your own version, it’s a good idea to check your applications and make sure there are no problems. But if you’re concerned about compatibility, it’s probably best to freeze Rails anyway so that server upgrades like this can’t affect your application.
If you’re interested in some notes about upgrading to Rails 2, our previous “Rails 2 update coming soon” post has some details.
As part of this upgrade, we also updated Ruby itself to version 1.8.5 (plus Debian security patches), because the ActiveSupport gem in 2.1.0 isn’t compatible with Ruby versions prior to 1.8.4.
(In case anyone’s searching the Internet with the same problem, older Ruby versions are the cause of an error saying “/usr/lib/ruby/gems/1.8/gems/activesupport-2.1.0/lib/active_support/core_ext/bigdecimal/conversions.rb:18: undefined method `yaml_as’ for ActiveSupport::CoreExtensions::BigDecimal::Conversions:Module”.)
on Wednesday, August 13, 2008 at 1:37 pm (Pacific) williamp wrote:
[newbie] I have ruby -v => 1.8.7 and rails -v => 2.10 but still get this error when I run rails
/usr/lib/ruby/gems/1.8/gems/activesupport-2.1.0/lib/active_support/core_ext/bigdecimal/conversions.rb:18: undefined method `yaml_as’ for ActiveSupport::CoreExtensions::BigDecimal::Conversions:Module (NoMethodError)
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require’
on Wednesday, August 13, 2008 at 2:50 pm (Pacific) Robert Mathews wrote:
williamp — just to confirm, you aren’t a Tiger Technologies customer, correct? You’re seeing this on some other server?
If so, it’s difficult to know what to suggest. All we can say is that on our servers, an old Ruby version was the cause of that problem. You might want to type “ruby -v” on the command line and make sure that it really is running Ruby 1.8.7, and not some older version. Perhaps you accidentally have two versions of Ruby installed….?
(If we’ve misunderstood and you are a Tiger Technologies customer who has compiled your own version of Ruby 1.8.7, please contact our friendly support team for help.)
on Thursday, August 14, 2008 at 9:22 am (Pacific) williamp wrote:
you’re quite right — this is macosx, there was a /usr/bin/ruby back at 1.8.2 — dont know why some web advice countenances leaving an out of date version on the machine. blew that away and we’re in business