rpmfusion repo is not enabled on images beginning Oct 5th 2024

[Renner0E]

I just noticed this when I build my own image with blue-build FROM bazzite:latest that packages from rpmfusion can not be installed because the repo is not enabled on the image.

bazzite:latest also doesn't have any patented codecs related -freeworld packages installed

rpm -qa | grep -- -freeworld

last good image with rpmfusion
✅ ghcr.io/ublue-os/base-main:20241004

podman run -it ghcr.io/ublue-os/base-main:20241004 bash

rpm -qa | grep rpmfusion
rpmfusion-nonfree-release-40-1.noarch
rpmfusion-free-release-40-1.noarch

bad images starting from Oct 5th with rpmfusion missing
❌ ghcr.io/ublue-os/base-main:20241005

podman run -it ghcr.io/ublue-os/base-main:20241005 bash

rpm -qa | grep rpmfusion

[fiftydinar]

Universal Blue switched from RPMFusion to negativo17 repo.

It results in less potential package skew, while downstream users have to layer RPMFusion themself & then fiddle with disabling/enabling negativo17 repo, as it's not compatible with RPMFusion.

mesa-freeworld is not installed, because negativo's mesa contains the needed freeworld patch.

Regarding other codecs, negativo also covers this well.

See:
#636

[Renner0E]

Thanks for the quick answer.

It results in less potential package skew, while downstream users have to layer RPMFusion themself & then fiddle with disabling/enabling negativo17 repo, as it's not compatible with RPMFusion

Is this documented somewhere? So I can enable rpmfusion repos in blue-build.
I want to install the mpd package. It's only available on rpmfusion.

[fiftydinar]

Is this documented somewhere? So I can enable rpmfusion repos in blue-build. I want to install the mpd package. It's only available on rpmfusion.

Officially by Universal Blue, no. Only Discord chat & GitHub discussion is a source at the moment.

About switching to RPMFusion repo, you may take a look here.
Some users asked a question about this in BlueBuild Discord server:
https://www.answeroverflow.com/m/1292525826696548513

[bsherman]

I've been spending time today PR/issue cleanup.

Bottom line, looks like this happened but a corresponding docs update was not completed.

We need to update all the docs to reflect the correct state. This includes repo READMEs/scripts, websites, and our discourse wiki docs.