--- Comment #8 from Kevin Kofler <kevin(a)tigcc.ticalc.org> ---
(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.
That behavior complied to user expectations and allowed resolving issues with
broken Obsoletes. How would you fix an unwanted entirely unversioned Obsoletes
with your approach? There is just no way to fix it then.
You may consider the DNF/libsolv behavior as "correct" under some formal
definition, but it does NOT fulfill user expectations, so I consider it wrong.
And I am really fed up of unhelpful behavior constantly being dismissed as "not
a bug, works by design" (see also bug #1699672, which makes weak dependencies
DNF uses libsolv as a solver that consider all possibilities,
is capable to resolve transaction that YUM was unable to.
But DNF is not capable of resolving this transaction that YUM would have been
able to. At least not without falsely complaining about "broken" dependencies,
which are not broken.
The situation here is based on packaging error that could be resolved
1. To overcome the issue it requires release of liberation-narrow-fonts with
version 1:2.0.0 or higher.
2. Return the obsolete in liberation-fonts to keep upgrade path.
2 would be completely wrong behavior. liberation-fonts does NOT replace
liberation-narrow-fonts, and liberation-narrow-fonts is specifically packaged
as a separate package to provide that font. And at least WINE actually wants
that font, it seems (which is why people are now seeing the "broken"
dependencies without explicitly having installed liberation-narrow-fonts).
1 is doable, but very ugly, and it would not be possible if the Obsoletes had
been entirely unversioned.
I insist: a solution in DNF is needed.
You are receiving this mail because:
You are on the CC list for the bug.