New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RubyGems after 2.4.8 is broken on JRuby #3718

Closed
headius opened this Issue Mar 9, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@headius
Member

headius commented Mar 9, 2016

We're going to need to work with RG folks to get recent RG releases working on JRuby.

At a minimum we have:

We want to ship JRuby 9.1 and 1.7.25 soon with updated RubyGems, but for now we're stuck.

cc @tenderlove @indirect @segiddins

@segiddins

This comment has been minimized.

Show comment
Hide comment
@segiddins

segiddins Mar 9, 2016

As I commented on that issue, I have a fix that'll be ready really soon.

As I commented on that issue, I have a fix that'll be ready really soon.

@segiddins segiddins referenced this issue Mar 9, 2016

Merged

[Resolver] Fix platform sorting #1542

4 of 4 tasks complete

homu added a commit to rubygems/rubygems that referenced this issue Mar 10, 2016

Auto merge of #1542 - rubygems:seg-fix-jruby-platform, r=indirect
[Resolver] Fix platform sorting

# Description:

Fixes #1541.
Fixes jruby/jruby#3718.

# Tasks:

- [x] Describe the problem / feature
- [x] Write tests
- [x] Write code to solve the problem
- [ ] Get code review from coworkers / friends

I will abide by the [code of conduct](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md).
@headius

This comment has been minimized.

Show comment
Hide comment
@headius

headius Apr 19, 2016

Member

All known issues with RubyGems were fixed as of 2.6.2, and we are running that version for 9.1 now.

Member

headius commented Apr 19, 2016

All known issues with RubyGems were fixed as of 2.6.2, and we are running that version for 9.1 now.

@headius headius closed this Apr 19, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment