Should I Disable Third Party Repos Before Upgrade?

Ask Fedora
1

I have vscode repo that Microsoft one. Should I disable it before any upgrade?

1 Like
2

The upgrade process is made for the Fedora Repositories. It can resolve the dependencies of them.

Everything else can cause issues with the upgrade because of not having the information of the external repositories.

I think yes, it makes sense to deactivate and activate after the upgrade.

3

You also need to consider the packages from the third party repositories. Even when you disable the repository, they can still cause conflicts.

After disabling the third party repository, you can run dnf list --extras to see which packages doesn’t come from the active repositories. This also includes Fedora packages that has been discontinued.

3 Likes
4

I just run the command for testing purposes without disabling only extra repo that is vscode and I get this code and I’m not capable of understand what the result means

dnf list --extras
Updating and loading repositories:
 Fedora 41 - x86_64 - Updates           100% | 105.0 KiB/s |  22.1 KiB |  00m00s
 Copr repo for PyCharm owned by phracek 100% |   3.8 KiB/s |   2.1 KiB |  00m01s
 Fedora 41 - x86_64                     100% | 152.0 KiB/s |  26.4 KiB |  00m00s
 RPM Fusion for Fedora 41 - Free        100% |  38.3 KiB/s |   8.9 KiB |  00m00s
 RPM Fusion for Fedora 41 - Free - Upda 100% |  15.9 KiB/s |   8.2 KiB |  00m01s
 Visual Studio Code                     100% |  13.9 KiB/s |   1.5 KiB |  00m00s
 Fedora 41 - x86_64 - Updates           100% |   2.2 MiB/s |   3.3 MiB |  00m01s
 Visual Studio Code                     100% |   1.0 MiB/s | 101.7 KiB |  00m00s
Repositories loaded.
1 Like
5

It shows a list of packages not present in any active repository. In this case the list is empty. To see what comes from Visual Studio, you should disable that repository first.

2 Likes
6

I disabled and final result is this

dnf list --extras
Updating and loading repositories:
Repositories loaded.
Extra packages
code.x86_64 1.99.0-1743632525.el8 code
7

There are often issues with 3rd party repositories when using a new Fedora version. I usually remove 3rd party packages before upgrading and then reinstall once upgrade is working. If Visual Studio Code is essential to your use case, you could try installing it in the Live Installer environment or a virtual machine with F42 to be sure it works before upgrading.

8

Would adding all third-party repositories solely to a distrobox image be a workaround?

9

Hey guys, I just wanna make sure I don’t make a mess. This is my current repo situation:

    - 3 enabled (default):

fedora.repo
fedora-updates.repo
fedora-cisco-openh264.repo

    - 5 enabled (third-party):

_copr:copr.fedorainfracloud.org:phracek:PyCharm.repo
_copr:copr.fedorainfracloud.org:codifryed:CoolerControl.repo

brave-browser.repo
librewolf.repo
teamviewer.repo

    - 5 enabled (rpmfusion):

rpmfusion-free.repo
rpmfusion-free-updates.repo
rpmfusion-nonfree.repo
rpmfusion-nonfree-updates.repo
rpmfusion-nonfree-steam.repo

    - 5 disabled (and removed):

google-chrome.repo
fedora-updates-testing.repo
rpmfusion-free-updates-testing.repo
rpmfusion-nonfree-updates-testing.repo
rpmfusion-nonfree-nvidia-driver.repo

Extra packages
brotherlegacyusb.x86_64 1.1.1-0    <unknown>
hll2375dwpdrv.i386      4.0.0-1    <unknown>
viber.x86_64            23.2.0.3-2 <unknown>

Should I just disable all the repos (except the 3 default ones), run dnf list --extras and then remove ALL the extra packages?

After that I should be ready to upgrade to F42?

1 Like