Repository navigation
docs: record package availability - #860
hivecommons-hive[bot] merged 4 commits into
Conversation
|
@mrbobbytables this PR is back in your court ( Review asks:
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 (2 waiting): fixes are handed out before new work as soon as you have capacity. |
fddf32e to
a6a8e07
Compare
|
stage 080-awaiting-merge-admission: no activity for 30m0s: merge-train:queued-behind#840:8/8:0/0:.packit.yaml,factory-build-backlog.toml,upstream-sources.json,architecture.md,+16 |
|
stage 080-awaiting-merge-admission → 050-review-pending: contributor-lane:no-verdict |
1 similar comment
|
stage 080-awaiting-merge-admission → 050-review-pending: contributor-lane:no-verdict |
|
@mrbobbytables this PR is back in your court ( Review asks:
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 (2 waiting): fixes are handed out before new work as soon as you have capacity. |
There was a problem hiding this comment.
Summary: This change records which of a batch of system tools are now published in the project's package repository, and marks two of them as deliberately skipped by the Utah image. I checked the published repository metadata and Utah's decision records directly; every claim holds up. One small readability note about where a comment was placed.
style
- low — snapshot header reads as describing the codec entries below it.
config/factory-build-backlog.toml:262-267puts the 2026-10-31 factory snapshot comment ("Published NEVRAs below establish metadata presence…") insidepackages = [, directly above the#476codec block (lines 268-273), none of which carrypublished_nevra. The five entries it actually describes are at lines 454-455, 514, 677-678. Existing convention keeps snapshot headers abovepackages = [in the section preamble (e.g. the GNOME #483 block at lines 255-258). Suggested: move the comment up to join the section preamble.
# Latest rebuilds of gnome-tour, gnome-browser-connector and gnome-remote-desktop failed in run 40151594832; their earlier RPMs remain published.
+# Factory image snapshot 2026-10-31: digest
+# sha256:d3dadc279e529a0646d3558bfc150066f21f0f5cca3d1a5a733798c60253e984,
+# source revision c9f1be7f33fa269928cf3056695d51150200e74b (on main),
+# run 41233305890, repomd SHA-256 5752786befbfbe662b7e387818240872aff632390bd336f7a1ad2a09731a6079,
+# primary SHA-256 10161bb9fb4942907844f1110c882da1b4bc09e6de15fb35250ff84147fd3cf4.
+# published_nevra fields citing run 41233305890 establish metadata presence, not runtime resolution.
# Packages that left the backlog because a recipe was imported.
# Each entry: package name and the commit that closed the gap.
packages = [
- # Factory image snapshot 2026-10-31: digest
- # sha256:d3dadc279e529a0646d3558bfc150066f21f0f5cca3d1a5a733798c60253e984,
- # source revision c9f1be7f33fa269928cf3056695d51150200e74b (on main),
- # run 41233305890, repomd SHA-256 5752786befbfbe662b7e387818240872aff632390bd336f7a1ad2a09731a6079,
- # primary SHA-256 10161bb9fb4942907844f1110c882da1b4bc09e6de15fb35250ff84147fd3cf4.
- # Published NEVRAs below establish metadata presence, not runtime resolution.
# Codec recipe imports for #476; publication and runtime proof remain separate.Verified independently at head 8fb146b: image layer sha256:66367e… repomd.xml SHA-256 and primary checksum match the PR body; primary.xml lists exactly the five NEVRAs added and none of the thirteen named as absent; Utah baselines/triage.toml@4eee67d L388-394 waives exactly qemu-user-static-aarch64 and rpm-ostree; python3 tools/factory_build_backlog.py --check passes (142 entries, 125 pending).
No findings from: correctness, security, intent-alignment, docs-currency.
Confidence: 5/5 (safe)
— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88
8fb146b to
2c90a21
Compare
|
Hive base moved: rebased onto 🐝 Hive Agent: |
|
Moved the factory snapshot evidence above the packages array in the section preamble, so it no longer reads as describing the codec entries. The correction is pushed. 🐝 Hive Agent: |
|
stage 080-awaiting-merge-admission → 050-review-pending: required-check-pending:Canary |
|
stage 080-awaiting-merge-admission: no activity for 30m0s: merge-train:queued-behind#855:3/4:0/0:.packit.yaml,factory-build-backlog.toml,upstream-sources.json,factory-build-backlog.md,+12 |
|
stage 080-awaiting-merge-admission → 050-review-pending: contributor-lane:no-verdict |
🐝 Possible duplicateThis PR changes exactly the same files as #855, which was opened first:
Evidence — identical changed-file set (2 file(s)):
This is a suggestion, not a verdict. Hive will not close, label, approve or merge anything here — a human decides. It was produced by comparing changed-file sets across open PRs, which is a candidate generator: PRs that share a file are not necessarily the same work. Here the patches DIFFER, so this is the weaker tier: dependency-bump PRs that edit one shared manifest, and unrelated fixes to one busy file, both land in it. Read the diffs before acting. |
|
@mrbobbytables this PR is back in your court ( Review asks:
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 (2 waiting): fixes are handed out before new work as soon as you have capacity. |
|
@mrbobbytables the hive has adopted this PR ( |
Record current package identities for five outputs already published by the factory and move two exact Utah waivers out of the pending set. Keep publication separate from runtime confirmation, and document why a waiver does not cover sibling outputs. Assisted-by: Auto via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Hive-Run: projectbluefin#490 Hive-Plan: issue-490/implementation Hive-Spec: issue-490#acceptance-and-proof Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com>
Keep the factory snapshot evidence outside the package-entry list. Assisted-by: Auto via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com>
e7f48da to
0c1d32e
Compare
|
hive/awaiting-ci: rebased onto main; CI pending — sweep will merge when green. 🐝 Hive Agent: — hive: agent=scanner backend=copilot model=claude-opus-5.5 copilot=1.0.88 |
|
stage 080-awaiting-merge-admission → 074-adopted-by-hive: required-check-pending:Unit tests |
|
stage 080-awaiting-merge-admission → 074-adopted-by-hive: contributor-lane:no-verdict |
|
stage 080-awaiting-merge-admission → 074-adopted-by-hive: pending: head pushed 2m3s ago (< min_head_age) |
|
Merged by hive contributor-lane auto-merge: CI green for ≥30m, reviewer verdict approve, head |
Summary: This records which requested system tools are already published in the project's package repository and which the Utah system image has chosen not to include. It avoids duplicate work and keeps the remaining missing tools visible instead of implying they are ready to install.
What I need from you: Review the evidence and the two waiver reconciliations.
Changes
rsync,smartmontools,smartmontools-selinux,spice-vdagent, andsshpass.qemu-user-static-aarch64andrpm-ostreeto[wontfix]using Utah's exact, pinned triage decisions. Keeprpm-ostree-libsseparate; it has no waiver of its own.Snapshot evidence
The factory image
ghcr.io/projectbluefin/utah-packages@sha256:d3dadc279e529a0646d3558bfc150066f21f0f5cca3d1a5a733798c60253e984was published by run 41233305890, which completed successfully. Its source revisionc9f1be7f33fa269928cf3056695d51150200e74bis onmain; the image'srepomd.xmlSHA-256 is5752786befbfbe662b7e387818240872aff632390bd336f7a1ad2a09731a6079, and its primary metadata checksum is10161bb9fb4942907844f1110c882da1b4bc09e6de15fb35250ff84147fd3cf4. These observations confirm the five package identities below are present, but not that they were freshly built in that run or installable in Utah.Hummingbird's repository metadata fetched at 2026-10-31 20:00:08 UTC had repomd SHA-256
0f4f52f776762f82c1027fc0ab4efb58dd261c074c4e92a441fdde22dee3c889and primary checksum20bb6c41b5662992b577b632d6e265c8b5e829802ad326ee535b0c7a9f7472ba. Of the named outputs, that snapshot containsrclone-0:1.75.2-2.hum1.x86_64andrsync-0:3.5.1-1.hum1.x86_64; no permitted-repository solver transaction was run for them.Utah triage was checked at commit
4eee67d0495406aba69a8e10926a3f30a7cf8437inbaselines/triage.toml. The exact waiver records are at qemu-user-static-aarch64 and rpm-ostree.Output-by-output disposition
qemu-guest-agentqemuqemu-user-static-aarch64qemu[wontfix](lines 388–390).rclonerclonerealmdrealmdresticresticrpm-ostreerpm-ostree[wontfix](lines 392–394).rpm-ostree-libsrpm-ostreersyncrsyncrsync-0:3.5.1-1.hum1.bfin.x86_64; also present in Hummingbird metadata.smartmontoolssmartmontoolssmartmontools-1:7.5-11.hum1.bfin.x86_64.smartmontools-selinuxsmartmontoolssmartmontools-selinux-1:7.5-11.hum1.bfin.noarch.spice-vdagentspice-vdagentspice-vdagent-0:0.23.0-3.hum1.bfin.x86_64; Utah triage marks it planned (line 153).spice-webdavdphodavsshpasssshpasssshpass-0:1.09-13.hum1.bfin.x86_64; Utah triage marks it planned (line 324).sssd-clientsssdsssdrecipe; absent from both indexes. Build and runtime proof remain open.sssd-commonsssdsssdrecipe; absent from both indexes; Utah triage marks it planned (line 238).sssd-kcmsssdsssdrecipe; absent from both indexes; Utah triage marks it planned (line 243).sssd-krb5-commonsssdsssdrecipe; absent from both indexes. Build and runtime proof remain open.sssd-nfs-idmapsssdsssdrecipe; absent from both indexes. Build and runtime proof remain open.Refs #490 (the accepted system-tools parity batch) — ten outputs remain unpublished,
rclonestill needs permitted-repository installability proof, and the five published outputs still need dependency and runtime checks.— hive: backend=copilot model=gpt-6-luna