Fedora 41 package upgrade fails
I am looking for help to solve this problem when upgrading fedora packages to a new version, because when I try to upgrade I get the following failures ( I am currently on fedora 41 workstation also this information is shown in the neofetch attached as an image ) [[enter image description here](https://i.sstatic.net/eAsrYUmv.png)](https://i.sstatic.net/pzlwXc9f.png)
I tried to do a (sudo dnf -y update) as I normally do in order to update the packages and then do the upgrade but from the beginning I got it wrong
Looking at those various images it seems you have many repos enabled that are NOT fedora repos. The errors seem related to trying to get data from several non-fedora repos.
Sublime
Fedora 41 VirtualBox (an oracle repo)
and signature errors on the google chrome repo
I also see ‘fedora updates testing’ and ‘rpmfusion nonfree updates testing’ enabled which should have been disabled by default when fedora was updated to the final release version.
To see the full list of enabled repos in a form that is usable please run dnf repolist and post that output as text that you copy and paste here. Keep the on-screen formatting by highlighting the text you paste then click the </> button on the toolbar
Probably most of these could be disabled and only enabled when necessary.
copr:copr.fedorainfracloud.org:atim:ytop Copr repo for ytop owned by atim
copr:copr.fedorainfracloud.org:group_kernel-vanilla:stable Copr repo for stable owned by @kernel-vanilla
coprdep:copr.fedorainfracloud.org:group_kernel-vanilla:fedora Copr copr.fedorainfracloud.org/@kernel-vanilla/stable runtime dependency #1 - @kernel-vanilla/f
Dropbox Dropbox Repository
gitlab.com_paulcarroty_vscodium_repo download.vscodium.com
nodesource Node.js Packages for Fedora Linux 30 - x86_64
remi Remi's RPM repository - Fedora 41 - x86_64
rpmfusion-free-updates-testing RPM Fusion for Fedora 41 - Free - Test Updates
rpmfusion-nonfree-updates-testing RPM Fusion for Fedora 41 - Nonfree - Test Updates
rpmsphere RPM Sphere - Basearch
rpmsphere-noarch RPM Sphere - Noarch
s3-us-west-2.amazonaws.com_brave-rpm-release_x86_64_ Brave Browser
skype-stable Skype stable for Linux
sublime-text Sublime Text - x86_64 - Stable
sublime-text-dev Sublime Text - x86_64 - Dev
teams teams
teamviewer TeamViewer - x86_64
updates-testing Fedora 41 - x86_64 - Test Updates
virtualbox Fedora 41 - x86_64 - VirtualBox
yandex-browser yandex-browser
yandex-browser-beta yandex-browser-beta
You would know exactly which of those are required but none are directly supported by fedora. The 3 *-testing repos should definitely be disabled. The sublime-text-dev also (it was one of those with the errors you reported).
The virtualbox repo could be replaced and have fewer problems by installing VirtualBox from the rpmfusion repo. Doing so would ensure that updates always remain in sync with fedora.
The rpmsphere repo contains software that has caused problems for some but not all.
You have the brave-browser repo as well as s3-us-west-2.amazonaws.com_brave-rpm-release_x86_64_ and having 2 repos for the same browser can be a problem.
I guess that overall what I am suggesting is that you clean up the number of repos that are enabled full time, eliminate the unnecessary ones and ensure that only the ones that are truly needed are active. This avoids issues that occur when packages may conflict and/or the repos are out of sync.
Well then I remove these packages and everything would be fine with exactly which commands I would remove these packagescopr:copr.fedorainfracloud.org:atim:ytop Copr repo for ytop owned by atim copr:copr.fedorainfracloud.org:group_kernel-vanilla:stable Copr repo for stable owned by @kernel-vanilla coprdep:copr.fedorainfracloud.org:group_kernel-vanilla:fedora Copr copr.fedorainfracloud.org/@kernel-vanilla/stable runtime dependency #1 - @kernel-vanilla/f Dropbox Dropbox Repository gitlab.com_paulcarroty_vscodium_repo download.vscodium.com nodesource Node.js Packages for Fedora Linux 30 - x86_64 remi Remi's RPM repository - Fedora 41 - x86_64 rpmfusion-free-updates-testing RPM Fusion for Fedora 41 - Free - Test Updates rpmfusion-nonfree-updates-testing RPM Fusion for Fedora 41 - Nonfree - Test Updates rpmsphere RPM Sphere - Basearch rpmsphere-noarch RPM Sphere - Noarch s3-us-west-2.amazonaws.com_brave-rpm-release_x86_64_ Brave Browser skype-stable Skype stable for Linux sublime-text Sublime Text - x86_64 - Stable sublime-text-dev Sublime Text - x86_64 - Dev teams teams teamviewer TeamViewer - x86_64 updates-testing Fedora 41 - x86_64 - Test Updates virtualbox Fedora 41 - x86_64 - VirtualBox yandex-browser yandex-browser yandex-browser-beta yandex-browser-beta
You would use only the repo name in the first column of that listing.
From the docs for dnf5 the command is slightly different than it was with dnf4.
dnf5 config-manager setopt repoid1.enabled=1 repoid2.enabled=0
Sets override to enable repository identified by repoid1 and disable repository identified by repoid2.
For example, to disable the repo for remi the command would be sudo dnf config-manager setopt remi.enabled=0
You could manage each one with a single command as shown by the example command I quoted above from the docs.
