From Fedora Project Wiki

(change the bootloader instructions for 15 to 16)
(add upgrade Fedora 21 -> Fedora 22 (not yet released))
(135 intermediate revisions by 53 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, 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.


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 23: Line 23:
== Instructions to upgrade using yum ==
== Instructions to upgrade using yum ==


=== 1.  Back up your system ===
=== 1.  Backup 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.
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 ===
=== 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.
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 [http://docs.fedoraproject.org/install-guide/ Installation Guide] and [http://docs.fedoraproject.org/release-notes/ Release Notes] for the version you plan to upgrade to - they contain important information regarding upgrading issues. Finally, check the list of [[Common bugs]].
General advice on upgrading Fedora can be found on the [[Upgrading]] page. You should also read the [http://docs.fedoraproject.org/install-guide/ Installation Guide] and [http://docs.fedoraproject.org/release-notes/ Release Notes] for the version you plan to upgrade to - they contain important information regarding upgrading issues. Finally, check the list of [[Common bugs]].
Line 38: Line 38:


{{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 54:
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 84:


<pre>
<pre>
yum update yum
# yum update yum
</pre>
</pre>


Line 89: Line 100:


<pre>
<pre>
yum clean all
# yum clean all
</pre>
</pre>


Line 97: Line 108:


<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>


{{admon/warning|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.
{{admon/warning|If you experience any dependency problems, you have to solve them manually. Most often it is enough to remove several problematic package(s). Be very careful when doing so however.
}}
}}


'''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.
'''Note:''' While it is recommended to upgrade to intermediate releases if upgrading from an older release (for example upgrading from Fedora 19 to 20, then 20 to 21), 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 ===
=== 5. Make sure Fedora is upgraded ===
Line 112: Line 123:


<pre>
<pre>
yum groupupdate Base
# yum groupupdate 'Minimal Install'
</pre>
</pre>


Line 118: Line 129:


<pre>
<pre>
yum grouplist
# yum grouplist
</pre>
</pre>


Line 124: Line 135:


<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 138: Line 147:
Before booting you should usually install the bootloader from your new grub by running
Before booting you should usually install the bootloader from your new grub by running
<pre>
<pre>
/sbin/grub-install BOOTDEVICE
/usr/sbin/grub2-install BOOTDEVICE
</pre>
- where BOOTDEVICE is usually <code>/dev/sda</code> (If you get an error '/dev/sda does not have any corresponding BIOS drive' from that, then try <tt>/usr/sbin/grub2-install --recheck /dev/sda</tt>).
 
It might also be necessary to update the grub config file:
<pre>
cp --backup=numbered -a /boot/grub2/grub.cfg{,.bak} # create backup copy
/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg # update config file
</pre>
</pre>
- where BOOTDEVICE is usually <code>/dev/sda</code> (If you get an error '/dev/sda does not have any corresponding BIOS drive' from that, then try <tt>/sbin/grub-install --recheck /dev/sda</tt>). For Fedora 16 and later, use <code>/sbin/grub2-install</code> instead of <code>/sbin/grub-install</code>. See [[#15-16|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:
Also, the order of init scripts could have changed from the previous version. A command to reset the order is:
<pre>
<pre>
cd /etc/rc.d/init.d; for f in *; do /sbin/chkconfig $f resetpriorities; done
cd /etc/rc.d/init.d; for f in *; do [ -x $f ] && /sbin/chkconfig $f resetpriorities; done
</pre>
</pre>


Line 155: Line 170:
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>
yum update yum
yum --releasever=rawhide distro-sync --skip-broken --nogpgcheck
</pre>
 
{{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>


Upgrade all packages with
See the [[Releases/Rawhide|Rawhide]] release page for more information on Rawhide.


<pre>
<pre>
yum update yum
# yum install fedora-repos-rawhide yum-utils
yum clean all
# yum-config-manager --disable fedora updates updates-testing
yum --releasever=16 --disableplugin=presto distro-sync
# yum-config-manager --enable rawhide
# yum update yum
# yum --releasever=rawhide distro-sync --nogpgcheck
</pre>
</pre>


{{admon/warning|Bootloader change|After the update, 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 you are upgrading from {{FedoraVersion|21}} or later, replace the first command with {{command|yum install fedora-repos-rawhide yum-utils}}.


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 [[#bootloader|above]] with reinstalling the bootloader.
{{Anchor|20-21}}


{{Anchor|14-15}}
=== Fedora 21 -> Fedora 22 (not yet released) ===


=== Fedora 14 -> Fedora 15 ===
# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-22-$(uname -i)
# yum update yum
# yum clean all
# yum --releasever=22 distro-sync


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.
=== Fedora 20 -> Fedora 21 ===


<pre>
# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-21-$(uname -i)
rpm --import https://fedoraproject.org/static/069C8460.txt
# yum update yum
</pre>
# yum clean all
# yum --releasever=21 distro-sync


Upgrade all packages with
Fedora 21 split into different products. Execute '''one''' of those commands:


<pre>
# yum install system-release-workstation
yum update yum
# yum install system-release-cloud
yum clean all
# yum install system-release-server
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.
or this one if you want to have non-productized Fedora
* 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.


==== VirtualBox guest upgrades ====
# yum install system-release-nonproduct
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>
If you change your mind, you can easily switch between products.  
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 ===
# yum swap system-release-cloud system-release-workstation


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.
Swapping to workstation sometimes may require you to use {{command|yum shell}} as it may require multiple packages to be swapped.


<pre>
Many people report (e.g. bugs 1035326, 1044184, 1002331) that after upgrade some files have incorrect SELinux context. It is recommend to run:
rpm --import https://fedoraproject.org/static/97A1071F.txt
</pre>


Upgrade all packages with
  # restorecon -R /
 
<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.
{{Anchor|19-20}}


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:
=== Fedora 19 -> Fedora 20 ===
<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:
Install the new Fedora 20 gpg key and upgrade:  
<ol>
# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-20-$(uname -i)
<li><code>yum install selinux-policy selinux-policy-targeted</code>
# yum update yum
<li><code>fixfiles restore</code>
# yum clean all
<li><code>reboot</code>
# yum --releasever=20 --setopt=deltarpm=0 distro-sync
</ol>


=== Upgrading from legacy end of life (EOL) Fedoras ===
=== Upgrading from legacy end of life (EOL) Fedoras ===
{{admon/note|Yum upgrading from older versions|Upgrading from older versions of Fedora is archived here: [[Upgrading from EOL Fedora using yum]]}}
{{admon/note|Yum upgrading from older versions|Upgrading from older versions of Fedora is archived here: [[Upgrading from EOL Fedora using yum]]}}


[[Category:FAQ]][[Category:How to]][[Category:Documentation]]
[[Category:FAQ]]
[[Category:How to]]
[[Category:Documentation]]

Revision as of 10:14, 2 March 2015

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

Upgrading Fedora using yum directly

Warning.png
Upgrading using the yum method described here is not recommended for new users. Use FedUp instead
For upgrades, the recommended upgrade method is the FedUp tool. This section has instructions on using FedUp to upgrade. 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.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.png
If you experience any dependency problems, you have to solve them manually. Most often it is enough to remove several problematic package(s). Be very careful when doing so however.

Note: While it is recommended to upgrade to intermediate releases if upgrading from an older release (for example upgrading from Fedora 19 to 20, then 20 to 21), 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

/usr/sbin/grub2-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 /usr/sbin/grub2-install --recheck /dev/sda).

It might also be necessary to update the grub config file:

cp --backup=numbered -a /boot/grub2/grub.cfg{,.bak} # create backup copy
/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg # update config file

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-repos-rawhide yum-utils
# yum-config-manager --disable fedora updates updates-testing
# yum-config-manager --enable rawhide
# yum update yum
# yum --releasever=rawhide distro-sync --nogpgcheck

If you are upgrading from 39 or later, replace the first command with yum install fedora-repos-rawhide yum-utils.


Fedora 21 -> Fedora 22 (not yet released)

# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-22-$(uname -i)
# yum update yum
# yum clean all
# yum --releasever=22 distro-sync

Fedora 20 -> Fedora 21

# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-21-$(uname -i)
# yum update yum
# yum clean all
# yum --releasever=21 distro-sync

Fedora 21 split into different products. Execute one of those commands:

# yum install system-release-workstation
# yum install system-release-cloud
# yum install system-release-server

or this one if you want to have non-productized Fedora

# yum install system-release-nonproduct

If you change your mind, you can easily switch between products.

# yum swap system-release-cloud system-release-workstation

Swapping to workstation sometimes may require you to use yum shell as it may require multiple packages to be swapped.

Many people report (e.g. bugs 1035326, 1044184, 1002331) that after upgrade some files have incorrect SELinux context. It is recommend to run:

 # restorecon -R /

Fedora 19 -> Fedora 20

Install the new Fedora 20 gpg key and upgrade:

# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-20-$(uname -i)
# yum update yum
# yum clean all
# yum --releasever=20 --setopt=deltarpm=0 distro-sync

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