Backport #7869

Revert JSON version bump, since it posibly breaks Ruby backward compatibility

Added by vo.x (Vit Ondruch) over 7 years ago. Updated about 1 year ago.



Although reverting version bump means that Ruby's JSON will differs from RubyGems version of JSON, it prevents possible compatibility issues for every project, which might use Bundler to specify its dependencies. Although for regular user, this incompatibility might be fixed by simple 'bundle update' command, it is not doable for Linux distributions, which provides packaged Ruby, including JSON gem, but are not responsible for every Ruby project on the system.

See ruby-core:52254 for more discussion.

Thank you.


0001-Revert-JSON-version-bump.patch (1.18 KB) 0001-Revert-JSON-version-bump.patch vo.x (Vit Ondruch), 02/17/2013 08:26 AM

Updated by usa (Usaku NAKAMURA) over 7 years ago

I've read the discussion from [ruby-core:52254], and I may understand your
But my conclusion is:
You should do "bundle install" after updating ruby, because bundler says so.

I cannot understand the situation where you can update ruby but cannot perform bundle install (or update).

Therefore, I continue the principle of "changing the version of bundled gem, if it is updated."
But this subject is still open.
Please show your opinions on this ticket, guys and dolls.

Updated by vo.x (Vit Ondruch) over 7 years ago

I am speaking from Fedoras, RHEL's Ruby packager point of view. So Ruby updates are my responsibility and we do care to provide latest Ruby. On the other hand, I have no idea what application our users run with the Ruby I provide. There is no way how to run "bundle install" since I don't know if my users are using Bundler or where they applications are located.


Updated by jeremyevans0 (Jeremy Evans) about 1 year ago

  • Status changed from Open to Closed

Also available in: Atom PDF