Alright, great to know that was fixed in 3.2.13.rc :). I'll check what we can do regarding i18n. Thanks!
On Tue, Mar 12, 2013 at 6:00 PM, byrnejb <[email protected]> wrote: > > > On Tuesday, 12 March 2013 16:40:23 UTC-4, Carlos Antonio da Silva wrote: > >> There was a problem with i18n versions, so someone locked it to 0.6.1 >> before releasing the first rc =(. It's already fixed but the rc is locked >> and probably 3.2.13 will be, need to check that. >> >> >> On Tue, Mar 12, 2013 at 5:38 PM, James B. Byrne <[email protected]>wrote: >> >>> Bundler could not find compatible versions for gem "i18n": >>> In Gemfile: >>> rails (= 3.2.13.rc2) ruby depends on >>> i18n (= 0.6.1) ruby >>> >>> >>> i18n (0.6.4) >>> >>> Unfortunately, I have another dependency that requires I18n (0.6.4) so >>> downgrading is not an option I am prepared to consider. Is there some >>> reason that RoR-3.2.12 works with 0.6.4 and 3.2.13 does not? >>> >>> > > I extracted the bits of interest and tested them against ror-3.2.13rc2. > The test now passes. So, I will roll this back into the project and go on > from there. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- At. Carlos Antonio -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
