"nothing provides system-release(32)" rebase with rpmfusion repos installed

Hello SB,

The rpmfusion Configuration guide for Silverblue suggests enabling the repos using the repo rpms.

Trying to trigger a rebase from F32 to F33 with these repo rpms installed will show the following problems:

 Problem 1: conflicting requests
  - nothing provides system-release(32) needed by rpmfusion-nonfree-release-32-1.noarch
 Problem 2: conflicting requests
  - nothing provides system-release(32) needed by rpmfusion-free-release-32-1.noarch

What’s the best practice to enable rpmfusion on SB to allow a rebase?

For the moment the safest bet is to remove rpm-fusion and layered packages > rebase > install rpm-fusion for next release > reboot > install packages again from rpm fusion > reboot (total of two reboots instead of the usual one for a rebase).

That won’t work because the “old repository rpm” is nowhere to be found in the new 33 repository. What I do is instead of installing the rpm for the repository, I just put the repo file in /etc/yum.repos.d, that way, it’ll be able to find packages installed from the rpmfusion for either 32 or 33. I also have to import the version rpm keys inside /etc/pki/rpm-gpg.

Or just be patient and wait for rpmfusion packages for 33.

The advantages to using repo files and pgp keys is that you can easily rebase between major fedora versions and not having to uninstall all the packages manually.

Good point. I usually only go forward unless something is really broken. I always pin the previous major branch before a rebase to a new major release. If you are doing a lot of testing or need to use more than one release, I can see where your approach is useful.