Bug 1036708 - Ruby specifies a wrong version of bundled RubyGems
Summary: Ruby specifies a wrong version of bundled RubyGems
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: ruby
Version: 22
Hardware: All
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-02 13:57 UTC by Josef Stribny
Modified: 2016-01-04 05:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-04 13:46:56 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Josef Stribny 2013-12-02 13:57:21 UTC 
Description of problem:

Ruby specifies it bundles RubyGems v2.0.3, but since last rebase to Ruby 2.0.0-p353, it should specify v2.0.14 as v2.0.14 comes with p353[1].


How reproducible:

Compare Ruby 2.0.0-p353 sources/changelog[1] with the version used in spec.

OR

`gem -v` prints the version of RubyGems used if you build and install the package.


Actual results:

Ruby states bad version of bundled RubyGems (2.0.3).


Expected results:

Ruby should state 2.0.14 as a version of bundled RubyGems.


Additional info:

This affects builds ruby-2.0.0.353-16.fc19 and ruby-2.0.0.353-16.fc20 which are in testing for f19/f20.


[1] http://svn.ruby-lang.org/repos/ruby/tags/v2_0_0_353/ChangeLog
Comment 1 Vít Ondruch 2014-01-03 15:06:58 UTC 
Fix for this issue is pushed info F19+ dist-git. Since this is minor issue (the independent rubygems package wins over this one), it can wait for next release ...
Comment 2 Jaroslav Reznik 2015-03-03 17:10:47 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 3 Vít Ondruch 2015-11-04 13:46:56 UTC 
This is resolved for current releases and the remaining Fedora versions are EOL already.
Note You need to log in before you can comment on or make changes to this bug.