What
elements/bluefin-server/os-countme.bst sources the shared countme reporter from projectbluefin/common and pins:
ref: v2026.08-108-gd46c4df9f9988002120cff4a66df8b163070fe6d
That commit is the tip of the branch in projectbluefin/common#1112, not main. It was pinned there so #94 builds before the reporter lands upstream.
What fixed looks like
Once projectbluefin/common#1112 merges:
bst track elements/bluefin-server/os-countme.bst
and the ref moves to a commit on main that contains system_files/shared/usr/libexec/bluefin-countme.
Why it needs a human
bst track generates the ref; it cannot be hand-written correctly. Until it is re-tracked, this image builds against a branch commit that will be garbage-collected if the branch is deleted after merge, at which point the build breaks.
Impact
Low while the branch exists, hard failure once it is deleted.
Introduced by #94.
What
elements/bluefin-server/os-countme.bstsources the shared countme reporter from projectbluefin/common and pins:That commit is the tip of the branch in projectbluefin/common#1112, not
main. It was pinned there so #94 builds before the reporter lands upstream.What fixed looks like
Once projectbluefin/common#1112 merges:
and the
refmoves to a commit onmainthat containssystem_files/shared/usr/libexec/bluefin-countme.Why it needs a human
bst trackgenerates the ref; it cannot be hand-written correctly. Until it is re-tracked, this image builds against a branch commit that will be garbage-collected if the branch is deleted after merge, at which point the build breaks.Impact
Low while the branch exists, hard failure once it is deleted.
Introduced by #94.