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

gem list don't show some gems as default #4019

Closed
etehtsea opened this Issue Jul 18, 2016 · 10 comments

Comments

Projects
None yet
5 participants
@etehtsea
Contributor

etehtsea commented Jul 18, 2016

jruby 9.1.2.0 (2.3.0) 2016-05-26 7357c8f Java HotSpot(TM) 64-Bit Server VM 25.77-b03 on 1.8.0_77-b03 [darwin-x86_64]

$ gem list |grep default 
jar-dependencies (default: 0.3.2)
minitest (5.9.0, 5.8.4, default: 5.4.1)
net-telnet (default: 0.1.1)
power_assert (default: 0.2.3)
rake (11.2.2, 10.5.0, default: 10.4.2, 10.1.1)
rdoc (4.2.2, default: 4.2.0)
test-unit (default: 3.1.1, 2.5.5)

Gems that are missing from this list:

  • racc
  • psych
  • json
  • jruby-openssl
$ gem uninstall json
ERROR:  While executing gem ... (Gem::InstallError)
    gem "json" cannot be uninstalled because it is a default gem

P.S. Why rake is default on JRuby and is not on MRI?

@mkristian

This comment has been minimized.

Show comment
Hide comment
@mkristian

mkristian Jul 18, 2016

Member

rake is preinstalled with jruby but should not be a default gem.

the rest looks inconsistent as well.

Member

mkristian commented Jul 18, 2016

rake is preinstalled with jruby but should not be a default gem.

the rest looks inconsistent as well.

@etehtsea

This comment has been minimized.

Show comment
Hide comment
@etehtsea

etehtsea Aug 16, 2016

Contributor

Okay, issue that some gems aren't shown as default is unrelated to JRuby itself.
Leaving it open until rubygems will be updated.

Contributor

etehtsea commented Aug 16, 2016

Okay, issue that some gems aren't shown as default is unrelated to JRuby itself.
Leaving it open until rubygems will be updated.

homu added a commit to rubygems/rubygems that referenced this issue Aug 17, 2016

Auto merge of #1685 - etehtsea:fix-jruby-default, r=segiddins
Show default gems for all platforms

# Description:
Before:

On JRuby 9k:

```sh
gem list
*** LOCAL GEMS ***

did_you_mean (default: 1.0.1)
ffi (1.9.14 java)
jar-dependencies (default: 0.3.5, default: 0.3.2)
jruby-openssl (0.9.17 java) # <----
json (1.8.3 java) # <----
minitest (default: 5.4.1)
net-telnet (default: 0.1.1)
power_assert (default: 0.2.3)
psych (2.0.17 java) # <----
racc (1.4.14 java, 1.4.13 java) # <----
rake (default: 10.4.2)
rdoc (default: 4.2.0)
test-unit (default: 3.1.1)
```

After:

```sh

*** LOCAL GEMS ***

did_you_mean (default: 1.0.1)
ffi (1.9.14 java)
jar-dependencies (default: 0.3.5, default: 0.3.2)
jruby-openssl (default: 0.9.17 java) # <----
json (default: 1.8.3 java) # <----
minitest (default: 5.4.1)
net-telnet (default: 0.1.1)
power_assert (default: 0.2.3)
psych (default: 2.0.17 java) # <----
racc (default: 1.4.14 java, default: 1.4.13 java) # <----
rake (default: 10.4.2)
rdoc (default: 4.2.0)
test-unit (default: 3.1.1)
```

Original issue: jruby/jruby#4019

etehtsea added a commit to etehtsea/jruby that referenced this issue Aug 17, 2016

etehtsea added a commit to etehtsea/jruby that referenced this issue Aug 17, 2016

@headius

This comment has been minimized.

Show comment
Hide comment
@headius

headius Aug 17, 2016

Member

@etehtsea Help us by letting us know when there's a RubyGems release out. We can pull it into 9.1.3.0 if it's not too drastic.

Member

headius commented Aug 17, 2016

@etehtsea Help us by letting us know when there's a RubyGems release out. We can pull it into 9.1.3.0 if it's not too drastic.

@etehtsea

This comment has been minimized.

Show comment
Hide comment
@etehtsea

etehtsea Aug 17, 2016

Contributor

@headius for sure

Contributor

etehtsea commented Aug 17, 2016

@headius for sure

etehtsea added a commit to etehtsea/jruby that referenced this issue Aug 18, 2016

etehtsea added a commit to etehtsea/jruby that referenced this issue Aug 18, 2016

@headius headius added this to the JRuby 9.1.3.0 milestone Aug 19, 2016

@headius

This comment has been minimized.

Show comment
Hide comment
@headius

headius Aug 22, 2016

Member

I don't think this will be ready for 9.1.3.0. Bumping.

Member

headius commented Aug 22, 2016

I don't think this will be ready for 9.1.3.0. Bumping.

@headius headius modified the milestones: JRuby 9.1.4.0, JRuby 9.1.3.0 Aug 22, 2016

etehtsea added a commit to etehtsea/jruby that referenced this issue Oct 1, 2016

etehtsea added a commit to etehtsea/jruby that referenced this issue Oct 1, 2016

@headius headius closed this in #4198 Oct 5, 2016

headius added a commit that referenced this issue Oct 5, 2016

@headius headius referenced this issue Oct 5, 2016

Closed

Update RubyGems #4205

@etehtsea

This comment has been minimized.

Show comment
Hide comment
@etehtsea

etehtsea Nov 10, 2016

Contributor

please reopen, because fix didn't get into release.

Contributor

etehtsea commented Nov 10, 2016

please reopen, because fix didn't get into release.

@kares kares reopened this Nov 10, 2016

@enebo enebo modified the milestones: JRuby 9.1.7.0, JRuby 9.1.6.0 Nov 15, 2016

@headius

This comment has been minimized.

Show comment
Hide comment
@headius

headius Dec 13, 2016

Member

Still waiting on a RubyGems release with the patch in question. We can patch it ourselves, but the first time anyone (or anything, like rvm) updates RubyGems, it will wipe out our change.

I have requested a backport of the patch and a 2.6.9 release of RubyGems in rubygems/rubygems#1685.

Member

headius commented Dec 13, 2016

Still waiting on a RubyGems release with the patch in question. We can patch it ourselves, but the first time anyone (or anything, like rvm) updates RubyGems, it will wipe out our change.

I have requested a backport of the patch and a 2.6.9 release of RubyGems in rubygems/rubygems#1685.

@enebo enebo modified the milestones: JRuby 9.2.0.0, JRuby 9.1.7.0 Jan 10, 2017

@kares

This comment has been minimized.

Show comment
Hide comment
@kares

kares Aug 9, 2017

Member

this one is resolved by now, right? I am seeing default gems being reported using the current SNAPSHOT

Member

kares commented Aug 9, 2017

this one is resolved by now, right? I am seeing default gems being reported using the current SNAPSHOT

@etehtsea

This comment has been minimized.

Show comment
Hide comment
@etehtsea

etehtsea Aug 10, 2017

Contributor

@kares it seems that currently bundled rubygems is patched, but there is still no upstream rubygems version with this fix.

Contributor

etehtsea commented Aug 10, 2017

@kares it seems that currently bundled rubygems is patched, but there is still no upstream rubygems version with this fix.

@headius

This comment has been minimized.

Show comment
Hide comment
@headius

headius May 16, 2018

Member

I'm going to close this. If there's a RubyGems fix we don't have, or a fix that's not in RG, that needs to happen first. But we will be on latest RG for 9.2.

Member

headius commented May 16, 2018

I'm going to close this. If there's a RubyGems fix we don't have, or a fix that's not in RG, that needs to happen first. But we will be on latest RG for 9.2.

@headius headius closed this May 16, 2018

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