fix: correct runtime-dep derivation and fork versioning #3
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/image-runtime-deps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #2. #2 merged the runtime-dependency fixes and the PR-CI image build; its build-push run on main was cancelled at the version step, which this PR fixes.
This PR (one commit, build-push.yaml only): fork versioning. The conventional-commit scheme produced
1.0.0for the first fork build, implying our own v1. Version is now<upstream-ver>-bt<rev>(e.g.3.7.5-bt8) derived from the nearestupstream/*tag plus carried commit count -- the Debian idiom for a downstream. Self-updates on rebase; the git-tag-push step is dropped since the version needs no release tag, and the immutable short-sha image tag remains the deployment's exact-pin handle.For context, already landed on main via #2:
ldd(which needs the dynamic loader, unavailable under buildah chroot isolation) toobjdump -p(static ELFNEEDEDread), resolving SONAMEs via theldconfigcache andrealpath-canonicalizing beforedpkg -S(merged-/usr: ldconfig reports/lib/..., dpkg records/usr/lib/...)./out, not just the two binaries: acng's networking lives in its privatelibsupacng.so, which is what pulls inlibevent_pthreads-- inspecting only the daemon missed it.🤖 Generated with Claude Code
8f434c3894cd1399dcda