4 Ways to Upgrade from Fedora 17 to Fedora 18

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Get your own self-hosted blog with a Free Domain at ($3.45/month).
  4. Become a Supporter - Make a contribution via PayPal
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Ravi Saive

I am Ravi Saive, creator of TecMint. 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. Follow Me: Twitter, Facebook and Google+

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

3 Responses

  1. andrej says:

    fedup is nice, but for upgrading vintage systems (like fedora 17 at the end of 2015) one have to provide installation repository address using instrepo parameter:

    fedup –network 18 –instrepo http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/18/Fedora/x86_64/os/

  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.


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

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.