Repository navigation
kuma v44.15.2
- The fallback's full compiler survives its own output. The staged 44.15.1 binary generated a Containerfile whose niri-session patch asserted the unpatched line before sed'ing — and the release image the fallback compiles FROM was built by that very compiler, so the assertion failed and every upgrade that could not ride the delta lane (the 44→45 crossing, any full-rebuild move) died at the build (#70). The patch step is idempotent now (d80a9f2's fix, rebased onto this branch): the sed runs unconditionally and asserts the patched line, which holds on a virgin base and on a release image alike.
Static x86_64 binary, no runtime dependencies.
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v44.15.2/kuma-x86_64-unknown-linux-musl
$ chmod +x kuma-x86_64-unknown-linux-musl && sudo mv kuma-x86_64-unknown-linux-musl /usr/local/bin/kumaThe image build stages the layer's three binaries from beside
the running kuma on every compose, nostr or not, so they
install to the same place:
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v44.15.2/kuma-nostrd-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v44.15.2/kuma-nostr-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v44.15.2/nip46-relay-x86_64-unknown-linux-musl
$ chmod +x kuma-nostrd-x86_64-unknown-linux-musl kuma-nostr-x86_64-unknown-linux-musl nip46-relay-x86_64-unknown-linux-musl
$ sudo mv kuma-nostrd-x86_64-unknown-linux-musl /usr/local/bin/kuma-nostrd
$ sudo mv kuma-nostr-x86_64-unknown-linux-musl /usr/local/bin/kuma-nostr
$ sudo mv nip46-relay-x86_64-unknown-linux-musl /usr/local/bin/nip46-relayVerify it came from this workflow:
$ cosign verify-blob \
--bundle kuma-x86_64-unknown-linux-musl.bundle \
--certificate-identity-regexp '^https://github.com/Letdown2491/kumaOS/.+@refs/tags/' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
kuma-x86_64-unknown-linux-muslThe image this release publishes verifies with the committed
public key — the same key every kuma machine's own policy
enforces on update:
$ curl -sSLO https://github.com/Letdown2491/kumaOS/raw/v44.15.2/cosign.pub
$ cosign verify --key cosign.pub ghcr.io/letdown2491/kuma:niri-44.15.2The moving tag is the convenience and the digest is the proof;
the verify response prints the digest it checked, and the same
command against that digest pins the bytes:
$ cosign verify --key cosign.pub ghcr.io/letdown2491/kuma@sha256:<digest the verify above printed>Built from 20cf5c8832b246d21e61db2c18dce50537d7d8b3.
The installer media on this page verifies the same way:
$ cosign verify-blob \
--bundle kuma-x86_64.iso.bundle \
--certificate-identity-regexp '^https://github.com/Letdown2491/kumaOS/.+@refs/tags/' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
kuma-x86_64.iso