Repository navigation
fix: record that the dev-tools batch packages are now published - #968
Merged
hivecommons-hive[bot] merged 1 commit intoNov 9, 2026
Merged
hivecommons-hive[bot] merged 1 commit into
hivecommons-hive[bot] merged 1 commit into
Conversation
Fill published_run/published_nevra for all 17 projectbluefin#488 outputs observed in ghcr.io/projectbluefin/utah-packages@sha256:11318e23d0f093c58fa8136e48ae7c8acae9e849c272152055473b707aff5d72 (run 42559053279, revision ff2affe): mtr, nano, nfs-client-utils, nfs-common-utils, nfs-utils, nfsv3-client-utils, nfsv4-client-utils, nilfs-utils, ntfs-3g-system-compression, nvme-cli, nvtop, oddjob, oddjob-mkhomedir, open-vm-tools, open-vm-tools-desktop, pinentry, pinentry-gnome3. Point nilfs-utils and open-vm-tools* at their merged adoption PRs (projectbluefin#715, projectbluefin#892) instead of the closed proposals (projectbluefin#702, projectbluefin#812). Record that the image's factory-state label marks mtr, ntfs-3g-system-compression and open-vm-tools as failed at their current input digest, so their published RPMs are retained older builds. Runtime proof stays open on the issue. Refs projectbluefin#488 Assisted-by: Claude Opus via omp Hive-Run: projectbluefin#488 Hive-Plan: factory-build-backlog dev-tools reconciliation Hive-Spec: issue-488#acceptance-publication-evidence Signed-off-by: Karibhou <Karibhou@users.noreply.github.com>
22 tasks
Contributor
Contributor
|
Merged by hive contributor-lane auto-merge: CI green for ≥30m, reviewer verdict approve, @Karibhou holds the trusted tier in this hive's contributor registry. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary: The project keeps a list of the programs Bluefin needs that must be built into its own package collection. All 17 developer and system tools in this batch (for example the
nanotext editor, network-share tools, the VMware guest helpers and the password-prompt dialogs) are now really present in the published collection, but the list still said "not yet proven". This records where and in which build each one appeared, so maintainers can see real progress. It does not claim they install and work correctly; those checks are still open.Refs #488 — remaining on that issue: install every output using only Hummingbird plus the factory repositories and exercise its representative command or payload (incl. VMware guest behavior). Also, three sources (
mtr,ntfs-3g-system-compression,open-vm-tools) have a failed latest rebuild; their published RPMs are older retained builds.What changed
config/factory-build-backlog.toml[resolved]records only (no names moved; auditor totals unchanged —dev-toolsstill shows none of these names pending).Evidence source:
ghcr.io/projectbluefin/utah-packages@sha256:11318e23d0f093c58fa8136e48ae7c8acae9e849c272152055473b707aff5d72, publishing run 42559053279 (in progress when read — publication observed, not a workflow-success claim), revisionff2affebb786e98a466ba95896374163ec20f60e(currentmain), primary metadata sha256f5f28143c3d3a0a3680325b05270573f656547211b33925a0086651a07480c10. NEVRAs read from each binary's own primary entry.nilfs-utilsandopen-vm-tools*records pointed at closed proposals (feat: add tools for managing NILFS filesystems #702, feat: prepare better support for VMware virtual machines #812); they now cite the merged adoption PRs (feat: add instructions to build NILFS filesystem utilities (adopts #702) #715, feat: prepare better support for VMware virtual machines #892).open-vm-toolswas built by the successful post-merge run 42216043584.org.projectbluefin.factory.statelabel listsmtr,ntfs-3g-system-compressionandopen-vm-toolsunderfailedat their current input digest. Their published RPMs are retained builds (primarybuildtime2026-10-27, 2026-10-28, 2026-11-06). Recorded in the catalog comment so publication evidence does not hide it.docs/skills/factory-build-backlog/diagnosing-drift.md: write-back — check cited sources against the image's factory-statefailedset and binarybuildtime.Per-output disposition (all 17 names in #488)
All 17:
[resolved]with import PR + publication fields above. Not covered here: permitted-repository install transactions and runtime exercise (no repository harness for that; stays on #488). Utah consumer issue: projectbluefin/utah#392.Verification
python3 tools/factory_build_backlog.py --check— passes.just check— 1491 passed, 2 skipped.just test— 1491 passed, 2 skipped.— hive: backend=omp model=anthropic/claude-opus-5-5
🐝 Hive Agent:
contributor| SHA:8c411c57