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
Unable to install gem at correct version (ruby 3.0.0): undefined method `request' for nil:NilClass #4338
Comments
I can confirm the installation works fine with ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-darwin20], so this appears to only be an issue with ruby gems and ruby 3. |
I can confirm this issue. The underlying error is that The problem here is that rubygems is unable to properly explain this and crashes instead. |
Fixing this issue is more complicated than it seems. To show proper explanation for resolution errors like this, we need to add the current ruby (and rubygems) version as metadata dependencies to the resolution (like bundler does), so that when conflicts happen, they make sense and can explain the error to the user. In #4110 I implemented a very basic approach of filtering out specs not matching the current ruby (and rubygems) version as they come from the API. However, that approach is not enough here. I have a WIP branch but it needs a lot of work. |
I've added an example gem that has this issue too (although simply running gem install as above might be simpler) https://github.com/iainbeeston/gem_testcase |
|
Update version with `Support Ruby 3.0.0`. More info: rubygems/rubygems#4338 (comment)
I'm having a problem or would like to suggest a feature.
My current problem is an inability to install gems at a specific version. I am running Ruby 3.0.0 on 13" Macbook Pro (Apple Silicon, M1) using a Terminal with Rosetta. rbenv was installed with homebrew, ruby was installed with rbenv, ruby gems was updated using
gem update --system
.This issue is related to:
gem
Here are my current environment details:
I will abide by the code of conduct.
The text was updated successfully, but these errors were encountered: