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
Bundler v2.3.36 incorrectly resolves to an incompatible pre-built gem instead of ruby platform one
#6482
Comments
|
The latest version of Bundler is 2.4.8. Does this problem still happen using that version? |
|
Yes it does. Sorry, forgot to specify that version as well. |
|
I'm confused. So this does work in Bundler 2.4.6, but does not work in Bundler 2.4.8? I was not expecting this kind of regression from the changes in the previous two versions. This issue seems similar to #6221, which was fixed by Bundler 2.4.3. |
|
Omg, sorry, I heavily misread. Let me clarify better. The The I hope this is better. |
|
Okay. I think that means you are reporting a bug we not only know about, but already fixed? If you ever run into this again in the future, please install the latest version of Bundler so that you are able to |
|
Yeah, we can't change the past and "erase bugs" from existing versions @jackorp |
|
Right, that is true. Thanks for the relevant pointers and sorry for the noise. |
Describe the problem as clearly as you can
We are using this app: https://github.com/sclorg/rails-ex
To test Ruby containers and the expected functionality.
Part of that is having a Gemfile that is compatible from Ruby 2.5 to Ruby 3.1 and onwards.
However, since Ruby 3.1.3, bundler fails to accept nokogiri 1.12.5 without pre-built native extensions as valid and attempts to use the
nokogiri-1.12.5-x86_64-linuxversion, which has a restriction on the Ruby version to be< 3.1.dev, therefore this one cannot be used. This wouldn't be a problem but it refuses to resolve the nokogiri tonokogiri-1.12.5which would work for us.Bundler seems to be confused from the conflict, it locks up in a loop in resolving deps:
Build with
--frozenfinally reveals what the actual problem is:I'd consider this a regression of behavior in Bundler shipped with Ruby 3.1.3. It works on bundler shipped with Ruby 3.2.1 as well as with bundler shipped with Ruby 3.1.2.
Did you try upgrading rubygems & bundler?
Yes, not a problem with Bundler version 2.4.6 bundled with Ruby 3.2.
Post steps to reproduce the problem
Simple:
0. Run Ruby 3.1.3
bundle install --path bundleAs we run it:
$ cat Dockerfile$ docker build --no-cache .Which command did you run?
bundle install --path bundleWhat were you expecting to happen?
Bundler resolves to
nokogiriwithout pre-built extensions as it did for bundler bundled with Ruby 3.1.2 and as it does for bundler bundled with Ruby 3.2.What actually happened?
Bundler locked up in an infinite loop similar to #6054
If not included with the output of your command, run
bundle envand paste the output belowEnvironment
Bundler Build Metadata
Gemfile
Gemfile
Gemfile.lock
The text was updated successfully, but these errors were encountered: