-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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 2.2.15 doesn't use prepackaged libv8 version; tries to build locally #4513
Comments
Hi! Can you try bundler 2.2.14? I fixed a regression in 2.2.15 that I haven't released yet, I plan to do that in the next few days. |
Hi, thanks for your amazing fast response! :-) Locally it seems to work with
I couldn't test it on the debian server since I failed to change the default-bundler version and had no time to investigate other ways to inject this into the capistrano deployment, yet. So my guess would be: yes, seems to be 2.2.15 only. So we hope for a soon release of 2.2.16 where the issue is hopefully gone? :) Thanks again! |
Yes, this was fixed by #4497, and I expect to release it in a couple of days. |
Closing since this is fixed. |
Seems to be fixed with 2.2.16, thank you very much! |
No problem! |
* Bundler 2.2.16 - rubygems/rubygems#4513 - rubyjs/libv8#310 (comment) - rubygems/rubygems#4497 - https://heroku.support/978905 * Apply suggestions from code review Co-authored-by: Ed Morley <501702+edmorley@users.noreply.github.com> Co-authored-by: Ed Morley <501702+edmorley@users.noreply.github.com>
Describe the problem as clearly as you can
Hello, I have massive problems with bundler > 2.1.
On my Kubuntu 20.10 (amd64 notebook) machine as well while our capistrano deployment on an Debian GNU/Linux 10 (buster) amd64 virtual server using Ruby 3.0.1 and bundler 2.2.15 the bundle process is fetching all the libv8 sources (1-2GBytes btw) and tries to compile them. This fails (for reasons I better do not want to understand at this point), but the core issue is that it doesn't use the prebuild packages (e.g. 8.4.255.0 x86_64-linux, see https://rubygems.org/gems/libv8/versions ).
When running
bundle _2.1.4_ update
locally I am able to update/install my dependencies since it uses the prebuild gem version.I think this is related to the issues mentioned here: rubyjs/libv8#310 (comment)
Since the old bundler version seems to work fine I'd say that the behavior isn't intended, is it?
Thanks for any hints!
Post steps to reproduce the problem
Run bundle update on a project using e.g. libv8 with Ruby 3.0.1 (might be optional) an bundler 2.2.15
What were you expecting to happen?
Bundler successfully installs libv8 using the prebuilt version
What actually happened?
Downloads the sources and tries to compile them.
Environment
Bundler Build Metadata
Bundler settings
The text was updated successfully, but these errors were encountered: