https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #4 from Marek Blaha <mblaha(a)redhat.com> ---
May I ask you what version of dnf are you using?
My first thought was, that the provide/obsolete are missing in newer version by
a mistake. But in liberation-fonts changelog I found:
* Mon Jun 24 2019 Vishal Vijayraghavan <vvijayra AT redhat DOT com> -
1:2.00.5-3
- Resolves: rhbz#1643920: Removed Obsoletes: %{fontname}-narrow-fonts and
Provides: %{fontname}-narrow-fonts macro
- Splitted the font family(mono, sans and serif) into diferrent root font
directories
Now the situation is confusing for the dependency solver:
- given the obsolete/provide in the version
liberation-fonts-1:2.00.5-1.fc30.noarch, this is the best version of
liberation-narrow-fonts package
- at the same time liberation-fonts-1:2.00.5-3.fc30.noarch is the best version
of liberation-fonts
this end in solution where two versions of liberation-fonts are about to be
installed, which is not viable.
I'm not sure how to solve this situation, but better workaround at the moment
is not to use versionlock (as I recommended in comment#1), but exclude
liberation-fonts-1:2.00.5-1.fc30.noarch package. E.g. adding
excludepkgs=liberation-fonts-1:2.00.5-1.fc30.noarch
line into [main] section of /etc/dnf/dnf.conf
--
You are receiving this mail because:
You are on the CC list for the bug.