FreeREAC package repository

Signed RPMs for the openmixer console (openmixer and its plugin collections) and for mod-host, the LV2 plugin host the console spawns for channel inserts, served over dnf. The REAC transport stack (reac-pw, libreac) is served here too.

Install

sudo dnf config-manager addrepo --from-repofile=https://freereac.github.io/rpm/freereac.repo
sudo rpm --import https://freereac.github.io/rpm/RPM-GPG-KEY-freereac
sudo dnf install openmixer

For the REAC transport alone — a Roland stagebox on a Linux machine without the console:

sudo dnf install reac-pw

reac-pw pulls libreac and libreac-transport with it (currently 1.0.1).

openmixer is the console — server, web UI and manual — and mod-host comes along with it: openmixer-server requires the plugin host, and since no Fedora repository carries it, this one does.

openmixer-full adds the REAC stagebox transport on top and resolves here: reac-pw and libreac are in this repository. Install openmixer for the console alone, or openmixer-full for the console plus the REAC transport.

What is here

path	contents
rpm/	the dnf repository: fedora/<releasever>/<arch>/ + repodata/
	noarch packages live inside each arch directory — dnf's $basearch never resolves to a sibling noarch/ tree
rpm/freereac.repo	the repo definition (gpgcheck=1, repo_gpgcheck=1)
rpm/RPM-GPG-KEY-freereac	the public signing key

Packages and the repository metadata are both signed. dnf verifies each package against the key above and verifies repomd.xml before trusting the metadata.

How it is published

Generated by packaging/publish-repo.sh in the openmixer repository — it builds (or collects) the RPMs in dependency order (mod-host → libreac → reac-pw → openmixer), signs them, runs createrepo_c, detach-signs the metadata, and emits this tree. See packaging/README.md there for the walkthrough and key-rotation notes.

Nothing is published automatically yet; CI automation is tracked in openmixer#321.