`bundle lock --update` and `bundle update --all` fail with `GemNotFound` when a locked top-level gem version was yanked and only older versions remain

オープン
#10,079 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
55/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
ruby
領域
backend, devtools

調査の方向性

Start with Definition#resolution_base, additional_base_requirements_to_prevent_downgrades, and Resolver#setup_solver in the Bundler resolver code. Trace how base_requirements filters candidates before find_names_to_relax and @base.unlock_names run. Reproduce with the supplied yanked-gem steps; done when bundle lock --update and bundle update --all resolve aa (1.0.0) as the named update commands do.

索引モデルが issue の本文から書いたものです。

説明

Describe the problem as clearly as you can

When a top-level gem in Gemfile is locked to 2.0.0 and 2.0.0 is later yanked from the gem source while 1.0.0 remains available, both bundle lock --update and bundle update --all fail with exit code 7 (Bundler::GemNotFound) and print a contradictory error claiming no gem matching aa was found while listing aa-1.0.0 in the source. Naming the gem explicitly (bundle update aa or bundle lock --update aa) or locking without a prior Gemfile.lock succeeds and resolves aa (1.0.0).

In Definition#resolution_base, additional_base_requirements_to_prevent_downgrades sets base_requirements["aa"] to >= 2.0.0. During Resolver#setup_solver, prepare_dependencies checks versions_for(dep_package, dep_range) (which filters candidates through base_requirements["aa"]), relaxes ignores_prereleases? and prefer_local? when empty, but does not relax base_requirements["aa"], so it calls raise_not_found! before solve_versions can run find_names_to_relax and @base.unlock_names.

Did you try upgrading rubygems & bundler?

Yes. Reproduced on RubyGems / Bundler 4.1.0 (Ruby 4.0.9) and on ruby/rubygems master (5879ffe34b, 4.2.0.dev).

Post steps to reproduce the problem
mkdir repro-yank-update && cd repro-yank-update
mkdir -p repo/gems repo/quick/Marshal.4.8 app

ruby - << 'RUBY'
require "rubygems/package"
require "zlib"

specs = ["1.0.0", "2.0.0"].map do |v|
  Gem::Specification.new do |s|
    s.name = "aa"
    s.version = v
    s.summary = "aa"
    s.authors = ["test"]
  end
end
specs.each do |s|
  gem_file = Gem::Package.build(s, true)
  File.rename(gem_file, "repo/gems/" + gem_file)
  File.binwrite("repo/quick/Marshal.4.8/" + s.original_name + ".gemspec.rz",
    Zlib::Deflate.deflate(Marshal.dump(s)))
end
File.binwrite("repo/specs.4.8.gz",
  Zlib.gzip(Marshal.dump(specs.map { |s| [s.name, s.version, "ruby"] })))
File.binwrite("repo/prerelease_specs.4.8.gz", Zlib.gzip(Marshal.dump([])))
RUBY

cat > app/Gemfile <<GEMFILE
source "file://$PWD/repo"
gem "aa"
GEMFILE

(cd app && BUNDLE_PATH=vendor/bundle bundle lock)

# Yank 2.0.0 from the source, leaving 1.0.0 available
ruby - << 'RUBY'
require "zlib"
require "fileutils"

FileUtils.rm_f(["repo/gems/aa-2.0.0.gem", "repo/quick/Marshal.4.8/aa-2.0.0.gemspec.rz"])
File.binwrite("repo/specs.4.8.gz",
  Zlib.gzip(Marshal.dump([["aa", Gem::Version.new("1.0.0"), "ruby"]])))
RUBY

cd app
BUNDLE_PATH=vendor/bundle bundle lock --update
BUNDLE_PATH=vendor/bundle bundle update --all
BUNDLE_PATH=vendor/bundle bundle update aa
Which command did you run?

bundle lock --update and bundle update --all

What were you expecting to happen?

Both bundle lock --update and bundle update --all should resolve all dependencies against the versions currently available in the source (https://bundler.io/man/bundle-update.1.html) and update Gemfile.lock to aa (1.0.0), matching bundle update aa and bundle lock --update aa.

What happened instead?
$ BUNDLE_PATH=vendor/bundle bundle lock --update
Writing lockfile to /tmp/repro-yank-update/app/Gemfile.lock
Fetching source index from file:///tmp/repro-yank-update/repo/
Could not find gems matching 'aa' valid for all resolution platforms (ruby,
x86_64-linux) in rubygems repository
file:///tmp/repro-yank-update/repo/
or installed locally.

The source contains the following gems matching 'aa':
  * aa-1.0.0

$ BUNDLE_PATH=vendor/bundle bundle update --all
Fetching source index from file:///tmp/repro-yank-update/repo/
Could not find gems matching 'aa' valid for all resolution platforms (ruby,
x86_64-linux) in rubygems repository
file:///tmp/repro-yank-update/repo/
or installed locally.

The source contains the following gems matching 'aa':
  * aa-1.0.0

$ BUNDLE_PATH=vendor/bundle bundle update aa
Fetching source index from file:///tmp/repro-yank-update/repo/
Resolving dependencies...
Resolving dependencies...
Fetching aa 1.0.0 (was 2.0.0)
Installing aa 1.0.0 (was 2.0.0)
Note: aa version regressed from 2.0.0 to 1.0.0
Bundle updated!
If not included with the output of your command, run bundle env and paste the output below
## Environment

```
Bundler       4.1.0
  Platforms   ruby, x86_64-linux
Ruby          4.0.9p0 (2026-10-23 revision 3e93b23afcec3433f6aecc34b5d832799d754238) [x86_64-linux]
  Full Path   /opt/ruby-4.0.9/bin/ruby
  Config Dir  /opt/ruby-4.0.9/etc
RubyGems      4.1.0
  Gem Home    /opt/ruby-4.0.9/lib/ruby/gems/4.0.0
  Gem Path    /home/user/.local/share/gem/ruby/4.0.0:/opt/ruby-4.0.9/lib/ruby/gems/4.0.0
  User Home   /home/user
  User Path   /home/user/.local/share/gem/ruby/4.0.0
  Bin Dir     /opt/ruby-4.0.9/bin
Git           2.39.5
```

## Bundler Build Metadata

```
Timestamp  2026-11-16
Git SHA    9af9267
```

## Bundler settings

```
path
  Set via BUNDLE_PATH: "/tmp/repro-yank-update/app/vendor/bundle"
```

## Gemfile

### Gemfile

```ruby
source "file:///tmp/repro-yank-update/repo"
gem "aa"
```

### Gemfile.lock

```
GEM
  remote: file:///tmp/repro-yank-update/repo/
  specs:
    aa (2.0.0)

PLATFORMS
  ruby
  x86_64-linux

DEPENDENCIES
  aa

CHECKSUMS
  aa (2.0.0)

BUNDLED WITH
  4.1.0
```

Credit: https://ucsbplse.github.io/

主要言語
Ruby
スター
4k
フォーク
2k
平均マージ
1日 20時間
マージ済み PR(30日)
75

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

ruby/rubygems のほかの issue

ruby/rubygems の issue をすべて見る

似ている issue

Ruby の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。