Did You Know?
Donate to TecMint

We are pleased to announce our new TecMint Q/A section to submit your Linux questions

4 Ways to Upgrade from Fedora 17 to Fedora 18

Download Your Free eBooks NOW - 10 Free Linux eBooks for Administrators

This guide shows you 4 ways to upgrade Fedora 17 to Fedora 18, but official recommended way is using tool called FedUp (FEDora UPgrade). Please note that Preupgrade tool is replaced by FedUp tool and it is not available since Fedora 17. FedUp is the only recommended way to Upgrade your fedora system. This upgrade procedure works for both Desktop as well as Server up-gradation. You may visit to know more about FedUp (Fedora Updater) tool at https://fedoraproject.org/wiki/FedUp.

Upgrade Fedora 17 to Fedora 18

Upgrade from Fedora 17 to Fedora 18

Up-gradation Pre-requisites and Procedures:

  1. Please take important data backup before upgrading your existing Fedora 17 Operating system.
  2. All the commands mentioned in this article need to be executed using root user.
  3. Upgrade Fedora 17 with YUM.
  4. Install / Upgrade FedUp tool.
  5. Enable SELinux Permissive mode.

Method 1: Clean Install

Clean Install always be preferred method for many people and it works 100% correctly. If you are looking for clean Fedora 18 installation, then check out the following article that describes a Fedora 18 basic installation guide with screenshots.

  1. Fedora 18 Installation Guide

Method 2: FedUp (Fedora Updater)

Upgrade Fedora 17 with FedUp command, this will install and upgrade latest packages with kernel as well. During the upgrade process latest kernel got installed and the system needs reboot. FedUp is the new tool and it is the only official recommended way to Upgrade your fedora system now on.

# yum update
# yum -y update
# yum clean all
# reboot

Next, install the latest FedUp tool.

# yum install fedup

Once FeedUp tool installed, run the command and point it to Fedora 18 Network install. We enabled the logging, so if anything goes wrong check for errors in the log and correct it.

# fedup-cli --network 18 --debuglog fedupdebug.log

Once the upgrade process prepared, it will asked you to reboot the system.

# reboot

If reboot succeed, a new Entry added to Grub Menu. Select the System Upgrade (fedup) from the boot menu. The upgrade can take bit longer time. Once upgrade completes, you can log into Fedora 18 system.

Method 3: Yum Upgrade

This method is for only experience users and it involves manual steps. This method uses old YUM Preupgrade tool, now it is not available in latest Federa 18/17. Here we are using YUM tool that simple updates your Fedora 17 packages from Fedora 18 repos.

# yum update
# yum clean all

Next, import and install the new Fedora 18 Public Key with the help of the following command.

# rpm --import https://fedoraproject.org/static/DE7F38BD.txt

Set SELinux to Permissive Mode. The Permissive mode required for upgrade, because during upgrade process several packages attempt to create users and groups. If you not use this mode, you may end up with errors in yum update.

# setenforce Permissive

Upgrade all the packages by syncing your Fedora 17 to Fedora 18.

# yum --releasever=18 --disableplugin=presto distro-sync

Due to an upgrade rpm queries (rpm -qa) will not work, so rebuild rpm database like this.

# rpm --rebuilddb

Method 4: Fedora Upgrade Script

Upgrade Fedora is a small shell script that updates next version using Yum Upgrade, means the script only upgrades from Fedora 17 -> Fedora 18. You cannot upgrade older version – for example, upgrade from Fedora 16 to Fedora 18 with this script.

Please note that this is not the official supported and recommended way to upgrade Fedora, means it is not tested by Fedora QA team. The script is available for download from the GitHub.

  1. https://github.com/xsuchy/fedora-upgrade

Ravi Saive

Owner at TecMint.com
Simple Word a Computer Geek and Linux Guru who loves to share tricks and tips on Internet. Most Of My Servers runs on Open Source Platform called Linux.

Linux Services & Free WordPress Setup

Our post is simply ‘DIY’ aka ‘Do It Yourself, still you may find difficulties and want us to help you out. We offer wide range of Linux and Web Hosting Solutions at fair minimum rates. Please submit your orders by Clicking Here.

2 Responses

  1. Richard says:

    I tried to upgrade with FedUp but this didn’t work at all & I ended up losing all data from my previous F17 install! I tried reinstalling F17 & did not succeed. I had an old Ubuntu 12.04 disc so I installed that & tried to upgrade to Ubuntu12.10-this seemed to work but the home button would not work so there was something wrong with that install. I then retried my F17 install disc & F17 install worked & I tried FedUp upgrade again with no success. I instead took the 32 bit ISO F18 & burnt it to new DVD disc & this installed fine. I am now trying to add features to F18 (LAMP stack/right click menu etc) and look forward to using F18. This whole process took a couple of days and this install is only on my secondary desktop computer which I use for Linux developing purposes as my main computer is a PC running Windows7. So not a smooth upgrade but finally got F18 working.

  2. Thanks Ravi for the procedures depicted here!

    I needed to bring all my ~50 machines that were still under F17 to F20, and with a broken fedup that wouldn’t go all the way up, I chose to do F17->F18 and then repeat fedup (updated as part of the upgrade) to reach F20.

    This worked nicely (but needed some patience).

    The only issues were the keys to the repositories. In the middle point (F18) I just made sure to import the new keys such as:
    rpmkeys –import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-20-x86_64

    I also disabled the rpmfusion repositories, that would cause problems due also to GPG keys, and -re-enabled them at the end.

    Other component that caused trouble was google-chrome – the F17 systems had a non-upgradable version that needed to be removed, then at the end I just reinstalled it.

    Doing all the lot took less than 1 week, including making full data backups and negotiating with users for best times – even on a fast machine with a local repository it would take hours (3 to 4 or more in slow machine cases), but at the end most of the things were OK and the users went merrily back to work.

    Except of a couple of individual issues, the fedup procedure worked just fine.


Leave a Reply

This work is licensed under a (cc) BY-NC | TecMint uses cookies. By using our services, you comply to use of our cookies. More info: Privacy Policy.
© 2012-2014 All Rights Reserved.