Managing repository before I upgrade to Fedora 35

I’m quite surprised by the long list of repositories I have. Some doubts I want to clear about them are:

  1. Why do I have Kubernetes when I don’t use Kubernetes? Can I remove it?
  2. My guess is, Chromium uses by google-chrome repository for installation, right? If so, I can’t remove it.
  3. Is there a way to list all packages which I have installed from repo like debuginfo, source, testing, etc because they might create problems? I might have installed packages to generate coredump. Is there a way to track any/all such debugging packages?
  4. Can I remove all testing, debugging and source repos all together which are already disabled?
  5. Which repo needs to be disabled in order to safely upgrade from F34 to F35? Command?
pranav@fedora ~> dnf repolist all | grep -i 'disabled'
fedora-cisco-openh264-debuginfo             Fedora 34 openh264 (From Ci disabled
fedora-debuginfo                            Fedora 34 - x86_64 - Debug  disabled
fedora-modular-debuginfo                    Fedora Modular 34 - x86_64  disabled
fedora-modular-source                       Fedora Modular 34 - Source  disabled
fedora-source                               Fedora 34 - Source          disabled
google-chrome                               google-chrome               disabled
rpmfusion-free-debuginfo                    RPM Fusion for Fedora 34 -  disabled
rpmfusion-free-source                       RPM Fusion for Fedora 34 -  disabled
rpmfusion-free-updates-debuginfo            RPM Fusion for Fedora 34 -  disabled
rpmfusion-free-updates-source               RPM Fusion for Fedora 34 -  disabled
rpmfusion-free-updates-testing              RPM Fusion for Fedora 34 -  disabled
rpmfusion-free-updates-testing-debuginfo    RPM Fusion for Fedora 34 -  disabled
rpmfusion-free-updates-testing-source       RPM Fusion for Fedora 34 -  disabled
rpmfusion-nonfree-debuginfo                 RPM Fusion for Fedora 34 -  disabled
rpmfusion-nonfree-nvidia-driver             RPM Fusion for Fedora 34 -  disabled
rpmfusion-nonfree-nvidia-driver-debuginfo   RPM Fusion for Fedora 34 -  disabled
rpmfusion-nonfree-nvidia-driver-source      RPM Fusion for Fedora 34 -  disabled
rpmfusion-nonfree-source                    RPM Fusion for Fedora 34 -  disabled
rpmfusion-nonfree-steam                     RPM Fusion for Fedora 34 -  disabled
rpmfusion-nonfree-steam-debuginfo           RPM Fusion for Fedora 34 -  disabled
rpmfusion-nonfree-steam-source              RPM Fusion for Fedora 34 -  disabled
rpmfusion-nonfree-updates-debuginfo         RPM Fusion for Fedora 34 -  disabled
rpmfusion-nonfree-updates-source            RPM Fusion for Fedora 34 -  disabled
rpmfusion-nonfree-updates-testing           RPM Fusion for Fedora 34 -  disabled
rpmfusion-nonfree-updates-testing-debuginfo RPM Fusion for Fedora 34 -  disabled
rpmfusion-nonfree-updates-testing-source    RPM Fusion for Fedora 34 -  disabled
updates-debuginfo                           Fedora 34 - x86_64 - Update disabled
updates-modular-debuginfo                   Fedora Modular 34 - x86_64  disabled
updates-modular-source                      Fedora Modular 34 - Updates disabled
updates-source                              Fedora 34 - Updates Source  disabled
updates-testing-modular                     Fedora Modular 34 - x86_64  disabled
updates-testing-modular-debuginfo           Fedora Modular 34 - x86_64  disabled
updates-testing-modular-source              Fedora Modular 34 - Test Up disabled
pranav@fedora ~> dnf repolist all | grep -i 'enabled'
code                                        Visual Studio Code          enabled
copr:copr.fedorainfracloud.org:tgerov:vpcs  Copr repo for vpcs owned by enabled
fedora                                      Fedora 34 - x86_64          enabled
fedora-cisco-openh264                       Fedora 34 openh264 (From Ci enabled
fedora-modular                              Fedora Modular 34 - x86_64  enabled
kubernetes                                  Kubernetes                  enabled
nordvpn                                     NordVPN YUM repository - x8 enabled
nordvpn-noarch                              NordVPN YUM repository - no enabled
rpmfusion-free                              RPM Fusion for Fedora 34 -  enabled
rpmfusion-free-updates                      RPM Fusion for Fedora 34 -  enabled
rpmfusion-nonfree                           RPM Fusion for Fedora 34 -  enabled
rpmfusion-nonfree-updates                   RPM Fusion for Fedora 34 -  enabled
teams                                       teams                       enabled
updates                                     Fedora 34 - x86_64 - Update enabled
updates-modular                             Fedora Modular 34 - x86_64  enabled
pranav@fedora ~>

if you issue the command “dnf repolist” it will show only the repos that are currently enabled. (the same list you got with dnf repolist all | grep -i 'enabled')
None of us can answer why you have all those repos enabled, but I will tell you a few commands to make certain you get a clean upgrade.

  1. Yes, that can be removed. Easiest is to either disable it or simply remove the containing file from /etc/yum.repos.d/

  2. No. The google-chrome repository is for google-chrome AKA Chrome. Chromium is from chromium.org

  3. no easy way other than by dnf commands.

  4. Not recommended unless you are 100% certain the .repo file will never be used and does not contain currently used repos. Several .repo files contain multiple repo definitions.
    For example, the rpmfusion-nonfree.repo file contains 4 different repo definitions, only one of which is enabled by default. Many others are simiilar.

For most I would simply disable them and not attempt to remove the .repo file. Once disabled they do not affect any future updates.

  1. I would recommend that you do the following commands to make certain the upgrade from fedora 34 to 35 goes smoothly.
sudo dnf config-manager --disable code copr:copr.fedorainfracloud.org:tgerov:vpcs kubernetes nordvpn* teams
sudo dnf upgrade --refresh
sudo dnf distro-sync

sudo dnf system-upgrade --releasever=35 download

If there are any errors when you try the download step then those need to be sorted before you can continue. Usually by removing the conflicting packages. The distro-sync usually avoids these errors.
Once the download completes you are ready to do the final reboot step and it should just work well.

I did all this (except for disabling repos since I have no unnecessary enabled repos) and my laptop upgraded to the branched version of fedora 35 flawlessly and has had no issues with it.

Once you have completed the upgrade you can use a command similar to the disable command to re-enable those repos you want to have active.

sudo dnf config-manager enable <repo name>

After upgrade the distro, doesn’t the repo upgrade its itself from “RPM Fusion for Fedora 34” to “RPM Fusion for Fedora 35”? Or do I have to do this manually?

Isn’t its a good idea to remove old repos since they were made for F34?

The rpmfusion repos are also managed by the update. and no, it is not necessary to remove any repos. Disabling them is enough if there is an issue with conflicts.

My suggestions above are so that there are no conflicts with out-of-tree repos while doing a release upgrade.

The repo files for the most part automatically adjust for the running version since almost all contain something like this in the repo url

[rpmfusion-free]
name=RPM Fusion for Fedora $releasever - Free
#baseurl=http://download1.rpmfusion.org/free/fedora/releases/$releasever/Everything/$basearch/os/
metalink=https://mirrors.rpmfusion.org/metalink?repo=free-fedora-$releasever&arch=$basearch

Notice the $releasever and $basearch variables used. Those select the current running version of the OS and the architecture used, which for fedora 35 will be “35” and “x86_64”.
The system-upgrade process requires that you tell it the releasever to download and it automatically finds the current architecture used. Once you have completed the upgrade then the repo files will work for the new version the same as they already work for fedora 34.

1 Like