GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing github.com — ci(fresh-install): the tumbleweed leg refreshes before it installs and stops when the refresh fails by NopeCharon · Pull Request #871 · mcpp-community/mcpp

Conversation

NopeCharon commented Oct 30, 2026

Copy link

Copy Markdown

Contributor

Summary

The Linux distro (tumbleweed) leg of ci-fresh-install ran zypper -n install ... alone. That install refreshes the repositories first, and when the refresh fails it keeps going on stale or empty metadata. The leg then went red with No provider of 'binutils' found, which names a package and not the repository that could not be read.

The leg's setup now runs zypper -n --gpg-auto-import-keys refresh as its own command and retries it once after 15 seconds. The install runs only after a refresh succeeds. If the refresh fails twice, the step ends with zypper's own refresh error and exit status. --gpg-auto-import-keys accepts a repository's new signing key, which -n alone rejects. A rolling image can run into such a key.

Closes #523.

Criteria

I ran the exact setup string under sh -e in opensuse/tumbleweed:latest (aarch64), the shell GitHub uses for a container step. I checked it against the value the YAML parses to.
- Failing refresh. I added a repository at an unreachable URL first. Both refreshes fail and the install never starts. The step exits 4, and its last line is "Some of the repositories have not been refreshed because of an error." Before this change, the install would have gone on to the No provider of ... errors.
- Healthy repositories. "All repositories have been refreshed." prints, then the install proceeds.
python3 .github/tools/check_workflow_assertions.py passes.
This workflow runs after a release, daily, and on dispatch, but not on pull requests. Its next scheduled run is the first run in CI.

Intersections

New rule or feature	Invariant it crosses	Test at the crossing
The refresh is a separate gate before the install	Every distro leg installs `findutils`, `binutils` and `file` before mcpp runs	The leg's `Install prerequisites` step itself: the install line is unchanged
The step's status is the refresh's	`Install xlings + mcpp` runs only after the prerequisites step succeeds	none needed: the step order is unchanged

Compatibility

This changes only the tumbleweed leg. Before, a refresh failure in any configured repository could slip through if the install still found its packages. Now that failure fails the leg, after one retry, and the error names the repository.

Checks before merging

bash .github/tools/check_docs_style.sh, check_docs_structure.sh and check_version_pins.sh pass.
python3 .github/tools/check_workflow_assertions.py passes (a step asserts what its name says).
No commit on the branch carries an attribution trailer:
git log origin/main..HEAD -i --grep='Co-Authored-By' prints nothing.
The squash merge is given an explicit subject and body, so GitHub does not
compose one from the branch's commits. Suggested subject: ci(fresh-install): the tumbleweed leg refreshes before it installs and stops when the refresh fails.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions


          ci(fresh-install): the tumbleweed leg refreshes before it installs an…

bf54baf

…d stops when the refresh fails

The tumbleweed leg ran `zypper -n install ...` alone. That install refreshes
the repositories itself, and when the refresh fails it continues on stale or
empty metadata, so the leg went red with

    Some of the repositories have not been refreshed because of an error.
    No provider of 'binutils' found.

The second line is the one a reader acts on, and it names a package rather
than the repository that could not be read.

The leg's setup now runs `zypper -n --gpg-auto-import-keys refresh` as its
own command, retries it once after 15 seconds, and installs only after it
succeeds. A refresh that fails twice ends the step with zypper's own refresh
error and status. --gpg-auto-import-keys accepts a repository's new signing
key, which `-n` alone rejects on a rolling image.

Measured in opensuse/tumbleweed:latest (aarch64) under `sh -e`, as a
container step runs: with a repository at an unreachable URL added, both
refreshes fail, the install never starts and the step exits 4 after
"Some of the repositories have not been refreshed"; without it the refresh
succeeds and the install proceeds.

Closes mcpp-community#523.

This branch has not been deployed

No deployments

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

ci(fresh-install): tumbleweed 腿在 zypper 刷新失败时继续安装,于是红在「找不到 binutils」而不是「刷新失败」

Uh oh!

There was an error while loading. Please reload this page.

1 participant

Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.