| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://github.com/rubygems/rubygems/commit/bb66253f2c
|
|
|
|
|
|
|
|
|
|
|
| |
Because bundler needs to support older versions of rubygems, we can't
actually rely on Gem::CIDetector (yet - in a year or so they might be
able to consolidate, if they don't change futher). So we're copying it
into the Bundler:: namespace, and enforcing that they stay completely in
sync with a test. No other tests are needed, since Gem::CIDetector is
already tested, and this is and will remain identical.
https://github.com/rubygems/rubygems/commit/abc67f0da1
|
|
|
|
|
|
|
|
|
|
| |
Generally the removed message is very similar, but often it needs to
specify that the feature has "been removed" instead of "will be
removed", or "been deprecated". And a few chunks of text needed more
substantial updates. And a number of them seemed to have been carefully
crafted to make sense in either context, so I left those alone.
https://github.com/rubygems/rubygems/commit/8d42cf9104
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/e41156e272
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We lock the checksum for each resolved spec under a new CHECKSUMS
section in the lockfile.
If the locked spec does not resolve for the local platform, we preserve
the locked checksum, similar to how we preserve specs.
Checksum locking only makes sense on install. The compact index
information is only available then.
https://github.com/rubygems/rubygems/commit/bde37ca6bf
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/63b422b71a
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/34d096e38a
|
| |
|
| |
|
|
|
|
| |
This reverts commit 69580f8b72f41c58cae57d1ada4db909922b3891.
|
|
|
|
|
|
| |
to Bundler.
https://github.com/rubygems/rubygems/commit/d768be0c65
|
|
|
|
|
|
|
|
| |
Recent bugs fixed made me realize we were relying on state too much
here. We only need to keep incomplete specs to be able to expire them
and retry resolution without them locked. If we use a separate class, we
can do that more transparently and handle them just like we handle
"missing specs".
|
|
|
|
|
| |
Just like gem sources, a "style-only" change, like adding a trailing
slash, should not expire them.
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/4909d071d2
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/5c5d0c5350
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/23880353c1
|
|
|
|
| |
from https://github.com/rubygems/rubygems/commit/0635c1423db5d7c461d53bf0c3329bca75de7609
|
|
|
|
| |
from https://github.com/rubygems/rubygems/commit/72fd3dd2096af16d797ad0cd8e0d2a8869e240b3
|
| |
|
|
|
|
|
|
| |
response. - adds Bundler#safe_load_marshal and Bundler::SAFE_MARSHAL_CLASSES listing safe classes to deserialize
https://github.com/rubygems/rubygems/commit/e947c608cc
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/bc84b2d262
|
|
|
|
|
|
| |
https://github.com/rubygems/rubygems/pull/5960
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/6214d00b2315ed37c76b1fbc1c72f61f92ba5a65
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/16c3535413afebcdbab7582c6017c27b5da8a8dc
|
|
|
|
|
|
|
|
| |
Also typo is fixed.
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
https://github.com/rubygems/rubygems/commit/9c1ea52ddf
|
|
|
|
| |
Pick from https://github.com/rubygems/rubygems/commit/6b3a5a9ab0453463381a8164efb6298ea9eb776f
|
|
|
|
|
|
|
|
| |
It's explicitly loaded when monkeypatching RubyGems, which we do very
early. So neither autoloading it, nor explicitly loading it anywhere
else is necessary.
https://github.com/rubygems/rubygems/commit/fbc7a57161
|
|
|
|
| |
Merge from https://github.com/rubygems/rubygems/commit/2af2520b4a7ab1c6eb1fdc3d2ef4d8c062d96ad7
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If BUNDLE_PATH is configured to a symlinked path, installing gems with
symlinks would crash with an error like this:
```
Gem::Package::SymlinkError: installing symlink 'man/man0/README.markdown' pointing to parent path /usr/home/stevewi/srv/mail/lib/tools/.vendor/ruby/3.1.0/gems/binman-5.1.0/README.markdown of /srv/mail/lib/tools/.vendor/ruby/3.1.0/gems/binman-5.1.0 is not allowed
```
This commit fixes the problem by changing the bundle path to be the
realpath of the configured value, right after we're sure the path has
been created.
https://github.com/rubygems/rubygems/commit/3cd3dd142a
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/800a973e00
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is hiding a real bundler issue as a "network error". It's more
helpful to get a proper bug report, with stack trace and so on.
So stop re-raising errors when evaluating unmarshaled responses as
network errors, and only raise Marshal errors when the Marshal format is
invalid, not whenever marshalled gemspecs can't be loaded because that
may hide actual client errors, like missing `YAML` constants.
https://github.com/rubygems/rubygems/commit/05ea907e1c
|
| |
|
| |
|
|
|
|
|
|
|
| |
This allows `Source::Git` to no longer load the `digest` gem as it is causing
issues on Ruby 3.1.
https://github.com/rubygems/rubygems/pull/4989/commits/c19a9f2ff7
|
|
|
|
|
|
| |
Same reason as in the previous commit.
https://github.com/rubygems/rubygems/commit/f00a6c8516
|
|
|
|
|
|
| |
versions
https://github.com/rubygems/rubygems/commit/9c88db949d
|
|
|
|
|
|
| |
Since it clears both home and path.
https://github.com/rubygems/rubygems/commit/fadf5e03ea
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/a296052670
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/4188ebd568
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/986e889a79
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/a7023c6c21
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
relative file
Ruby 1.9.2 removed "." from LOAD_PATH for robustness and security reasons.
This code was introduced by https://github.com/rubygems/rubygems/commit/56fc830e19a573a5905eba7f4714ad1f21ed1927 commit
to helping users understand the issue and had a guard condition to include the message for `RUBY_VERSION >= "1.9"`.
However, the guard condition was removed as part of the "Ruby version leftover" cleanup by
https://github.com/rubygems/rubygems/commit/8c9cf76e419fbd8ba83144d701b24ca388813b14
Ruby 1.9 development was ended a long time ago and this message is not useful anymore.
https://github.com/rubygems/rubygems/commit/a23609b15a
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|