Repository navigation
Conversation
os-countme.bst pinned v2026.08-108-gd46c4df, the tip of the unmerged projectbluefin/common#1112 branch (101 commits behind main, at risk of garbage collection). Re-track to common main (v2026.08-207-g725dbf68) with bst source track. Common main ships the shared client gated to Dakota: the units carry ConditionOSRelease=ID=bluefin-dakota and ConditionPathExists=/run/ostree-booted, and the script exits unless image-name starts with dakota and it can prove a stable/testing stream from bootc. This image is ID=bluefin-server, declares only image-name "server", and is a DDI with no bootc, so install unit drop-ins that clear the Dakota/ostree conditions (keeping the opt-out conditions) and POSIX-sh substitutions that accept the server name, report repo=server, and tag the ping "none" (a sysupdate DDI has no container stream). A failed ping is retried daily by the timer, so the service treats curl's transient exit statuses as success rather than landing in systemctl --failed. Closes projectbluefin#95 Assisted-by: Claude Opus 5.5 via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Marking this draft. Re-tracking is needed (the old pin only exists on the closed projectbluefin/common#1112 branch), but common main's client is now gated to Dakota (ConditionOSRelease=ID=bluefin-dakota, /run/ostree-booted, image-name dakota*, a bootc stream tag). This PR adapts it by rewriting four lines of the shared script at build time and widening SuccessExitStatus. That works, and it fails the build if common changes those lines, but it forks shared behaviour inside this repo. Preferred: teach projectbluefin/common's bluefin-countme about DDI images (image-name server, no bootc tag, ID=bluefin-server), then this element becomes a plain re-track. Maintainers: also confirm the countme service accepts repo=server with no tag before any of this ships. |
|
Related finding (from #278): common's |
|
Closing after re-evaluation. This was a hedge against the pinned ref ( |
What
elements/bluefin-server/os-countme.bstpinnedv2026.08-108-gd46c4df..., the tip of the unmerged, now-closed projectbluefin/common#1112 branch (feat/first-party-countme-client). That commit is 101 commits behind commonmainand survives only on the PR branch, so a branch deletion would break fresh builds. This re-tracks the element to commonmain(bst source track), moving the ref tov2026.08-207-g725dbf68....The catch: main's reporter is Dakota-scoped
I diffed the four installed files between the pinned ref and common main. The shared client was deliberately narrowed to Dakota (projectbluefin/common#1112 was closed unmerged in favor of the Dakota-scoped #1154):
bluefin-countmeimage-namestarts withdakota, and hard-fails without astable/testingtag resolved from a bootc refimage-name: serverand is a DDI with no bootcbluefin-countme.serviceConditionOSRelease=ID=bluefin-dakota,ConditionPathExists=/run/ostree-booted,After=ublue-booted-image.service(does not exist here)bluefin-countme.timer03-bluefin-countme.presetenable bluefin-countme.timer)jqandcurl(the reporter's only deps) are already depended on; the element needs no new runtime deps.How this image adapts the shared client
The element keeps sourcing the four files from common main (so we still track the same reporter as the family) and adds:
bluefin-countme.{service,timer}.d/10-bluefin-server.conf) that clearConditionOSRelease=andConditionPathExists=and re-assert only the three opt-out conditions, so the units actually run onID=bluefin-server, non-ostree. The service drop-in also clears the danglingAfter=ublue-booted-image.service. The preset still enables the timer.shbut nosed/grep/awk) that accept theserverimage name, setREPO="server", and reporttag=none— a sysupdate-delivered DDI has no container stream, so there is no tag to wait on. Anchor counters fail the build if common rewords any substituted line, so drift breaks loudly instead of silently stopping the count.SuccessExitStatus=list so a transient ping failure (no route/DNS, curl exit 28 etc.) is retried by the daily timer rather than showing up insystemctl --failed— the pinned reporter exited 0 in that case for the same reason.Net effect: this image keeps counting as
repo=serverwith the same install-age buckets, through the same shared client.Verification
flock /tmp/opencode/bst.lock just validate— exit 0.flock /tmp/opencode/bst.lock just export-image— exit 0. Mounted the built/usrerofs: all four adaptation anchors landed inlibexec/bluefin-countme(bash -nclean), both drop-ins installed, preset intact,image-info.json={"image-name": "server"}.flock /tmp/opencode/qemu.lock just dogfood-checkwith aDOGFOOD_EXTRA_PROBErunningsystemctl start bluefin-countme.service; systemctl status …— PASS,PROBE failed=0. Probe showedenabledtimer, the10-bluefin-server.confdrop-in applied, and the unit ran the helper to completion (Deactivated successfully); curl'sstatus=28is the expected no-internet ping timeout under QEMU slirp and is absorbed bySuccessExitStatus.image-name: serverwith no bootc: reportsrepo=server&tag=none&flavor=main&countme=1, exit 0.pytest tests/unit— 371 passed (also in a throwaway detached worktree withoutfiles/boot-keys);bats tests/unit— 74 ok;python3 .github/scripts/docs-checks.py— passed.tests/unit/test_build_depends.pyonly asserts the curl/jq deps, still present); no doc references countme.Closes #95
Assisted-by: Claude Opus 5.5 via GitHub Copilot
Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com