From: Greg.mpls@... Date: 2017-08-28T16:02:22+00:00 Subject: [ruby-core:82489] [Ruby trunk Bug#13843] [PATCH] RubyGems 2.6.13 - Align lib/rubygems/resolver.rb with rubygems/rubygems Issue #13843 has been updated by MSP-Greg (Greg L). At rubygems/rubygems, the patch for resolver.rb was accepted first, then the patch to extend appveyor testing to include trunk was accepted. [Appveyor results](https://ci.appveyor.com/project/segiddins/rubygems/build/634) and [Travis results](https://travis-ci.org/rubygems/rubygems/builds/2692249220). Sorry if I'm being a PITA, but since I'm testing a lot these days, the idea that a trunk build from last week (gem -v 2.6.12) which had a `gem update --system` done would have different code than a current build (gem -v 2.6.13) is not another vector/dimension I want present in things to keep track of... ---------------------------------------- Bug #13843: [PATCH] RubyGems 2.6.13 - Align lib/rubygems/resolver.rb with rubygems/rubygems https://bugs.ruby-lang.org/issues/13843#change-66300 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.5.0dev (2017-08-25 trunk 59654) [x64-mingw32] * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- Currently, the file `lib/rubygems/resolver.rb` differs between ruby/ruby and rubygems/rubygems in the `search_for` method. Attached patch aligns them and adds the test for it, which is also missing from ruby/ruby. Tested against MinGW trunk builds and Travis. See [rubygem/rubygems PR 1993](https://github.com/rubygems/rubygems/pull/1993) ---Files-------------------------------- gem_resolver.patch (2.46 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: