| Age | Commit message (Collapse) | Author |
|
This option is similar to the `bundle install --quiet` option
https://github.com/rubygems/rubygems/commit/3bd773d827
|
|
Bundler always exits with a status code.
https://github.com/rubygems/rubygems/commit/3a38bd0b12
|
|
compatible requirements
https://github.com/rubygems/rubygems/commit/a8d14c1fc2
|
|
wrong source
https://github.com/rubygems/rubygems/commit/1e5780db0a
Co-authored-by: Taylor Thurlow <thurlow@hey.com>
|
|
https://github.com/rubygems/rubygems/commit/d5dce93167
|
|
https://github.com/rubygems/rubygems/commit/432fe083a6
|
|
https://github.com/rubygems/rubygems/commit/55eb6630a8
|
|
We fixed some issues recently where Bundler would try to activate a
pysch spec with missing extensions and crash. However, as a side effect,
we started printing warnings about missing extensions in situations
where we did not warn before.
It may be interesting to warn on these new situations too, but in order
to minimize changes for now, I'm reverting to printing warnings in the
same situations as before.
https://github.com/rubygems/rubygems/commit/51ebff6982
|
|
NFS shares seem to support flock these days, but they need read-write
permissions.
https://github.com/rubygems/rubygems/commit/1c492804cd
|
|
This reverts commit https://github.com/rubygems/rubygems/commit/e04e00f7bb5b.
https://github.com/rubygems/rubygems/commit/554ece1587
|
|
https://github.com/rubygems/rubygems/commit/c80998a22a
|
|
https://github.com/rubygems/rubygems/commit/74e8eff779
|
|
Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
Notes:
Merged: https://github.com/ruby/ruby/pull/11860
|
|
for some reason
https://github.com/rubygems/rubygems/commit/f8f589b1b8
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11835
|
|
It does not have ruby code, so we should not prepend `ruby` to the
command the re-execute it.
https://github.com/rubygems/rubygems/commit/e04e00f7bb
|
|
Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/272f3464a3
|
|
Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/085bafd8d4
|
|
Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/06eec6d855
|
|
3.0 has been EOL since march, drop support for it before the 3.4 release is cut
Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/fc1f03b06a
|
|
https://github.com/rubygems/rubygems/commit/f11e42a3c5
|
|
https://github.com/rubygems/rubygems/commit/72d8d4dbba
|
|
frozen mode
https://github.com/rubygems/rubygems/commit/4c79ab9b2e
|
|
activation under bundler
Closes https://github.com/rubygems/rubygems/pull/8068
This issue only occurs if the underlying stub is a gem stub:
https://github.com/Earlopain/rubygems/blob/f56098d8a193dcb94584d721e82b8cff397e5265/bundler/lib/bundler/stub_specification.rb#L109-L112
https://github.com/rubygems/rubygems/commit/9b0152b3d5
|
|
source controlled
https://github.com/rubygems/rubygems/commit/b2adcc0173
|
|
This was introduced by https://github.com/rubygems/rubygems/commit/0b7be7bb7705, because
the original patch was not adapted to some recent refactorings.
https://github.com/rubygems/rubygems/commit/0bca60d6e5
Co-authored-by: Hiroshi SHIBATA <hsbt@ruby-lang.org>
|
|
available remotely
https://github.com/rubygems/rubygems/commit/1a7a3fdeb9
|
|
See https://github.com/rubygems/rubygems/issues/8046 for details
Prior to this commit a cached git source without a specific ref wouldn't
survive pushing to a remote and then pulling on a different machine.
We'd end up without a refs directory in the cache, at which point git
won't recognize it as a repo.
This commit fixes the problem by adding a refs directory if it's not
already there. This needs to be done as early as possible, so any git
commands will work as expected, so this commit adds it before creating
the app cached git proxy.
https://github.com/rubygems/rubygems/commit/8c89f0b065
|
|
It was printing incorrect output and returning incorrect status.
https://github.com/rubygems/rubygems/commit/96f5979c7d
|
|
It has been supported since RubyGems 2.2.0 via https://github.com/rubygems/rubygems/commit/4525e45a4d45
Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/bf39c583e8
|
|
https://github.com/rubygems/rubygems/commit/907d46964d
|
|
https://github.com/rubygems/rubygems/commit/7cf2fdcfa1
|
|
https://github.com/rubygems/rubygems/commit/3434f094a2
|
|
included
https://github.com/rubygems/rubygems/commit/b9a2d4d539
|
|
Removes an (in my opinion) excessive indirection and handles options
more consistently.
https://github.com/rubygems/rubygems/commit/642e6d2c0c
|
|
https://github.com/rubygems/rubygems/commit/7ddf1dc70a
|
|
By the time `cached_gem` is called, default gem cache has already been
handled. So no need to try redownload it again, it's enough to check the
cache location directly.
https://github.com/rubygems/rubygems/commit/70e10236b6
|
|
https://github.com/rubygems/rubygems/commit/edbb2e3475
|
|
match
https://github.com/rubygems/rubygems/commit/174a8e5284
|
|
https://github.com/rubygems/rubygems/commit/03ddfd7610
Co-authored-by: Jonathan Hefner <jonathan@hefner.pro>
|
|
has extensions and `gemspec` DSL is being used
In a `bundle exec` context, the local specification will actually be
part of the known specifications, so RubyGems will assume it has already
been installed, which is not actually true.
This will cause `RequestSet` to rebuild extensions for a gem that's not
actually installed, causing errors.
The fix is to make sure detection of installed activation requests
considers not only that there's a known spec with the same full name as
the one being installed, but also that this spec is installed in the
same gem_home were pretend to install the new gem.
https://github.com/rubygems/rubygems/commit/a8ef1286a6
|
|
actually useful
DSLError prints the specific line in a Gemfile where the error was
raised. That's helpful when the error was explicitly raised by the
Gemfile DSL or, in the case it's implicitly raised, when the offending
code lives right in the Gemfile.
If it's an internal error, or something buried dowm in user code called
from the Gemfile, `DSLError` is not helpful since it hides the actual
culprit.
This commit tries to only raise `DSLError` in the cases mentioned above
and otherwise let the original error be raised.
https://github.com/rubygems/rubygems/commit/b30ff5a682
|
|
Things like OOM, or StackOverflow should be raised immediately.
https://github.com/rubygems/rubygems/commit/11691ce492
|
|
https://github.com/rubygems/rubygems/commit/b4ecb66224
|
|
string
https://github.com/rubygems/rubygems/commit/ab44fa9ee4
|
|
Currently, an exe file isn't executable when generating new gems
because it doesn't have the correct permission.
This PR sets the correct permission same as files under the `bin`.
https://github.com/rubygems/rubygems/commit/6509bf128a
|
|
https://github.com/rubygems/rubygems/commit/d46b6a49af
|
|
https://github.com/rubygems/rubygems/commit/8d94c14ca0
Co-authored-by: Jonathan Hefner <jonathan@hefner.pro>
|
|
`DSL#to_definition` already verifies this.
https://github.com/rubygems/rubygems/commit/c596f0af83
|
|
https://github.com/rubygems/rubygems/commit/0b7be7bb77
Co-authored-by: Jonathan Hefner <jonathan@hefner.pro>
|