Permalink
Browse files

Tighten up AS.gemspec.

Apparently 0.6.2 has a call to force_encoding, which is not around
in 1.8.7.
  • Loading branch information...
1 parent 1a88523 commit 197b9f4d61260bea9e2a0a4883977e02164a0667 @steveklabnik steveklabnik committed Feb 27, 2013
Showing with 1 addition and 1 deletion.
  1. +1 −1 activesupport/activesupport.gemspec
@@ -18,6 +18,6 @@ Gem::Specification.new do |s|
s.rdoc_options.concat ['--encoding', 'UTF-8']
- s.add_dependency('i18n', '~> 0.6')
+ s.add_dependency('i18n', '= 0.6.1')
s.add_dependency('multi_json', '~> 1.0')
end

6 comments on commit 197b9f4

💩, their master should be already handling it, but we may need another release fixing the problem.

Member

steveklabnik replied Feb 27, 2013

/me nods

Contributor

sferik replied Mar 19, 2013

It looks like i18n 0.6.4 was released on the same day as this patch, which fixed the problem on 1.8.7.

The same day, 641a27d was applied to the 3-2-stable branch. How come this change didn’t make it into the 3.2.13 release?

Member

steveklabnik replied Mar 19, 2013

How come this change didn’t make it into the 3.2.13 release?

The release branch has it in it: https://github.com/rails/rails/commits/3-2-13

👎

I coded a project using Rails 3.2.11 with I18n 0.6.4, now I can't upgrade to Rails 3.2.13 because it is forcing I18n 0.6.1 wich expects an array of translations, but I18n 0.6.4 save just a string. All my project has just the first char at translated strings.

Owner

rafaelfranca replied Apr 9, 2013

@dlibanori use 3-2-stable

Please sign in to comment.