<div>On 11/16/05, Justin Conover <<a href="mailto:justin.conover@gmail.com">justin.conover@gmail.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div> <div>On 11/16/05, Bob Chiodini <<a href="mailto:robert.chiodini-1@ksc.nasa.gov" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> robert.chiodini-1@ksc.nasa.gov</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Wed, 2005-11-16 at 06:44 -0600, Robin Holt wrote: > On Wed, Nov 16, 2005 at 02:54:31PM +0530, Rahul Sundaram wrote: > > Enable fedora-devel and extras-devel repository and disable the rest and > > run yum update. Post the output of that to the list if you need help. > > You might workaround dependencies by installing a minimal number of > > packages or ignore some of the packages in the update by using the > > exclude option in yum. man yum and yum.conf for details. > > You probably have to remove some of your older kernels from FC4 as well. > If your existing kernel is 2.6.13 something or later, then do an > rpm -qa | grep kernel > > Any kernels which are not 2.6.13 or later, rpm -ev the package name > (including -devel). > > Otherwise, I got things to upgrade fairly smoothly. > > Good Luck, > Robin > How timely. I'm going thru this right now and have been for the past two days. In addition to the others' responses, so far this is what I did: Clean "everything" install of FC4 from CDs. Download the latest development kernel, kernel-devel, initscripts, kudzu, kudzu-devel, hwdata. --nodeps install of the downloaded packages. You may only need the new kernel, try that first. That might avoid the libc problems below. Reboot to the new kernel, you'll get errors from kudzu, etc. about libc. You will also need to manually set up networking (ifconfig, route). Remove the original kernel (yum remove kernel-2.6.11*, I think). This fixes the kudzu conflict with the < 2.6.13 kernel. Turn off gpgcheck in /etc/yum.repos.d/fedora-devel.repo. For some reason gnome-panel is not signed. Memory get a little foggy here: These packages caused ssh/ssl grief and were not necessary for me: yum remove Canna* iiimf* ppp* w3c* hpoj perl-RPM2 yum --exclude dlm-* --exclude=cman-kernel --exclude=lvm2-cluster --exclude=gulm* --exclude=magma* upgrade This is where I am now. At last count there were over 1200 packages to be upgraded. Bob... -- fedora-test-list mailing list <a href="mailto:fedora-test-list@redhat.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> fedora-test-list@redhat.com</a> To unsubscribe: <a href="https://www.redhat.com/mailman/listinfo/fedora-test-list" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">https://www.redhat.com/mailman/listinfo/fedora-test-list </a> </blockquote></div> </div> I wouldn't be doing "nodeps" on anything, good way to hose your system. Like its been mentioned, I would remove all your 2.6.13 kernels first, fc4 has a 2.6.14 kernel. rpm -qa kernel\* yum remove <old-kernels> <old-kernel-devel> yum update kernel yum If you get a lot of old package deps, the easiest thing to do is yum remove <all problems> and if you have to, get to a pretty lean rawhide box and then use groupinstalls yum groupupdate or groupinstall Base Gnome, stuff you use example yum groupinstall "Base" "GNOME Desktop Environment" "X Window System" "System Tools" Quotes are important if it is more than one word, just like scripting/coding yum grouplist will show you what is important Just a note, with all the new xorg updates this could be a painful time :) have fun! </blockquote></div> Oh, after the "yum update kernel yum" I would reboot first, this is pretty much how I move box's to rawhide.