Description of problem: During the F-13 beta process, the following packages were shipped: NetworkManager{,-{glib,gnome}}-0.8.0-0.4.git20100211.fc13.x86_64 initscripts-9.11-1.fc13.x86_64 These were upgraded in F-13 final: NetworkManager to 0.8.1-0.1.git20100510.fc13.x86_64 initscripts to 9.12-1.fc13.x86_64 However, using yum to update NetworkManager fails, apparently 0.8.0 ">=" 0.8.1. updating initscripts fails as it conflicts with NM 0.8.0 (so the failure to update NM blocks the initscripts update). Updating via rpm -Uvh works as expected Version-Release number of selected component (if applicable): yum-3.2.27-4.fc13.noarch How reproducible: Always Steps to Reproduce: 1. Download the older NM and initscripts RPMs from Koji 2. rpm -Uvh --oldpackage them 3. yum update NetworkManager 4. yum update initscripts Actual results: #3 does not update anything. #4 fails because of file conflicts with NM. Expected results: Should work fine Additional info:
you need to provide A LOT more information here. Specifically what is the failure that you received from yum?
provide: yum --disablerepo=updates list initscripts NetworkManager\*
As I said in email, it's not a yum bug if you exclude packages and then can't update them.
Apologies -- turns out I did add an exclusion back in March, and had forgotten about it in the meantime.