FC4 to FC5 upgrade via yum

[Jim Cornette]

Jim Duda wrote:
> I'm trying to upgrade from FC4 to FC5 via yum.  I followed the 
> instructions found at http://fedoraproject.org/wiki/YumUpgradeFaq
> 
> I'm not able to get through the initial yum update.  I've removed all 
> the packages I can which had dependencies, and I'm down to the following 
> list:
> 
> Error: Missing Dependency: libneon.so.24 is needed by package librpm4.4
> Error: Missing Dependency: kernel-headers >= 2.6.18 is needed by package 
> audit-libs-python
> Error: Missing Dependency: libgnutls.so.12 is needed by package heartbeat
> Error: Missing Dependency: libgnutls.so.12(GNUTLS_1_2) is needed by 
> package heartbeat
> Error: hal conflicts with kernel < 2.6.17
> Error: Missing Dependency: libgnutls.so.12(GNUTLS_1_2) is needed by 
> package stonith
> Error: Missing Dependency: libdbus-1.so.2 is needed by package 
> notify-daemon
> Error: Missing Dependency: libgnutls.so.12 is needed by package stonith
> 
> I don't have audit-libs-python, heartbeat, hal, or stonith.  Any attempt 
> to even use rpm -e <any of the four> results in "package not installed."
> 
> I'm afraid to remove librpm4.4 as that will remove yum itself.
> 
> I have a custom kernel 2.6.17.13, so I don't want to install another 
> kernel unless I have too.
> 
> This installation is loaded on a LTSP diskless boot environment, so, a 
> fresh install is rather cumbersome, hence the yum upgrade attempt.
> 
> Can anyone recommend a solution at to how to resolve this list of issues 
> so I can do the yum update?
> 
> Thanks,
> 
> Jim
> 
You might try to upgrade groups of packages that relate to the problem, 
like gnutls to see if it pulls in the additional packages. You might 
have to remove the conflicting packages and then build them again from 
source after upgrade or change the repository from FC4 to FC5 versions 
before attempting an upgrade.
You might try also to retrieve the packages in smaller groups and check 
what more packages are available to install after the upgrades progress 
to a manageable amount remaining.

It should be possible to determine what needs to be removed, upgraded 
from another repo and the like.
Just do the upgrade from a VT instead of a graphical terminal since some 
of the upgrades will eventually respawn the GUI server. When that 
happens your rpm database will be a mess.

That's all I can think of.
Jim

-- 
You will be advanced socially, without any special effort on your part.