This page contains information explaining how to upgrade Fedora using
- 1 Recommendations
- 2 For direct yum upgrades
- 3 Participate
- 4 Instructions to upgrade using yum
- 4.1 1. Back up your system
- 4.2 2. Read about common problems
- 4.3 3. Clean Stuff
- 4.4 4. Do the upgrade
- 4.5 5. Make sure Fedora is upgraded
- 4.6 6. Preparing for reboot
- 5 Version specific notes
PreUpgrade is a slightly different upgrade method where all the packages are downloaded before the system is rebooted into the Anaconda installer.
For direct yum upgrades
When upgrading with yum you don't get any help from Anaconda, but if you are lucky you 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) Rebooting after such an upgrade is always very exciting.
A live upgrade with yum usually works well with a typical installation and when following the advice below.
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. Back up your system
Back up 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 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.)
Now is a good time to remove packages you don't use - especially non-standard packages.
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
Go to a text console
ctrl + alt + F2
log in as root, and go into runlevel 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
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
yum clean all
Upgrade all packages
yum --releasever=<release_number_you_want_to_sync_to> distro-sync
Note: While it is recommended to upgrade to intermediate releases if upgrading from an older releases (for example upgrading from 12-13, then 13-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
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 Base
You might want to update other groups too, see
yum groupupdate "GNOME Desktop Environment" \ "Development Tools" "Server Configuration Tools" \ "Hardware Support" "Sound and Video" \ "Graphical Internet" "Fonts" \ "Games and Entertainment" "Printing Software" \ "Administration Tools" "Office/Productivity" "System Tools"
6. Preparing for reboot
Before booting you should usually install the bootloader from your new grub by running
- 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.)
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 /sbin/chkconfig $f resetpriorities; done
package-cleanup --orphans to find packages that haven't been upgraded.
Version specific notes
To development version
yum update yum yum --releasever=rawhide distro-sync --skip-broken
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.
rpm --import https://fedoraproject.org/static/97A1071F.txt
Upgrade all packages with
yum update yum yum clean all yum --releasever=14 distro-sync
- 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.
Fedora 12 -> Fedora 13
First install the new fedora 13 gpg key. You may wish to verify this package against https://fedoraproject.org/keys and the fedora ssl certificate.
rpm --import https://fedoraproject.org/static/E8E40FDE.txt
Upgrade all packages with
yum update yum yum clean all yum --releasever=13 distro-sync
- Testing shows that upgrading within X will cause X to hang when installing
bitmap-fonts-compat, but it can be done anyway by making sure that
bitmap-fonts-compatis the last package to update ... YMMV.
- Intel video no longer works without Kernel Mode Setting (KMS). You must remove 'nomodeset' from your /etc/grub.conf kernel command line, if present.
- nVidia video no longer works without kernel mode Setting (KMS). You must remove 'nomodeset' from your /etc/grub.conf kernel command line, if present.
- It may be necessary to run "db_recover -h /var/lib/ldap/ ; chown ldap:ldap /var/lib/ldap/*" once in order for slapd to start.
Fedora 11 -> Fedora 12
- All Fedora 12 RPM packages use XZ/LZMA compression, which is only supported by the rpm-4.7.1-1 update (or later) for Fedora 11. Before upgrading from Fedora 11, run
yum update rpm.
- It is not possible to update directly from Fedora 10 or earlier with yum. To upgrade from Fedora 10, first update to Fedora 11, and then upgrade from Fedora 11 to Fedora 12. If you are using a release before Fedora 10, use one of the official upgrade methods or backup your data, perform a fresh installation, and restore from backup.
- Upgrades from Fedora 11 might currently fail with missing dependencies (for example related to
). The dependencies are ok, but Fedora 11
has problems resolving them (bug 519172).
- If your root filesystem does not mount with 'defaults' options, you will need to add the root filesystem's mount options to grub.conf with the kernel flag
rootflags- initramfs does not pick up the options the way initrd used to. e.g. if you mount your root with the flags
data=journal,relatimethen you would add to the end of the 'kernel' line in grub.conf:
rootflags=data=journal,relatime. After updating to dracut-004-4.fc12 or later, this kernel flag can be removed.