On Wed, 7 Feb 2007, Ville Skyttä wrote:
In case you're not aware of it, yum (more or less by design AFAIK) bumps the severity of a single dependency problem among a batch of updates into the *sum* of all other problems fixed in the batch, including security ones and across all repos, by refusing to install any of them unless the user manually cherry picks the packages not affected by the dependency issue separately.
I've noticed this too, on several occasions.I wonder what the reasoning is behind this construction, i.e. why not just hold back libmtp-0.1.3 in this case informing the users that it'll break, and the only thing I can think of is that is designed for consistent repositories, so this is supposed to break thusly as an indication of the problem.
But with no policies and tools for keeping the repositories consistent, yum design and the FC repositories are at odds.
Linus