On Mon, 1 Dec 2008, "Jóhann B. Guðmundsson" wrote:
File a bug against yum see what Seth has to say.. Came across this in F9 cycle I think., You might need to "help" yum a bit.. yum -y update --skip-broken -x packageStart with the first then continue adding -x package until you hit the one(s) causing this..Then mentioned the package(s) that causes this on your bug report.
Actually, Tim does most of the skip-broken spelunking. Credit where it is due.
Also before filing a bug - get yum 3.2.20-4.fc9 from updates-testing and try it there. It might still fail but the debugging from that version should be better.
Thanks, -sv