Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/stevenharman/bundler_issue_4452
https://github.com/stevenharman/bundler_issue_4452
Last synced: 2 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/stevenharman/bundler_issue_4452
- Owner: stevenharman
- Created: 2021-03-15T14:23:45.000Z (almost 4 years ago)
- Default Branch: main
- Last Pushed: 2021-03-15T14:27:37.000Z (almost 4 years ago)
- Last Synced: 2025-01-03T15:45:42.826Z (11 days ago)
- Language: Ruby
- Homepage:
- Size: 1.95 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Bundler: Multi-source Gemfile.lock Issue
This repo contains a minimal set of code to reproduce an issue with incompatible `Gemfile.lock` files.
## The Problem
We have multiple sources in our Gemfile - rubygems and a private gem server.
When generating with Bundler 2.2.14 the Gemfile.lock has multiple GEM sections, one for each of the two source declared in the Gemfile.
This is as expected.However, when trying to bundle install for deployment with an older Bundler (2.2.11, for example), an error is raised.
This happens in practice when deploying to Heroku, for example, because the heroku/ruby build pack uses Bundler 2.2.11.## Bundler Issue on GitHub
I've used this code to open an [Issue on Bundler](https://github.com/rubygems/rubygems/issues/4452).
Check there for current status, updates, etc…