diff options
author | Bundlerbot <bot@bundler.io> | 2019-11-21 11:25:57 +0000 |
---|---|---|
committer | Bundlerbot <bot@bundler.io> | 2019-11-21 11:25:57 +0000 |
commit | a11c104c5b6222c018248b585cca2a4f340a9a71 (patch) | |
tree | 0ea1c3ba26a851bacfa8862450941479a41a8862 /man/bundle-update.1 | |
parent | 97886b1f38b8b8944adf18d636a1b97e410e2e5a (diff) | |
parent | 320ac535f15169d19e1d393095eed586d6b1f8b5 (diff) | |
download | bundler-a11c104c5b6222c018248b585cca2a4f340a9a71.tar.gz |
Merge #7442
7442: Fix `bundle exec`'ing to rubygems being silent r=deivid-rodriguez a=deivid-rodriguez
### What was the end-user problem that led to this PR?
The problem was that #7401 caused a regression where `bundle exec`'ing to rubygems would silence rubygems output.
### What was your diagnosis of the problem?
My diagnosis was that the removal of:
* Code where `Bundler::RGProxy` would be only set conditionally on `Bundler.ui =` not being passed `nil`.
* Code setting `Bundler.ui` to `nil` right before shelling during `bundle exec`.
caused rubygems UI to be silent during `bundle exec gem`.
### What is your fix for the problem, implemented in this PR?
My fix is to explictly "unsilence" rubygems UI before `bundle exec` calls.
### Why did you choose this fix out of the possible options?
I chose this fix because it's more explicit than the previous one.
Fixes #7441.
Co-authored-by: David RodrÃguez <deivid.rodriguez@riseup.net>
Diffstat (limited to 'man/bundle-update.1')
0 files changed, 0 insertions, 0 deletions