On Thu, 6 Apr 2017 08:56:35 +1000, Stephen Morris wrote: > This issue is occurring for me on F25 with the update I have just > attempted, but I don't understand why, as, in the dnf output there is a > message that liba52 0.7.4-26.fc25 is replacing a52dec.x86_64 > 0.7.4-21.fc25, and there is also a message that a52dec x86_64 > 0.7.4-26.fc25 has broken dependencies. As a fresh reply to this thread, the full story is that the package maintainer has broken a52dec in earlier updates already. Users are pretty much doomed now and either get a52dec removed or see the brokendep/conflict warning/error. Or they've had a52dec removed before by one of the faulty updates and have reinstalled a52dec manually afterwards. What a mess! _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
