Repository navigation
Conversation
Utah's parity target moves from Bluefin classic (ublue bluefin:stable and projectbluefin/bluefin base.toml) to projectbluefin/dakota (ghcr.io/projectbluefin/dakota:testing). Structural differences are tracked under #1236 and its children #1222-#1235. - Freeze the manifest: packages/bluefin.toml becomes packages/base.toml, a Utah-owned base manifest frozen from projectbluefin/bluefin@bb63fd16 (2026-09-17) and edited by hand. Content and sections are unchanged; every consumer (Containerfile, install/verify/repo-availability scripts, site data, package snapshot, Justfile, pages.yml, tests, docs) uses the new path. - Delete the Bluefin-classic sync machinery: .bluefin-parity-ref, the check-parity recipe and the build.yml "Check Bluefin parity" step, update-bluefin-parity.yml, audit-bluefin-parity.py with its recipes, baseline and tests. - Baselines measure Dakota vs Utah only. image-baseline.py extract works on an image without rpm and attributes each Dakota file to a guessed element (elements.tsv names plus an alias table); gap/check compare Dakota's user-visible paths with Utah's surface, grouped by item. baselines/bluefin is gone; baselines/dakota/surface.tsv is measured from dakota:testing and elements.tsv refreshed from publish.yml run 43552592054. - triage.toml is rewritten for the 264 Dakota items: epic children for the structural moves, waivers for GNOME OS/BuildStream internals and Flatpak-first apps, #1236 for apps and tools Utah should ship, and the remaining libraries and SDK tools untriaged by area. - `just baselines` and image-baselines.yml measure dakota:testing and utah:testing only. The site group and doc counts read "base manifest". - AGENTS.md, README, SKILL router, package-contract, ci-workflows, docs-parity, containerfile, desktop-contract skills and references, baselines/README, utah.toml headers and the site describe Dakota as the target and base.toml as Utah-owned. Assisted-by: Claude Opus via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danathar, hanthor The full list of commands accepted by this bot can be found here. Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@hanthor this PR is back in your court ( Failing checks:
Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path. Queued in your relay fix queue (5 waiting): fixes are handed out before new work as soon as you have capacity. |
7fa3cf8
ℹ️ Sentinel notice — informational; author is trusted (owner), merge is not blockedHive flagged this PR (author @hanthor, head
Hive did not add the |
Danathar
left a comment
There was a problem hiding this comment.
Stand-in review (the hive's reviewers are out of quota). Changes requested, for one cross-repo dependency. Inside this repo the cleanup is complete.
The problem: projectbluefin/utah-packages fetches this repo's packages/bluefin.toml by name from main. tools/utah_install_set.py:49 ("manifest": "packages/bluefin.toml") is called by publish-repository.yml:548 ("Fetch what Utah installs"). After the rename to base.toml, that fetch 404s. The step is continue-on-error and falls back to the factory's own base image, so publishing won't break. But the factory silently stops resolving Utah's real install set, which is the gate that catches a package publish breaking Utah's image (the libgphoto2 and libppd cases in that tool's docstring). Please land the matching one-line change in utah-packages (packages/bluefin.toml → packages/base.toml) first, or with this PR, or keep a bluefin.toml alias until it does.
Checked in this repo: no leftover references at head to bluefin.toml, .bluefin-parity-ref, audit-bluefin-parity, update-bluefin-parity, check-parity, check-audit-parity or baselines/bluefin. The base.toml rename is carried through the Containerfile, Justfile, tests and docs. The contract keeps its name and in-image path (/usr/share/utah/bluefin-desktop.toml), and the testsuite doesn't read these files. No runtime files change, so there's no E2E impact.
Could not verify: that just check passes with the regenerated triage.toml and GAP.md (about 860 lines). CI will show that once contract is unblocked (#1243).
|
The cross-repo dependency from my review is now handled by projectbluefin/utah-packages#1052, which fetches |
Danathar
left a comment
There was a problem hiding this comment.
Approving at 7fa3cf8. My only blocker, utah-packages fetching packages/bluefin.toml by name, is fixed by projectbluefin/utah-packages#1052 (approved). Merge order: land utah-packages#1052 first or together with this, otherwise the factory's "what Utah installs" check silently falls back until it does.
…n.toml (#1052) projectbluefin/utah#1253 renames Utah's base manifest from packages/bluefin.toml to packages/base.toml with unchanged sections. The advisory install-set check fetched the old name from Utah's main, so the rename would 404 the fetch and silently drop the check. Fetch base.toml first and fall back to bluefin.toml only on a 404, so the check works on both sides of the rename. Assisted-by: Claude Opus via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: hivecommons-hive[bot] <280983584+hivecommons-hive[bot]@users.noreply.github.com> Co-authored-by: mergeraptor[bot] <267480593+mergeraptor[bot]@users.noreply.github.com>
Part 6/7 of the Dakota parity stack (epic #1236). Base:
feat/dakota-desktop-defaults; review and merge in order.Retires
just check-parity,update-bluefin-parity.ymland the audit-bluefin-parity tooling. Required checks are unchanged.Utah's parity target moves from Bluefin classic (ublue bluefin:stable and
projectbluefin/bluefin base.toml) to projectbluefin/dakota
(ghcr.io/projectbluefin/dakota:testing). Structural differences are tracked
under #1236 and its children #1222-#1235.
Utah-owned base manifest frozen from projectbluefin/bluefin@bb63fd16
(2026-09-17) and edited by hand. Content and sections are unchanged; every
consumer (Containerfile, install/verify/repo-availability scripts, site
data, package snapshot, Justfile, pages.yml, tests, docs) uses the new path.
check-parity recipe and the build.yml "Check Bluefin parity" step,
update-bluefin-parity.yml, audit-bluefin-parity.py with its recipes,
baseline and tests.
an image without rpm and attributes each Dakota file to a guessed element
(elements.tsv names plus an alias table); gap/check compare Dakota's
user-visible paths with Utah's surface, grouped by item. baselines/bluefin
is gone; baselines/dakota/surface.tsv is measured from dakota:testing and
elements.tsv refreshed from publish.yml run 43552592054.
structural moves, waivers for GNOME OS/BuildStream internals and
Flatpak-first apps, [Epic] Dakota parity #1236 for apps and tools Utah should ship, and the
remaining libraries and SDK tools untriaged by area.
just baselinesand image-baselines.yml measure dakota:testing andutah:testing only. The site group and doc counts read "base manifest".
docs-parity, containerfile, desktop-contract skills and references,
baselines/README, utah.toml headers and the site describe Dakota as the
target and base.toml as Utah-owned.
Verified:
just checkpasses at the stack tip (1,329 tests). An image build hasn't run yet.