Repository navigation
kuma v45.2.1
-
A restored machine no longer restores again on every boot. The restore unit's sandbox — tightened in 45.1.0 to exactly the paths the script writes — left out the snapshot's PARENT directories, and restic's restore applies each directory's stored ownership on the way down: the chowns on
/var,/etcand/etc/NetworkManagerfailed against the read-only sandbox, restic counted them into its exit code, and the script died onset -ebefore it could clear the restore request. Every file came back; the machine then carried a failed unit and re-ran the restore on every boot after it. The parents join the sandbox's writable set — the ownership being applied is the machine's own, a no-op on a converged system — and the test pins all three. -
A locked keyring no longer reads as "no vault exists". The vault is found by searching the Secret Service, and a locked login collection answers that search exactly like an empty one — so a machine whose keyring daemon died mid-session (see next entry) was told, on every unlock attempt, that no vault existed, which reads as advice to run
setupand threatens an overwrite of a key nobody can see. The empty search now double-checks the collection's ownLockedproperty before it is believed: a shut wall is an error naming the lock, and only a genuinely absent vault reads as absent. -
The daemon's startup unlock rides a retry burst. The session's first minute is the Secret Service's worst — gnome-keyring 51.1 aborts on bursts of fresh
OpenSessionconnections (an upstreamplain_negotiatebug, see hey-cli#352/#453 for the identical backtrace), and the daemon's login-morning handshake could land in the storm and take a single NoReply as the whole session's answer, stranding the bunker locked even though the PAM-unlocked daemon survived. The startup posture now gives the same wall three tries, two seconds apart, and a vault that is genuinely absent or locked still fails fast on the last error. -
The battery's flaky laps say what hurt. A smoke lap that failed on a flaky fixture now names the flake in its verdict instead of a bare red, so a rerun can be judged against what actually failed.
-
The changelog reads newest first, and something checks. The v45.2.0 bump renamed Unreleased in place, burying the new release under the previous one; the file's convention is restored and the container battery now holds it: Unreleased is the first section and every version heading descends.
-
The battery's hibernate lap declines what its fixture cannot prove. The diagnostics of this cycle found the "flaky" hibernate reds are neither flaky nor ours: kernel 7.3's virtio-gpu driver refuses S4 on any virgl device, and the fixture's GPU is virgl because the desktop cannot boot headless without it. The lap now asks the still-live guest why the machine never powered down; the kernel's refusal reads as a loud, permanent warning naming exactly which checks the run did and did not make, and a guest without the refusal still fails honestly.
-
The publish road grants what its validation road needs. The release workflow's permissions line up with the validation jobs it runs.
Static x86_64 binary, no runtime dependencies.
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.2.1/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/v45.2.1/kuma-nostrd-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.2.1/kuma-nostr-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.2.1/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/v45.2.1/cosign.pub
$ cosign verify --key cosign.pub ghcr.io/letdown2491/kuma:niri-45.2.1The 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 c7e5729bc0f93e51aff0043fa27d2cd1eb350186.
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