| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
backport of ae865a073c4e713d6f9c2a6143a0e81041031eb8
|
| |
|
| |
|
|\
| |
| | |
[LockfileParser] Leniently handle unknown states
|
| | |
|
|/
|
|
| |
[ci skip]
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
Version 1.8.9
Conflicts:
CHANGELOG.md
lib/bundler/version.rb
|
| | |
|
| | |
|
| |\
| | |
| | |
| | | |
Version 1.7.15
|
| | |
| | |
| | |
| | | |
[ci skip]
|
| | |\
| | | |
| | | | |
Replace locked gem sources with Gemfile equivalents.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously, an up-to-date lock file would retain the aggregate gem
source on all dependencies, so if the gems were not installed locally,
you'd get an ambiguous gem warning and possibly the wrong source
selected.
Fixes #3585
|
| | |/ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Long config values get wrapped to a second line. If they contain certain
special characters they will also get surrounded by quotes. When this
happened, we would add extra quotes to the value each time the config
file was saved. 94fd250935314aee86759de3e9b0e98a709823ed fixed this
issue for non-wrapped lines. Now it is fixed for wrapped lines as well.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
fixes hanging specs on 1.8.7 on Travis, I hope
|
| | | |
|
| | |
| | |
| | |
| | | |
this passed for me locally because my `rspec` bin was pointing to the
system Ruby 2.0 instead of Ruby 1.8.7 like it was supposed to be :open_mouth:
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
fixes #3520
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since rubygems/rubygems@4fa03bb7aac9f25f44394e818433fdda9962ae8d
rubygems lazily loads specs from the filesystem for a particular name.
So if you request the "foo" gem, then rubygems will go to the FS and
find the gemspecs with the "foo" name. **Before** the change, rubygems
would search through the loaded spec list for a gem with that name.
Bundler assumed that rubygems would always search through that spec
list, so it sets the specs and relies on that internal behavior. Since
the internal behavior changed, we need to take that in to account in the
bundler internals.
This patch changes bundler to search through the spec list for a gem
with a particular name. Gem::Specification.stubs should be supported in
the future (though not recommended because loading every spec isn't
super performant).
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, an up-to-date lock file would retain the aggregate gem
source on all dependencies, so if the gems were not installed locally,
you'd get an ambiguous gem warning and possibly the wrong source
selected.
Fixes #3585
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This silently hides StandardErrors :(
Fixes #3549
This reverts commit f740c40598142d990d59e129293c22c5d6f980b7.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since 17a4fc47bfad02de553e5a53b00ad38b4c905e18, any gem name starting with an
existing const name has been regarded as "Invalid gem name" by `bundle gem` command.
However, "gem-foo" or "rails-bar" should be totally valid and rather preferable
naming for plugins for RubyGems/Rails.
This commit changes the rule to raise error only when the new gem name fully
matches an existing const name.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since rubygems/rubygems@4fa03bb7aac9f25f44394e818433fdda9962ae8d
rubygems lazily loads specs from the filesystem for a particular name.
So if you request the "foo" gem, then rubygems will go to the FS and
find the gemspecs with the "foo" name. **Before** the change, rubygems
would search through the loaded spec list for a gem with that name.
Bundler assumed that rubygems would always search through that spec
list, so it sets the specs and relies on that internal behavior. Since
the internal behavior changed, we need to take that in to account in the
bundler internals.
This patch changes bundler to search through the spec list for a gem
with a particular name. Gem::Specification.stubs should be supported in
the future (though not recommended because loading every spec isn't
super performant).
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, an up-to-date lock file would retain the aggregate gem
source on all dependencies, so if the gems were not installed locally,
you'd get an ambiguous gem warning and possibly the wrong source
selected.
Fixes #3585
|
| | | |
|
| | | |
|