Zen

Source string Source string

461/10000 · 461

The string is read-only.

English Actions
If you are upgrading across two releases or fewer from Fedora Linux 20 or later, this step should be unnecessary. If you are upgrading from an older Fedora Linux or upgrading across three or more releases, you may need to import the signing key for the target release.
If it turns out not to be, you should be able to import keys like so:
# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-23-x86_64
, replacing "23" and "x86_64" with the new Fedora Linux version and your architecture, respectively.
You can also find package signing keys for currently-supported releases https://getfedora.org/keys/[here]. Keys for EOL releases can be found https://getfedora.org/keys/obsolete.html[here]. Click _Primary_ (or _Secondary_, if you are using a secondary architecture), and you will see _Get it from: Fedora Project_, where _Fedora Project_ is a link. Copy that URL, and run:
# rpm --import (url)
to install the key. On old releases, `rpm` may have trouble doing this; if that happens, download the file with `curl -o` or `wget` and import the downloaded file.
Clean the cache
Then remove all traces of the version you are leaving from the dnf cache in `/var/cache/dnf`.
# dnf clean all
Upgrade all packages
*Never upgrade on battery power* + Never run the upgrade operation on battery power! Always connect to the mains, if using a laptop. However, if your system does have a battery, it's a good idea to ensure it's charged and connected in case of a power outage during the upgrade.
*Do not interrupt an upgrade for any reason* + Once a live upgrade is started, do not stop the upgrade by rebooting, killing the process, or by any other method until it is complete. Interrupting an upgrade will cause the affected system to be in a mixed state -- partially the old release and partially the new release. In this state, the system will not be reliable and will not operate as expected. You can try running `dnf distro-sync` and `package-cleanup --problems` to try and fix the problems.
Run the upgrade command:
# dnf --releasever=<target_release_number> --setopt=deltarpm=false distro-sync
*Dependency issues* + If you experience any dependency problems, you have to solve them manually. 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. Usually you will be able to reinstall the important package once the upgrade is complete.
If it seems like you must remove a package with many dependencies, especially ones that look important, please be careful. If you are attempting to upgrade across multiple releases, try a smaller jump to see if that avoids the problem.
If you are at all unsure in any way, ask for help on a mailing list, forum or IRC before removing packages.
5. Make sure Fedora Linux is upgraded
Distro-sync will usually take care of upgrades for the third party repositories you have enabled as well. Confirm with `dnf repolist` after the upgrade process is over. `dnf` might complain about conflicts or requirements. That is probably because you have used non-standard repositories or installed non-standard packages manually. Try to guess which packages cause the problem (or at least is a part of the dependency chain) - uninstall them and try again. Remember to install the packages again if they are essential.
Ensure that all (new) essential packages from the new version are installed with
# dnf group upgrade 'Minimal Install'
You might want to update other groups too, see
# dnf group list -v
For example
# dnf group upgrade "GNOME Desktop" \
"Development Tools" "Sound and Video" \
"Games and Entertainment" "Administration Tools" \
"Office/Productivity" "System Tools"
6. Preparing for reboot
Before booting you should usually install the bootloader from your new grub by running
/usr/sbin/grub2-install BOOTDEVICE
where BOOTDEVICE is often `/dev/sda` or `/dev/vda` for some virtual machine installs. If you have more than one hard disk, make sure you use the correct device!
If you get an error (e.g. `/dev/sda does not have any corresponding BIOS drive`) from that, then try `/usr/sbin/grub2-install --recheck BOOTDEVICE`.

Loading…

User avatar None

Source string added
*Dependency issues* + If you experience any dependency problems, you have to solve them manually. 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. Usually you will be able to reinstall the important package once the upgrade is complete.
4 years ago
Browse all string changes

Things to check

Unpluralised

The string is used as plural, but not using plural forms

Reset

Glossary

English English
No related strings found in the glossary.

5994814 String information

Source string description
type: Plain text
Flags
no-wrap, read-only
Source string location
./pages/upgrading-fedora-online.adoc:165
String age
4 years ago
Last updated
a year ago
Source string age
4 years ago
Translation file
pot/master/pages/upgrading-fedora-online.pot, string 55