Werewolf (Fedora 8) Upgrade in 3 Easy Steps Using yum

Recently, there was a request in one of my comments on this post. The request was for an easy way to upgrade from Fedora 7 to Fedora 8. So I took this on as a bit of a challenge. I feel pretty comfortable with yum and I thought it would be a good and easy task.

A bit of warning here, make sure your current Moonshine ( Fedora 7 ) release is update by running yum update. Also, it is recommended that backups be made of files being modified. If you don’t backup the file, it may be impossible to fix in the future. YOU HAVE BEEN WARNED

Let’s upgrade Moonshine ( Fedora 7 ) to Werewolf ( Fedora 8 ) in three easy steps:

First things first, lets print out some version info:

$ cat /etc/*release
Fedora release 7 (Moonshine)
Fedora release 7 (Moonshine)
$ uname -r

Its easy to tell that this machine is indeed using Moonshine ( Fedora 7 ), so let’s upgrade!

Step 1 – Modify the yum repo files

Located in /etc/yum.repos.d directory are where the yum repository files are stored. We need to modify one line so that yum will know where to look:

$ su -
# vim /etc/yum.repos.d/fedora.repo

Find the first line that starts:


and change it:


What changed? Well, the $releasever value is the current value for our version of fedora, in this case 7. By changing it to 8, it’ll load the correct repositories for Werewolf (F8) instead of Moonshine (F7). Save the file, and now we’re ready to move onto the next step.

Step 1 (Alternate)

Since posting this, I’ve learned that another option is available. To update the repositories, its possible to install an rpm to accomplish the same as above and it won’t require Step 3.

Choose your mirror from http://mirrors.fedoraproject.org. I picked University of Oregon’s site because it was close to me.

# rpm -Uvh \

Your ftp/http line here may be different, that is fine. This command installs the updated repositories for Werewolf ( Fedora 8 )

Step 2 – Upgrade

In this step, we just need to run (as root):

# yum update
fedora               100% |===============| 2.1 kB   00:00
primary.sqlite.bz2   100% |===============| 4.9 MB   00:03
Setting up Update Process
Resolving Dependencies
.. snip ..

A few prompts will appear, after the repository data is loaded, a list of several hundred megs (possibly a gigabyte or more) of packages will be ready to install. This is the moment of truth.

Transaction Summary
Install     88 Package(s)
Update     836 Package(s)
Remove       1 Package(s)

Total download size: 1.0 G
Is this ok [y/N]:

Start the download of over 800 packages (in my case) and install and update your system. If you feel a bit of trepidation, I concur. Its still exciting though, isn’t it?

Is this ok [y/N]: y

Now aren’t you excited! In about 30-45 minutes, you’ll have a newly upgraded Werewolf ( Fedora 8 ).

Downloading Packages:
orca- 100% |=========================| 1.5 MB    00:01
.. snip ..

Step 3 – Cleanup and Reboot

Welcome to your new Werewolf. Treat it wisely. First things first though, we need to clean up our editing from step 1:

# vim /etc/yum.repos.d/fedora.repo

Find the first line that starts:


and change it:


Save the file, or if you prefer, copy the backup you made over the modified repo file.

In addition, there are some items that aren’t in Fedora 8 the same way they were in Fedora 7. For these, read this guide. I didn’t have these problems myself, ymmv.

To get the newly updated kernel and all the new goodness of Werewolf, a reboot is necessary. Enjoy your new Lycanthrope on the flip side.



This entry was posted in Fedora, Guru, Install, Releases, Tech, Tools, Yum and tagged , , , , . Bookmark the permalink.

15 Responses to Werewolf (Fedora 8) Upgrade in 3 Easy Steps Using yum

  1. Nils says:

    Beware of “Cannot upgrade F7 -> F8 with DVD on x86_64” https://bugzilla.redhat.com/show_bug.cgi?id=371111 though.

    If doing a yum upgrade (as opposed to one with the installer), you might be better off by grabbing and installing a new (F8) fedora-release instead of modifying the repo definitions manually, that way all repos should switch to the new version and yum shouldn’t hang because it can’t resolve dependencies.

  2. JP says:

    Why can’t this be made into a formal process/rpm? I think the Fedora devs, who I’m very appreciative to, should consider this a requirement for F9 big problem.

  3. JG says:

    This seemed to proceed fine for my older 32-bit Athlon system, but then yum entered into an infinite loop when trying to process dependencies for yelp and devhelp:

    –> Running transaction check
    —> Package yelp.i386 0:2.20.0-2.fc8 set to be updated
    –> Processing Dependency: gecko-libs = for package: yelp
    –> Processing Dependency: xine-lib = 1.1.7 for package: xine-lib-extras-nonfree
    —> Package devhelp.i386 0:0.16.1-2.fc8 set to be updated
    –> Processing Dependency: gecko-libs = for package: devhelp
    –> Processing Dependency: libmpcdec.so.3 for package: mplayer-gui
    –> Processing Dependency: libmpcdec.so.3 for package: mplayer
    –> Processing Dependency: libmpcdec.so.3 for package: gstreamer-plugins-bad
    –> Processing Dependency: libmpcdec.so.3 for package: vlc
    –> Processing Dependency: libneon.so.25 for package: gstreamer-plugins-bad
    –> Processing Conflict: glibc-common conflicts glibc > 2.6
    –> Processing Conflict: elfutils-libelf conflicts elfutils > 0.127-1.fc7
    –> Processing Conflict: elfutils-libelf conflicts elfutils-libs > 0.127-1.fc7
    –> Processing Conflict: elfutils-libelf conflicts elfutils-libelf-devel > 0.127-1.fc7
    –> Processing Conflict: elfutils-libs conflicts elfutils > 0.127-1.fc7
    –> Processing Conflict: pam conflicts db4 >= 4.6.0
    –> Processing Conflict: glibc-common conflicts glibc Restarting Dependency Resolution with new changes.

    This just repeats endlessly (as I type this!)

  4. Joel says:


    Is the process I used for my upgrade.


    – I needed to run a yum update kernel before doing the big package update. Otherwise it had problems resolving dependencies and wanted to include .i586 and .i686 kernels.

    – After the upgrade I had an issue with audio. The files in /dev/snd/ were owned by root and pulseaudio couldn’t access them… just a lead in case someone else sees that.

  5. Jim says:

    I’m using Parallels via OSX to run Fedora, and although I have no trouble bringing up the fedora.repo file, I can’t seem to edit it. The cursor just moves around and I can’t type anything or delete anything. It’s acting like it’s a read only file. Is this because of the virtualization involved, or am I missing something much more basic here? Thanks.

  6. herlo says:


    As a recommendation, make sure you are root when you edit these files. Another thought might be the editor you are using. Personally, I dig vim as my favorite editor, but it requires a learning curve to get started. Maybe gedit /etc/yum.repos.d/fedora.repo would be more your style.

    Another thought would be to perform the alternate step 1 I recently discovered myself.



  7. Jim says:

    Thanks Herlo. Actually I followed your directions to the letter and did switch to root before attempting to edit the file. Therefore, I must be missing something in vim – I’m used to using pico. Thanks for your suggestion.

  8. janschan says:

    “Total download size: 1.0 G”?!
    It’s too big for my network!
    It will cost 2-3 days!
    So, can I upgrade my os in DVD ISO?

    first, mount it to somewhere.
    second, yum update *.rpm from it.



  9. herlo says:


    yes, you can upgrade from the DVD using yum. However, I’d recommend just sticking the DVD in and rebooting your machine. Choose upgrade and you’ll be off to the races. Be forewarned that as with any upgrade, it is best to backup your data.



  10. Janschan says:

    Thanks for your recommendation, but I have no DVD burners.
    I just down a fedora 8 DVD iso file now.

    and as Nils said, there’s a bug in upgrade fedora 7 to fedora 8 with DVD.


  11. fedorax says:

    (1085/1215): openoffice.o 100% |=========================| 1.4 MB 03:39
    (1086/1215): mesa-libGLU- 100% |=========================| 203 kB 00:35
    (1087/1215): xmms-sid-0.8 100% |=========================| 120 kB 00:32
    (1088/1215): gcc-4.1.2-33 100% |=========================| 5.2 MB 14:07
    (1089/1215): libxcb-1.0-3 100% |=========================| 117 kB 00:11
    (1090/1215): audit-libs-1 100% |=========================| 61 kB 00:04
    (1091/1215): nfs-utils-li 100% |=========================| 59 kB 00:16
    (1092/1215): libgail-gnom 100% |=========================| 26 kB 00:05
    (1093/1215): directfb-1.0 100% |=========================| 1.0 MB 02:42
    (1094/1215): akode-pulsea 100% |=========================| 7.8 kB 00:00
    (1095/1215): psacct-6.3.2 100% |=========================| 59 kB 00:04
    (1096/1215): mono-data-1. 100% |=========================| 1.8 MB 01:11
    (1097/1215): hal-libs-0.5 100% |=========================| 60 kB 00:11
    (1098/1215): kdenetwork-3 100% |=========================| 10 MB 09:12
    (1099/1215): perl-IO-Sock 100% |=========================| 50 kB 00:10

    The exitement awaiting…..
    I’ll follow up later… since the process still going on.. just about 115 package to go!!
    Very simple yet works step to upgrading from f7 > f8.

  12. fedorax says:

    [bates@bates ~]$ uname -r
    [bates@bates ~]$ cat /etc/*release
    Fedora release 8 (Werewolf)
    Fedora release 8 (Werewolf)
    Fedora release 8 (Werewolf)
    [bates@bates ~]$

    Finally I’m done with no errors.
    Thanx again for the usefull simple guide!

  13. Matt says:

    “#yum clean all” may be required after installing fedora-release to get yum to realize you want the packages for the new release, otherwise it may show you updates for 7 instead.

  14. Centos Gone says:

    this also works to convert from Centos! Thanks for the tip!

  15. Pingback: Clint Savage: Wow: UTOSC 2009 is actually 2 weeks away! | TuxWire : The Linux Blog

Leave a Reply

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