diff options
| author | David RodrÃguez <deivid.rodriguez@riseup.net> | 2024-01-12 14:53:40 +0100 |
|---|---|---|
| committer | Hiroshi SHIBATA <hsbt@ruby-lang.org> | 2024-01-19 11:28:11 +0900 |
| commit | db44088c2a92040879386aa5f268db4c858e4e5b (patch) | |
| tree | d7518e3cf9a9ea381f2c8b06ce859a4293c8c7d0 /spec | |
| parent | f1f5f22d22a149f20e019728b1ab35593d29d81a (diff) | |
[rubygems/rubygems] Fix activation conflicts when circularly requiring a gem
If a gem is required circular, and there are unresolved specs depending
on it, we may end up in an activation conflict.
The solution is to not try to activate unresolved gems when requiring a
default gem, regardless of it having already been activated or not.
https://github.com/rubygems/rubygems/commit/3b2b8f4e3e
Diffstat (limited to 'spec')
0 files changed, 0 insertions, 0 deletions