David Rodríguez 466a760e18 [rubygems/rubygems] Fix yanked gems being unintentionally update when other gems are unlocked ... This is a regression from a change intended to raise errors when user puts a gem under an incorrect source in the Gemfile by mistake. To fix the issue, we revert the change that caused it and implement it in a different way that restores the resolver independency from real specifications. Now it deals only with names and versions and does not try to materialize anything into real specifications before resolving. https://github.com/rubygems/rubygems/commit/d2bf1b86eb		2022-08-06 15:41:46 +09:00
..
cli
compact_index_client
fetcher
installer
man
plugin
resolver
settings
source
templates
ui
vendor
.document
build_metadata.rb
bundler.gemspec
capistrano.rb
cli.rb
compact_index_client.rb
constants.rb
current_ruby.rb
definition.rb
dep_proxy.rb
dependency.rb
deployment.rb
deprecate.rb
digest.rb
dsl.rb
endpoint_specification.rb
env.rb
environment_preserver.rb
errors.rb
feature_flag.rb
fetcher.rb
friendly_errors.rb
gem_helper.rb
gem_helpers.rb
gem_tasks.rb
gem_version_promoter.rb
graph.rb
incomplete_specification.rb
index.rb
injector.rb
inline.rb
installer.rb
lazy_specification.rb
lockfile_generator.rb
lockfile_parser.rb
match_platform.rb
mirror.rb
plugin.rb
process_lock.rb
remote_specification.rb
resolver.rb
retry.rb
ruby_dsl.rb
ruby_version.rb
rubygems_ext.rb
rubygems_gem_installer.rb
rubygems_integration.rb
runtime.rb
self_manager.rb
settings.rb
setup.rb
shared_helpers.rb
similarity_detector.rb
source.rb
source_list.rb
source_map.rb
spec_set.rb
stub_specification.rb
ui.rb
uri_credentials_filter.rb
vendored_fileutils.rb
vendored_molinillo.rb
vendored_persistent.rb
vendored_thor.rb
vendored_tmpdir.rb
vendored_tsort.rb
vendored_uri.rb
version.rb
version_ranges.rb
vlad.rb
worker.rb
yaml_serializer.rb