| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
- add new rubygems 2.5.0
- update rubygems 2.2.3 to 2.2.5
- remove rbx-2, it has never passed
- stop testing Ruby 1.9.2, it’s unused enough now
|
|\
| |
| | |
Retry Fetch operation on Zlib error.
|
| |
| |
| |
| |
| | |
I really don't like this solution, but it's the simplest one so we can
recover from that error on 1.8.7.
|
| |
| |
| |
| | |
This fixes #4074
|
|\ \
| |/
|/|
| |
| |
| | |
Handle invalid RubyGems config files
Fixes #4042.
|
|/
|
|
| |
Fixes #4042.
|
|\
| |
| |
| |
| | |
Extract exception classes to a separate file
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix Gem::SystemExitException initialization
Previously, we would attempt to initialize `Gem::SystemExitException`
without an argument, which would result in an `ArgumentError` since the
argument is required (from Rubygems 1.3 all the way to 2.4).
I don't know how we missed this all this time. Maybe that path is not
even hit anymore.
Anyway, we don't even have to initialize a new exception, just re-raising the
one we've rescued is sufficient.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, we would attempt to initialize Gem::SystemExitException
without an argument, which would result in an `ArgumentError` since the
argument is required (from Rubygems 1.3 all the way to 2.4).
I don't know how we missed this all this time. Maybe that path is not
even hit anymore.
Anyway, we don't even have to initialize a new exception, just re-raising the
one we've rescued is sufficient.
|
|\ \
| |/
|/| |
Make SSL Verify Mode a number setting
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Warn if RUBYGEMS_GEMDEPS env. variable is set
Closes #3656.
|
| |/
| |
| |
| | |
Closes #3656.
|
|\ \
| |/
|/| |
Include revision hash in Source::Git#to_s
|
|/
|
|
|
|
|
|
|
| |
This effectively changes the output of commands that use Source::Git#to_s
(ie. `bundle install`). For example:
Using rack 1.0.0 from git@github.com:rack/rack.git (at master@574b147)
Closes #3433.
|
|\
| |
| | |
Send X-Gemfile-Source header to source mirrors
|
| |
| |
| |
| |
| | |
Since gemstash will only support RubyGems >= 2.4 (bundler/gemstash#32),
we only set this header in RubyGems 2.0+.
|
| |
| |
| |
| |
| | |
This is essentially Gem::RemoteFetcher with added support for setting
extra HTTP headers to be sent when fetching the gems.
|
| | |
|
|/
|
|
|
| |
Using `Source::Rubygems::Remote#original_uri` we can now retrieve the
original, unmirrored rubygem source URI.
|
|\
| |
| |
| |
| | |
[RuboCop] Update to 0.34.2
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| | |
[Resolver] Resolve for a given ruby version
Take the definition's ruby version into account when resolving, to try and avoid conflicts with incompatible `required_ruby_version`s. This will mostly help once the compact index is in use.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
[Index] Handle when comparing against an index with no gemspec
Closes #4004.
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Remove excessive periods from DSL error messages
Apparently, a period is already added when interpolating those messages,
some lines below.
|
| | |
| | |
| | |
| | |
| | | |
Apparently, a period is already added when interpolating those messages,
some lines below.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove `autoload :Specification`
This constant isn't defined anymore
|
| | | |
| | | |
| | | |
| | | |
| | | | |
- This class was removed in 2010 but the autoload was neglected 64b8b5
- Closes #4050
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Refactoring config.rb
My main goal was to show the structure of the run method:
1. Guard Clauses
2. Message to user
3. Save new settings
and to separate the message texts from the rest of the logic.
So the class and methods are easier to understand read.
While doing that I reduced the complexity of the run method by
extracting methods. This should improve the Code Climate rating of
Bundler::CLI::Config substantially.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
My main goal was to show the structure of the run method:
1. Guard Clauses
2. Message to user
3. Save new settings
and to separate the message texts from the rest of the logic.
So the class and methods are easier to understand read.
While doing that I reduced the complexity of the run method by
extracting methods. This should improve the Code Climate rating of
Bundler::CLI::Config substantially.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Add more `Env` tests
|
| |/ / / |
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add missing backtick in Bundler::GemHelper#sh
Since across the codebase and documentation shell commands are displayed
wrapped in backticks, the command included in the error output of
Bundler::GemHelper#sh should also be displayed in the same format.
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
Since across the codebase and documentation shell commands are displayed
wrapped in backticks, the command included in the error output of
Bundler::GemHelper#sh should also be displayed in the same format.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
clean: add test for not removing git extensions artifacts
Unfortunately https://github.com/bundler/bundler/pull/4030 was merged before I had a chance to write a test. I confirmed that the test did not pass before my patch.
Any ETA of 1.10.7 which includes #4030? :heart:
@indirect @segiddins @andremedeiros @skottler
|
| |/ / |
|
| | | |
|
| | |
| | |
| | |
| | | |
this speeds up these tests by a huge amount, since we stop downloading
and installing a crapton of gems live over the internet
|