From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.20 Description of problem: system-config-netboot-0.1.8-1 was installed with the original install of FC3. There have since been several updates, but the nightly yum update does not see them. It has seen and gotten all updates to other packages. up2date (specifically, the little red exclamation mark icon on the gnome panel, and the window that pops up when you click it) does see that the update hasn't installed. I've tried running yum update manually, just to make sure something wasn't messed up with the cron command, but it didn't see that there was anything to update. I'm not sure if this is a problem with yum or the system-config-netboot RPM package. Feel free to reassign. I'm also puzzled as to why nobody else has reported this, since I would think everyone running nightly updates would see it. However, it's happened on both FC3 machines here. I've never actually used system-config-netboot, nor do I do any netbooting to or from these machines. Version-Release number of selected component (if applicable): system-config-netboot-0.1.8-1 and later? or maybe yum... How reproducible: Always Steps to Reproduce: 1.see above 2. 3. Actual Results: see above Expected Results: see above Additional info: Yum.conf is the system default, no mods. --jh--
This problem is caused by the change from using an architecture specific RPM for system-config-netboot to a noarch RPM (the package contains NO architecture specific files) - rpm cannot handle upgrades from arch-specific to no-arch. You'll need to upgrade this manually: $ wget \ ftp://download.fedora.redhat.com/pub/fedora/linux/core/updates/3/i386/system-config-netboot-0.1.16-1_FC3.noarch.rpm $ rpm -Uvh --force system-config-netboot-0.1.16-1_FC3.noarch.rpm After this, subsequent upgrades will be installed normally through yum/up2date. If, as you say: " I've never actually used system-config-netboot, nor do I do any netbooting to or from these machines ", then you'd be better off simply doing $ rpm -e system-config-netboot which would also fix the problem.