Description of problem: When the latest perl update was pushed into the update tree (for 5.8.5-11), only the x86_64 RPM was pushed. Until the i386 RPM is also pushed, people who installed for dual-mode application support will get errors attempting to update using YUM. Or worse, using up2date I'm not sure that they *will* get any errors. This sort of thing has happened a couple of times in FC3 x86_64 updates repository. May I suggest adding a sanity script to the pre-push master updates repository that checks to ensure that forall xxx.x86_64.rpm there also exists xxx.i386.rpm (or some such)? Might help prevent future update glitches in FC4. I rated this security because currently executing updates are failing, and this means that the automated update scheme isn't getting security patches either until this is resolved.
*** This bug has been marked as a duplicate of 156288 ***