Yum updating redhat repositories
If you are upgrading from an older Fedora or upgrading across three or more releases, you may need to import the signing key for the target release.
If you switch to Rawhide from a standard Fedora release (or vice versa) then most of the time you will need to install the Rawhide release RPMs from the 3rd party repository as well (or the standard ones, if switching back).
Note that the upgrade is likely to fail if there are outdated dependencies from packages not backed by a dnf repository or backed by a repository which isn't ready for the new version.
It is a good idea to do the upgrade outside the graphical environment.
Log out of your graphical desktop and then A small script named fedora-upgrade is available which aims to automate the process outlined below.
If you are upgrading using Dnf and it shows any general dependency issues, please file them in Bugzilla.
But please read this page, all references pages and search the mailing list archives before filing bugs. If you want to help make live upgrades work smoothly, join the Live Upgrade Special Interest Group.Also you might want to remove some cache files that are no longer used, for example files from older Fedora releases in the following directories: Note: the release-specific notes for End of life releases are on the EOL packager manager upgrade page.If you are upgrading to a final release from an Alpha, Beta, or release candidate, please see Upgrading from pre-release to final.These are often caused by packages being retired in the newer release, but not properly obsoleted.Often it is enough to remove several problematic package(s).You may find that a package you care about depends on a package that must be removed for the upgrade to proceed.