https://bugzilla.redhat.com/show_bug.cgi?id=1748187
Zbigniew Jędrzejewski-Szmek <zbyszek(a)in.waw.pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zbyszek(a)in.waw.pl
--- Comment #11 from Zbigniew Jędrzejewski-Szmek <zbyszek(a)in.waw.pl> ---
(In reply to Jaroslav Mracek from comment #6)
The behavior of YUM was incorrect. YUM always considered only latest
packages for transaction, the older packages were completely ignored
therefore YUM was unable to handle many situations.
DNF uses libsolv as a solver that consider all possibilities, therefore dnf
is capable to resolve transaction that YUM was unable to.
After reading this, I still don't understand *why* dnf takes into account
the Obsoletes from a removed package. If instead of Obsoletes, the old removed
package had Provides:foo, and an installed package had Requires:foo, dnf would
consider this an unsatisfied dependency. Similarly, if we have foo-1.0, and
bar-1.0 with Requires foo=1.0, and we upgrade to foo-1.1 and bar-1.1 with
Requires foo=1.1, this is OK. We go from one consistent state to another
consistent state.
--
You are receiving this mail because:
You are on the CC list for the bug.