enricobuehler
12843fe253
Adds a client-selectable **preferred codec** and wires the core + ABI + probe + Linux client to
negotiate and decode it. (Windows/Apple/Android follow in 2b.)
**Core:**
- `Hello.preferred_codec` (a single CODEC_* bit, 0 = auto) — a soft hint appended after
`video_codecs`. `resolve_codec(client, host, preferred)` now honors the preference when the host
can also emit it, else falls back to precedence (HEVC > AV1 > H.264). Roundtrip + preference tests.
- `NativeClient::connect` takes `video_codecs` + `preferred_codec`; `NativeClient.codec` exposes the
resolved `Welcome.codec`.
- ABI: `punktfunk_connect_ex7` (adds the two codec params; `ex6` delegates to it advertising
HEVC-only) + `punktfunk_connection_codec` getter + `PUNKTFUNK_CODEC_{H264,HEVC,AV1}` constants
(drift-guarded against the wire values). Header regenerated.
**Host:** passes `hello.preferred_codec` into `resolve_codec`.
**probe:** `--codec h264|hevc|av1|auto` sets the preference (still advertises it can decode all
three); the dump extension already follows the resolved codec.
**Linux client:** advertises the codecs FFmpeg can actually decode (`decodable_codecs()`), threads
the user's `codec` setting as the preference, and builds the decoder — both the software and VAAPI
paths, plus the mid-session VAAPI→software demotion — from the negotiated `Welcome.codec` instead of
hardcoding HEVC. New "Video codec" dropdown in Preferences (Automatic/HEVC/H.264/AV1).
Live-validated on the dev box: probe `--codec hevc` against a software (H.264-only) host resolves to
H.264 (graceful soft-preference fallback), no failure. clippy + core (57) + host (133) tests green.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
125 lines
6.0 KiB
Markdown
125 lines
6.0 KiB
Markdown
# punktfunk-host — RPM (Bazzite / Fedora Atomic) via the Gitea registry
|
|
|
|
`punktfunk-host` is published as an RPM to **Gitea's RPM package registry** in the public `unom`
|
|
org (stable groups `bazzite`/`fedora-44`, canary groups `bazzite-canary`/`fedora-44-canary`), so
|
|
Bazzite / Fedora Atomic hosts layer and update it with `rpm-ostree`. CI (`.gitea/workflows/rpm.yml`)
|
|
builds and publishes on every push to `main` (a rolling `0.5.0-0.ciN.g<sha>` build to the `*-canary`
|
|
groups) and on `vX.Y.Z` tags (a clean `X.Y.Z-1` to the base groups, plus attached to the unified
|
|
Gitea Release) — separate repos, so a stable box never jumps to a canary build (see
|
|
[Release Channels](https://punktfunk.unom.io/docs/channels)). The `baseurl` below subscribes to the
|
|
`bazzite` stable group; use `bazzite-canary` for the latest main builds. The RPM is built in the
|
|
Fedora 43 image (`ci/fedora-rpm.Dockerfile`) so its auto-generated library Requires
|
|
(`libavcodec.so.NN`, …) match Bazzite's sonames; the NVIDIA driver lib (`libcuda.so.1`) is
|
|
excluded — NVENC/EGL come from whatever NVIDIA stack the host runs (a weak Recommends).
|
|
|
|
This is the same package as the [COPR](../copr/README.md) / [bootc](../bootc/Containerfile)
|
|
paths — same spec (`punktfunk.spec`) — just self-hosted in Gitea instead of COPR, mirroring the
|
|
[Debian/apt](../debian/README.md) setup.
|
|
|
|
## Install on a Bazzite host (one-time)
|
|
|
|
```sh
|
|
# Add the repo. Packages are GPG-signed (gpgcheck=1, the packages@unom.io key) AND the repo
|
|
# metadata is Gitea-signed (repo_gpgcheck=1); gpgkey lists both so dnf/rpm-ostree imports each.
|
|
sudo tee /etc/yum.repos.d/punktfunk.repo >/dev/null <<'REPO'
|
|
[gitea-unom-bazzite]
|
|
name=punktfunk (unom, Bazzite)
|
|
baseurl=https://git.unom.io/api/packages/unom/rpm/bazzite
|
|
enabled=1
|
|
gpgcheck=1
|
|
repo_gpgcheck=1
|
|
gpgkey=https://git.unom.io/api/packages/unom/rpm/repository.key
|
|
https://git.unom.io/api/packages/unom/generic/punktfunk-keys/1/RPM-GPG-KEY-punktfunk
|
|
REPO
|
|
|
|
# Layer the host + the web console (pairing/status), then reboot into the new deployment.
|
|
# (punktfunk Recommends punktfunk-web; list it explicitly so it's pulled regardless of weak-dep
|
|
# settings. The registry carries punktfunk-web because CI builds the spec --with web; COPR can't.)
|
|
rpm-ostree install punktfunk punktfunk-web
|
|
systemctl reboot
|
|
```
|
|
|
|
> If `rpm-ostree` can't complete the metadata GPG check non-interactively, set `repo_gpgcheck=0`
|
|
> (TLS-only trust to the self-hosted registry).
|
|
|
|
## Per-package signing (`gpgcheck=1`, active)
|
|
|
|
CI GPG-signs every RPM: `packaging/rpm/sign-rpms.sh` (run from `rpm.yml` between build and publish)
|
|
signs with the dedicated EdDSA key **`packages@unom.io`** (`AF245C506F4E4763`) and self-verifies
|
|
with `rpmkeys --checksig` before publishing, so an unsigned/bad build never reaches the registry.
|
|
The public key is served from the registry (the `gpgkey=` URL above) and committed at
|
|
`packaging/rpm/RPM-GPG-KEY-punktfunk`. (This is a GPG/OpenPGP key — a `step-ca`/X.509 cert can't
|
|
sign RPMs; step-ca is only for registry/console TLS.)
|
|
|
|
How it was set up (and how to rotate the key):
|
|
|
|
```sh
|
|
# 1. Generate a DEDICATED, passphrase-less signing key (separate from the Gitea metadata key).
|
|
gpg --batch --gen-key <<EOF
|
|
%no-protection
|
|
Key-Type: eddsa
|
|
Key-Curve: ed25519
|
|
Name-Real: punktfunk packages
|
|
Name-Email: packages@unom.io
|
|
Expire-Date: 0
|
|
%commit
|
|
EOF
|
|
gpg --armor --export-secret-keys packages@unom.io # -> the RPM_GPG_PRIVATE_KEY CI secret
|
|
gpg --armor --export packages@unom.io > packaging/rpm/RPM-GPG-KEY-punktfunk # public half
|
|
|
|
# 2. Add the armored PRIVATE key as the RPM_GPG_PRIVATE_KEY Gitea Actions secret. Commit the public
|
|
# half and publish it to the registry so the gpgkey= URL resolves:
|
|
curl --user "<user>:<write:package-PAT>" --upload-file packaging/rpm/RPM-GPG-KEY-punktfunk \
|
|
https://git.unom.io/api/packages/unom/generic/punktfunk-keys/1/RPM-GPG-KEY-punktfunk
|
|
```
|
|
|
|
Rotating the key means a new generic-registry version (bump `punktfunk-keys/1` → `/2` and the
|
|
`gpgkey=` URL), since the registry rejects re-uploading an existing file.
|
|
|
|
After reboot, as the desktop user:
|
|
|
|
```sh
|
|
ujust add-user-to-input-group # virtual gamepads need /dev/uinput (re-login).
|
|
# Bazzite is atomic — use ujust, NOT `usermod -aG input`.
|
|
mkdir -p ~/.config/punktfunk
|
|
cp /usr/share/punktfunk/host.env.bazzite ~/.config/punktfunk/host.env # gamescope defaults
|
|
systemctl --user enable --now punktfunk-host
|
|
# Web console — enable it and read the auto-generated login password (then open http://<host-ip>:3000):
|
|
systemctl --user enable --now punktfunk-web
|
|
journalctl --user -u punktfunk-web-init | sed -n 's/.*password generated: //p'
|
|
```
|
|
|
|
(See [`../bazzite/README.md`](../bazzite/README.md) for the full appliance walkthrough —
|
|
udev/group, `host.env`, the Steam session unit, firewall, verify.)
|
|
|
|
## Updates
|
|
|
|
```sh
|
|
rpm-ostree upgrade # pulls the newest punktfunk with the system update
|
|
systemctl reboot # rpm-ostree changes apply on reboot
|
|
```
|
|
|
|
Layered packages are re-resolved against their repos on every `rpm-ostree upgrade`, so the box
|
|
tracks new builds automatically (Bazzite's auto-update timer does this for you). To pin or stop
|
|
tracking: `rpm-ostree override` / `rpm-ostree uninstall punktfunk`.
|
|
|
|
## Build an RPM locally
|
|
|
|
```sh
|
|
PF_VERSION=0.0.1 bash packaging/rpm/build-rpm.sh # host + client
|
|
PF_VERSION=0.0.1 PF_WITH_WEB=1 bash packaging/rpm/build-rpm.sh # + punktfunk-web (needs bun on PATH)
|
|
# -> dist/punktfunk-0.0.1-1.fcNN.x86_64.rpm (+ punktfunk-web-0.0.1-1.fcNN.x86_64.rpm with PF_WITH_WEB=1;
|
|
# the web subpackage vendors a bun binary, so it's arch-specific, not noarch)
|
|
```
|
|
|
|
Run it inside the Fedora 43 builder image so the deps resolve and match Bazzite:
|
|
|
|
```sh
|
|
docker build -f ci/fedora-rpm.Dockerfile -t punktfunk-fedora-rpm ci
|
|
docker run --rm -v "$PWD:/src" -w /src punktfunk-fedora-rpm \
|
|
bash -lc 'git config --global --add safe.directory /src && PF_VERSION=0.0.1 bash packaging/rpm/build-rpm.sh'
|
|
```
|
|
|
|
A plain `rpmbuild`/COPR build with no `pf_version`/`pf_release` defines produces `0.3.0-1` (the
|
|
spec defaults).
|