Skip to content

Conversation

deivid-rodriguez
Copy link
Contributor

What was the end-user or developer problem that led to this PR?

When bundle install --prefer-local is run, Bundler will install a remote gem even if the same gem is available as a default gem.

What is your fix for the problem, implemented in this PR?

Make sure to always prefer default gems over remote gems when --prefer-local is given.

Closes #8180.

Make sure the following tasks are checked

@deivid-rodriguez deivid-rodriguez force-pushed the deivid-rodriguez/prefer-local-fixes branch from cbd45f7 to 3df86cd Compare January 17, 2025 07:36
@deivid-rodriguez deivid-rodriguez merged commit 209b93a into master Jan 17, 2025
91 checks passed
@deivid-rodriguez deivid-rodriguez deleted the deivid-rodriguez/prefer-local-fixes branch January 17, 2025 09:10
deivid-rodriguez added a commit that referenced this pull request Feb 17, 2025
…fixes

Fix `--prefer-local` not respecting default gems

(cherry picked from commit 209b93a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bundle install with default gems already installed in ruby tries to install them again

1 participant