Repository navigation
chore(deps): update quay.io/hummingbird-community/bootc-os:latest docker digest to 51fa61e - #28
mergeraptor[bot] wants to merge 15 commits into
Conversation
1eb5e35 to
5cf3bed
Compare
5cf3bed to
7dc1ab4
Compare
🛑 Fix loop escalated — human attention neededThis PR has failed CI on 1 distinct fix attempts (new commits, still red). The hive has stopped dispatching further automated fixes for it. Failing checks: build_kernel / Check all testing builds successful, build_kernel / image (gaming, utah-kernel, testing, x86_64), build_kernel / image (nvidia, utah-kernel, testing, x86_64), build_kernel / image (nvidia-gaming, utah-kernel, testing, x86_64), build_main / Check all testing builds successful, build_main / image (main, utah, testing, x86_64) Raw failure evidence (from check-run annotations): Remove the |
…ker digest to 51fa61e
7dc1ab4 to
e18e87c
Compare
🛑 Fix loop escalated — human attention neededThis PR has failed CI on 1 distinct fix attempts (new commits, still red). The hive has stopped dispatching further automated fixes for it. Failing checks: build_kernel / Check all testing builds successful, build_kernel / image (gaming, utah-kernel, testing, x86_64), build_kernel / image (nvidia, utah-kernel, testing, x86_64), build_kernel / image (nvidia-gaming, utah-kernel, testing, x86_64), build_main / Check all testing builds successful, build_main / image (main, utah, testing, x86_64) Raw failure evidence (from check-run annotations): Remove the |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
🛑 Fix loop escalated — human attention neededThis PR has failed CI on 1 distinct fix attempts (new commits, still red). The hive has stopped dispatching further automated fixes for it. Failing checks: build_kernel / Check all testing builds successful, build_kernel / image (gaming, utah-kernel, testing, x86_64), build_kernel / image (nvidia, utah-kernel, testing, x86_64), build_kernel / image (nvidia-gaming, utah-kernel, testing, x86_64), build_main / Check all testing builds successful, build_main / image (main, utah, testing, x86_64) Raw failure evidence (from check-run annotations): Remove the |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
The previous package image omitted the contract RPMs required by the image resolver, causing CI to fail with No match for argument errors. Pin the published repository digest that contains the complete dependency set. Assisted-by: Claude Sonnet 5 via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: GitHub Copilot <223556219+Copilot@users.noreply.github.com>
🛑 Fix loop escalated — human attention neededThis PR has failed CI on 1 distinct fix attempts (new commits, still red). The hive has stopped dispatching further automated fixes for it. Failing checks: build_main / image (main, utah, testing, x86_64) Raw failure evidence (from check-run annotations): Remove the |
Signed-off-by: GitHub Copilot <223556219+Copilot@users.noreply.github.com>
🛑 Fix loop escalated — human attention neededThis PR has failed CI on 1 distinct fix attempts (new commits, still red). The hive has stopped dispatching further automated fixes for it. Failing checks: build_kernel / Check all testing builds successful, build_kernel / image (gaming, utah-kernel, testing, x86_64), build_kernel / image (nvidia, utah-kernel, testing, x86_64), build_kernel / image (nvidia-gaming, utah-kernel, testing, x86_64), build_main / Check all testing builds successful, build_main / image (main, utah, testing, x86_64) Raw failure evidence (from check-run annotations): Remove the |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Copilot <223556219+Copilot@users.noreply.github.com>
🛑 Fix loop escalated — human attention neededThis PR has failed CI on 1 distinct fix attempts (new commits, still red). The hive has stopped dispatching further automated fixes for it. Failing checks: build_main / Check all testing builds successful, build_main / image (main, utah, testing, x86_64) Raw failure evidence (from check-run annotations): Remove the |
Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
🛑 Fix loop escalated — human attention neededThis PR has failed CI on 1 distinct fix attempts (new commits, still red). The hive has stopped dispatching further automated fixes for it. Failing checks: build_kernel / Check all testing builds successful, build_kernel / image (gaming, utah-kernel, testing, x86_64), build_kernel / image (nvidia, utah-kernel, testing, x86_64), build_kernel / image (nvidia-gaming, utah-kernel, testing, x86_64), build_main / Check all testing builds successful, build_main / image (main, utah, testing, x86_64) Raw failure evidence (from check-run annotations): Remove the |
Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
🛑 Fix loop escalated — human attention neededThis PR has failed CI on 1 distinct fix attempts (new commits, still red). The hive has stopped dispatching further automated fixes for it. Failing checks: build_kernel / Check all testing builds successful, build_kernel / image (gaming, utah-kernel, testing, x86_64), build_kernel / image (nvidia, utah-kernel, testing, x86_64), build_kernel / image (nvidia-gaming, utah-kernel, testing, x86_64), build_main / Check all testing builds successful, build_main / image (main, utah, testing, x86_64) Raw failure evidence (from check-run annotations): Remove the |
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
🛑 Fix loop escalated — human attention neededThis PR has failed CI on 1 distinct fix attempts (new commits, still red). The hive has stopped dispatching further automated fixes for it. Failing checks: build_kernel / Check all testing builds successful, build_kernel / image (gaming, utah-kernel, testing, x86_64), build_kernel / image (nvidia, utah-kernel, testing, x86_64), build_kernel / image (nvidia-gaming, utah-kernel, testing, x86_64), build_main / Check all testing builds successful, build_main / image (main, utah, testing, x86_64) Raw failure evidence (from check-run annotations): Remove the |
fwupd and tailscale are absent from enabled repositories, so exclude them from the install transaction while retaining optional unit configuration. Assisted-by: Claude Sonnet 5 via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
The updated bootc base reports Fedora 43 while the package repository digest was built for Fedora 44, causing broad package resolution failures. Restore the matching base and package repository pins. Assisted-by: Claude Sonnet 5 via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
[scanner]
|
|
[scanner] build_main/build_kernel failures are not caused by this digest bump: scanner agent (ACMM L5 — hold-gated mode)🐝 Hive Agent: — hive: agent=scanner backend=copilot model=kimi-k3 copilot=1.0.78 |
hanthor
left a comment
There was a problem hiding this comment.
Clean diff, but it cannot be validated while main is red — and this is the riskiest of the three digest bumps
Unlike #29/#30/#36, this PR is properly scoped: 2 files (Containerfile, Containerfile.kernel), +3/-2, no stray packages/utah.toml hunk. Renovate has rebased it 13 times and it is still clean. Good.
But it bumps quay.io/hummingbird-community/bootc-os — the base image for the entire OS — in both the final and stage positions. That is the highest-blast-radius change of any open dependency PR, and it is the one that most needs a green build to confirm.
It cannot get one. main@636b48e fails Build Utah at Containerfile:81, scheduled run 34654001732:
install: cannot create regular file '/usr/local/libexec/utah-install-packages': No such file or directory
Error: building at STEP "RUN for pair in install-packages.py:utah-install-packages ..."
error: recipe `build-ghcr` failed with exit code 1
That failure is itself a base-image change, which makes this bump directly relevant
Worth connecting: /usr/local/libexec stopped existing because the Hummingbird base image changed. #56's description says so explicitly — "the current base image no longer ships /usr/local/libexec". So the c5539f9 → 51fa61e class of bump is precisely what broke the build in the first place.
Which means merging this one blind carries the same risk again: a new base digest can remove another directory, drop another package, or change another default, and Utah will find out at STEP 10 of a 20-minute build. Two consequences:
- #56 must land first (with its
${pair##:*}typo corrected — it currently moves the failure from exit 1 to exit 127). Until then there is no green baseline to compare against, so a red build on this PR tells you nothing about the digest. - After #56 lands, re-run this before merging. A digest bump whose last CI run predates the base-branch fix is not evidence of anything. Renovate's automerge label should stay off until that run is green.
Worth doing while it waits
Since a base-image bump has already broken the build once through a silently-removed path, this is a good argument for the kind of guard #56 should carry: a just check assertion that every utah-* name invoked by a later RUN is actually produced by the install loop. That turns "base image removed a directory" from a 20-minute image-build failure into a 20-second contract failure — and it would catch the next bump too.
Also confirm the stage and final digests are meant to move together. They do in this diff (both c5539f9 → 51fa61e), which is right, but Containerfile.kernel pins the base independently and AGENTS.md notes that edits to kernel-cache inputs force a ~45-minute cache rebuild. Worth knowing that cost is being paid when this merges.
Same reasoning applies to #27 (ghcr.io/ublue-os/brew) and #25 (ghcr.io/projectbluefin/common) — both are cleanly scoped 2-file digest bumps blocked on the same red base, though neither carries this one's blast radius.
No objection to the change itself. It just needs a real green run behind it, and that needs #56.
Generated by Claude Code
|
[scanner] CI root cause: the build failures are systemic, not from this PR. scanner agent (ACMM L5 — hold-gated mode)🐝 Hive Agent: — hive: agent=scanner backend=copilot model=kimi-k3 copilot=1.0.78 |
[scanner] build_main/build_kernel failures are upstream of this PR: the image build's dnf transaction fails on 31 broken deps in the Hummingbird (utah-packages) repo — e.g.
|
|
This PR contains the following updates:
c5539f9→51fa61ec5539f9→51fa61eConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate CLI.