enricobuehler
58cb416abb
ci / web (push) Failing after 44s
ci / rust (push) Successful in 1m7s
apple / swift (push) Successful in 1m16s
ci / docs-site (push) Failing after 38s
docker / build-push (., web/Dockerfile, punktfunk-web) (push) Successful in 5s
deb / build-publish (push) Failing after 2m20s
docker / build-push (ci, ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Successful in 4s
docker / build-push (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Successful in 4s
docker / build-push (ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora-rpm) (push) Successful in 2m21s
docker / deploy-docs (push) Successful in 18s
rpm / build-publish (push) Successful in 3m57s
Mirrors the apt pipeline for Fedora Atomic / Bazzite. New `rpm` workflow builds the host RPM in a Fedora 43 builder image (ci/fedora-rpm.Dockerfile — matches Bazzite's libavcodec.so.61, with a self-contained 16-symbol libcuda link stub so no NVIDIA packages are needed in CI) and uploads to Gitea's public RPM registry (group "bazzite") on every main push (rolling 0.0.1-0.ciN.<sha>) and v* tag (clean X.Y.Z-1). Bazzite hosts then track it with `rpm-ostree upgrade`. - packaging/rpm/build-rpm.sh: git-archive tarball + rpmbuild (--nodeps, since the toolchain is rustup + dnf, not RPMs); copies to dist/, asserts no cuda/nvidia leak. - punktfunk.spec: overridable pf_version/pf_release for CI snapshots; exclude libcuda.so from auto-Requires (NVENC/EGL come from the driver, out of band) — same NVIDIA filter as the .deb; fix a bogus changelog weekday. - docker.yml builds+pushes the new fedora-rpm image; packaging README + rpm/README document the rpm-ostree install/update path (recommended option). Builder image seeded to the registry so rpm.yml's first run finds it. RPM build + clean-Requires verified locally in the image (libavcodec.so.61 / libavutil.so.59, no cuda). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
66 lines
2.8 KiB
Markdown
66 lines
2.8 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 (group `bazzite`), 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.0.1-0.ciN.<sha>` build) and on `v*` tags (a clean `X.Y.Z-1`). 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
|
|
# Trust + add the repo (rpm-ostree reads /etc/yum.repos.d). Public registry, no auth.
|
|
curl -fsSL https://git.unom.io/api/packages/unom/rpm/bazzite.repo \
|
|
| sudo tee /etc/yum.repos.d/punktfunk.repo
|
|
|
|
# Layer the package, then reboot into the new deployment.
|
|
rpm-ostree install punktfunk
|
|
systemctl reboot
|
|
```
|
|
|
|
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
|
|
```
|
|
|
|
(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 # -> dist/punktfunk-0.0.1-1.fcNN.x86_64.rpm
|
|
```
|
|
|
|
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.0.1-1`.
|