# Build the punktfunk-host RPM and publish it to Gitea's RPM package registry, so Bazzite / # Fedora Atomic hosts layer + update it with rpm-ostree. Counterpart to deb.yml (apt). Runs in # the Fedora 43 builder image (ci/fedora-rpm.Dockerfile) so the RPM's auto library Requires # (libavcodec.so.NN, …) match the target's sonames. # # Registry (public, unom org), group "bazzite": # repo file https://git.unom.io/api/packages/unom/rpm/bazzite.repo # Box setup (once): see packaging/rpm/README.md # # REGISTRY_TOKEN: repo Actions secret, a PAT with write:package scope (shared with docker.yml). name: rpm on: push: branches: [main] tags: ['v*'] workflow_dispatch: env: REGISTRY: git.unom.io OWNER: unom jobs: build-publish: runs-on: ubuntu-24.04 # One RPM per target whose ffmpeg soname must match (a binary RPM is soname-coupled to its # base): Fedora 43 == Bazzite (libavcodec.so.61), Fedora 44 == the Fedora KDE spin (.so.62). # Each builds in its matching builder image and publishes to its own registry group. strategy: fail-fast: false matrix: include: - image: punktfunk-fedora-rpm # Fedora 43 == Bazzite base group: bazzite - image: punktfunk-fedora44-rpm # Fedora 44 == Fedora KDE spin group: fedora-44 container: image: git.unom.io/unom/${{ matrix.image }}:latest timeout-minutes: 90 env: CARGO_HOME: /usr/local/cargo steps: - uses: actions/checkout@v4 # rpmbuild + git archive need the checkout trusted; cache the crates download. # The client link deps are also baked into the fedora-rpm image, but this job runs # against the image from the PREVIOUS push (docker.yml bootstrap note) — keep it # green across image changes; a no-op once the image has them. - name: Prep run: | git config --global --add safe.directory "$PWD" dnf -y install gtk4-devel libadwaita-devel SDL3-devel - uses: actions/cache@v4 with: path: /usr/local/cargo/registry key: cargo-home-${{ hashFiles('Cargo.lock') }} restore-keys: cargo-home- - name: Version # Tag v1.2.3 -> 1.2.3-1 (release); main push -> 0.0.1-0.ciN.g, whose release "0." # sorts BEFORE the eventual "1" yet increases by run number, so `rpm-ostree upgrade` # always moves to the newest main build. run: | SHORT=$(echo "$GITHUB_SHA" | cut -c1-8) case "$GITHUB_REF" in refs/tags/v*) V="${GITHUB_REF_NAME#v}"; R="1" ;; *) V="0.0.1"; R="0.ci${GITHUB_RUN_NUMBER}.g${SHORT}" ;; esac echo "PF_VERSION=$V" >> "$GITHUB_ENV" echo "PF_RELEASE=$R" >> "$GITHUB_ENV" echo "rpm $V-$R" - name: Build RPM run: PF_VERSION="$PF_VERSION" PF_RELEASE="$PF_RELEASE" bash packaging/rpm/build-rpm.sh - name: Publish to the Gitea RPM registry env: TOKEN: ${{ secrets.REGISTRY_TOKEN }} run: | # Publish only the main package (skip -debuginfo/-debugsource subpackages). for rpm in dist/*.rpm; do case "$rpm" in *debuginfo*|*debugsource*) echo "skip $rpm"; continue;; esac echo "uploading $rpm" curl -fsS --user "enricobuehler:$TOKEN" --upload-file "$rpm" \ "https://$REGISTRY/api/packages/$OWNER/rpm/${{ matrix.group }}/upload" done echo "published to $OWNER/rpm/${{ matrix.group }}"