Upgrading Fedora using yum

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(drop the note about a dracut/systemd bug that was fixed months ago)
(Fedora 19 -> Fedora 20: gpg key is already published)
(46 intermediate revisions by 20 users not shown)
Line 5: Line 5:
 
== Upgrading Fedora using yum directly ==
 
== Upgrading Fedora using yum directly ==
  
{{admon/warning| Version updates without using anaconda - such as the yum method described here - is unsupported and not recommended! |
+
{{admon/warning| Upgrading using the yum method described here is not recommended for new users.  Use FedUp instead |
  
The recommended installation method is with a boot media with the Anaconda installer as detailed in the [http://docs.fedoraproject.org/install-guide/ Installation Guide] or use [[PreUpgrade]]. [[PreUpgrade]] is a slightly different upgrade method where all the packages are downloaded before the system is rebooted into the Anaconda installer.
+
For upgrades to Fedora 18 and later, the recommended upgrade method is the [[FedUp]] tool. [[FedUp#How_Can_I_Upgrade_My_System_with_FedUp?|This section]] has instructions on using FedUp to upgrade.
 +
 
 +
For upgrades to Fedora 17 and earlier, the recommended installation method is with a boot media with the Anaconda installer as detailed in the [http://docs.fedoraproject.org/install-guide/ Installation Guide] or via [[PreUpgrade]]. [[PreUpgrade]] is a slightly different upgrade method where all the packages are downloaded before the system is rebooted into the Anaconda installer.
  
 
Although upgrades with yum do work, they are not explicitly tested as part of the release process by the [[QA|Fedora QA]] and are not documented in the [http://docs.fedoraproject.org/en-US/Fedora/{{FedoraVersion}}/html/Installation_Guide/index.html Fedora installation guide].  If you are not prepared to resolve issues on your own if things break, you should probably use the recommended installation methods instead.}}
 
Although upgrades with yum do work, they are not explicitly tested as part of the release process by the [[QA|Fedora QA]] and are not documented in the [http://docs.fedoraproject.org/en-US/Fedora/{{FedoraVersion}}/html/Installation_Guide/index.html Fedora installation guide].  If you are not prepared to resolve issues on your own if things break, you should probably use the recommended installation methods instead.}}
  
When upgrading with yum you don't get any help from Anaconda, but with a typical system it might be able to upgrade systems remotely over ssh and with limited downtime. (You will still need to reboot to get the new kernel and system libraries/services running).  
+
When upgrading with yum you don't get any help from FedUp or Anaconda, but with a typical system it might be able to upgrade systems remotely over ssh and with limited downtime. (You will still need to reboot to get the new kernel and system libraries/services running).  
  
 
A live upgrade with yum usually works well with a typical installation and when following the advice below.
 
A live upgrade with yum usually works well with a typical installation and when following the advice below.
Line 38: Line 40:
  
 
{{admon/tip|Find unused config files|Merge and resolve the changes found by the following script: <code>yum install rpmconf; rpmconf -a</code>
 
{{admon/tip|Find unused config files|Merge and resolve the changes found by the following script: <code>yum install rpmconf; rpmconf -a</code>
Now find and remove old config which nobody owns: <code>find /etc /var -name '*.rpm?*'</code>}}
+
Now find and remove old config which nobody owns: <code>find /etc /var -name '*?.rpm?*'</code>}}
  
 
Now is a good time to remove packages you don't use - especially non-standard packages.
 
Now is a good time to remove packages you don't use - especially non-standard packages.
Line 54: Line 56:
 
Note that the upgrade is likely to fail if there are outdated dependencies from packages not backed by a yum repository or backed by a repository which isn't ready for the new version.
 
Note that the upgrade is likely to fail if there are outdated dependencies from packages not backed by a yum 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  
+
It is a good idea to do the upgrade outside the graphical environment. Log out of your graphical desktop and then
 +
 
 +
==== fedora-upgrade ====
 +
 
 +
A small script named fedora-upgrade is available which aims to automate the process outlined below. To run it, do the following
 +
 
 +
<pre>$ sudo yum install fedora-upgrade
 +
$ sudo fedora-upgrade
 +
</pre>
 +
 
 +
 
 +
Alternatively, follow the manual steps:
  
 
==== Go to a text console ====
 
==== Go to a text console ====
Line 73: Line 86:
  
 
<pre>
 
<pre>
yum update yum
+
# yum update yum
 
</pre>
 
</pre>
  
Line 89: Line 102:
  
 
<pre>
 
<pre>
yum clean all
+
# yum clean all
 
</pre>
 
</pre>
  
Line 97: Line 110:
  
 
<pre>
 
<pre>
yum --releasever=<release_number_you_want_to_sync_to> distro-sync
+
# yum --releasever=<release_number_you_want_to_sync_to> distro-sync
 
</pre>
 
</pre>
  
Line 112: Line 125:
  
 
<pre>
 
<pre>
yum groupupdate Base
+
# yum groupupdate 'Minimal Install'
 
</pre>
 
</pre>
  
Line 118: Line 131:
  
 
<pre>
 
<pre>
yum grouplist
+
# yum grouplist
 
</pre>
 
</pre>
  
Line 124: Line 137:
  
 
<pre>
 
<pre>
yum groupupdate "GNOME Desktop Environment" \
+
# yum groupupdate "GNOME Desktop" \
"Development Tools" "Server Configuration Tools" \
+
    "Development Tools" "Sound and Video" \
"Hardware Support" "Sound and Video" \
+
    "Games and Entertainment" "Administration Tools" \
"Graphical Internet" "Fonts" \
+
    "Office/Productivity" "System Tools"
"Games and Entertainment" "Printing Software" \
+
"Administration Tools" "Office/Productivity" "System Tools"
+
 
</pre>
 
</pre>
  
Line 155: Line 166:
 
If you are upgrading to a final release from an alpha, beta, preview, or other [[Releases/Rawhide|Rawhide]] release, please see [[Upgrading from pre-release to final]].
 
If you are upgrading to a final release from an alpha, beta, preview, or other [[Releases/Rawhide|Rawhide]] release, please see [[Upgrading from pre-release to final]].
  
=== To development version ===
+
{{Anchor|Rawhide}}
 +
=== To rawhide ===
  
<pre>
+
See the [[Releases/Rawhide|Rawhide]] release page for more information on Rawhide.  
yum update yum
+
yum --releasever=rawhide distro-sync --nogpgcheck
+
</pre>
+
 
+
{{Anchor|16-17}}
+
=== Fedora 17 -> Fedora 18 ===
+
 
+
{{admon/warning||This references an unreleased version of Fedora.  The steps here may change before release.}}
+
 
+
First install the new Fedora 18 gpg key
+
 
+
rpm --import https://fedoraproject.org/static/DE7F38BD.txt
+
 
+
Upgrade all packages with
+
  
 
<pre>
 
<pre>
yum update yum
+
# yum install fedora-release-rawhide
yum clean all
+
# yum-config-manager --disable fedora updates updates-testing
yum --releasever=18 --disableplugin=presto distro-sync
+
# yum-config-manager --enable rawhide
 +
# yum update yum
 +
# yum --releasever=rawhide distro-sync --nogpgcheck
 
</pre>
 
</pre>
  
 +
{{Anchor|19-20}}
 +
=== Fedora 19 -> Fedora 20 ===
  
* rebuild rpm database
+
Install the new Fedora 20 gpg key and upgrade:
<pre>
+
# rpm --import https://fedoraproject.org/static/246110C1.txt
rpm --rebuilddb
+
# yum update yum
</pre>
+
# yum --releasever=20 distro-sync
  
* Due to [https://fedoraproject.org/wiki/Features/DisplayManagerRework DisplayManagerRework] you have to re-enable your display manager by
 
<pre>
 
systemctl enable --force xyzdm.service
 
</pre>
 
  
* If gdm does not offer you a login prompt (just a "spinner"), or if you have other issues related to polkit failing to start, run
+
{{Anchor|18-19}}
  
<pre>
+
=== Fedora 18 -> Fedora 19 ===
yum reinstall polkit systemd
+
systemctl restart polkit.service
+
systemctl restart gdm.service
+
</pre>
+
  
Related bugs:  {{bz|852403}} {{bz|841451}}
+
{{admon/warning|Incompatible systemd cgroups hierarchy layout|
 +
systemd in F19 lays out its cgroups hierarchy differently than in previous Fedora releases.
  
=== Fedora 16 -> Fedora 17 ===
+
The new hierarchy has some advantages, but it is incompatible with the old one. No live conversion of the hierarchy is performed during the package upgrade,
 +
so the upgraded systemd will not understand the previous state of the system correctly. This is known to affect the tracking of user sessions by systemd-logind ([[rhbug:962983|bug #962983]]).
  
{{admon/warning||There is a general warning about upgrading via. yum being unsupported [[Upgrading_Fedora_using_yum#Upgrading_Fedora_using_yum_directly | at the top of this page]]. However Fedora 17 is '''very special'''. You should '''seriously consider''' stopping now and just using anaconda via. DVD or preupgrade, unlike all previous releases it's what the yum/rpm developers recommend. Continue at your own risk. }}
+
Expect breakage in active user sessions and make sure to reboot soon after performing the upgrade. If your screen locks during the upgrade, you may not be able to log back in due to the cgroup changes. Running the upgrade in a screen(1) session has been reported as a workaround (re-attach from a vt). }}
  
First install the new Fedora 17 gpg key
+
Install the new Fedora 19 gpg key and upgrade:
 +
# rpm --import https://fedoraproject.org/static/FB4B18E6.txt
 +
# yum update yum
 +
# yum --releasever=19 distro-sync
  
  rpm --import https://fedoraproject.org/static/1ACA3465.txt
+
If you use Fedora ARM, run these commands instead:
 +
  # rpm --import https://fedoraproject.org/static/BA094068.txt
 +
# yum update yum
 +
# yum --releasever=19 distro-sync
  
Fedora 17 will locate the entire base operating system in /usr. The directories
+
{{Anchor|17-18}}
/bin, /sbin, /lib, /lib64 will only be symlinks:
+
+
/bin → /usr/bin
+
/sbin → /usr/sbin
+
/lib → /usr/lib
+
/lib64 → /usr/lib64
+
  
Some reasoning behind this change is outlined here:
+
=== Fedora 17 -> Fedora 18 ===
+
http://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge
+
  
Currently installed systems need some manual steps to convert the current system
+
{{admon/note | Recommended Upgrade Method (Fedora 17 and newer)|Upgrading with FedUp is the recommended way to upgrade your system!Please check [https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F How Can I Upgrade My System with FedUp?]}}
to match the layout of Fedora 17. After that, the system can continue to
+
be updated with YUM as usual.
+
  
Some RPM packages in Fedora 17 are carrying an RPM dependency guard, which
 
will make sure, they can only be installed when /bin, /sbin, /lib, /lib64 are
 
symlinks and not directories like in Fedora 16 and older.
 
  
The installed system’s base filesystem layout can not be safely altered, while
+
'''Note: One user has reported problems trying to upgrade an Intel Mac UEFI installation using this method, including the manual bootloader migration.''' [http://anee.me/dont-update-fedora-17-to-18-using-yum-on-macbook-pro/ Read more]
the system itself is running on top of it. Dracut, the initramfs used to find
+
and mount the root filesystem, can be instructed to convert the filesystem to
+
match Fedora 17’s expectations.
+
 
+
If your system has a split-off /usr, a separate mount point, the dracut /usr
+
mount conversion logic might not work. If /usr resides on the net, then you should add "rd.neednet=1" and the network settings like "ip=dhcp" on the kernel command line.
+
/usr on iSCSI, FCoE, NBD also is supported, as long as “netroot=...” is
+
specified on the kernel command line for these disks (see man dracut.kernel(7)).
+
If you have /usr on LVM, MD raid or DM raid, make sure the kernel command line has either all settings like "rd.lvm.lv=..." to ensure the /usr device is accessible in dracut or just remove all restrictions like "rd.lvm...", "rd.md...", "rd.dm...". Either way, you should probably use anaconda to update, if you are experiencing problems with a separate /usr.
+
 
+
If you have /var on a separate partition, you will have to manually convert "/var/run" and "/var/lock" to a symbolic link.
+
 
+
# mv -f /var/run /var/run.runmove~
+
# ln -sfn ../run /var/run
+
# mv -f /var/lock /var/lock.lockmove~
+
# ln -sfn ../run/lock /var/lock
+
 
+
Here are the steps to prepare your system, to convert it, and to be able to
+
continue updating your installed system with yum:
+
 
+
Download and install the most recent dracut packages:
+
# yum update dracut
+
 
+
You should at least have [http://harald.fedorapeople.org/downloads/dracut/dracut-009-15.fc15/dracut-009-15.fc15.noarch.rpm dracut-009-15.fc15] for Fedora 15 or [https://admin.fedoraproject.org/updates/dracut-013-22.fc16 dracut-013-22.fc16] for Fedora 16.
+
 
+
Turn off any "hostonly" settings in /etc/dracut.conf*, if you turned on "hostonly".
+
 
+
Update the installed initramfs image for your current kernel, and instruct
+
dracut to include the dracut module to convert your current filesystem:
+
# dracut --force --add convertfs
+
 
+
If your system has a split-off /usr, a separate mount point, and you don't know the kernel command line parameter to add, you can also try (dracut tries to generate them internally), but you have to install at least [https://admin.fedoraproject.org/updates/dracut-018-55.git20120606.fc16 dracut-018].
+
# dracut -H --force --add convertfs
+
 
+
If dracut detects ‘rd.convertfs’ on the kernel command line at bootup, it starts
+
the filesystem conversion of the root filesystem. If it is already converted, it will just do nothing.
+
 
+
{{admon/warning||<code>dracut</code> will by default update the initramfs for the currently running kernel. Make sure that no new kernel has been installed since last boot and that you really will boot into the updated initramfs.}}
+
 
+
Change the following kernel commandline parameter directly in the bootloader
+
menu, which is shown during bootup, or edit the line in <code>/etc/grub*.cfg</code>  to remove ro and rhgb and append <code>rw rd.info rd.convertfs enforcing=0</code>
+
 
+
Explanation of the options:
+
 
+
- remove “ro” (read only)
+
- append “rw” (read write) to let dracut mount your root filesystem writeable
+
- remove “rhgb” (Red Hat graphical boot) to disable the graphical bootsplash
+
- append “rd.info” to get a more verbose output from dracut
+
- append “rd.convertfs” to enable the /usr-move conversion script in dracut
+
- append “enforcing=0” to disable SELinux enforcement
+
 
+
During bootup, dracut will now convert your filesystem, and /lib, /lib64, /bin
+
and /sbin should then all be symbolic links to the corresponding directories in
+
/usr.
+
 
+
After the conversion, the system needs to be immediately updated to Fedora 17. No
+
packages from Fedora 16 or Fedora 15, or older rawhide packages must be installed anymore.
+
Make sure to disable any Fedora 15 and Fedora 16 repositories in yum!
+
 
+
Any files with conflicting names, which the conversion could not resolve, will
+
be backed up to files named *.usrmove~ residing in /usr/lib, /usr/lib64,
+
/usr/bin and /usr/sbin.
+
 
+
Verify that dracut really completed the conversion. The log messages, which dracut has generated during bootup, can be retrieved with:
+
# dmesg | grep dracut
+
 
+
After a successful conversion, revert the changes made to the kernel command
+
line in the bootloader config file /etc/grub*.cfg.
+
 
+
Then run,
+
 
+
# rm -f /var/lib/rpm/__*
+
# rpm --rebuilddb
+
# yum --releasever=17 update rpm
+
# rm -f /var/lib/rpm/__*
+
# rpm --rebuilddb
+
# yum --releasever=17 --disableplugin=presto distro-sync
+
# fixfiles onboot 
+
 
+
After upgrading, all should be set and done.
+
 
+
Have fun with your system and say “Good bye” to /bin, /sbin, /lib, /lib64 and
+
meet them in /usr.
+
 
+
{{Anchor|15-16}}
+
 
+
=== Fedora 15 -> Fedora 16 ===
+
 
+
First install the new fedora 16 gpg key. You may wish to verify this package against  https://fedoraproject.org/keys and the fedora ssl certificate.
+
 
+
<pre>
+
rpm --import https://fedoraproject.org/static/A82BA4B7.txt
+
</pre>
+
 
+
Next run {{command|chkconfig --list}} and note the enabled services; you will need to re-enable these with {{command|systemctl enable ''xxxxx''.service}} after you reboot, as the {{package|sysvinit}} settings aren't propagated into {{package|systemd}}. See [http://fedoraproject.org/wiki/Common_F16_bugs#Upgrade_from_previous_releases_resets_the_enablement_status_of_services release notes] for more details.
+
 
+
Upgrade all packages with
+
 
+
<pre>
+
yum update yum
+
yum clean all
+
yum --releasever=16 --disableplugin=presto distro-sync
+
</pre>
+
 
+
{{admon/warning|Bootloader change|After the upgrade, you will have the {{package|grub2}} and {{package|grub-efi}} packages installed and the {{package|grub}} package removed. However, grub will still be installed to the MBR and booting should still work. You can follow the instructions below to switch to grub2 if you choose. If installed, the {{package|firstaidkit-plugin-grub}} package may prevent the upgrade; do simply remove that package if that is the case.}}
+
 
+
If your system uses a BIOS, or you installed Fedora via BIOS emulation mode on an EFI system (not native EFI mode), you can switch to Fedora 16's supported grub2 bootloader with the following instructions. If your system was installed by native EFI boot, do not switch to grub2, as its EFI support is still unreliable. Fedora 16's supported bootloader for native EFI installations is still grub-legacy, so you should simply continue to use the system without making any special changes to the bootloader configuration.
+
 
+
To switch to grub2, run the command {{command|su -c '/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg'}}, then proceed as described [[#6._Preparing_for_reboot|above]] with reinstalling the bootloader, but call {{command|grub2-install /dev/XXX}} instead of{{command| grub-install /dev/XXX}}.
+
 
+
Known you upgrade -specific issues (for common problems, see references above):
+
* Bug [https://bugzilla.redhat.com/show_bug.cgi?id=743022 743022] - F15->F16 yum update fails with IMSM (BIOS) raid
+
 
+
 
+
{{Anchor|14-15}}
+
 
+
=== Fedora 14 -> Fedora 15 ===
+
 
+
First install the new fedora 15 gpg key. You may wish to verify this package against  https://fedoraproject.org/keys and the fedora ssl certificate.
+
 
+
<pre>
+
rpm --import https://fedoraproject.org/static/069C8460.txt
+
</pre>
+
 
+
Upgrade all packages with
+
 
+
<pre>
+
yum update yum
+
yum clean all
+
yum --releasever=15 --disableplugin=presto distro-sync
+
</pre>
+
 
+
* Do not run this from within an X terminal. Testing shows that X might hang while updating bitmap font packages.
+
* There exist .drpms, but they don't match, due to a format change, so better disable the presto plugin by adding the option "--disableplugin=presto" (without quotes) when running yum.
+
* The F15 <code>screen</code> client is not capable of attaching to F14 <code>screen</code> sessions.  Thus, if you want to run the upgrade under <code>screen</code>, you should either upgrade <code>screen</code> itself in a separate operation or make a separate copy of <code>screen</code> to use throughout the process.
+
* mysql 5.5.20 shipped with F15 uses InnoDB as default storage engine. After upgrading, mysqld could refuse to start-up with error ''Unknown/unsupported storage engine: InnoDB'' if argument ''skip-innodb'' is given on command line or configuration file ''/etc/my.cnf''. Workarounds are removing the line (InnoDB will be run as default engine), or adding ''default-storage-engine'' command options specifying some other storage engine.
+
 
+
==== VirtualBox guest upgrades ====
+
The steps above work perfectly for upgrading a Fedora 14 guest to Fedora 15, but you also need to remove the Guest Additions. If you forget, F14 -> F15 upgrades will seem to fail after the first reboot. If that happens, log in to the console with CTRL+ALT+F2 and reinstall the guest additions manually:
+
 
+
<pre>
+
mount /dev/cdrom /media
+
# if /dev/cdrom does not exist, try:
+
# mount /dev/sr0 /media
+
/bin/sh /media/VBoxLinuxAdditions.run
+
reboot
+
</pre>
+
 
+
{{Anchor|13-14}}
+
 
+
=== Fedora 13 -> Fedora 14 ===
+
 
+
First install the new fedora 14 gpg key. You may wish to verify this package against  https://fedoraproject.org/keys and the fedora ssl certificate.
+
 
+
<pre>
+
rpm --import https://fedoraproject.org/static/97A1071F.txt
+
</pre>
+
 
+
Upgrade all packages with
+
 
+
<pre>
+
yum update yum
+
yum clean all
+
yum --releasever=14 distro-sync
+
</pre>
+
  
* If using VirtualBox from the Oracle repository, you must remove the VirtualBox-3.1 package before upgrading. After the upgrade is finished, install VirtualBox-3.2.
+
# Install the new Fedora 18 gpg key: {{command|su -c 'rpm --import https://fedoraproject.org/static/DE7F38BD.txt'}}
 +
# If you are using SELinux in Enforcing mode, make sure your selinux-policy is up to date: {{command|su -c 'yum update selinux-policy'}}
 +
# Upgrade all packages:
 +
## {{command|su -c 'yum update yum'}}
 +
## {{command|su -c 'yum clean all'}}
 +
## {{command|su -c 'yum --releasever<nowiki>=</nowiki>18 --disableplugin<nowiki>=</nowiki>presto distro-sync' }} '''It is recommended that updates be enabled for this step, for best results.'''
 +
# Rebuild rpm database: {{command|su -c 'rpm --rebuilddb'}}, or rpm -qa will not work due to an upgrade of rpm
  
If you are running SELinux you may be locked out of your machine and required to boot to single user mode to fix up your machine. [[rhbug:702865|Redhat bug 702865]] describes a fix as:
+
If you used an outdated <code>selinux-policy</code> package in Enforcing mode during the upgrade, you may notice errors in the yum output when several packages attempt to create users and/or groups, and after the upgrade you may have problems related to these packages, including issues with logging in via GDM (you may just see a spinning cursor) and/or performing actions requiring administrative privileges. This is a result of [[rhbug:844167|bug #844167]]. If you have this problem, you should re-install the affected packages with {{command|su -c 'yum reinstall (packagenames)'}}, and then reboot. Affected packages may include libvirt-daemon and polkit: {{command|su -c 'yum reinstall libvirt-daemon polkit'}}
<ol>
+
<li><code>setenforce 0</code>
+
<li><code>yum remove selinux-policy selinux-policy-targeted</code>
+
<li><code>rm -rf /etc/selinux/targeted</code>
+
</ol>
+
  
If, after upgrading you want selinux back:
+
Due to [[Features/DisplayManagerRework]], the upgrade may leave you without a display manager enabled. To solve this problem, use {{command|su -c 'systemctl enable ''yourdm''.service'}}, replacing ''yourdm'' with the display manager you intend to use, e.g. <code>gdm</code> or <code>kdm</code>.
<ol>
+
<li><code>yum install selinux-policy selinux-policy-targeted</code>
+
<li><code>fixfiles restore</code>
+
<li><code>reboot</code>
+
</ol>
+
  
 
=== Upgrading from legacy end of life (EOL) Fedoras ===
 
=== Upgrading from legacy end of life (EOL) Fedoras ===

Revision as of 07:10, 4 September 2013

This page contains information explaining how to upgrade Fedora using yum.

Contents

Upgrading Fedora using yum directly

Warning (medium size).png
Upgrading using the yum method described here is not recommended for new users. Use FedUp instead
For upgrades to Fedora 18 and later, the recommended upgrade method is the FedUp tool. This section has instructions on using FedUp to upgrade.

For upgrades to Fedora 17 and earlier, the recommended installation method is with a boot media with the Anaconda installer as detailed in the Installation Guide or via PreUpgrade. PreUpgrade is a slightly different upgrade method where all the packages are downloaded before the system is rebooted into the Anaconda installer.

Although upgrades with yum do work, they are not explicitly tested as part of the release process by the Fedora QA and are not documented in the Fedora installation guide. If you are not prepared to resolve issues on your own if things break, you should probably use the recommended installation methods instead.

When upgrading with yum you don't get any help from FedUp or Anaconda, but with a typical system it might be able to upgrade systems remotely over ssh and with limited downtime. (You will still need to reboot to get the new kernel and system libraries/services running).

A live upgrade with yum usually works well with a typical installation and when following the advice below.

Participate

If you are upgrading using Yum and it shows any general dependency issues, please file them in http://bugzilla.redhat.com. But please read this page, all references pages and search the mailing list archives before filing bugs. And of course, please help keep this page updated.

If you want to help make live upgrades work smoothly, join the Live Upgrade Special Interest Group.

Instructions to upgrade using yum

1. Backup your system

Backup any personal data to an external hard drive or to another machine. If there is some unrecoverable error that requires a fresh install, you don't want to lose any data.

2. Read about common problems

Further down in this page there is a list of common problems specific to yum upgrades for specific versions. Some of them require attention before the upgrade.

General advice on upgrading Fedora can be found on the Upgrading page. You should also read the Installation Guide and Release Notes for the version you plan to upgrade to - they contain important information regarding upgrading issues. Finally, check the list of Common bugs.

3. Clean Stuff

Review and remove all .rpmsave and .rpmnew files before and after upgrading. (And if you have selinux enabled then remember to check security context if you move config files around.)

Idea.png
Find unused config files
Merge and resolve the changes found by the following script: yum install rpmconf; rpmconf -a Now find and remove old config which nobody owns: find /etc /var -name '*?.rpm?*'

Now is a good time to remove packages you don't use - especially non-standard packages.

Idea.png
Find and review "unused" packages
You can find packages not required by other packages with the tool package-cleanup from the yum-utils package: yum install yum-utils; package-cleanup --leaves. These packages could be candidates for removal, but check to see whether you use them directly or if they are used by applications not backed by rpm packages. Remove them with yum remove package-name-and-version.
Another useful tool for cleaning up unused packages is rpmreaper. It's an ncurses application that lets you view rpm dependency graph and mark packages for deletion. Marking one package can make other packages leaf, which you can see immediately, so you don't have to run the tool several times to get rid of whole sub-tree of unused packages. Install with: yum install rpmreaper.
Idea.png
Find and review "lost" packages
You can find orphaned packages (ie packages not in the repositories anymore) with: package-cleanup --orphans. This will also show packages which have been partially uninstalled but where the "%postun" script failed.

4. Do the upgrade

If you have 3rd party repositories configured, you may need to adjust them for the new Fedora version. If you switch from one Fedora release to another there is often nothing that needs to be done. 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 yum 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

fedora-upgrade

A small script named fedora-upgrade is available which aims to automate the process outlined below. To run it, do the following

$ sudo yum install fedora-upgrade 
$ sudo fedora-upgrade


Alternatively, follow the manual steps:

Go to a text console

ctrl + alt + F2

(or)

log in as root, and go into runlevel 3

init 3

Update yum to latest version available in your Fedora version

# yum update yum

Install the new fedora gpg key for the version you are updating to

Keys you may find and verify at

https://fedoraproject.org/keys

or see a version specific update instructions at the bottom.

Clean the cache

Then remove all traces of the version you are leaving from the yum cache in /var/cache/yum.

# yum clean all

Upgrade all packages

Warning (medium size).png
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 yum distro-sync and package-cleanup --problems to try and fix the problems.
# yum --releasever=<release_number_you_want_to_sync_to> distro-sync
Warning (medium size).png
If you experience any dependency problems, you are at your own and you have to solve them manually. If you are not able to, use preupgrade! Most often it is enough to remove several problematic package(s). Be sure to not remove half of your installation.

Note: While it is recommended to upgrade to intermediate releases if upgrading from an older release (for example upgrading from Fedora 12 to 13, then 13 to 14), depending on what version you are upgrading from, this step may fail with an error about GPG keys being in the wrong format. To overcome this, you can add the "--nogpgcheck" switch to the above yum distro-sync command.

5. Make sure Fedora is upgraded

Distro-sync will usually take care of upgrades for the third party repositories you have enabled as well. Confirm with
 yum repolist 
after the upgrade process is over. yum 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

# yum groupupdate 'Minimal Install'

You might want to update other groups too, see

# yum grouplist

For example

# yum groupupdate "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

/sbin/grub-install BOOTDEVICE

- where BOOTDEVICE is usually /dev/sda (If you get an error '/dev/sda does not have any corresponding BIOS drive' from that, then try /sbin/grub-install --recheck /dev/sda). For Fedora 16 and later, use /sbin/grub2-install instead of /sbin/grub-install. See below first for important information about upgrading to Fedora 16 from prior releases.

Also, the order of init scripts could have changed from the previous version. A command to reset the order is:

cd /etc/rc.d/init.d; for f in *; do [ -x $f ] && /sbin/chkconfig $f resetpriorities; done

Again, run package-cleanup --orphans to find packages that haven't been upgraded.

Version specific notes

From pre-release

If you are upgrading to a final release from an alpha, beta, preview, or other Rawhide release, please see Upgrading from pre-release to final.

To rawhide

See the Rawhide release page for more information on Rawhide.

# yum install fedora-release-rawhide
# yum-config-manager --disable fedora updates updates-testing
# yum-config-manager --enable rawhide
# yum update yum
# yum --releasever=rawhide distro-sync --nogpgcheck

Fedora 19 -> Fedora 20

Install the new Fedora 20 gpg key and upgrade:

# rpm --import https://fedoraproject.org/static/246110C1.txt
# yum update yum
# yum --releasever=20 distro-sync


Fedora 18 -> Fedora 19

Warning (medium size).png
Incompatible systemd cgroups hierarchy layout
systemd in F19 lays out its cgroups hierarchy differently than in previous Fedora releases.

The new hierarchy has some advantages, but it is incompatible with the old one. No live conversion of the hierarchy is performed during the package upgrade, so the upgraded systemd will not understand the previous state of the system correctly. This is known to affect the tracking of user sessions by systemd-logind (bug #962983).

Expect breakage in active user sessions and make sure to reboot soon after performing the upgrade. If your screen locks during the upgrade, you may not be able to log back in due to the cgroup changes. Running the upgrade in a screen(1) session has been reported as a workaround (re-attach from a vt).

Install the new Fedora 19 gpg key and upgrade:

# rpm --import https://fedoraproject.org/static/FB4B18E6.txt
# yum update yum
# yum --releasever=19 distro-sync

If you use Fedora ARM, run these commands instead:

# rpm --import https://fedoraproject.org/static/BA094068.txt
# yum update yum
# yum --releasever=19 distro-sync

Fedora 17 -> Fedora 18

Note.png
Recommended Upgrade Method (Fedora 17 and newer)
Upgrading with FedUp is the recommended way to upgrade your system!Please check How Can I Upgrade My System with FedUp?


Note: One user has reported problems trying to upgrade an Intel Mac UEFI installation using this method, including the manual bootloader migration. Read more

  1. Install the new Fedora 18 gpg key: su -c 'rpm --import https://fedoraproject.org/static/DE7F38BD.txt'
  2. If you are using SELinux in Enforcing mode, make sure your selinux-policy is up to date: su -c 'yum update selinux-policy'
  3. Upgrade all packages:
    1. su -c 'yum update yum'
    2. su -c 'yum clean all'
    3. su -c 'yum --releasever=18 --disableplugin=presto distro-sync' It is recommended that updates be enabled for this step, for best results.
  4. Rebuild rpm database: su -c 'rpm --rebuilddb', or rpm -qa will not work due to an upgrade of rpm

If you used an outdated selinux-policy package in Enforcing mode during the upgrade, you may notice errors in the yum output when several packages attempt to create users and/or groups, and after the upgrade you may have problems related to these packages, including issues with logging in via GDM (you may just see a spinning cursor) and/or performing actions requiring administrative privileges. This is a result of bug #844167. If you have this problem, you should re-install the affected packages with su -c 'yum reinstall (packagenames)', and then reboot. Affected packages may include libvirt-daemon and polkit: su -c 'yum reinstall libvirt-daemon polkit'

Due to Features/DisplayManagerRework, the upgrade may leave you without a display manager enabled. To solve this problem, use su -c 'systemctl enable yourdm.service', replacing yourdm with the display manager you intend to use, e.g. gdm or kdm.

Upgrading from legacy end of life (EOL) Fedoras

Note.png
Yum upgrading from older versions
Upgrading from older versions of Fedora is archived here: Upgrading from EOL Fedora using yum