From Fedora Project Wiki

(→‎Fedora 20 -> Fedora 21: shutdown issues)
(278 intermediate revisions by 87 users not shown)
Line 1: Line 1:
= Upgrading Fedora Using Yum =
{{autolang|base=yes}}


{{admon/caution|Although upgrades with yum have been tested and work, live upgrades are not recommended by the Fedora Project. If you are not prepared to resolve issues on your own if things break, you should probably use the recommend installation methods 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]. [[PreUpgrade]] is a slightly different upgrade method where the all packages are downloaded before the system is rebooted into the Anaconda installer.
{{admon/warning| Upgrading using the yum method described here is not recommended for new users. Use [[FedUp]] instead }}


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 without any downtime. But the system must be rebooted to get the new kernel and system libraries and services running, so currently you can't avoid having some downtime. Rebooting after such an upgrade is always very exciting.
This page contains information explaining how to upgrade Fedora using {{command|yum}}.


With a typical installation and when following advices here, then live upgrade with yum usually works well.  
== Upgrading Fedora using yum directly ==
 
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.}}
 
When upgrading with yum you don't get any help from [[FedUp]], 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).
 
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.}}
 
A live upgrade with yum usually works well with a typical installation and when following the advice below.


== Participate ==
== Participate ==


If you are upgrading using Yum and it shows up any general dependency issues, please file them in http://bugzilla.redhat.com. But please read this page and all references pages and search the mailing list archives before filing bugs. And of course, please help keeping this page updated.
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 [[SIGs/LiveUpgrade Live Upgrade Special Interest Group]].
If you want to help make live upgrades work smoothly, join the [[SIGs/LiveUpgrade | Live Upgrade Special Interest Group]].


== Instructions to upgrade using yum ==
== Instructions to upgrade using yum ==


=== 0Back up your system ===
=== 1Backup 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.


=== 1. Read about common problems ===
=== 2. Read about common problems ===


Further down in this page there's 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 [[DistributionUpgrades]]. You should also read the release notes for the version you upgrade to (for example [http://docs.fedoraproject.org/release-notes/f9/en_US/sn-Installer.html#Upgrade-Related-Issues Fedora 9]) - it contains important information regarding upgrading issues.
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]].


=== 2. Clean Stuff ===
=== 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.)
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.)


{{admon/tip|Find unused config files|Merge and resolve the changes found by the following script: <code>for a in $(find /etc /var -name '*.rpm?*'); do diff -u $a ${a%.rpm?*}; done</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 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.


{{admon/tip|Find and review "unused" packages| You can find packages not required by other packes with the tool <code>package-cleanup</code> from the <code>yum-utils</code> package: <code>yum install yum-utils; package-cleanup --leaves</code>. These packages could be candidates for removal, but check if you use them directly or if they are used by applications not backed by rpm packages. Remove them with rpm -e package-name-and-version.  
{{admon/tip|Find and review "unused" packages| You can find packages not required by other packages with the tool <code>package-cleanup</code> from the <code>yum-utils</code> package: <code>yum install yum-utils; package-cleanup --leaves</code>. 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 <code>yum remove package-name-and-version</code>.<br/>
Another useful tool for cleaning up unused packages is <code>rpmreaper</code>.  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: <code>yum install rpmreaper</code>.
}}
}}


{{admon/tip|Find and review "lost" packages| You can find orphaned packages (ie packages not in the repositories anymore) with: <code>package-cleanup --orphans</code>. This will also show packages which have been partially uninstalled but where the "%postun" script failed.}}
{{admon/tip|Find and review "lost" packages| You can find orphaned packages (ie packages not in the repositories anymore) with: <code>package-cleanup --orphans</code>. This will also show packages which have been partially uninstalled but where the "%postun" script failed.}}


Make sure you have the <code>yum-fastestmirror</code> package installed so that yum uses the "best" mirror.
=== 4. Do the upgrade ===


<pre>
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).
yum install yum-fastestmirror
</pre>


Then remove all traces of the version you are leaving from the yum cache in <code>/var/cache/yum</code>.
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.


<pre>
It is a good idea to do the upgrade outside the graphical environment. Log out of your graphical desktop and then
yum clean all
</pre>


=== 3. Switch repositories ===
==== fedora-upgrade ====


Update the packages that decide which yum repositories to use.
A small script named fedora-upgrade is available which aims to automate the process outlined below. To run it, do the following


<pre>
<pre>$ sudo yum install fedora-upgrade
rpm -Uhv ftp://download.fedora.redhat.com/pub/fedora/linux/releases/<ReleaseNumber>/Fedora/<Arch>/os/Packages/fedora-release-*.noarch.rpm
$ sudo fedora-upgrade
</pre>
</pre>


For Fedora 9, as an example,


<pre>
Alternatively, follow the manual steps:
rpm -Uvh ftp://download.fedora.redhat.com/pub/fedora/linux/updates/9/i386.newkey/fedora-release-*.noarch.rpm
</pre>


(The architecture doesn't matter for this <code>noarch</code> package.)
==== Go to a text console ====
 
Make sure the new repo files isn't placed as <code>.rpmnew</code> files, perhaps by


<pre>
<pre>
mv /etc/yum.repos.d/fedora-updates.repo.rpmnew /etc/yum.repos.d/fedora-updates.repo
ctrl + alt + F2
mv /etc/yum.repos.d/fedora.repo.rpmnew /etc/yum.repos.d/fedora.repo
</pre>
</pre>


If you have 3rd party repos configured then enable their repositories for the new Fedora version. If you switch from one Fedora relase to another there is often nothing that needs to be done; is you switch to rawhide then you most of the time need to install the rawhide release rpms from the 3rd party repo as well.
(or)
 
Note that the upgrade is likely to fail if there are outdated dependencies from packages not backed by a yum repo or backed by a repo which isn't ready for the new version.
 
=== 4. Do the upgrade ===
 
If using selinux make sure it is in permissive mode - neither disabled nor enforcing.


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
log in as root, and go into multi-user.target


<pre>
<pre>
ctrl + alt + F1
systemctl isolate multi-user.target
</pre>
</pre>


log in as root, and go into runlevel 3
==== Update yum to latest version available in your Fedora version ====


<pre>
<pre>
telinit 3
# yum update yum
</pre>
</pre>


{{admon/warning|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, doing so 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.  The only way to recover from this is to reinstall if it occurs.}}
==== Install the new fedora gpg key for the version you are updating to ====


{{admon/tip|Update important packages first| You can start try to update the update machinery first with <code>yum update rpm\* yum\*</code>. Another idea is to start with <code>glibc</code>. In both cases dependencies might however expand it to an almost full upgrade anyway. And doing a full upgrade might be more safe. YMMV.
Keys you may find and verify  at
}}


Upgrade all packages with
https://fedoraproject.org/keys


<pre>
or see a version specific update instructions at the bottom.
yum upgrade
</pre>


<code>yum</code> 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.
==== Clean the cache ====


Ensure that all (new) essential packages from the new version is installed with
Then remove all traces of the version you are leaving from the yum cache in <code>/var/cache/yum</code>.
 
<pre>
yum groupupdate Base
</pre>
 
You might want to update other groups too, see


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


For example
==== Upgrade all packages ====


<pre>
{{admon/warning|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 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"
</pre>


=== 5. Preparing for reboot ===
Before booting you should usually install the bootloader from your new grub by running
<pre>
<pre>
/sbin/grub-install BOOTDEVICE
# yum --releasever=<release_number_you_want_to_sync_to> distro-sync
</pre>
</pre>
- where BOOTDEVICE usually is <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>.)


Also, the order of init scripts could have changed from the previous version. A command to reset the order is:
{{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.
<pre>
}}
cd /etc/rc.d/init.d; for f in *; do /sbin/chkconfig $f resetpriorities; done
</pre>
 
Again, run <code>package-cleanup --orphans</code> to find packages that hasn't been upgraded.


== Version specific notes ==
'''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.


=== Fedora 9 -> Fedora 10 Beta ===
=== 5. Make sure Fedora is upgraded ===


* Check the [[Releases/10/Beta/ReleaseNotes| Fedora 10 Beta Release Notes]]
Distro-sync will usually take care of upgrades for the third party repositories you have enabled as well. Confirm with <pre> yum repolist </pre> after the upgrade process is over.  <code>yum</code> 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.
* GDM starts on tty1 by default, not tty7.
* anaconda by default now refers to encrypted devices by UUID, not by device name, to better handle device name changes. An encrypted device using partition <code>/dev/sda1</code> with UUID <code>12345678-1234-1234-1234-123456789012</code> would now be called <code>/dev/mapper/luks-12345678-1234-1234-1234-123456789012</code> instead of <code>/dev/mapper/luks-sda1</code>. You may wish to make the same changes on your system on upgrade; if you do, make sure to run <code>mkinitrd</code> afterwards.
* If you use non-root encrypted devices, you will need to re-run <code>mkinitrd</code> for any older kernels that you want to still boot on the system.


=== Fedora 8 -> Fedora 9 ===
Ensure that all (new) essential packages from the new version are installed with
 
* If you are running as a <code>xen</code> Host (Dom0) you should not upgrade to Fedora 9. [http://www.redhat.com/archives/fedora-xen/2008-March/msg00013.html]
* Upgrading the thunderbird package will [https://bugzilla.redhat.com/show_bug.cgi?id=446351 fail] . The current workaround is <code>yum remove thunderbird; yum install thunderbird></code>.
* If you are upgrading to Fedora 9 and use <code>emacs</code>, you must upgrade to the latest version of <code>emacs</code> for your prior release to ensure a clean upgrade. Fedora 8 users must have <code>emacs-22.1-10.fc8</code> or later, while Fedora 7 users must have <code>emacs-22.1-7.fc7</code>.  Bug report [https://bugzilla.redhat.com/show_bug.cgi?id=239745 here] .
* Due to the switch from sysvinit to [http://fedoraproject.org/wiki/Features/Upstart Upstart] , it is recommended that users who do an upgrade on a live filesystem to Fedora 9 reboot soon afterwards. If you do not reboot, you may want to take careful note of any '/etc/inittab.rpmsave' or '/etc/inittab.rpmnew' files. When rebooting after an upgrade then be aware that sysvinit that was used to start the system can't be used to shut it down.
* You may find that after upgrading, you can no longer log in to GNOME. If this is the case, use ctrl-alt-F1 to access command prompt, then check the tail of .xsession-errors. If you see a comment like "(named color or font does not exist)", then you may be able to fix this using http://matthew.peach.net.nz/2008/05/18/how-to-fix-badname-named-color-or-font-does-not-exist-error/.
 
=== Fedora 7 -> Fedora 8 ===
 
* New pulseaudio and flash support packages must be installed manually:


<pre>
<pre>
yum groupinstall sound-and-video gnome-desktop (if you are using Gnome)
# yum groupupdate 'Minimal Install'
yum groupinstall sound-and-video kde-desktop (if you are using KDE)
yum install libflashsupport paman padevchooser
</pre>
</pre>


* The Fedora 7 avahi packagage fails to uninstall; remove it manually with
You might want to update other groups too, see


<pre>
<pre>
rpm -e --noscripts avahi-0.6.17-1.fc7
# yum grouplist
</pre>
</pre>


* On 64 bit machines (x86_64) you may have to remove some 32 bit libraries. For example dbus:
For example


<pre>
<pre>
yum erase dbus.i386
# yum groupupdate "GNOME Desktop" \
    "Development Tools" "Sound and Video" \
    "Games and Entertainment" "Administration Tools" \
    "Office/Productivity" "System Tools"
</pre>
</pre>


* You may find it easier to use the yum shell to stack these commands in a single transaction:
=== 6. Preparing for reboot ===
 
{{Anchor|bootloader}}


Before booting you should usually install the bootloader from your new grub by running
<pre>
<pre>
yum shell
/usr/sbin/grub2-install BOOTDEVICE
> erase dbus.i386
> update
> run
</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>/usr/sbin/grub2-install --recheck /dev/sda</tt>).


* A lot of KDE packages are no longer multilib in F8. If you are on x86_64, you will need to erase the i386 versions of these packages by hand, like so:
It might also be necessary to update the grub config file:
 
<pre>
<pre>
yum erase kde{accessibility{,-devel},base,edu,graphics,multimedia{,-extras},network,sdk,utils{,-devel},webdev}.i386
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>


* Various other packages including Beryl are no longer in F8 and not obsoleted:
Also, the order of init scripts could have changed from the previous version. A command to reset the order is:
 
<pre>
<pre>
yum erase beryl\*
cd /etc/rc.d/init.d; for f in *; do [ -x $f ] && /sbin/chkconfig $f resetpriorities; done
</pre>
</pre>


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


=== Fedora Core 6 -> Fedora 7 ===
== Version specific notes ==


* Fedora 7 replaces the old IDE subsystem with libata. Drive device names which previously started /dev/hd.. will become /dev/sd.. after the upgrade. /dev/hda1 will usually become /dev/sda1, although there may not be a direct relationship between the old and new device names (for example hdd does not necessarily become sdd). Before you reboot be sure to change all references to /dev/hd.. in your config, especially /etc/fstab - where it however may be simpler to refer to filesystems by label (check out the programs blkid, tune2fs, and mlabel). LVM Volume names are not affected. In /boot/grub/device.map change /dev/hd.. to /dev/sd.. before running grub-install - and don't change (hd0). Changing /boot/grub/grub.conf may also be required.
=== From pre-release ===


* The libata layer represents all hard disks as SCSI disks, which are limited to 15 partitions in the kernel. IDE hard disks with more than 15 partitions are not supported in Fedora 7.
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]].


* On a system which has been upgraded from releases prior to FC6 you may need to remove up2date and rhnlib <code>rpm -e rhnlib up2date</code>
{{Anchor|Rawhide}}
=== To rawhide ===


* If you see the message <code>package gpm-1.20.1-84.fc6 (which is newer than gpm-1.20.1-83.fc7) is already installed</code> when performing a <code>yum update</code> uninstall and reinstall the gpm package.
{{admon/warning| Rawhide is the development branch of Fedora. It is meant to be used by developers and testers to provide feedback to the Fedora Project.}}


* If you had installed Suns jre it might be removed during upgrade. Be aware that <code>jre-6u1</code>/<code>jre-1.6.0_01-fcs</code> requires <code>compat-libstdc++-33</code>.
See the [[Releases/Rawhide|Rawhide]] release page for more information on Rawhide.  


* If you get <code>Error: Missing Dependency: python(abi) = 2.4 is needed by package libxml2-python</code> and/or <code>Error: Missing Dependency: python(abi) = 2.4 is needed by package rpm-python</code> during your <code>yum upgrade</code> ensure you have done a <code>yum clean all</code> and check that both the <code>base</code> and <code>updates</code> repositories are available from your mirror. You will need the <code>updates</code> repo for the upgrade to succeed.
<pre>
## Fedora 20
# yum install fedora-release-rawhide yum-utils


=== Fedora Core 5 -> Fedora Core 6 ===
## Or


* After upgrading, you cannot use the DVD ISO loopback mounted as a repository directly (e.g. no <code>baseurl=file:///mnt/fc6/</code>) because the repodata files contain URLs of type <code>media://</code>  which yum can't handle.  You can use the loopback-mounted DVD for the initial upgrade from FC5 -> FC6, just not thereafter.  After removing the <code>baseurl=file:///</code> option from your <code>fedora-core.repo</code> file, remember to <code>yum clean all</code>.
## Fedora 21+
# yum install fedora-repos-rawhide yum-utils


=== Fedora Core 4 -> Fedora Core 5 ===
## All Fedora
# yum-config-manager --disable fedora updates updates-testing
# yum-config-manager --enable rawhide
# yum update yum
# yum --releasever=rawhide distro-sync --nogpgcheck


* Before upgrading update your kernel first.
## Optional: it is generally advised to do a selinux autorelabel and reboot
 
# touch /.autorelabel
* Make sure you have the latest kernel ABOVE 2.6.14 and uninstall all kernel versions before it, otherwise initscripts and a few other packages will conflict and prevent the ugprade. Use something like the command below
</pre>
 
* Install <code>fedora-release</code> in the Fedora Core 5 version. Check our [http://fedora.redhat.com/Download/mirrors.html mirror sites]  for a faster download.


* Update your system
If you are upgrading from {{FedoraVersion|21}} or later, replace the first command with {{command|yum install fedora-repos-rawhide yum-utils}}.


* After upgrading, selinux permissions may be incorrect, causing interesting failures such as metacity not starting. As suggested below, to fix this, run <code>touch /.autorelabel</code> and reboot


=== Fedora Core 3 -> Fedora Core 4 ===
{{Anchor|20-21}}


* make sure you're on the latest version of yum for FC3:
=== Fedora 21 -> Fedora 22 (not yet released) ===
<code> yum update yum </code>
* Download fedora-release for FC4:
* wget http://yourmirrorhere/pub/fedora/linux/core/4/$yourarch/os/Fedora/RPMS/fedora-release-4-2.noarch.rpm
* <code>rpm -Uvh /path/to/fedora-release-4-2.noarch.rpm</code>
* yum update ( This will start the upgradation process to FC4)
* Once you have updated, run: <code>yum groupinstall "GNOME Desktop Environment"</code> (change GNOME to KDE if appropriate). That'll get you some new packages that were added in FC4 like Evince and NetworkManager.
* Some new groups were added - <code> yum grouplist </code> - check out Eclipse and Java Development in particular.


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


* Postgres database in FC4 has a newer incompatible format from the previous versions. Manual dump and restoration is required if you using this database. Look at the postgres documentation for more details on this.
=== Fedora 20 -> Fedora 21 ===


* kernel requires kernel-utils (or vice-versa) run:
# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-21-$(uname -i)
<pre>
# yum update yum
yum update kernel
# yum clean all
reboot
# yum --releasever=21 distro-sync
yum remove kernel-2.6.11\*FC3\*
yum upgrade
reboot
</pre>


* Takes forever and a day and hangs at:
Fedora 21 split into different products. Execute '''one''' of those commands:
<code> Reading repository metadata in from local files </code>
This means you have too much crap in your rpmdb and it's taking a while to go through it. Check out how many kernels you have installed: rpm -q kernel kernel-smp and remove the old ones you may also try running: rpm --rebuilddb and see if it helps any. I've found that removing old kernels and rebuilding the rpmdb helped this problem.


* x86_64 upgrade requires removal of certain i386 packages before update
# yum install system-release-workstation
<pre>
# yum install system-release-cloud
yum remove perl.i386
# yum install system-release-server
TODO: Add list of bonobo i386 packages to remove here
</pre>
* Error: Missing Dependency: libpython2.3.so.1.0 is needed by package koffice
koffice was removed from Fedora Core and not moved to extras - so there's no way to complete an upgrade to FC4
without removing it. run:
<pre>
yum remove koffice
</pre>
then your update should complete.


* x86_64 systems seems to hang during "Running Transaction Test"
or this one if you want to have non-productized Fedora


Seems related to [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=155730 Bug 155730] -- Maybe a update to the "rpm-4.3.3-3.0.fc3" (currently in updates-testing) might solve this. Ugly workaround (to be done as root):
  # yum install system-release-nonproduct
<pre>
: > /var/log/lastlog
</pre>


* GPG check fails with this message :
If you change your mind, you can easily switch between products.
<pre>
warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID db42a60e
public key not available for <some_package>
Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora


The GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora (0x4F2A6FD2)
# yum swap system-release-cloud system-release-workstation
is already installed but is not the correct key for this package.
Check that this is the correct key for the "Fedora Core 4 - i386 - Base" repository.
</pre>
Edit /etc/yum.repos.d/fedora.repo and replace the line
<pre>
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
</pre>
with:
<pre>
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY
</pre>


* SELinux gets messed up. I had to redownload the selinux-policy-targeted RPM from my mirror, do a forced uninstall of the old package, clean out the .rpmnew and .rpmsave files then install the new policy. Then I had to run "/sbin/fixfiles relabel" and wait. If I didn't do that, I found I couldn't log in.
Swapping to workstation sometimes may require you to use {{command|yum shell}} as it may require multiple packages to be swapped.
* If SELinux does give you problems, it can be disabled on bootup by pressing "a" on the grub bootup menu, then adding "enforcing=off" to the arguments list.


* RPM complains about missing diskspace, but there is a lot free. If you are really sure your diskspace is enough, set
Many people report (e.g. bugs 1035326, 1044184, 1002331) that after upgrade some files have incorrect SELinux context. It is recommend to run:
<pre>
diskspacecheck=0
</code> in <code>/etc/yum.conf</code>.
The RPM transaction will need a lot of diskspace temporarily (much more than one might think), so be careful.
Don't forget to remove that later after the upgrade.


* Yum complains about files conflicting in the GCC package.  This system was upgraded from Fedora Core 1.  Remove the gcc32 package:
  # restorecon -R /
<pre>
sudo rpm -e gcc32
</pre>


* Some of your modules don't load after the upgrade.  When you investigate modprobe doesn't work as expected.  Run depmod:
Appear to be enable to shutdown/reboot gracefully afterwards:
<pre>
sudo depmod -ae -F /boot/System.map-[your <code>uname -a</code> kernel version here]
</pre>


* Yum has been reported to be hanging after upgrading. Updating the pysqlite package might fix it.
# shutdown -h now
Failed to start poweroff.target: Connection timed out
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.


=== Fedora Core 2 -> Fedora Core 3 ===
{{Anchor|19-20}}


Go here for most of this info:
=== Fedora 19 -> Fedora 20 ===
http://linux.duke.edu/~skvidal/misc/fc2-fc3-update-with-yum.txt


=== Fedora Core 1 -> Fedora Core 2 ===
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


Just Upgrade using anaconda - save yourself a world of pain. But if you really want to try, there's these hints by Seth Vidal: http://linux.duke.edu/~skvidal/misc/fc1-fc2-yum-hints.txt
=== 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]]}}


----
[[Category:FAQ]]
[[CategoryFAQ|  CategoryFAQ]]
[[Category:How to]]
[[Category:Documentation]]

Revision as of 18:16, 14 May 2015


Warning.png
Upgrading using the yum method described here is not recommended for new users. Use FedUp instead

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

Upgrading Fedora using yum directly

For upgrades, the recommended upgrade method is the FedUp tool. This section has instructions on using FedUp to upgrade.}}

When upgrading with yum you don't get any help from FedUp, 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).

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

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 multi-user.target

systemctl isolate multi-user.target

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

Warning.png
Rawhide is the development branch of Fedora. It is meant to be used by developers and testers to provide feedback to the Fedora Project.

See the Rawhide release page for more information on Rawhide.

## Fedora 20
# yum install fedora-release-rawhide yum-utils

## Or

## Fedora 21+
# yum install fedora-repos-rawhide yum-utils

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

## Optional: it is generally advised to do a selinux autorelabel and reboot
# touch /.autorelabel

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 /

Appear to be enable to shutdown/reboot gracefully afterwards:

# shutdown -h now
Failed to start poweroff.target: Connection timed out
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.

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