On Mon, 5 Aug 2013 13:51:41 -0700 Daniel Hedlund <[email protected]> wrote:
> I sat down a played on John's laptop directly for a few minutes. > When he upgraded to Fedora 17 it only partially upgraded his system > and then bailed for an unknown reason, but likely due to unresolved > conflicts or dependencies. Most of the things that worked on his > system were packages that did not get upgraded; he was running a F16 > version of the kernel and Xorg but everything that was going through > systemd was referencing F17 libraries that did not get installed on > his system. Trying to install these RPMs resulted in even more > dependencies and conflicts that needed upgrading. A quick 'rpm -qa | > grep f16' resulted in about 1k packages. Doing 'rpm -qa | grep f17' > also resulted in around 1k packages, meaning about 50% upgrade. > > Since he was still running a F16 kernel that came bundled with his > network drivers, his hardware was detected and a physical link was > observable (ie via mii-tool). However, many of the libraries that > the network tools relied on got removed or changed to incompatible > versions during the upgrade and no longer functioned. Even the most > basic ifconfig and ip commands wouldn't work because, while it could > assign an IP address to the interface, it could not interface with > the part of the system that managed the routing table and all DNS > resolver related libraries were missing. Ouch. Ouch, ouch, ouch. Hades on a hoverboard. Helen Damnation, and other unpleasant people. At this point I'm tempted to say start over. Re-partition the disk to something reasonable (none of this "put everything in one big partition" crap*), and install Fedora 19 instead of 17. (F17 no longer being supported and all.) Then install all the extra programs, and document what has to be done to make them work. Buy an engineering log book, or one of those green 1/5-inch grid pads. PSU bookstore should have both. HOWEVER, that said, I know John doesn't want to go through all the pain of making all that stuff work again. So here's my last gasp thought on the subject. Mount the F17 installation DVD -- don't try to run it, just mount it. Navigate to the Packages directory and see what's there. It'll either be all of the packages, or a set of directories, one for each letter of the alphabet. If it's one massive directory full of packages, fine. Get the list of all the F16 packages still installed, strip off the version info, and feed it to yum. You may need a "--local" flag; I don't remember when they removed that option. If it's a set of directories, do the same basic thing, but sort the list of packages into alphabetized chunks, and feed them to yum one letter at a time. A small bash script should work just fine. That _should_ get enough of F17 installed that you can do whatever else you need to do. No guarantees. I still recommend documenting your additional software. Stuff from Fedora or the RPMFusion repos most likely won't need that; they're set up to work "out of the box", so to speak. But other stuff will need more attention, as you've found out. * I could go on a rather, um, inflamed rant on the subject, but I'll spare us all. (I'm too lazy to write it.) I will just say that putting everything in one massive partition is, IMO, a bad idea. John, if you want to know how I recommend setting up a disk, and why, let me know and I'll write something up for you. Anyway, I hope this helps. Good luck. --Dale -- "Who cares if it doesn't do anything? It was made with our new Triple-Iso-Bifurcated-Krypton-Gate-MOS process ..." _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
