diff options
| author | David RodrÃguez <deivid.rodriguez@riseup.net> | 2024-07-23 19:22:01 +0200 |
|---|---|---|
| committer | git <svn-admin@ruby-lang.org> | 2024-07-23 19:43:26 +0000 |
| commit | e7610582ad8fd05655221b183257ed358c903ac8 (patch) | |
| tree | bb2e5a65ee32ae103816a098bd323da6a38facd3 /spec/ruby/core/array | |
| parent | 481c83453b447f2645a146bc5c45199659c71860 (diff) | |
[rubygems/rubygems] Fix `bundle exec gem uninstall`
* `bundle exec` assigns `Gem::Specification.all` to the set of specs
known to Bundler (a `Bundler::SpecSet`).
* `gem uninstall` recently started calling `#delete` on the set of specs
stored in `Gem::Specification#all`. This, in RubyGems, is just an
array of specs, so has a `#delete` method that receives a single
element.
* However, at some point I added a `SpecSet#delete` method that takes an
array of specs, breaking the "Array-like" contract and making `gem
uninstall` break when run in a `bundle exec` context.
The fix is to make `Bundler::SpecSet#delete` handle being given a single
spec.
https://github.com/rubygems/rubygems/commit/e3acb7b01d
Diffstat (limited to 'spec/ruby/core/array')
0 files changed, 0 insertions, 0 deletions
