The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing âdnf clean packagesâ.
Error: GPG check FAILED
I do not understand GPG Key are configured as Ubuntu. Where do I find and download new GPG keys which should be replaced in Fedora Release (Modern) :: Fedora Docs
It is always recommended (and supported) to only upgrade 1 or 2 levels at a time. It may work to upgrade 3 levels at once but that is not supported nor recommended by fedora.
I would first (temporarily) disable any 3rd party repos in use, then do the OS upgrade. After the upgrade is completed and successful then you could enable the 3rd party repos needed and upgrade their software as well.
Since the error is github related and GH is 3rd party that seems likely to fix that error.
I found a application called Package http://ww38.packagekit.org/. Very usefull as it is GUI and where it is possible to remove package by name like GH.
Thank you very much r@h.c (email removed_signed @augenauf)
Licensed under the GNU General Public License Version 2
Only drawback to that is you are on 34 and wanting to upgrade to 37 so installing another 3rd party package may cause more problems. Dnf is easy to work with even enabling or disabling repos so I follow the KISS principle. Keep It SimpleâŚ
With that list I would suggest that you use the --disablerepo option for each of the copr and the gh-cli repos with your sudo dnf upgrade --refresh and with the sudo dnf system-upgrade download commands to disable those repos and avoid interfering with the OS upgrade.
Alternatively you could use dnf config-manager --disable copr:* gh-cli which would disable those repos, then do the system-upgrade all the way through. If you do it this way they can be re-enabled by replacing --disable in that command line with --enable
The first way only disables the repo for the one command where that disablerepo option is used. The second way (semi)permanently disables the repo until it is re-enabled. I personally prefer the second method when using several commands in a row that need the repo disabled, but it is up to you.
Error:
Problem 1: package Rack-v1-1.1.6-13.fc34.x86_64 requires libGLEW.so.2.1()(64bit), but none of the providers can be installed
libGLEW-2.1.0-9.fc34.x86_64 does not belong to a distupgrade repository
problem with installed package Rack-v1-1.1.6-13.fc34.x86_64
Problem 2: package annobin-9.79-5.fc34.x86_64 requires (gcc >= 11 with gcc < 12), but none of the providers can be installed
gcc-11.3.1-2.fc34.x86_64 does not belong to a distupgrade repository
problem with installed package annobin-9.79-5.fc34.x86_64
Problem 3: package compat-golang-github-google-v35-devel-35.2.0-1.fc34.noarch requires golang-ipath(github.com/google/go-github) = 35.2.0-1.fc34, but none of the providers can be installed
golang-github-google-devel-35.2.0-1.fc34.noarch does not belong to a distupgrade repository
problem with installed package compat-golang-github-google-v35-devel-35.2.0-1.fc34.noarch
Problem 4: package protonvpn-gui-1.7.0-11.noarch requires python(abi) = 3.9, but none of the providers can be installed
python3-3.9.13-1.fc34.x86_64 does not belong to a distupgrade repository
problem with installed package protonvpn-gui-1.7.0-11.noarch
Problem 5: package protonvpn-1.0.0-3.noarch requires protonvpn-cli, but none of the providers can be installed
package python3-protonvpn-nm-lib-3.8.0-6.fc34.noarch conflicts with protonvpn-cli < 3.11.0 provided by protonvpn-cli-2.2.11-6.fc37.noarch
protonvpn-cli-3.11.1-4.noarch does not belong to a distupgrade repository
problem with installed package python3-protonvpn-nm-lib-3.8.0-6.fc34.noarch
problem with installed package protonvpn-1.0.0-3.noarch
Problem 6: package python3-3.9.13-1.fc34.x86_64 requires python3-libs(x86-64) = 3.9.13-1.fc34, but none of the providers can be installed
package python3-proton-client-0.7.1-2.noarch requires python(abi) = 3.9, but none of the providers can be installed
python3-libs-3.9.13-1.fc34.x86_64 does not belong to a distupgrade repository
problem with installed package python3-proton-client-0.7.1-2.noarch
(try to add ââallowerasingâ to command line to replace conflicting packages or ââskip-brokenâ to skip uninstallable packages)
As previously noted, upgrades are always recommended to be done one release version at a time, and only supported for 2 versions.
Have you tried sudo dnf system-upgrade download --releasever=35?
Have you tried sudo dnf system-upgrade download --releasever=35 --disablerepo=gh-cli as suggested?
Have you looked at man dnf system-upgrade for assistance in how it functions and how to format your commands?
Have you considered that it may be necessary to remove the conflicting packages before the upgrade can be properly completed?
Problem 1: package compat-golang-github-docker-distribution-devel-2.8.0~beta.1-1.20220203gitb609265.fc34.noarch requires golang-ipath(github.com/distribution/distribution/v3) = 2.8.0~beta.1-1.20220203gitb609265.fc34, but none of the providers can be installed
golang-github-distribution-3-devel-2.8.0~beta.1-1.20220203gitb609265.fc34.noarch does not belong to a distupgrade repository
problem with installed package compat-golang-github-docker-distribution-devel-2.8.0~beta.1-1.20220203gitb609265.fc34.noarch
Problem 2: package protonvpn-gui-1.7.0-11.noarch requires python(abi) = 3.9, but none of the providers can be installed
python3-3.9.13-1.fc34.x86_64 does not belong to a distupgrade repository
problem with installed package protonvpn-gui-1.7.0-11.noarch
Problem 3: package protonvpn-1.0.0-3.noarch requires protonvpn-cli, but none of the providers can be installed
package python3-protonvpn-nm-lib-3.8.0-6.fc34.noarch conflicts with protonvpn-cli < 3.11.0 provided by protonvpn-cli-2.2.6-2.fc35.noarch
package python3-protonvpn-nm-lib-3.8.0-6.fc34.noarch conflicts with protonvpn-cli < 3.11.0 provided by protonvpn-cli-2.2.11-3.fc35.noarch
protonvpn-cli-3.11.1-4.noarch does not belong to a distupgrade repository
problem with installed package python3-protonvpn-nm-lib-3.8.0-6.fc34.noarch
problem with installed package protonvpn-1.0.0-3.noarch
Problem 4: package python3-3.9.13-1.fc34.x86_64 requires python3-libs(x86-64) = 3.9.13-1.fc34, but none of the providers can be installed
package python3-proton-client-0.7.1-2.noarch requires python(abi) = 3.9, but none of the providers can be installed
python3-libs-3.9.13-1.fc34.x86_64 does not belong to a distupgrade repository
problem with installed package python3-proton-client-0.7.1-2.noarch
(try to add ââallowerasingâ to command line to replace conflicting packages or ââskip-brokenâ to skip uninstallable packages)
Work down that list, one package at a time, removing the conflicted packages that are not part of fedora until the conflicts are cleaned up.
These 2 in particular are clearly telling you the problem compat-golang-github-docker-distribution-devel-2.8.0~beta and golang-github-distribution-3-devel-2.8.0~beta.
Both of which were installed from github.
The remainder seem related to protonvpn packages their need for python 3.9 on fedora 34 with python 3.11 on fedora 37. Removing the protonvpn packages will probably clear all that up.
Always use the recommended sudo dnf upgrade --refresh step first to verify that fedora is up to date, and maybe add sudo dnf distro-sync --refresh --allowerasing to clean up other packages before even starting the system-upgrade.
There are many cases where version upgrades are not possible with 3rd party software installed and some of those can be seen with a quick search on this forum. It is up to the user to read the error messages and learn what the corrective actions are with experience and over time.