Repository navigation
Conversation
chairlift (projectbluefin/chairlift) is a Go/GTK4/Libadwaita system management tool now owned by projectbluefin, released straight to GitHub Releases (its own release.yml, no external package repo). It doesn't fit the utah-packages factory, which rebuilds Fedora's own desktop stack from dist-git recipes for an independently-shipped project like this one — so it's installed the same way uupd already is here: curl the release asset, verify its digest, and install it, folded into the same RUN layer per this Containerfile's own layer-cost discipline. Installs the self-contained `projectbluefin-chairlift` RPM (not the `-system-integration` variant, which is for a user-scoped install alongside a separately-provided bootc-staging helper — Utah is a full system image, so the self-contained package is the right one). CHAIRLIFT_VERSION/CHAIRLIFT_SHA256 follow the same ARG pin + Renovate pattern as UUPD_VERSION/UUPD_SHA256 immediately above them.
|
The image build fails, but at STEP 10/32 — the |
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
|
Is Utah going to have a way for end users to layer an RPM? Chairlift isn't the only package where the "latest/best" RPMs are produced by the upstream. Some, for example, Xpra and NVIDIA, also provide repositories. |
Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
[scanner] CI root cause for the red image builds:
|
[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.
Digest and URL verified against the real release
Checked the pin rather than trusting it:
$ curl -sSL https://github.com/projectbluefin/chairlift/releases/download/v0.12.0/checksums.txt \
| grep 'projectbluefin-chairlift-0.12.0-1.x86_64.rpm'
56109c3b5955cc4c8f9a94e7e56dd6cf5f79f4ed2a4687847d13c4fdc802838b projectbluefin-chairlift-0.12.0-1.x86_64.rpmMatches CHAIRLIFT_SHA256 exactly. The URL template also renders correctly — ${CHAIRLIFT_VERSION#v} turns v0.12.0 into 0.12.0, producing projectbluefin-chairlift-0.12.0-1.x86_64.rpm, which is the asset name in checksums.txt. The sha256sum --check --strict runs before dnf install, matching the existing UUPD_SHA256 pattern directly above it.
The choice of projectbluefin-chairlift over -system-integration is right for a full system image, and the reasoning for bypassing the utah-packages factory (an independently-released Go project with its own published RPM, versus a factory that rebuilds Fedora dist-git recipes) holds up.
Note: this PR also carries the main-unblocking Containerfile fix
Not mentioned in the description, but the diff includes:
- install -m 0755 "/tmp/utah-scripts/${pair%%:*}" "/usr/local/libexec/${pair##*:}" || exit 1; \
+ install -D -m 0755 "/tmp/utah-scripts/${pair%%:*}" "/usr/local/libexec/${pair##*:}" || exit 1; \That is the fix for the failure currently reddening main and every PR branched from it — and notably it is correct here, where #56 (the PR dedicated to this fix) has a ${pair##*:} → ${pair##:*} typo that leaves the build failing with exit 127 instead of exit 1.
Worth deciding deliberately where that line lands. Two reasonable options:
- Let #56 carry it (it should — that is its whole subject), fix the typo there, and drop the hunk here. This PR then becomes a clean single-purpose chairlift addition.
- Or, if #56 stalls, this is a working copy of the fix and landing it here unblocks the repo sooner.
Either way it should not land twice. #46 carries a third copy of the same change.
On the test plan
Both boxes are still unchecked, and they can't be checked yet: main@636b48e fails Build Utah at Containerfile:81 before ever reaching the chairlift step (run 34654001732). This PR's own run 34528103385 shows contract passing and all four image jobs failing.
Interesting consequence though: with the install -D fix in this branch, the image build here should get past STEP 10 — so if it is still failing, it is failing somewhere new and the log is worth reading before assuming it is the same inherited breakage.
The honesty in the Verification section about not having run a full image build is appreciated. Once the base is green this should be a short PR to confirm — the digest is right, the shell is right, and it mirrors an existing proven pattern.
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 |
castrojo
left a comment
There was a problem hiding this comment.
Approved: chairlift release asset URL and sha256 checksum verified against upstream release v0.12.0; layer implementation matches existing uupd pattern.
[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.
|
|
|
Closing as stale: conflicts with the Generated by Claude Code |
Summary
Adds chairlift (Go/GTK4/Libadwaita system management tool, now owned by projectbluefin) to the Utah image, installed the same way
uupdalready is — curl the GitHub Release RPM, verify its digest, install with dnf5/dnf.Doesn't go through the
utah-packagesfactory: that rebuilds Fedora's own desktop stack from dist-git recipes, which doesn't fit an independently-released Go project with its own RPM already published to GitHub Releases (chairlift's own release.yml).Installs the self-contained
projectbluefin-chairliftpackage (not-system-integration, which is for a user-scoped install alongside a separately-provided bootc-staging helper — not applicable to a full system image).Verification
I don't have a way to run Utah's full Hummingbird-based image build locally, so this is unverified by an actual build. What I did check:
CHAIRLIFT_SHA256are real — downloaded and checksum-verified against v0.12.0's checksums.txt.bash -n, then ran the extracted fragment against the real downloaded RPM).uupdARG-pin/Renovate/layer-folding pattern immediately above it in the Containerfile.Test plan