(Few wording clarifications in the intro) |
m (add autolang template) |
||
Line 1: | Line 1: | ||
{{autolang|base=yes}} | |||
{{admon/note|Read [[Upgrading Fedora using yum]] as well|This page is an addendum to [[Upgrading Fedora using yum]]. It contains the problems you might encounter running <code>yum update</code> between specific EOL Fedora releases. Please be sure to read [[Upgrading Fedora using yum]] for an overview of the entire process as well as notes on upgrading from the oldest supported release to the current release.}} | {{admon/note|Read [[Upgrading Fedora using yum]] as well|This page is an addendum to [[Upgrading Fedora using yum]]. It contains the problems you might encounter running <code>yum update</code> between specific EOL Fedora releases. Please be sure to read [[Upgrading Fedora using yum]] for an overview of the entire process as well as notes on upgrading from the oldest supported release to the current release.}} | ||
Revision as of 16:24, 13 January 2011
Version specific notes for EOL releases
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
ortotem-gstreamer
). The dependencies are ok, but Fedora 11PolicyKit-kde
has problems resolving them (bug 519172).yum
- 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 flagsdata=journal,relatime
then 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.
Fedora 10 -> Fedora 11
- It is only possible to upgrade to Fedora 11 from an updated Fedora 10. Older systems must be upgraded to Fedora 10 first. The RPM format has been changed for Fedora 11, so the older
rpmlib
must be updated first. Otherwise the process will fail withrpmlib(FileDigests)
dependency problems. Support for the new format has been backported to Fedora 10 in an update.
yum update rpm
- New
initrd
built when installing a new kernel while running Fedora 10 might fail. To solve that boot with an old kernel (to get the new userspace) and (re)install the new kernel. - Systems with PAE support (indicated by
pae
in/proc/cpuinfo
) should usekernel-PAE.i686
. The new kernel must be changed/installed manually: SetDEFAULTKERNEL=kernel-PAE
in/etc/sysconfig/kernel
andyum install kernel-PAE
. Refer to Dave Jones' blog post for details. - The yum update step should NOT be run inside a gnome desktop session/gnome-terminal. 494046 could result in a unusable install when gnome-terminal segfaults during the upgrade. Update should be run in a vty, runlevel 3, or a screen session.
- fedora-release-11-1.noarch changes the yum mirrorlist URL so that it uses a "metalink", but the version of yum currently in F10 doesn't understand this syntax, leading to yum downloads failing with this error message:
YumRepo Error: All mirror URLs are not using ftp, http[s] or file. Eg. </metalink>/
This is 498720. Workaround is to manually edit the URL in /etc/yum.repos.d/fedora.repo as described at https://www.redhat.com/archives/fedora-list/2009-June/msg00783.html
- Some packages in Fedora 10 are regarded as newer than those supplied by Fedora 11 and its updates repository. These include ntpd, ntpdate (506040, 504980), unique, unique-devel, eclipse-changelog, eclipse-svnkit and svnkit. You may wish to remove these before performing the upgrade, then reinstall them afterwards. Doing so may require
--nodeps
. - Some i386 packages in Fedora 10 are replaced with i586, i686 or x86_64 packages in Fedora 11. These include gpm.i386, glibc-2.9-3.i386. You may wish to remove these before performing the upgrade, then reinstall them afterwards. Doing so may require
--nodeps
. - mplayer-1.0-0.104.20090204svn.fc10 from the RPM Fusion repository has a dependency on libfaad.so.0 that the depsolve doesn't find, but rpm_check_debug does. You may wish to remove mplayer before performing the upgrade, then reinstall them afterwards. Doing so may require
--nodeps
.
Fedora 9 -> Fedora 10
- Check the Fedora 10 Installation Guide and Fedora 10 Release Notes
fedora-release
packages can be found atrpm -Uvh ftp://download.fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os/Packages/fedora-release-*.noarch.rpm
- 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
/dev/sda1
with UUID12345678-1234-1234-1234-123456789012
would now be called/dev/mapper/luks-12345678-1234-1234-1234-123456789012
instead of/dev/mapper/luks-sda1
. You may wish to make the same changes on your system on upgrade; if you do, make sure to runmkinitrd
afterwards. - If you use non-root encrypted devices, you will need to re-run
mkinitrd
for any older kernels that you want to still boot on the system. - It's been reported that there are problems with Pidgin i.e.:
pidgin-2.5.2-2.fc9.i386 from installed has depsolving problems - Error: Missing Dependency: libedataserver-1.2.so.9 is needed by package pidgin-2.5.2-2.fc9.i386 (installed)
- the fix was to remove Pidgin
Fedora 8 -> Fedora 9
- Check the Installer section in Release Notes)
- After "the incident" you should use updated fedora-release packages from
rpm -Uvh ftp://download.fedora.redhat.com/pub/fedora/linux/updates/9/i386.newkey/fedora-release-*.noarch.rpm
- If you are running as a
xen
Host (Dom0) you should not upgrade to Fedora 9. [1] - Upgrading the thunderbird package will fail . The current workaround is
yum remove thunderbird; yum install thunderbird>
. - If you are upgrading to Fedora 9 and use
emacs
, you must upgrade to the latest version ofemacs
for your prior release to ensure a clean upgrade. Fedora 8 users must haveemacs-22.1-10.fc8
or later, while Fedora 7 users must haveemacs-22.1-7.fc7
. Bug report here. - Due to the switch from sysvinit to 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:
yum groupinstall sound-and-video gnome-desktop (if you are using Gnome) yum groupinstall sound-and-video kde-desktop (if you are using KDE) yum install libflashsupport paman padevchooser
- The Fedora 7 avahi packagage fails to uninstall; remove it manually with
rpm -e --noscripts avahi-0.6.17-1.fc7
- On 64 bit machines (x86_64) you may have to remove some 32 bit libraries. For example dbus:
yum erase dbus.i386
- You may find it easier to use the yum shell to stack these commands in a single transaction:
yum shell > erase dbus.i386 > update > run
- 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:
yum erase kde{accessibility{,-devel},base,edu,graphics,multimedia{,-extras},network,sdk,utils{,-devel},webdev}.i386
- Various other packages including Beryl are no longer in F8 and not obsoleted:
yum erase beryl\*
Fedora Core 6 -> Fedora 7
- 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.
- 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.
- On a system which has been upgraded from releases prior to FC6 you may need to remove up2date and rhnlib
rpm -e rhnlib up2date
- If you see the message
package gpm-1.20.1-84.fc6 (which is newer than gpm-1.20.1-83.fc7) is already installed
when performing ayum update
uninstall and reinstall the gpm package.
- If you had installed Suns jre it might be removed during upgrade. Be aware that
jre-6u1
/jre-1.6.0_01-fcs
requirescompat-libstdc++-33
.
- If you get
Error: Missing Dependency: python(abi) = 2.4 is needed by package libxml2-python
and/orError: Missing Dependency: python(abi) = 2.4 is needed by package rpm-python
during youryum upgrade
ensure you have done ayum clean all
and check that both thebase
andupdates
repositories are available from your mirror. You will need theupdates
repo for the upgrade to succeed.
- Since Fedora Core 6 uses python 2.4 and Fedora 7 uses python 2.5, do not try and run
yum upgrade yum\* rpm\*
before upgrading everything else - this succeeds but leaves yum in an unusable state.
Fedora Core 5 -> Fedora Core 6
- After upgrading, you cannot use the DVD ISO loopback mounted as a repository directly (e.g. no
baseurl=file:///mnt/fc6/
) because the repodata files contain URLs of typemedia://
which yum can't handle. You can use the loopback-mounted DVD for the initial upgrade from FC5 -> FC6, just not thereafter. After removing thebaseurl=file:///
option from yourfedora-core.repo
file, remember toyum clean all
.
Fedora Core 4 -> Fedora Core 5
- Before upgrading update your kernel first.
- 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
- Install
fedora-release
in the Fedora Core 5 version. Check our mirror sites for a faster download.
- Update your system
- After upgrading, selinux permissions may be incorrect, causing interesting failures such as metacity not starting. As suggested below, to fix this, run
touch /.autorelabel
and reboot
Fedora Core 3 -> Fedora Core 4
- make sure you're on the latest version of yum for FC3:
yum update yum
- Download fedora-release for FC4:
- wget http://yourmirrorhere/pub/fedora/linux/core/4/$yourarch/os/Fedora/RPMS/fedora-release-4-2.noarch.rpm
rpm -Uvh /path/to/fedora-release-4-2.noarch.rpm
- yum update ( This will start the upgradation process to FC4)
- Once you have updated, run:
yum groupinstall "GNOME Desktop Environment"
(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 -
yum grouplist
- check out Eclipse and Java Development in particular.
Problems:
- 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.
- kernel requires kernel-utils (or vice-versa) run:
yum update kernel reboot yum remove kernel-2.6.11\*FC3\* yum upgrade reboot
- Takes forever and a day and hangs at:
Reading repository metadata in from local files
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 remove perl.i386 TODO: Add list of bonobo i386 packages to remove here
- 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:
yum remove koffice
then your update should complete.
- x86_64 systems seems to hang during "Running Transaction Test"
Seems related to 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):
: > /var/log/lastlog
- GPG check fails with this message :
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) 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.
Edit /etc/yum.repos.d/fedora.repo and replace the line
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
with:
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY
- 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.
- 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
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: <pre> sudo rpm -e gcc32
- Some of your modules don't load after the upgrade. When you investigate modprobe doesn't work as expected. Run depmod:
sudo depmod -ae -F /boot/System.map-[your <code>uname -a</code> kernel version here]
- Yum has been reported to be hanging after upgrading. Updating the pysqlite package might fix it.
Fedora Core 2 -> Fedora Core 3
Go here for most of this info: http://linux.duke.edu/~skvidal/misc/fc2-fc3-update-with-yum.txt
Fedora Core 1 -> Fedora Core 2
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