Skip to content

chore(deps): update ghcr.io/projectbluefin/common docker digest to 0f58c6d - #25

Closed
mergeraptor[bot] wants to merge 10 commits into
mainfrom
renovate/ghcr.io-projectbluefin-common
Closed

mergeraptor[bot] wants to merge 10 commits into
mainfrom
renovate/ghcr.io-projectbluefin-common

Conversation

@mergeraptor

@mergeraptor mergeraptor Bot commented Aug 30, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
ghcr.io/projectbluefin/common stage digest fb943c8 → 0f58c6d

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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 this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@mergeraptor
mergeraptor Bot force-pushed the renovate/ghcr.io-projectbluefin-common branch from 1c7d834 to 045b99f Compare September 2, 2026 00:40
@mergeraptor mergeraptor Bot changed the title chore(deps): update ghcr.io/projectbluefin/common docker digest to 4cf1be9 chore(deps): update ghcr.io/projectbluefin/common docker digest to cbcf13f Sep 2, 2026
@mergeraptor mergeraptor Bot changed the title chore(deps): update ghcr.io/projectbluefin/common docker digest to cbcf13f chore(deps): update ghcr.io/projectbluefin/common docker digest to 71cf1d9 Sep 2, 2026
@mergeraptor
mergeraptor Bot force-pushed the renovate/ghcr.io-projectbluefin-common branch from 045b99f to 96a371a Compare September 2, 2026 06:32
@mergeraptor mergeraptor Bot changed the title chore(deps): update ghcr.io/projectbluefin/common docker digest to 71cf1d9 chore(deps): update ghcr.io/projectbluefin/common docker digest to a6e5369 Sep 2, 2026
@mergeraptor
mergeraptor Bot force-pushed the renovate/ghcr.io-projectbluefin-common branch 2 times, most recently from 4af6078 to c40176d Compare September 5, 2026 00:40
@mergeraptor mergeraptor Bot changed the title chore(deps): update ghcr.io/projectbluefin/common docker digest to a6e5369 chore(deps): update ghcr.io/projectbluefin/common docker digest to 6474619 Sep 5, 2026
@mergeraptor
mergeraptor Bot force-pushed the renovate/ghcr.io-projectbluefin-common branch from c40176d to c1fbfd1 Compare September 6, 2026 00:42
@hivecommons-hive

Copy link
Copy Markdown
Contributor

🛑 Fix loop escalated — human attention needed

This 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):

build_kernel / Check all testing builds successful: Process completed with exit code 1.
build_kernel / image (gaming, utah-kernel, testing, x86_64): Final attempt failed. Child_process exited with error code 1
build_kernel / image (gaming, utah-kernel, testing, x86_64): Attempt 2 failed. Reason: Child_process exited with error code 1
build_kernel / image (gaming, utah-kernel, testing, x86_64): Attempt 1 failed. Reason: Child_process exited with error code 1
build_kernel / image (gaming, utah-kernel, testing, x86_64): Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Remove the needs-human label after addressing the root cause to return the PR to the automated fix lane.

@mergeraptor mergeraptor Bot changed the title chore(deps): update ghcr.io/projectbluefin/common docker digest to 6474619 chore(deps): update ghcr.io/projectbluefin/common docker digest to 0f58c6d Sep 6, 2026
@mergeraptor
mergeraptor Bot force-pushed the renovate/ghcr.io-projectbluefin-common branch from c1fbfd1 to 6f484ca Compare September 6, 2026 03:20
@hivecommons-hive

Copy link
Copy Markdown
Contributor

🛑 Fix loop escalated — human attention needed

This 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):

build_kernel / Check all testing builds successful: Process completed with exit code 1.

Remove the needs-human label after addressing the root cause to return the PR to the automated fix lane.

Signed-off-by: GitHub Copilot <223556219+Copilot@users.noreply.github.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

🛑 Fix loop escalated — human attention needed

This 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):

build_kernel / Check all testing builds successful: Process completed with exit code 1.

Remove the needs-human label after addressing the root cause to return the PR to the automated fix lane.

@mergeraptor

mergeraptor Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate 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.

⚠️ Warning: custom changes will be lost.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Copilot <223556219+Copilot@users.noreply.github.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

🛑 Fix loop escalated — human attention needed

This 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):

build_main / Check all testing builds successful: Process completed with exit code 1.
build_main / image (main, utah, testing, x86_64): Final attempt failed. Child_process exited with error code 1
build_main / image (main, utah, testing, x86_64): Attempt 2 failed. Reason: Child_process exited with error code 1
build_main / image (main, utah, testing, x86_64): Attempt 1 failed. Reason: Child_process exited with error code 1
build_main / image (main, utah, testing, x86_64): Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Remove the needs-human label after addressing the root cause to return the PR to the automated fix lane.

Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

🛑 Fix loop escalated — human attention needed

This 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):

build_kernel / Check all testing builds successful: Process completed with exit code 1.
build_kernel / image (gaming, utah-kernel, testing, x86_64): Final attempt failed. Child_process exited with error code 1
build_kernel / image (gaming, utah-kernel, testing, x86_64): Attempt 2 failed. Reason: Child_process exited with error code 1
build_kernel / image (gaming, utah-kernel, testing, x86_64): Attempt 1 failed. Reason: Child_process exited with error code 1
build_kernel / image (gaming, utah-kernel, testing, x86_64): Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Remove the needs-human label after addressing the root cause to return the PR to the automated fix lane.

Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

🛑 Fix loop escalated — human attention needed

This 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):

build_kernel / Check all testing builds successful: Process completed with exit code 1.

Remove the needs-human label after addressing the root cause to return the PR to the automated fix lane.

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

🛑 Fix loop escalated — human attention needed

This 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):

build_kernel / Check all testing builds successful: Process completed with exit code 1.

Remove the needs-human label after addressing the root cause to return the PR to the automated fix lane.

sec-check[bot] and others added 4 commits September 9, 2026 12:38
Assisted-by: Claude 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>
Assisted-by: Claude 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>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

[scanner] Build Utah fails identically on main: the Containerfile script-install step breaks on missing /usr/local/libexec parent dirs — fix is pending review in utah#56. This PR goes green after utah#56 merges and CI reruns.

🐝 Hive Agent: scanner | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: unknown

— hive: agent=scanner backend=copilot model=kimi-k3

@hivecommons-hive

Copy link
Copy Markdown
Contributor

[scanner] build_main/build_kernel failures are not caused by this digest bump: utah-install-packages fails with "No match for argument" for many packages (adw-gtk3-theme, alsa-firmware, containerd, fzf, ...) because the Utah package factory does not ship them yet. Blocked on utah-packages#51 / utah-packages#70 (add the required recipes). Re-run after the factory PRs land.


scanner agent (ACMM L5 — hold-gated mode)

🐝 Hive Agent: scanner | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: unknown

— hive: agent=scanner backend=copilot model=kimi-k3 copilot=1.0.78

@hivecommons-hive

Copy link
Copy Markdown
Contributor

[scanner] CI root cause: the build failures are systemic, not from this PR. utah-install-packages cannot resolve packages from the utah-packages repo (e.g. nothing provides anaconda-webui / python3-dbus-next needed by anaconda-live, hwdata/i2c-tools/libXrandr/libdrm needed by ddcutil) because the utah-packages build pipeline is currently red: its pinned quay.io/packit/packit digest was pruned upstream and Hummingbird ruby3.3/3.4/4.0 default-gems conflict. Fixes are open at utah-packages#87 (packit repin), utah-packages#83 (ruby exclusion), and utah-packages#57 (anaconda-live exclusion). Once those land and the package repo republishes, re-run here — no change needed on this branch.


scanner agent (ACMM L5 — hold-gated mode)

🐝 Hive Agent: scanner | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: unknown

— hive: agent=scanner backend=copilot model=kimi-k3 copilot=1.0.78

@hivecommons-hive

Copy link
Copy Markdown
Contributor

[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. nothing provides anaconda-webui needed by anaconda-live, nothing provides hwdata needed by ddcutil. Root cause chain in utah-packages: dead SRPM lane (deleted packit image pin; fixes #85/#87), ruby default-gems conflict (#83), closure gaps (#57/#81/#89). Nothing to change here — re-run once the utah-packages fixes land and the repo republishes.

🐝 Hive Agent: scanner | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: unknown

— hive: agent=scanner backend=copilot model=kimi-k3 copilot=1.0.78

@hivecommons-hive

Copy link
Copy Markdown
Contributor

build_main / build_kernel is red here for reasons external to this PR's diff: Build Utah has been failing on the default branch main since 2026-09-11. Tracked as one repository incident in #109 — evidence, root causes and handling are there. Please do not re-run or repair this check on this PR; it is deferred until that incident closes or main is green.

🐝 Hive Agent: scanner | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-opus-5 copilot=1.0.78

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correctness review — requires human attention

  1. CI is still red at the head SHA (1983156). All four image builds fail at the "Build Image" step (build_main / image (main, utah, testing, x86_64) and the three build_kernel variants), so the new COMMON_IMAGE_SHA pin (Containerfile:11) is not yet buildable. The stacked workaround commits did not fix the root cause — the last three commits (8f1cd0f, 9636682, b7cace7, 1983156) are empty "retrigger" commits and the failure persists.

  2. Out-of-scope, unreviewed build-logic edits on an automerge-enabled "digest-only" PR. The PR body claims a pure digest bump (fb943c8 → 0f58c6d), but the head also contains hand edits pushed by bots: RUN mkdir -p /usr/local/libexec (Containerfile:71, Containerfile.kernel:28) and install -m → install -D -m (Containerfile:82). These never appear in the PR description, and the history flip-flops: install -D added (88d9645), reverted (e5297d0), re-added (334644e); BASE_IMAGE/PACKAGE_IMAGE_SHA bumped (334644e) then reverted (e0c0882). This is trial-and-error churn, not a diagnosed fix — and with automerge enabled, a green run would merge these side changes silently.

  3. Minor: with mkdir -p /usr/local/libexec at Containerfile:71, the -D flag at Containerfile:82 is redundant (harmless, but pick one).

Recommend a human determine why the 0f58c6d common digest breaks the build (build logs are not publicly readable) rather than letting further bot retries land collateral Containerfile changes.

— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.78

@hanthor hanthor closed this Sep 18, 2026
@mendezr mendezr mentioned this pull request Sep 21, 2026
19 of 29 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants