Upgrading from Fedora 7 to Fedora 8 with yum

Fedora 8 has been released so it is time to upgrade once again. First you should go back and upgrade to Fedora 7 if you haven't already. From there it is even easier this time to upgrade. Here are the steps you need to do the upgrade from Fedora 7 to Fedora 8:

  1. yum update
  2. yum clean all
  3. I like to repeated update and clean all a second time to make sure everything got updated
  4. Run the following command to update the yum repo on your box:
    rpm -Uhv http://mirror.anl.gov/pub/fedora/linux/releases/8/Fedora/i386/os/Packages/fedora-release-8-3.noarch.rpm  http://mirror.anl.gov/pub/fedora/linux/releases/8/Fedora/i386/os/Packages/fedora-release-notes-8.0.0-3.noarch.rpm
    
  5. Next do a yum -y update
  6. I needed to remove a couple packages to get the dependencies to work out. This seems to be a normal need now when upgrading but isn't usually a big deal. In this case I had to remove the heliodor and beryl-settings that both had to do with beryl.
  7. In my case the total set of packages it needed to download was 1.2G so it took about an hour to download and install. Now it was time for a reboot.
  8. The reboot went so fast I almost didn't believe it rebooted. This was the smoothest upgrade I have had so far.

Tags: ,

53 thoughts on “Upgrading from Fedora 7 to Fedora 8 with yum

  1. Lee

    Hello,

    nice guide, I had a similar problem when upgrading about the dependencies issue. Got it resolve much the same way though.

    http://www.leenukes.co.uk/?p=39

    Can you confirm if your gedit has a application bar above it? The one with Close, Minimize. Maximize etc.

    I'll put a screen shot on over the weekend if I get chance.

  2. Larry

    I followed the directions and updated the repo info.

    But when I tried yum -y update,

    I got:

    Setting up Update Process
    No Packages marked for Update

    What now?

  3. Mark

    I have complete steps 1 to 3 but when I come to do the rpm -Uhv I get the following error:

    error: Failed dependencies:
    fedora-release = 7 is needed by (installed) yum-fedorafaq-7-2007.11.02.noarch

    When I do a a uname -r I get the following:

    # uname -r
    2.6.23.1-21.fc7

    Do you have any ideas?

  4. David

    Hi All,

    If you use JAVA you might not want to upgrade yet. If you do you might get this problem:

    java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.

    So i installed the fc7 libX11-1.0.3-8.fc7.i386.rpm and libX11-devel-1.0.3-8.fc7.i386.rpm with the following command :

    rpm -ihv –force libX11-1.0.3-8.fc7.i386.rpm libX11-devel-1.0.3-8.fc7.i386.rpm
    (you can find them by fc7 search in http://rpm.pbone.net/index.php3/stat/2/simple/2)

    and then removed the problematic version (libX11-1.1.3-4.fc8.i386.rpm and libX11-devel-1.1.3-4.fc8.i386.rpm) via SMART package manager.

    It worked so try it out until an update comes out with this resolved.

  5. Andy

    Hi All,

    This worked a treat, not even any dependency issues. the only problem I have noticed is that whenever I run yumex I get "Metadata file does not match checksum" haven't used it in ages so not sure if this is related.

    Thanks

  6. Leif Gruenwoldt

    I got the following error during 'yum -y update'

    Error: Missing Dependency: gecko-libs = 1.8.1.8 is needed by package yelp
    Error: Missing Dependency: gecko-libs = 1.8.1.8 is needed by package epiphany
    Error: Missing Dependency: gecko-libs = 1.8.1.8 is needed by package devhelp

    I manually removed those rpms and redid the yum update. I figure if all goes well after the update to fedora 8 i will just reinstall those 3 rpm's one by one.

  7. Ken

    hey guys so i got to step 4 and did it fine but when i go to update it says that there is no Packages available for update …. not sure if i should restart just yet but any help would be great

  8. Glenn

    After I download and begin:

    yum update – it starts to downloaded the needed files and I get this error:

    Could not retrieve mirrorlist http://www.jpackage.org/jpackage_fedora-8.txt error was
    [Errno 14] HTTP Error 404: Not Found
    Error: Cannot retrieve repository metadata (repomd.xml) for repository: jpackage-fedora. Please verify its path and try again

    Any suggestions?

    Thanks,
    Glenn

  9. Philippe

    I got a loop:
    –> Running transaction check
    —> Package devhelp.i386 0:0.16.1-2.fc8 set to be updated
    –> Processing Dependency: gecko-libs = 1.8.1.8 for package: devhelp
    –> Processing Dependency: libiw.so.28 for package: kdenetwork
    –> Processing Dependency: libiw.so.28 for package: NetworkManager
    –> Running transaction check
    —> Package devhelp.i386 0:0.16.1-2.fc8 set to be updated
    –> Processing Dependency: gecko-libs = 1.8.1.8 for package: devhelp
    –> Processing Dependency: libiw.so.28 for package: kdenetwork
    –> Processing Dependency: libiw.so.28 for package: NetworkManager
    –> Running transaction check
    —> Package devhelp.i386 0:0.16.1-2.fc8 set to be updated
    –> Processing Dependency: gecko-libs = 1.8.1.8 for package: devhelp
    –> Processing Dependency: libiw.so.28 for package: kdenetwork
    –> Processing Dependency: libiw.so.28 for package: NetworkManager
    –> Running transaction check
    —> Package devhelp.i386 0:0.16.1-2.fc8 set to be updated

    What do you think??

  10. Felipe

    Upgraded sucessfully however there are still lots of FC7 packages installed:

    # yum list installed | grep fc7
    aspell.i386 12:0.60.5-3.fc7 installed
    aspell-pt.i386 50:0.50-12.fc7 installed
    automake14.noarch 1.4p6-15.fc7 installed
    bittorrent.noarch 4.4.0-5.fc7 installed
    dosfstools.i386 2.11-8.fc7 installed
    doxygen.i386 1:1.5.2-1.fc7 installed
    ethtool.i386 5-1.fc7 installed
    fbset.i386 2.1-24.fc7 installed
    festival.i386 1.96-1.fc7 installed
    festival-lib.i386 1.96-1.fc7 installed
    festival-speechtools-libs.i386 1.2.96-1.fc7 installed
    festvox-slt-arctic-hts.i386 0.20061229-1.fc7 installed
    gawk.i386 3.1.5-15.fc7 installed
    gdbm.i386 1.8.0-27.fc7 installed
    gdbm-devel.i386 1.8.0-27.fc7 installed
    gnome-mime-data.noarch 2.18.0-2.fc7 installed
    gnome-netstatus.i386 2.12.1-1.fc7 installed
    grep.i386 2.5.1-57.fc7 installed
    gtk-doc.noarch 1.8-2.fc7 installed
    htmlview.noarch 4.0.0-3.fc7 installed
    indent.i386 2.2.9-16.fc7 installed
    kernel.i686 2.6.23.1-21.fc7 installed
    kpartx.i386 0.4.7-11.fc7 installed
    libevent.i386 1.3b-1.fc7 installed
    libiec61883.i386 1.1.0-1.fc7 installed
    libiptcdata.i386 1.0.2-1.fc7 installed
    libopenraw.i386 0.0.2-5.fc7 installed
    libopenraw-gnome.i386 0.0.2-5.fc7 installed
    libsysfs.i386 2.1.0-1.fc7 installed
    mailx.i386 8.1.1-46.fc7 installed
    man.i386 1.6e-3.fc7 installed
    mktemp.i386 3:1.5-25.fc7 installed
    notify-python.i386 0.1.0-4.fc7 installed
    psgml.noarch 1.2.5-6.fc7 installed
    quota.i386 1:3.14-1.fc7 installed
    rp-pppoe.i386 3.8-1.fc7 installed
    ttmkfdir.i386 3.0.9-24.fc7 installed
    wavpack.i386 4.41-1.fc7 installed
    words.noarch 3.0-12.fc7 installed
    xorg-x11-util-macros.i386 1.1.5-1.fc7 installed
    zip.i386 2.31-3.fc7 installed

    What should I do? Remove them manually and reinstall??

    Suggestions?

  11. Felipe

    Well actually I just realised there are also some FC6 packages:

    # yum list installed | grep fc6
    dmidecode.i386 1:2.7-1.26.1.fc6 installed
    enchant.i386 1:1.3.0-1.fc6 installed
    keyutils-libs.i386 1.2-2.fc6 installed
    keyutils-libs-devel.i386 1.2-2.fc6 installed
    libavc1394.i386 0.5.3-1.fc6 installed
    libshout.i386 2.2.2-1.fc6 installed
    rng-utils.i386 1:2.0-1.14.1.fc6 installed
    splint.i386 3.1.1-15.fc6 installed
    xorg-x11-filesystem.noarch 7.1-2.fc6 installed

    Why does that happen? Should I care about that?

    # cat /proc/version
    Linux version 2.6.23.1-49.fc8 (kojibuilder@xenbuilder4.fedora.phx.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Thu Nov 8 21:41:26 EST 2007

  12. Jagtar

    Error: Missing Dependency: gecko-libs = 1.8.1.8 is needed by package yelp
    Error: Missing Dependency: gecko-libs = 1.8.1.8 is needed by package devhelp

    How to proceed after the above error after I did yum -y update

    then tried
    yum install gecko-libs
    got the following error message
    Requested dep: gecko-libs is provided by installed package
    Nothing to do

    then tried
    yum -y update gecko-libs
    Could not find update match for gecko-libs

  13. Antwaan

    Well i did steps 1-4 which i did 5 but it did nothin i did not see the "yum clean all" that i was suppose to do after the rpm install – but i did stick in the fedora dvd and it seems to be installing fine but i will report after it upgrades and let you know

  14. Antwaan

    Worked Good only thing that has given me troubles is the package/software updater i keep getin an errno 5 input/output error – anyone know how to fix this?

  15. Zumajim

    Thanks for posting this. I tried in vain to update Fedora 7 to 8 via DVD — it failed during dependency checks, evidently in some kind of endless loop. (It seems lots of folks are experiencing this problem.) In order to do your Yum upgrade, I had to uninstall two packages, NetworkManager and kdenetwork, which were causing a dependency loop too. Weird! But after that it was smooth sailing, even though it took 5 hours to download the 1200+ RPMs to do it. Great advice and thanks again.

  16. Mat Dac

    I also tried in vain to update Fedora 7 to 8 via DVD — it failed during dependency checks. The check did not reach an end even after 48 hours. I haven't solve the problem yet.

  17. Dandapani

    Trying this process to ugprade from FC6 to F8 on my laptop where the DVD drive is busted. The DVD upgrade hangs during the boot process. I am first upgrading yum and it brought in 199 packages for update. But first time through I had to manually remove some packages to eliminate dependencies:
    # rpm -e gnome-doc-utils yelp
    # rpm -e samba-common gnome-vfs2-smb samba-client
    So far so good…

  18. Dandapani

    Final status: I updated the kernel, then got brave and did the yum update. Took a few hours (slow laptop), but it finished and the reboot worked fine. I'm at F8 now. Thanks!

  19. Bates

    Very usefull guide.

    1st I gedit fedora.repo & replace old line with mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-8&arch=$basearch

    2nd I do # rpm -Uvh \
    ftp://ftp.osuosl.org/pub/fedora/linux/releases/8/Everything/i386/os/Packages/fedora-release-*.rpm

    3rd I do yum update

    Of course some package that in error with dependancy like heliodor and beryl-settings & 6 more package need to be removed.

    4th I do reboot

    5th After reboot, update available already popup require me to update all 891 new package.

    I'm done upgrading from moonshine to warewolf successfully!!!

    Once again, nice & usefull yet simple guide that works for me.

  20. ryan

    couple problems with the distribution …

    the current included php has a problem in php-mysql which causes stored procedures that return result sets to error-out.

    on virtuozzo the fc7->fc8 update causes the /etc/passwd and /etc/groups to become unreadable and the vm gets hosed.

  21. surya

    it shows kernel version for # uname -r
    2.6.20-1.2320.fc5

    while updating with # yum upgrade
    always im getting:

    Setting up Upgrade Process
    No Packages marked for Update

    Can anybody suggest the solution

  22. Rob Teed

    Upgrading Fedora7 to Fedora 8 with DVD.This is the fix I did.
    After using YUM to update Fedora 7 " Yum Update " I used " Yum clean all "
    Then I rebooted with my Fedora 8 DVD in the
    dvd drive, while it was booting I held
    down the "SHIFT" key. That brings up a menu.
    I think it was "F4" key I pushed.
    Then on the command line I typed:"linux updates=http://katzj.fedorapeople.org/updates-f8-yumloop.img"
    Without the quotes and only one space between the word linux and updates.
    Then hit enter and it booted up. Hope this helps.

  23. marco

    hello & thanks again for your great job carson. I've been using your meth to upgrade my fedora for a while now (fc5->fc6->f7->f8) and never had any problem neither with my personal laptop nor with professional dedicated server (ssh access only).

    This time from f7 to f8 I've had a perfect upgrade with my laptop but… a very strange issue after reboot : no response at all from distant server! no ping, no ssh, all services down.

    checking my logs in rescue mode I figured out that the box actually started fine but there was a problem with eth0 config making the box completely deaf.

    The explanation was that the upgrade process has replaced my old /etc/sysconfig/network-scripts/ifcfg-eth0 (configured for static ip with BOOTPROTO=static and IPADDR=xx.xx.xx.xx) with a new one configured with BOOTPROTO=dhcp and no IPADDR. I resolved the problem by replacing the new one by the .bak one and now it seems to work fine.

  24. Fr3d

    Perhaps you should mention that if you get this error:
    warning: /etc/yum.repos.d/fedora-updates.repo created as /etc/yum.repos.d/fedora-updates.repo.rpmnew
    warning: /etc/yum.repos.d/fedora.repo created as /etc/yum.repos.d/fedora.repo.rpmnew
    You need to swap the files around so it uses the Fedora 8 repos instead of 7 ;)
    Nice guide though, thanks :)

  25. Brian

    Tried this… FC7>FC8, got most of the way through…but it failed on FC8 dependency check on something called rsyslog vice syslog-ng error.

    I have no idea what these pkgs do so didn't go any further in attempts to rpm -e syslog-ng.

    Will have to do more research on this before I tray again.

    Cheers

  26. Mr. Meval

    I had several failures all of which there are excellent guides to fixing. I have crap going back to FC5!

    Sheesh.

    The instructions here have always been good. Systems with a lot of gunk are what'll nail you.

  27. Dave

    Marco,

    I administer several remote game servers. I recently had the misfortune to have to remotely tame an install of Fedora 7 done from a live CD image.

    I would strongly suggest removing NetworkManager from any server install.

    I wasted several hours discovering why a functioning system would lose the plot regarding its network configuration when I changed the default run level from 5 to 3 (full multi-user with no X). It turned out that NetworkManager was not being started at run level 3, hence my network config was changing unexpectedly and inconsistently.

    –Dave

  28. Darrell Duane

    when I ran yum update, I received an error indicating that the fc7 kernel was more recent than the fc8 kernel and it wouldn't update. I used rpm to remove the fc7 kernel and then yum update worked fine.

    –Darrell

  29. EPCTechno

    I would have to concur with Dave on post 34, NetworkManager is not for a SERVER_ENV whatsoever, it's only good for desktop/workstation. NetworkManager is a headache period, really you don't even need it.

  30. Alan

    These forums are great. I see all kinds of problems and all kinds of solutions. Different solutions to the same problems but unlike politics we get something done.

  31. lightpace

    i upgraded fc6 to fc8 directly ….everthing went well. except when i rebooted the box, the system prompts that it couldnt find my second physical hdd and cannot move onwards. if i choose fc6 from boot loader screen it works.. boots with fc6

  32. Ryan

    I went from fc6 to fc7 according to your "upgrade to Fedora 7" link at the top of this page, and all went well.

    I then followed the instructions and at step 5, after all the packages are downloaded, I receive this error:

    Transaction Check Error:
      package kernel-2.6.23.12-52.fc7 (which is newer than kernel-2.6.23.9-85.fc8) is already installed
    

    I am concerned mostly because I am now out of sync with both fc7 *and* fc8 ;)

  33. andy

    I too get Ryan's same error. Everything else acknowledges as being up to date when I do a rpm -q fedora-release

  34. Ammar

    Ryan, I just ran into the same Transaction Check Error. No need to be concerned with being out of sync with fc7 since you're moving to fc8. Removing the "newer" kernel with

    yum remove kernel-2.6.23.12-52.fc7

    and then, again,

    yum upgrade

    yields the desired Transaction Test Succeeded.

  35. Werner

    Hey Ryan, I have that exact same problem (Transaction Check Error: package kernel-2.6.23.12-52.fc7 (which is newer than kernel-2.6.23.9-85.fc8) is already installed). Have you found a solution yet?

  36. Dharmesh V Patel

    Did a two step upgrade from FC6 to Fedora 8. Both upgrades went perfect. I manually removed the avahi fc7 module after the FC7 to FC8 upgrade as it failed removal. Issued the rpm -e –noscripts avahi-0.6.17-1.fc7 command as instructed in the YumUpgradeFaqs located at: http://fedoraproject.org/wiki/YumUpgradeFaq

  37. Frank D. Gunseor

    Sirs:

    What a wonderful site. I have been able to upgrade from FC5 –> FC6 –> F7 –> F8, but I am having problems with the F8 upgrade.

    My system locked up during the initial run of the
    yum -y update command.

    After reboot F8 came up apparently fine, so I ran the yum clean all command.

    Now when I run the Software Update I get errors.

    I tried re-running the yum -y update command and I get the following:

    Transaction Summary
    =============================================================================
    Install 105 Package(s)
    Update 1193 Package(s)
    Remove 4 Package(s)

    Total download size: 1.5 G
    Downloading Packages:
    Running rpm_check_debug
    Running Transaction Test
    Finished Transaction Test

    Transaction Check Error:
    file /usr/share/man/man1/alias.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/bg.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/bind.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/break.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/builtin.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/cd.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/command.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/complete.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/continue.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/dirs.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/eval.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/exec.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/exit.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/fg.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/help.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/jobs.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/popd.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/pushd.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/read.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/return.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/set.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/source.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/trap.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/type.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/ulimit.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8
    file /usr/share/man/man1/umask.1.gz conflicts between attempted installs of bash-3.2-20.fc8 and fish-1.22.3-3.fc8

    Error Summary
    ————-

    [root@localhost fdavidg]#

    Any suggestions???

    Frank

  38. Magnus

    My upgrade can not fork…

    Downloading Packages:
    Running rpm_check_debug
    Running Transaction Test
    Finished Transaction Test
    Transaction Test Succeeded
    Running Transaction
    Updating : glib2 ################### [ 1/2073]
    error: Couldn't fork %post: Cannot allocate memory
    Updating : zlib ################### [ 2/2073]
    error: Couldn't fork %post: Cannot allocate memory
    Updating : atk ################### [ 3/2073]
    error: Couldn't fork %post: Cannot allocate memory
    Updating : popt ################### [ 4/2073]
    error: Couldn't fork %post: Cannot allocate memory

    […]

    Updating : libXau ################### [ 34/2073]
    error: Couldn't fork %post: Cannot allocate memory
    Updating : tcp_wrappers-libs ################### [ 35/2073]
    Updating : libxslt ################### [ 36/2073]
    error: Couldn't fork %post: Cannot allocate memory
    Segmentation fault

  39. Magnus

    The cannot allocate memory problem was solved by rebooting the system. However, 45 packets was installed twice – both the FC7 and the FC8 version. Solved that by:

    rpm -e chkconfig-1.3.36-1 `rpm -qa | grep "\.fc8"`

    After that, the installation worked as expected.

  40. Max

    I am getting this same error for all the packages I am trying to install using yum on FC8 i386:
    file [FILENAME HERE] conflicts between attempted installs of kernel-2.6.24.4-64.fc8.i686 and kernel-2.6.24.4-64.fc8.i586

    The exact same error message for all 92 packages. I have already downloaded them. What should I do?

  41. Max

    My problem is resolved:

    # uname -a

    I found out my version was i686, so I then excluded all the i586 packages.

    # yum –exclude=*.i586 update

    I received no transaction error and I didn't have to download anything again.

  42. Pingback: Upgrading from Fedora 8 to Fedora 9 with yum @ IONCANNON

Leave a Reply

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