<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ruby.git/spec/bundler/commands/exec_spec.rb, branch v3_4_9</title>
<subtitle>The Ruby Programming Language</subtitle>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/'/>
<entry>
<title>Merge RubyGems-3.6.6 and Bundler-2.6.6</title>
<updated>2025-04-09T00:54:29+00:00</updated>
<author>
<name>Hiroshi SHIBATA</name>
<email>hsbt@ruby-lang.org</email>
</author>
<published>2025-04-09T00:19:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=db2bf9f078c21b9e0234a736214ed74642d9f795'/>
<id>db2bf9f078c21b9e0234a736214ed74642d9f795</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge RubyGems-3.6.3 and Bundler-2.6.3</title>
<updated>2025-02-21T00:50:20+00:00</updated>
<author>
<name>Hiroshi SHIBATA</name>
<email>hsbt@ruby-lang.org</email>
</author>
<published>2025-02-21T00:27:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=19c69f382baa13cac3bf36b861067bdc424e1be1'/>
<id>19c69f382baa13cac3bf36b861067bdc424e1be1</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Enable pending exec spec</title>
<updated>2024-11-29T15:29:33+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>deivid.rodriguez@riseup.net</email>
</author>
<published>2024-11-28T18:48:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=73c4023c2df59c996f948bad4715349a167da254'/>
<id>73c4023c2df59c996f948bad4715349a167da254</id>
<content type='text'>
This is how Ruby works, and it's not going to change. So let's run the
test since it makes no sense to keep it pending.

https://github.com/rubygems/rubygems/commit/5f78d3c737
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This is how Ruby works, and it's not going to change. So let's run the
test since it makes no sense to keep it pending.

https://github.com/rubygems/rubygems/commit/5f78d3c737
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Improve heredoc indentation in exec specs</title>
<updated>2024-11-29T15:29:32+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>deivid.rodriguez@riseup.net</email>
</author>
<published>2024-11-28T18:47:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=d2e5994161795272d2cb207044156e8f0c40a95f'/>
<id>d2e5994161795272d2cb207044156e8f0c40a95f</id>
<content type='text'>
https://github.com/rubygems/rubygems/commit/abb658757f
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://github.com/rubygems/rubygems/commit/abb658757f
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Unify specs testing Bundler.setup failing behavior</title>
<updated>2024-11-29T15:29:32+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>deivid.rodriguez@riseup.net</email>
</author>
<published>2024-11-28T21:32:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=8b7516438100ff379e92ebc2b524cb9c16f3392c'/>
<id>8b7516438100ff379e92ebc2b524cb9c16f3392c</id>
<content type='text'>
They had slightly different behavior in Bundler 2 and Bundler 3 because
Bundler 3 will auto-clean after `bundle install`, so one of them system
installed gems won't be present when `Bundler.setup` fails.

We can unify the specs by moving installing system gems to _after_
`bundle install`, so the behavior in both cases is the same. Also, only
this spec actually needs these gems installed, so we can move that from
the `before` block to the body of the spec.

https://github.com/rubygems/rubygems/commit/b7251ec9c6
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
They had slightly different behavior in Bundler 2 and Bundler 3 because
Bundler 3 will auto-clean after `bundle install`, so one of them system
installed gems won't be present when `Bundler.setup` fails.

We can unify the specs by moving installing system gems to _after_
`bundle install`, so the behavior in both cases is the same. Also, only
this spec actually needs these gems installed, so we can move that from
the `before` block to the body of the spec.

https://github.com/rubygems/rubygems/commit/b7251ec9c6
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] move system_gems let commands</title>
<updated>2024-11-21T10:29:32+00:00</updated>
<author>
<name>sodacris</name>
<email>wjxa20152015@gmail.com</email>
</author>
<published>2024-11-20T23:14:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=42b0d4641699fb8effa3db46d6673a481f557ef1'/>
<id>42b0d4641699fb8effa3db46d6673a481f557ef1</id>
<content type='text'>
https://github.com/rubygems/rubygems/commit/1fc1e74f4d
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://github.com/rubygems/rubygems/commit/1fc1e74f4d
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Fix running `bundler` (with a final `r`) in a `bundle exec` context</title>
<updated>2024-10-23T08:52:46+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>deivid.rodriguez@riseup.net</email>
</author>
<published>2024-10-21T10:07:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=b843d4ee148c70a77b992291e226d23dc981368b'/>
<id>b843d4ee148c70a77b992291e226d23dc981368b</id>
<content type='text'>
https://github.com/rubygems/rubygems/commit/ad95a1dfaa
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://github.com/rubygems/rubygems/commit/ad95a1dfaa
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Remove outdated conditionals from tests</title>
<updated>2024-10-04T20:01:51+00:00</updated>
<author>
<name>Samuel Giddins</name>
<email>segiddins@segiddins.me</email>
</author>
<published>2024-10-02T16:19:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=db6e6155d673931d1ae6b962664684c4fe4937e6'/>
<id>db6e6155d673931d1ae6b962664684c4fe4937e6</id>
<content type='text'>
Signed-off-by: Samuel Giddins &lt;segiddins@segiddins.me&gt;

https://github.com/rubygems/rubygems/commit/06eec6d855
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Signed-off-by: Samuel Giddins &lt;segiddins@segiddins.me&gt;

https://github.com/rubygems/rubygems/commit/06eec6d855
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix test failure of e7610582ad8fd05655221b183257ed358c903ac8</title>
<updated>2024-07-24T05:04:13+00:00</updated>
<author>
<name>Nobuyoshi Nakada</name>
<email>nobu@ruby-lang.org</email>
</author>
<published>2024-07-24T05:04:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=f2f9d6ce49aaee6b6414c8442082166cf733ab00'/>
<id>f2f9d6ce49aaee6b6414c8442082166cf733ab00</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[rubygems/rubygems] Fix `bundle exec gem uninstall`</title>
<updated>2024-07-23T19:43:26+00:00</updated>
<author>
<name>David Rodríguez</name>
<email>deivid.rodriguez@riseup.net</email>
</author>
<published>2024-07-23T17:22:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=e7610582ad8fd05655221b183257ed358c903ac8'/>
<id>e7610582ad8fd05655221b183257ed358c903ac8</id>
<content type='text'>
* `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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* `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
</pre>
</div>
</content>
</entry>
</feed>
