How to upgrade from FC4 to FC5 via yum?
March 26th, 2006
Okay, this was something i wanted from the day i saw FC5 release news. Gnome 2.14… was dying to try it (outside vmware & outside a vnc session!)
But had absolutely no clue on how to start this upgrade as
yum upgrade
on vanilla FC4 just updates the system to latest package versions in FC4 repository. Also, i did not wanted to fiddle with yum.conf manually as the system under consideration is my production system! So no risks atall… or i would have to use my test system (which i’m still to get) as my production system. I would certainly not like that… & even my manager wont!
Okay, enough of crap… lets get to business!
NOTE - all steps are to be performed from a root console. You’ll need a decent internet connection to make this happen (in real time!)
0. yum update kernel kernel-devel initscripts kudzu
This should update your kernel to latest in FC4. This is an important step!
1. rpm -qa | grep fedora-release
2. if you find something like “fedora-release-4-2″ as the output, go to step 3, else to step 4
3. rpm -U http://download.fedora.redhat.com/pub/fedora/linux/core/5/i386/os/Fedora/RPMS/fedora-release-5-5.noarch.rpm
This will update your yum configuration to fetch latest fc5 rpm’s.
4. rpm -ivh http://download.fedora.redhat.com/pub/fedora/linux/core/5/i386/os/Fedora/RPMS/fedora-release-5-5.noarch.rpm
This will set up your yum repositories to fetch latest rpm’s.
5. [optional - steps 5-8] To add livna repositories (extra packages)
rpm -qa | grep livna
6. if you find something like “livna-release-4-0″, go to step 7, else to step 8
7. rpm -U http://rpm.livna.org/livna-release-5.rpm
8. rpm -ivh http://rpm.livna.org/livna-release-5.rpm
9. yum update yum
This is important as the latest yum package is damn faster than the old one. You’ll love the speed!
10. yum upgrade
This will fetch lots of package headers & in the end, you’ll need to say “Y” to start the actual packages download & install. If you want to skip the “y/N” stage, try this
yum -y upgrade
11. Enjoy the coolness!
![]()
Corrections/suggestions all welcome as comments.
Thanks ![]()
A new FC5 user
[update]
Try to leave the “optional” repositories till the upgrade is complete. This is just to make sure that unecessary deps are not created.
Also, if you get any broken dependencies for packages except (kudzu, initscripts), have a look at http://www.brandonhutchinson.com/Upgrading_Red_Hat_Linux_with_yum.html
Related fedoraforum.org thread -> Thread
![]()
Posted in Fedora Core, GNU/Linux | Comments (48)
March 24th, 2006 at 12:16 am
The upgrade sadly aborts with missing deps
http://forums.fedoraforum.org/showthread.php?t=100204
March 28th, 2006 at 2:27 am
No comments on FC5. Dropped in to say thnx for listing my blog here. It’s nice to c ur blog listed on a Red Hat guy’s space
March 28th, 2006 at 7:04 am
You are welcome Baxi. Btw, there’s nothing so special like “Red Hat guy’s”. Its just a plain & simple blog, which belongs to me. Red Hat just happens to be its part. This blog was here before i became part of RH & will be here even after me & RH part ways.
Thanks anyways
April 6th, 2006 at 1:49 pm
I get error as listed. Any idea how to fix it. Thanks. – Ds
Transaction Check Error: file /usr/share/locale/cs/LC_MESSAGES/wxstd.mo confli cts between attempted installs of compat-wxGTK-common-2.4.2-17.fc5 and wxGTK-2.6 .2-5.fc5
April 7th, 2006 at 2:13 am
Deepak, you might want to remove wxGTK in fc4, upgrade & then reinstall it once you get in FC5 successfully…
April 11th, 2006 at 6:12 am
You might want to start using yum update instead of yum upgrade as upgrade is deprecated and will be removed in the future.
Why don’t you ‘rpm -q fedora-release’ instead of ‘rpm -qa | grep fedora-release’? It’s a lot faster as you don’t need to query all rpms on your system. Same goes for ‘rpm -qa | grep livna’. Just do a ‘rpm -q livna-release’.
And why do you rpm -U the new *-release rpms and then rpm -ivh them after that? Does installing them twice help?
Other than that, this is just the way I updated my system from FC4 to FC5. Works like a charm.
April 11th, 2006 at 6:39 am
Hi Nils,
yum upgrade is necessary. Please refer to yum’s man page which says that “yum upgrade” includes the—obsoletes flag which helps when changing distro versions.
I did an “rpm -U” because if you have fedora-release-4.2 installed & try with “rpm -ivh fedora-release-5.5.rpm”, lots of conflicts arise.
I used “rpm -qa | grep package” only because you dont need the exact package name
Cheers!
April 11th, 2006 at 6:46 am
Hmm, I realised I was looking at a yum manpage on a FC2 box. There it says upgrade will be deprecated. I guess not then.
You’re right that you shouldn’t rpm -ivh fedora-release-5.5, but after you do -U (or -Uvh if you like) there is really no need to install it a second time. -U already took care of that for you. Actually -U is almost always a better idea than -i when using rpm (except for kernels and kernel modules probably).
I don’t know what you mean with your last comment. You know it’s called fedora-release, right? Well then just rpm -q fedora-release and it displays your version.
April 11th, 2006 at 6:56 am
See, the step 2 asks you to search for fedora-release. If you get a 4.2 version, goto step 3 (which says -U) or go to step 4 (which says -ivh).
I hope this solves your first concern
I always use -qa rather than -q as sometimes (infact, most of the times), i just remember the part of package’s name. & this step was totally out of that habit
Mayank
April 11th, 2006 at 8:00 am
Ok, sorry, now I see. You’re covering for people that somehow don’t have fedora-release installed. Still, if you go to step 3 it’s not very useful to go to step 4 after that.
April 11th, 2006 at 8:11 am
April 12th, 2006 at 5:43 pm
Just followed your guide, perfect, just what I needed. Thanks for providing the easy to follow steps. Take it easy.
April 13th, 2006 at 1:17 am
You are welcome Simon
April 17th, 2006 at 4:34 am
This was almost too easy!
You are the best Mayank
April 17th, 2006 at 4:36 am
Good to hear that it helped you.
Thanks
April 20th, 2006 at 1:01 am
Well, I’ve been trying it. Major pains. I had some conflicts due to an experiment with mono I did at one point; I accept that this is my problem and I need to clean it up. But yum has what I consider a severe bug! It will load a few hundred headers, detect a conflict, then blow all those headers away. It does the same for actual rpm packages. That’s hundreds of megabytes of wasted downloads! What is the rationale for this behavior, or is it just stupidity?
I haven’t looked in the bug database yet to see if this one is reported.
April 20th, 2006 at 1:40 am
Yeah, even i’ve faced this problem once in FC4. But i hope this bug/behaviour is not in new FC5’s yum. Have you upgraded yum before starting the upgrade?
April 21st, 2006 at 1:22 pm
The first thing to do is remove all the obsoleted RPMs. Look at the Fedora documentation site, then use rpm
e-nodeps on each RPM listed there, then try the upgrade.April 24th, 2006 at 1:38 am
Raj, i dont think leaving dependencies behind is a good idea, specially when upgrading to a new system.
April 24th, 2006 at 2:37 am
simply superb, very smooth process.
April 24th, 2006 at 3:15 am
Thanks Krishna
April 24th, 2006 at 10:01 am
In principle, I agree. Leaving orphan dependencies lying around is messy. But in practice you either do as I suggest or do a yum remove on each of the obsolete packages the web site lists, taking careful note of all the dependents that are removed with them and make a point of re-installing the ones you still want before progressing with the upgrade. It rather defeats the point of using yum to upgrade.
The bottom line is, if you want a pristine system, then you need to back-up user files, re-install from base media, then re-load form backup. If you want a working machine, remove the obstacles to the upgrade and get on with it.
Experience has taught me (in trying to upgrade from FC2 to FC3, then FC3 to FC4) you can have it clean or you can have it easy. You can’t have both.
April 24th, 2006 at 10:03 am
PS: Nevertheless, it’s useful to have a page which gives the hints for people to work from, so good work, even if we don’t necessarily agree 100%.
April 26th, 2006 at 5:38 am
Raj, though not completely, i somewhat agree with you
BTW, thanks for stopping by & i’m happy that it was of some help for you
April 28th, 2006 at 4:27 pm
Is this true, that you can’t have a clean system when you upgrade the easy way? What seems to be the problem and the difference between the two?
April 30th, 2006 at 6:42 pm
My upgrade for FC5 took one day. I had to uninstall wine and atifglrx. However, it was flawless. I am having problems getting wine back, but it seems to be an issue that will get resolved overtime. Also, I seem to have lost dual head support, but that’s ok too. It is well worth it, as dual-head and wine will gain support in the next few weeks. Thanks, this was great. I wish the download time didn’t take so long, but hey, that’s what I get for doing it over a T1 instead of FIOS. Thanks again,
TheTMickP
May 1st, 2006 at 2:03 am
You are welcome
May 3rd, 2006 at 6:58 pm
No, it’s not absolutely strictly true that you can’t have a clean upgrade, BUT it does depend on the FC4 installation you have. If you have an installation that doesn’t include any of the now obsolete packages (e.g. Canna, pcmcia-cs), then the upgrade should go nice and cleanly, without a hitch. But there are something like 50 packages that have been removed, and which will cause conflicts if you try to upgrade with them still installed. And if you use yum to remove them, they’ll take a lot of other basic things with them, which you then need to put back. The trouble with the RPM system is that many packages claim dependency on, or to be dependents of, other packages where the relationship is strictly optional, and yum isn’t smart enough to take account of that. When you remove any supporting package yum appears to rip out anything that’s remotely dependent on it – even when that dependency is optional. Hence my suggestion to use rpm—nodeps and the comment about easy or clean but not both.
If you start off with a relatively simple FC4 you should end up with the same equally simple FC5.
May 3rd, 2006 at 7:01 pm
Incidentally, since upgrading (which in total took over 10 days – slow internet connection – don’t ask), xine will now no longer display any video. It won’t even display the oscilloscope when listening to sounds. All I get is a blue screen. Research suggests that it is a libXv problem which I’m looking into even as I write, but if anyone else has a similar problem, or has already solved it, I’d appreciate some feedback.
July 6th, 2006 at 12:28 pm
1. Corporate proxies! A useful reminder would be nice in terms of consulting the `rpm` man page. The error message is terribly misleading when one has forgotten to take care of this. Yes, we could easily miss this since `rpm` and `yum` both have different strategies for picking up the proxy info (ugh).
2. I suggest that the “livno” repository be left off until the end of this long upgrade.
3. Warn folks that a judicious `yum clean all` might be a good idea to make sure that yum doesn’t get confused from a half-baked step from an update in the previous version. It doesn’t take very long so its worth it. When in doubt, clean.
That’s the end of my nag [(-;].
Thanks for the recipe,
Richard
July 7th, 2006 at 2:12 am
Thanks for the tip Richard
August 23rd, 2006 at 8:27 am
Thanks for the steps. They helped me upgrade from FC4 to FC5 successfully.
After step 0, I had to remove old version of kernel. Otherwise, last step was failing like this:
Error: Unable to satisfy dependencies
Error: Package initscripts conflicts with kernel < 2.6.12.
Error: Package kudzu conflicts with kernel < 2.6.13.
I had 2.6.11
The same instructions can be followed to upgrade with CDs; but no CD-ROM drive
I dumped all the rpms to a directory on NFS server and created a local repository.
August 23rd, 2006 at 9:22 am
Sateesh, I’m glad that it was of any help
& hey, thanks for the tip
September 5th, 2006 at 4:23 am
worked perfect !!
September 5th, 2006 at 4:59 am
I’m glad that i was of any help
November 2nd, 2006 at 1:47 am
Error: Package initscripts conflicts with kernel < 2.6.12.
Error: Package hal conflicts with kernel < 2.6.15.
Error: Package kudzu conflicts with kernel < 2.6.13.
November 15th, 2006 at 11:26 am
+edora-release-5-5.noarch.rpm
error: Failed dependencies:
fedora-release = 4 is needed by (installed)
+legacy-yumconf-4-2.fc4.noarch
November 15th, 2006 at 11:28 am
Removing the legacy-yumconf package made step 3 work.
November 16th, 2006 at 2:05 am
Aha, good
December 4th, 2006 at 2:20 pm
Error: Missing Dependency: libcrypto.so.5 is needed by package php-mysql
Error: Missing Dependency: libssl.so.5 is needed by package php
Error: Missing Dependency: libssl.so.5 is needed by package Nessus
Error: Missing Dependency: libcrypto.so.5 is needed by package mysqlclient14
Error: Missing Dependency: libcrypto.so.5 is needed by package php-cli
Error: Missing Dependency: libssl.so.5 is needed by package php-cli
Error: Missing Dependency: httpd-mmn = 20020903 is needed by package php
Error: Missing Dependency: libcrypto.so.5 is needed by package Nessus
Error: Missing Dependency: libssl.so.5 is needed by package php-mysql
Error: Missing Dependency: libcrypto.so.5 is needed by package php
Error: Missing Dependency: libssl.so.5 is needed by package mysqlclient14
December 6th, 2006 at 9:51 am
thank you so much for your guide!
ive successfully upgraded my FC4 box w/ plesk 8.0 to
FC5 plesk 8.1 w/ PHP5.1.6 and MySQL5 Support!
December 6th, 2006 at 4:15 pm
MakuChaku… I still have the errors that I posted a day ago…
Any Suggestions?
TIA
February 18th, 2007 at 2:35 am
hello
i have errors of Ramon Araujo and makuchaku
Any suggestions?
thanks
bye
March 18th, 2007 at 3:59 am
ISateesh: How did you remove the old version of kernel?
I’m getting the same error you where getting.
Cheers
March 18th, 2007 at 4:15 am
Got it. I used:
rpm -e kernel-2.6.11-1.1369_FC4
Cheers,
carlos
August 7th, 2007 at 3:27 am
Thanks - It helped me out.
August 7th, 2007 at 12:32 pm
I’m glad Sameer
August 22nd, 2007 at 9:43 am
After following instructions I get:
Error: Missing Dependency: libssl.so.5 is needed by package php
Error: Missing Dependency: libcrypto.so.5 is needed by package httpd
Error: Missing Dependency: libssl.so.5 is needed by package mod_ssl
Error: Missing Dependency: libssl.so.5 is needed by package perl-DBD-MySQL
Error: Missing Dependency: libcrypto.so.5 is needed by package php-mysql
Error: Missing Dependency: libssl.so.5 is needed by package php-mysql
Error: Missing Dependency: libcrypto.so.5 is needed by package php
Error: Missing Dependency: libssl.so.5 is needed by package httpd
Error: Missing Dependency: libcrypto.so.5 is needed by package perl-DBD-MySQL
Error: Missing Dependency: perl(:MODULE_COMPAT_5.8.8) is needed by package crypto-utils
Error: Missing Dependency: httpd-mmn = 20051115 is needed by package mod_authz_ldap
Error: Missing Dependency: perl(String::CRC32) is needed by package lftp
Error: Missing Dependency: perl-String-CRC32 is needed by package lftp
Error: Missing Dependency: libgcj.so.6 is needed by package struts11
Error: Missing Dependency: libaprutil-0.so.0 is needed by package httpd
Error: Missing Dependency: perl(:MODULE_COMPAT_5.8.8) is needed by package mod_perl
Error: Missing Dependency: xorg-x11-libs is needed by package pango
Error: Missing Dependency: httpd-mmn = 20051115 is needed by package mod_perl
Error: Missing Dependency: XFree86-libs >= 4.2.99 is needed by package libgnomeui
Error: Missing Dependency: libdpstk.so.1 is needed by package ImageMagick
Error: Missing Dependency: libdps.so.1 is needed by package ImageMagick
Error: Missing Dependency: howl = 0.9.8 is needed by package howl-libs
Error: Missing Dependency: xorg-x11-libs = 6.8.2-37.FC4.49.2.1 is needed by package xorg-x11-xfs
Error: Missing Dependency: perl(:MODULE_COMPAT_5.8.8) is needed by package newt-perl
Error: Missing Dependency: libapr-0.so.0 is needed by package httpd
Error: Missing Dependency: gnu-crypto-sasl-jdk1.4 >= 0:2.0.1-1jpp_2fc is needed by package jessie
Error: Missing Dependency: gnu-crypto-jce-jdk1.4 >= 0:2.0.1-1jpp_2fc is needed by package jessie
r package: geronimo-specs-compat
Solution?