> 1. what version of yum are you using on this 8.0 box? yum-1.0-1_80 > 2. what version of rpm on the 8.0 box? rpm-4.1-1.06 > try running a quick 'yum upgrade' on that system - with the fedora repos > in place - I think you'll find that fixes the problem. rats! - no luck with "yum upgrade" ========================================================================= Gathering package information from servers Getting headers from: depot PARC Red Hat Linux 8.0 base getting header.info from server Getting headers from: depot PARC Red Hat Linux 8.0 updates getting header.info from server Getting headers from: Duke Unix LUG Red Hat Linux 8.0 base getting header.info from server Getting headers from: Duke Unix LUG Red Hat Linux 8.0 updates getting header.info from server Getting headers from: Fedora Red Hat Linux 8 stable getting header.info from server Getting headers from: Fedora Red Hat Linux 8.0 stable getting header.info from server Getting headers from: PARC Red Hat Linux 8.0 base getting header.info from server Getting headers from: PARC Red Hat Linux 8.0 updates getting header.info from server Finding updated packages Best version for kernel-smp is 0:2.4.20-20.8 Best version for kernel-smp is 0:2.4.20-20.8 Best version for kernel is 0:2.4.20-20.8 Best version for kernel is 0:2.4.20-20.8 Best version for openssl is 0:0.9.6b-35.8 Best version for openssl is 0:0.9.6b-35.8 Best version for glibc is 0:2.3.2-4.80.6 Best version for glibc is 0:2.3.2-4.80.6 Best version for glibc-debug is 0:2.3.2-4.80.6 Best version for glibc-debug is 0:2.3.2-4.80.6 Downloading needed headers getting /var/cache/yum/fedoraupdates8/headers/WindowMaker-libs-0-0.80.2-0.fdr.2.rh80.i386.hdr getting /var/cache/yum/fedoraupdates8/headers/WindowMaker-0-0.80.2-0.fdr.5.rh80.i386.hdr getting /var/cache/yum/fedoraupdates8/headers/WindowMaker-devel-0-0.80.2-0.fdr.5.rh80.i386.hdr Finding obsoleted packages nulist = 179 uplist = 2 newlist = 177 obslist = 1 Resolving dependencies Dependencies resolved I will do the following: [update: WindowMaker.i386] [update: WindowMaker-libs.i386] Is this ok [y/N]: y Getting WindowMaker-0.80.2-0.fdr.5.rh80.i386.rpm Getting WindowMaker-libs-0.80.2-0.fdr.2.rh80.i386.rpm Calculating available disk space - this could take a bit Errors installing: ('file /usr/lib/libwraster.so.2.2.0 conflicts between attempted installs of WindowMaker-libs-0.80.2-0.fdr.2.rh80 and WindowMaker-0.80.2-0.fdr.5.rh80', (6, '/usr/lib/libwraster.so.2.2.0', 0L)) ===================================================================================== > no, there isn't, and the reason is that an update is a single operation, > either the whole requested set works or the whole thing fails. > One thing you can do, is this, do a yum check-update - and evaluate that > for what you consider security updates, then use those to update, but > the WindowMaker/WindowMaker-libs conflict looks like either a packaging > bug or something else, odd going on. I was able to mitigate the problem somewhat by using "exclude=WindowMaker*" line in yum.conf, but I would prefer not to edit all of our client yum.conf files. Was hoping for a single-point admin solution. Perhaps I could remove WindowMaker from the upgrade list by removing the rpms from our local repositories and then modifying our clients' yum.conf to only use our local servers and not the remote sites that we added for failover redundancy (insert hack here:). If this is an odd/rare instance, all of this is a non-issue. I am a bit skeptical though, since I saw our redcarpet (RH8/9) upgrades fail several times due to similar dependancy/conflict errors which required manual intervention to resolve. Thanks for your help and information. John.