Upgrading from FC6 to Fedora 7 with yum

Now that Fedora 7 has been release it is time to upgrade from that crusty old Fedora Core 6. Note that they have removed the "Core" from the name so a few things have changed with the paths used in yum. Last year I did a post on how to upgrade from FC5 to FC6 and this upgrade happened on the first box I used for that.

  1. Before you start see the note after these steps about checking for disk labels
  2. yum update
  3. yum clean all
  4. I repeated update and clean all a second time to make sure everything got updated
  5. I then ran the command:
    rpm -Uhv http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/x86_64/os/Fedora/fedora-release-7-3.noarch.rpm http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/x86_64/os/Fedora/fedora-release-notes-7.0.0-1.noarch.rpm
  6. I then found that I had to move fedora-development.repo and fedora-updates.repo out of /etc/yum.repos.d/ and replace them with fedora-development.repo.rpmnew and fedora-updates.repo.rpmnew. I also needed to remove a custom repo I had but no longer used so I didn't take time to figure out why it needed to be removed.
  7. I then did a yum -y update and waited
  8. After a good wait another X server was started so you may think about not doing the update while running under X. Luckily it was able to start on another console so all was ok. Now it was time for a reboot.
  9. After the reboot I had to fix up some NVidia issues but overall it looks like it upgraded without a problem

Notes on disk labels:

There are a few things listed in the release notes under Upgrade Related Issues.

The first was to make sure all your drives have labels. You can do this by running the command "/sbin/blkid" and then checking that each line that is not part of the LVM system has a LABEL entry. If you need to add a label to a drive use the "/sbin/e2label" command and then edit your /etc/fstab to use the label on boot instead of the device.

LABEL=/boot             /boot                   ext3    defaults        1 2

You don't need to label LVM drives since the LVM keeps track of the drives it uses on its own. The only drive I had on a stock install that wasn't under the LVM was /boot and it had a label already.

After you upgrade they sugest running the following command and then upgrading anything that has a date before the upgrade date:

rpm -qa –last > RPMS_by_Install_Time.txt

Tags: ,

93 thoughts on “Upgrading from FC6 to Fedora 7 with yum

  1. Orry

    I tried this upgrade but came up with this error:
    error: Failed dependencies:
    fedora-release = 6 is needed by (installed) yum-fedorafaq-6-2007.02.03.noarch

    Any Ideas???
    Please…

  2. bruk habtu

    Hey, i had dependancy issues will libgcj so i removed the stuff that required it (cairo-java libgconf-java glib-java libgtk-java frysk libgnome-java libglade-java ). Upgrade went smoothly but now i think i have broken some stuff. I tried reinstalling it but yum tells me that i need libgcj.so.8rh. Which doesnt seem to exist anywhere. I would like to reinstall those packages i removed.

  3. Rainer Molitor

    First thanxs for your information about the upgrade. I had to do it this way cause my hardware is really old and i have no DVD Drive and no fast USB for an external disk.

    I ran into a litte problem with missin dependancies to python(abi). I solved this problem just by: "rpm –rebuilddb" and now everything works fine.

  4. jonathan

    did anyone ever figure out the workaround for mkinitrd? I still get the error saying I need nash, even though the exact version it wasn't is installed.

  5. Geir Pedersen

    I had to uninstall Open Office and some other packages to get the update running.

    After update and reboot, I had problems reinstalling Open Office. Found I had to manually download and install (rpm -U –nodeps) certain packages.

    Thanks for the guide!

  6. jonathan

    I did get that fixed by uninstalling things related to nash, and uninstalling the x86 versions of mkinitrd. However I get an error saying thatfleminggent repo is not signed. and nothing installs.

  7. Tim

    Thanks for the rather simple instructions. I hit the libgcj issue as well. Upgrading i386 rpms not x86_64 rpms. The FC6 version is indeed newer. Zeroed in and resolved it no issues. Thanks to those who preceeded me.

    Have problems in FC7 running webmin in secure mode (https://…). Webmin works fine w/o secure mode. Looks like perl SSLeay is out of date. Failed to find an up to date FC7 perl module. The SSLeay module complains about an undefined subroutine: ::CTX_new being called by webmin.

    Also, logwatch perl choked on a rouge Errno.pm sitting in /usr/lib/perl5/site_perl/5.8.8. I removed it and logwatch works.

    Nice way to get from FC6 –> FC7.

  8. Mark

    RE: Instruction 6 – "move fedora-development.repo and fedora-updates.repo out of /etc/yum.repos.d/ and replace them with fedora-development.repo.rpmnew and fedora-updates.repo.rpmnew."
    I found that just adding the *.rpmnew files worked instead of moving the old out.
    Anybody Else?

  9. Scott

    Thank you very very much for this. I used to it upgrade FC-7 to 8. (There are various differences–for instance the release rpm is in a different location) but the basic concept made it simple.

    Thank you.

  10. Nick

    I recently tried the upgrade from fedora 6 to fedora 7 via yum. Everything looked ok until I rebooted the box. When using the 2.6.22.5-76 kernel, the box kernel panics with no init found. The legacy fedora 6 kernel will boot without issue. I read that fedora 7 has problems with unlabeled partitions, however the only labeled partition I have is /boot (which is labeled properly). Everything else is LVM. I'm at a complete loss at the moment.

  11. Tom Craddock

    Hi all,

    Ive been trying to follow all the above info, post and comments, and have run into a couple of problems already mentioned here, but never really got a clean answer about any of them. When I do yum -y update I get the below

    Error: Unable to satisfy dependencies
    Error: Package cairo-java needs libgcj.so.8rh, this is not available.
    Error: Package glib-java needs libgcj.so.8rh()(64bit), this is not available.
    Error: Package libglade-java needs libgcj.so.8rh()(64bit), this is not available.
    Error: Package mkinitrd needs nash = 5.1.19.0.3-1, this is not available.
    Error: Package libgnome-java needs libgcj.so.8rh()(64bit), this is not available.
    Error: Package cairo-java needs libgcj.so.8rh()(64bit), this is not available.
    Error: Package pidgin needs libedataserver-1.2.so.7, this is not available.
    Error: Package libgtk-java needs libgcj.so.8rh, this is not available.
    Error: Package glib-java needs libgcj.so.8rh, this is not available.
    Error: Package libvte-java needs libgcj.so.8rh()(64bit), this is not available.
    Error: Package libgnome-java needs libgcj.so.8rh, this is not available.
    Error: Package libgconf-java needs libgcj.so.8rh()(64bit), this is not available.
    Error: Package libvte-java needs libgcj.so.8rh, this is not available.
    Error: Package libglade-java needs libgcj.so.8rh, this is not available.
    Error: Package frysk needs libgcj.so.8rh()(64bit), this is not available.
    Error: Package mkinitrd needs libparted-1.8.so.2, this is not available.
    Error: Package libgtk-java needs libgcj.so.8rh()(64bit), this is not available.

    I already have nash 5.1.19.0.3-1 installed and have tried the –enable-testing to fix the libgcj problem, but then get another set of dep problems,

    Error: Unable to satisfy dependencies
    Error: Package mkinitrd needs nash = 5.1.19.0.3-1, this is not available.
    Error: Package frysk needs libgcj.so.7rh, this is not available.
    Error: Package pidgin needs libedataserver-1.2.so.7, this is not available.
    Error: Package mkinitrd needs libparted-1.8.so.2, this is not available.

    Yet again a problem with nash, I can remove the pidgin and frysk, I dont mind about them, but mkinitrd still doesnt want to work. Any ideas?

  12. Charles

    Hi,
    I'm exactly at the same situation than Nick, (and with no terminal access 'cause I rent a dedicated server).
    the old kernel is Fedora 5, the new one fedora 7.
    At this moment, it's booted on the old kernel but can't reboot it till I fix the grub problem.

    Thank for help

    Regards

    Tony

  13. Joe

    When I run 'yum -y upgrade', I also get several python dependency errors. How do I get around this?
    I tried doing a 'yum localinstall python…rpm, but I get the same errors. Seems like I am running into a circular dependency.

  14. Jon

    Do you have to label the swap partition? My blkid output says:

    /dev/hda3: LABEL="/" UUID="a2e18d02-c5e4-44a3-ab89-daa94cc7891c" SEC_TYPE="ext2" TYPE="ext3"
    /dev/hda2: TYPE="swap"
    /dev/hda1: LABEL="/boot" UUID="576180e9-03cc-4ff1-9a39-fb3c8eaa4e56" SEC_TYPE="ext2" TYPE="ext3"

    As you can see, /dev/hda2 is the swap, but there is no label. Attempting to label it, I get the error:

    /sbin/e2label: Bad magic number in super-block while trying to open /dev/hda2
    Couldn't find valid filesystem superblock.

    I'd hate to install and reboot only to find that I no longer have a swap drive…

  15. John

    How do you get around the python(abi) = 2.4 dependency issue. I tried to blow away what needs it but it was too much stuff like yum etc so I backed out. Also another poster said to rpm –rebuilddb but that didn't work.

    Also, I get hpijs needs libnetsnmp and I don't even have hpijs installed.

  16. Artem S. Tashkinov

    Nick & Charlie:

    Probably you have to recreate initrd of your Fedora 7 kernel by issuing this command under root account (or use sudo):

    mkinitrd /boot/initrd-2.6.22.5-76 2.6.22.5-76

    then check the contents of /boot/grub/grub.conf

  17. Pingback: Trylinux.org » Installing with Media is so 90s

  18. Edwin

    If you're new and hesitant to upgrade your system this way, don't forget that you can always burn the install DVDs and update that way. It's also the preferred method of upgrading that the Fedora mantainers recommend.

  19. Esteban

    I've tried everything here and moved ahead, to yum upgrade to FC7 but had more troubles.
    1) I had to erase many i386 libraries by hand (Mine is a 64bit PC with a FC7 x86_64). It looks like I had old libraries from previous installs that were not needed anymore. Sometimes I had to point to the whole name of the library which was causing the trouble to avoid having half my Fedora erased due to dependencies.
    2) Then I also had memory problems and sorted that out with starting my computer without Gnome or KDE (how is it called in English? In Spanish ys just a console "A prueba de fallos" or something like that. Then when I run yum -y update it worked out fine (after two days of struggle, of course).
    All this probably seem quiet obvius for most users but was missing in most sites so other newbies can probably appreciate the tip.
    thanks a lot

  20. Esteban

    One last thing: does anyone else have trouble after the upgrade with open office? I can't use it because it freezes my fedora both in gnome and KDE.
    ???

  21. Jon

    I have done several of these updates on several boxes, but only one has been set up with LVM's and it is giving me fits. I'm hoping I can get some insight! Here is my /etc/fstab:

    /dev/RootUsr/root / ext3 defaults 1 1
    LABEL=/boot /boot ext3 defaults 1 2
    devpts /dev/pts devpts gid=5,mode=620 0 0
    tmpfs /dev/shm tmpfs defaults 0 0
    /dev/Home/home /home ext3 defaults 1 2
    proc /proc proc defaults 0 0
    sysfs /sys sysfs defaults 0 0
    /dev/TmpVar/temp /tmp ext3 defaults 1 2
    /dev/RootUsr/usr /usr ext3 defaults 1 2
    /dev/RootUsr/usrlocal /usr/local ext3 defaults 1 2
    /dev/TmpVar/Var /var ext3 defaults 1 2
    LABEL=SWAP-sda5 swap swap defaults 0 0

    Here is my /etc/grub.conf:

    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE: You have a /boot partition. This means that
    # all kernel and initrd paths are relative to /boot/, eg.
    # root (hd0,0)
    # kernel /vmlinuz-version ro root=/dev/RootUsr/root
    # initrd /initrd-version.img
    #boot=/dev/sda
    default=0
    timeout=5
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    # FC7 is kernel panicing with being unable to find /dev/root, will set to boot in FC6 for now
    title Fedora (2.6.22.9-91.fc7)
    root (hd0,0)
    kernel /vmlinuz-2.6.22.9-91.fc7 ro root=/dev/RootUsr/root rhgb quiet
    initrd /initrd-2.6.22.9-91.fc7.img
    title Fedora Core (2.6.20-1.2925.fc6)
    root (hd0,0)
    kernel /vmlinuz-2.6.20-1.2925.fc6 ro root=/dev/RootUsr/root rhgb quiet
    initrd /initrd-2.6.20-1.2925.fc6.img

    and my /sbin/blkid:

    /dev/mapper/RootUsr-usr: UUID="30efb3c6-afbe-4317-b305-abfd963a937c" SEC_TYPE="ext2" TYPE="ext3"
    /dev/mapper/Home-home: UUID="94fbd273-d772-48e1-85bc-4b538da687f3" SEC_TYPE="ext2" TYPE="ext3"
    /dev/mapper/TmpVar-temp: UUID="0ceb8a2d-560e-413c-977c-21553ed0862f" SEC_TYPE="ext2" TYPE="ext3"
    /dev/mapper/TmpVar-Var: UUID="0698dc8b-a4bc-479a-9a78-a255adb64d19" SEC_TYPE="ext2" TYPE="ext3"
    /dev/mapper/RootUsr-root: UUID="8ece899e-6da2-4c5b-9bbb-10a9e3c508c9" SEC_TYPE="ext2" TYPE="ext3"
    /dev/mapper/RootUsr-usrlocal: UUID="0d01b49f-cba1-4891-94b5-126f1176dee4" SEC_TYPE="ext2" TYPE="ext3"
    /dev/sda1: LABEL="/boot" UUID="e7513adf-203b-4f57-a30f-52b4eec84b0a" SEC_TYPE="ext2" TYPE="ext3"
    /dev/sda5: TYPE="swap" LABEL="SWAP-sda5"
    /dev/RootUsr/root: UUID="8ece899e-6da2-4c5b-9bbb-10a9e3c508c9" SEC_TYPE="ext2" TYPE="ext3"

    I get a kernel panic with it saying it cannot mount /dev/root

    It boots fine if I roll back to FC6

  22. David

    It worked perfectly for me. I'm using raid.

    If, like me, you have the server in a remote location it's a good idea to use grub's "savedefault" and "fallback" features. That way you can tell grub to fall back to another kernel if the default panics.

  23. Mark

    After following this entire thread, I still have:

    Error: Missing Dependency: libnetsnmp.so.10 is needed by package hpijs
    Error: Missing Dependency: python(abi) = 2.4 is needed by package authconfig
    Error: Missing Dependency: python-abi = 2.4 is needed by package system-config-printer-libs
    Error: Missing Dependency: libedataserver-1.2.so.7 is needed by package pidgin
    Error: Missing Dependency: python(abi) = 2.4 is needed by package hplip
    Error: Missing Dependency: libnetsnmp.so.10 is needed by package hplip
    Error: Missing Dependency: python(abi) = 2.4 is needed by package rpm-python
    Error: Missing Dependency: libnetsnmp.so.10 is needed by package libsane-hpaio
    Error: Missing Dependency: python(abi) = 2.4 is needed by package system-config-printer-libs
    Error: Missing Dependency: python(abi) = 2.4 is needed by package libxml2-python
    Error: Missing Dependency: libpq.so.4 is needed by package dovecot

    What is the command to force the install? Or is that suggested?

  24. obmar

    keeps on stupping at this on doung a yum update.
    any suggestions?
    regards and tks

    –> Processing Dependency: libFLAC.so.7 for package: gstreamer08-plugins
    –> Processing Dependency: xine-lib = 1.1.9.1 for package: xine-lib-extras-nonfree
    –> Finished Dependency Resolution
    Error: Missing Dependency: libFLAC.so.7 is needed by package gstreamer08-plugins
    Error: Missing Dependency: xine-lib = 1.1.9.1 is needed by package xine-lib-extras-nonfree

  25. Philip Diaz

    I tried to upgrade fedora 6 to 7 and followed the instructions carefully. But after almost I was come-up an error such as -> Finished Dependency Resolution
    Error: Missing Dependency: python(abi) = 2.4 is needed by package authconfig
    Error: Missing Dependency: python(abi) = 2.4 is needed by package libxml2-python
    Error: Missing Dependency: python-abi = 2.4 is needed by package system-config-printer-libs
    Error: Missing Dependency: python(abi) = 2.4 is needed by package hplip
    Error: Missing Dependency: python(abi) = 2.4 is needed by package rpm-python
    Error: Missing Dependency: python(abi) = 2.4 is needed by package system-config-printer-libs
    Error: Missing Dependency: libedataserver-1.2.so.7 is needed by package pidgin

    I was tried to check the version of python installed and I am currently using Python 2.4.4 (#1, Oct 23 2006, 13:58:00)
    [GCC 4.1.1 20061011 (Red Hat 4.1.1-30)] on linux2
    Type "help", "copyright", "credits" or "license" for more information.

    Please help me to understand what's the meaning of the error were occured during yum update.

    I am looking forward for possible reply for the best minded people who are willing to share their ability and great knowledge to everyone.

    Thank you.

    Philip

  26. Greg James

    Zoltan,
    I had the same problem upgrading to F7. F7 would not see the boot drive and kept getting kernel panic. FC6 kernel would boot fine. Even when I booted with F8 install CD, the install did not see the hard drive.
    Two critical steps:
    1) manually change /boot/grub/device.map to it has /dev/sda and not /dev/hda.
    2) My old WD Cavier boot drive had the jumper on master. I changed the jumper to cable select (CS).
    Now F7 and F8 see the drive and everything works perfectly. I didn't think Fedora was picky about the master/slave/cable select thing, but starting in F7, it is.
    Hope this helps.
    Greg James

  27. Greg James

    Philip Diaz,
    I had a similar problem. I just rpm -e the packages having the problem then I could do the upgrade. Then I just yum installed them back in after the upgrade.
    Hope this helps.
    Greg James

  28. person1873

    i know people have been asking left right and center if it's possible to skip a version, and i'm no different appart from that i want to go from fc6 to f8. is this possible without the whole f7 step, could i just put the f8 repo's in rather than f7?

  29. Dharmesh V Patel

    This seems to be a very good guide EXCEPT that its for x86_64 systems. I did not realize that and stupidly fired the rpm -Uhv command on my non 64 bit system. I am still trying to recover. With more and more folks now running the new hardware which is 64bit, it might not be an issue but it might help if you put it up in the title that the steps are for x64 architecture. My upgrade is running currently and I will post the changes (no renaming to rpmnew is required etc) once the upgrade finishes. I intend to do a 2 step upgrade going from FC6 to Fedora 8.

  30. Dharmesh V Patel

    The two step upgrade went fine after I got the i386 versions of the rpms in the first command. All the dependency erros (there were hundereds of them) went away and an hour and half later I was at Fedora 7. I had the labels correctly and I followed the fedora Upgrading using yum instructions too and changed my boot drive to /dev/sda in the grub config (from /dev/hda/) before booting. Machine booted up just fine.

    Thanks for the instructions. They too came in pretty handy.

  31. anon

    I had a problem after the update on a system where LVM was on a soft RAID. The system has 2 ATA and 2 SATA drives on soft (md) RAID-1 configuration. Yes, I know, I could make raid on LVM by itself, but at the time it was built I was more familiar with md. Know, upon boot with the kernel of fedora 7, the order of drives changes, and sata drives do not come as sda/sdb but as sdbc/sdd, and the ata disks take the sda & sdb labels. As i have the / partition on ata disks, the system boots, but loses completely the filesystem on LVM (it does not get recognized). Any hints will be welcomed!

  32. Matt

    Good work Artem S. Tashkinov !!!

    Your tip to re-create the initrd image fixed my problem.

    Now I just need to figure out why udev is only building device nodes for 2 out of 4 drives in my RAID array… :-(

  33. Ron

    I ran yum update and only had issues with Python like others.. I removed authconfig vlc 4Suite (part of Python). upgrade went great.. I then reinstalled a VLC package for fc7 and we are in business. I'll update 4Suite tomorrow.. don't even know if I need it or not.
    I also have softraid with 2 250GB drives with LVM and everything was labelled correctly.

    FC6 to FC7 went fine.. and this is after having this server running about a year on FC6 with no problems..

    Thanks for all the good tips.

  34. doc

    for those on 64-bit machines having problems saying "nash" is required, etc., and in case you (i) forgot the extremely forgettable syntax for querying package architectures (i have run into this many times, and each time i come back here to remember, and re-figure this out):

    1. run this

    rpm -q –queryformat='%{N}-%{V}-%{R}.%{arch}\n' mkinitrd
    rpm -q –queryformat='%{N}-%{V}-%{R}.%{arch}\n' parted
    rpm -q –queryformat='%{N}-%{V}-%{R}.%{arch}\n' nash

    2. then remove the x86 ones (may vary):

    rpm -e parted-1.8.2-2.fc6.i386
    rpm -e mkinitrd-5.1.19.0.3-1.i386

    2. then yum upgrade works…

Leave a Reply

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