1st add the release-package manually using rpm-ostree install https://sth/release-package --> reboot
2nd remove the package which you just added.
3rd do rpm-ostree install release-package (it now fetches the release package from the package source you have removed in 2nd)
no painful release upgrades.
I think I get it, there is no need to write own packages, it is just that rpmfusions manual is bullshit, and the writer probably did not even realize it as it hits back as early as the next release change.
conesphere.social is proudly running via podman-tools/podman/coreos now. :) I do like that setup on small scaled and standalone servers.
Phew! This is such a moment when your stomach hurts badly. A moment when you realize that it was the right decision to forbid TCP/80 on all gitlab-runner boxes, and the question starts to think in: "Who else might be accidentally pulling libraries for @cryptpad via http because of insane git defaults?"
Ouch! This might be interesting... As a matter of fact I do operate a project has the exact need of staying Redhat compatible. If that project is moving towards Stream then fine otherwise it will get very interesting soon.