ruby.git/lib/bundler/endpoint_specification.rb, branch v3_2_11 The Ruby Programming Language Merge RubyGems-3.4.10 and Bundler-2.4.10 (#7479) 2023-03-28T11:36:47+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2023-03-28T11:36:47+00:00 c3c461c4ff1b998ac49ed1a3ad411d2f0a9123b8 * Merge RubyGems-3.4.7 and Bundler-2.4.7 * Merge RubyGems-3.4.8 and Bundler-2.4.8 * Skip failing test on MSWin * Merge RubyGems-3.4.9 and Bundler-2.4.9 * Merge RubyGems-3.4.10 and Bundler-2.4.10 --------- Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org> 
* Merge RubyGems-3.4.7 and Bundler-2.4.7

* Merge RubyGems-3.4.8 and Bundler-2.4.8

* Skip failing test on MSWin

* Merge RubyGems-3.4.9 and Bundler-2.4.9

* Merge RubyGems-3.4.10 and Bundler-2.4.10

---------

Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
 Merge RubyGems/Bundler master 2022-10-18T07:33:15+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2022-10-18T06:24:42+00:00 f5df47d1f3ec403d057f823375f1dfeea711caa6 https://github.com/rubygems/rubygems/commit/6214d00b2315ed37c76b1fbc1c72f61f92ba5a65 
  https://github.com/rubygems/rubygems/commit/6214d00b2315ed37c76b1fbc1c72f61f92ba5a65
Resync Bundler & RubyGems 2022-09-08T02:25:03+00:00 David Rodríguez deivid.rodriguez@riseup.net 2022-09-07T05:13:04+00:00 24fd2f73d0835eea534225a6381551d591764002 






Attempt to fix test-bundler
2022-09-05T04:45:13+00:00

Takashi Kokubun
takashikkbn@gmail.com

2022-09-05T04:44:52+00:00

277498e2a2b62b564e3d39ca54aa15b6e8a2c41a

f7cf641469161c3770b58f79e08e312512212aa8 broke spec/bundler/install/gems/resolving_spec.rb:356.
This line seems to impact that test, so I slightly modified the
implementation for that spec's case.





f7cf641469161c3770b58f79e08e312512212aa8 broke spec/bundler/install/gems/resolving_spec.rb:356.
This line seems to impact that test, so I slightly modified the
implementation for that spec's case.







[rubygems/rubygems] Fix resolution hanging on musl platforms
2022-09-05T02:43:14+00:00

David Rodríguez
deivid.rodriguez@riseup.net

2022-05-09T08:40:23+00:00

f7cf641469161c3770b58f79e08e312512212aa8

After recent musl support was added, Bundler started hanging in musl
platforms. I identified the issue where valid candidates were being
filtered out because their platform was specified as a string, and thus
`Gem::Platform.match_spec?` which under the hood ends up calling
`Gem::Platform#===` would return `nil`, because it does not support
comparing platforms to strings.

In particular, `Bundler::EndpointSpecification`'s platform coming from
the API was not instantiated as a `Gem::Platform`, hence the issue.

Also, this spec surfaced another issue where a bug corrected in
`Gem::Platform#match_platforms` had not been yet backported to Bundler.
So this commit also backports that to get the spec green across RubyGems
versions.

Finally, the fix in `Bundler::EndpointSpecification` made a realworld
spec start failing. This spec was faking out `rails-4.2.7.1` requirement
on Bundler in the `Gemfile.lock` file to be `>= 1.17, < 3` when the real
requirement is `>= 1.17, < 2`. Due to the bug in
`Bundler::EndpointSpecification`, the real requirement provided by the
compact index API (recorded with VCR) was being ignored, and the
`Gemfile.lock` fake requirement was being used, which made the spec
pass. This is all expected, and to fix the issue I changed the spec to
be really realworld and don't fake any Bundler requirements.

https://github.com/rubygems/rubygems/commit/faf4ef46bc





After recent musl support was added, Bundler started hanging in musl
platforms. I identified the issue where valid candidates were being
filtered out because their platform was specified as a string, and thus
`Gem::Platform.match_spec?` which under the hood ends up calling
`Gem::Platform#===` would return `nil`, because it does not support
comparing platforms to strings.

In particular, `Bundler::EndpointSpecification`'s platform coming from
the API was not instantiated as a `Gem::Platform`, hence the issue.

Also, this spec surfaced another issue where a bug corrected in
`Gem::Platform#match_platforms` had not been yet backported to Bundler.
So this commit also backports that to get the spec green across RubyGems
versions.

Finally, the fix in `Bundler::EndpointSpecification` made a realworld
spec start failing. This spec was faking out `rails-4.2.7.1` requirement
on Bundler in the `Gemfile.lock` file to be `>= 1.17, < 3` when the real
requirement is `>= 1.17, < 2`. Due to the bug in
`Bundler::EndpointSpecification`, the real requirement provided by the
compact index API (recorded with VCR) was being ignored, and the
`Gemfile.lock` fake requirement was being used, which made the spec
pass. This is all expected, and to fix the issue I changed the spec to
be really realworld and don't fake any Bundler requirements.

https://github.com/rubygems/rubygems/commit/faf4ef46bc







Merge rubygems/bundler HEAD
2022-08-23T01:45:57+00:00

Hiroshi SHIBATA
hsbt@ruby-lang.org

2022-08-22T02:52:51+00:00

f69244cee8c01d82e94d38032c82be684f37808a

  Pick from https://github.com/rubygems/rubygems/commit/6b3a5a9ab0453463381a8164efb6298ea9eb776f





  Pick from https://github.com/rubygems/rubygems/commit/6b3a5a9ab0453463381a8164efb6298ea9eb776f







[rubygems/rubygems] Remove unnecessary mixin inclusion
2022-08-23T01:45:57+00:00

David Rodríguez
deivid.rodriguez@riseup.net

2022-08-08T20:03:55+00:00

29c443fedc0d3692cb52241318abb0de619ae178

It's already included by the parent.

https://github.com/rubygems/rubygems/commit/3ffe389c44





It's already included by the parent.

https://github.com/rubygems/rubygems/commit/3ffe389c44







[rubygems/rubygems] Fix missing required rubygems version when using old APIs
2022-04-28T06:44:02+00:00

David Rodríguez
deivid.rodriguez@riseup.net

2022-04-26T12:53:55+00:00

5250210aa9f632a415e90deaac424ff69c37fb3e

A while ago, we fixed resolution when using old dependency endpoints to
also consider metadata dependencies, by requesting the full gemspec from
the marsahaled index, which includes this information as opposed to
these old APIs. This has made resolution slower, but correct, but also
introduced the issue that some old marshaled gemspecs don't include the
`required_rubygems_version` field because they were created with a
RubyGems version that predates its addition.

Use a default value in this case.

https://github.com/rubygems/rubygems/commit/5dc94afcc0

Co-authored-by: Ilya Dudarenko <i.dudarenko@tinkoff.ru>





A while ago, we fixed resolution when using old dependency endpoints to
also consider metadata dependencies, by requesting the full gemspec from
the marsahaled index, which includes this information as opposed to
these old APIs. This has made resolution slower, but correct, but also
introduced the issue that some old marshaled gemspecs don't include the
`required_rubygems_version` field because they were created with a
RubyGems version that predates its addition.

Use a default value in this case.

https://github.com/rubygems/rubygems/commit/5dc94afcc0

Co-authored-by: Ilya Dudarenko <i.dudarenko@tinkoff.ru>







Merge rubygems/rubygems HEAD.
2022-01-19T06:01:44+00:00

Hiroshi SHIBATA
hsbt@ruby-lang.org

2022-01-19T04:28:23+00:00

d22511fd7595ef1819baa42851d598d95b8f4d00

  Picked at 12aeef6ba9a3be0022be9934c1a3e4c46a03ed3a





  Picked at 12aeef6ba9a3be0022be9934c1a3e4c46a03ed3a







[rubygems/rubygems] Remove `syck` traces from `bundler`
2021-08-31T10:06:14+00:00

David Rodríguez
deivid.rodriguez@riseup.net

2020-07-08T21:26:28+00:00

4bc87cb1fb9ecbd227720bd48836935996574166

Same reason as in the previous commit.

https://github.com/rubygems/rubygems/commit/f00a6c8516





Same reason as in the previous commit.

https://github.com/rubygems/rubygems/commit/f00a6c8516