On Thu, 2016-12-01 at 17:03 -0500, Przemek Klosowski wrote:

> This got me thinking if there's a common root cause that could be 
> checked automatically? I didn't quite understand what exactly happened 
> in the affected packages to cause it.

No, they're usually all different little awkward packaging corner
cases.

Right, that's what I thought. Still, completely blocking the upgrade seems rude. Yum had an option --skip-broken  that would just leave such packages alone, but DNF claims it's an incorrect approach and drops it ( http://dnf.readthedocs.io/en/latest/cli_vs_yum.html ) . They seem to suggest that --best might help: I haven't tried it but I doubt it would solve the problems we discussed.

Maybe we need  a new option :  dnf update --skip-broken-yes-I-know-something-might-be-left-not-updated-but-I-need-to-update-this-system-and-will-mop-up-the-spills-later