Bug #13277: Ruby 2.4.0 gem server 2.6.8

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: 2.4.0
• Backport: 2.2: UNKNOWN, 2.3: DONTNEED, 2.4: DONE

[MSP-Greg (Greg L)]

People involved with larskanis/rubyinstaller2, a new Windows build system for Ruby based on msys2 packages and mingw, found that gem server (v2.6.8) is not working properly in 2.4.0.

One person used the gem update --system command, another copied files from trunk. Both updated to 2.6.10, and gem server worked fine.

Hence, could the next release be updated to 2.6.10?

[shevegen (Robert A. Heiler)]

I guess when a new ruby main release will happen, the distributed gem in the bundle will also be
updated. The last release happened at around xmas 2016 so I guess we may get a new ruby release
in a not too terribly long time (currently we have march so about 3 months have passed).

[larskanis (Lars Kanis)]

The related fix in the rubygems-2.6.9 changelog is https://github.com/rubygems/rubygems/blob/a2920e27661a18f60ad76b17b13961dd07f034d3/History.txt#L19

Please backport rubygems-2.6.10 to the next stable ruby-2.4 release.

[MSP-Greg (Greg L)]

Verified as fixed in oneclick / rubyinstaller #21. Please close.

[shyouhei (Shyouhei Urabe)]

• Status changed from Open to Closed

Closing. Thank you for the report.

[usa (Usaku NAKAMURA)]

• Backport changed from 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN to 2.2: UNKNOWN, 2.3: DONTNEED, 2.4: DONE