We need mkfontdir which is already a separate Provides by xorg-x11-font-utils. xorg-x11-font-utils is to be split up into multiple packages, see Bug 1932731, so let's get our BuildRequires to work smoothly across that change. Suggested diff: diff --git a/baekmuk-bdf-fonts.spec b/baekmuk-bdf-fonts.spec index 79fb20a..3849217 100644 --- a/baekmuk-bdf-fonts.spec +++ b/baekmuk-bdf-fonts.spec @@ -13,7 +13,7 @@ URL: http://kldp.net/projects/baekmuk/ Source: http://kldp.net/frs/download.php/1428/%{fontname}-%{version}.tar.gz Patch0: baekmuk-bdf-fonts-fix-fonts-alias.patch BuildArch: noarch -BuildRequires: xorg-x11-font-utils +BuildRequires: mkfontdir bdftopcf Conflicts: fonts-korean < 2.2-5 %description Verified successful build in a local F33 container with only the mkfontscale (Bug 1932734) and bdftopcf (Bug 1932736) packages installed, no xorg-x11-font-utils.
Why am I CCed on this bug? I don't comaintain this package. You added many unnecessary CCs.
Urgh, I think that's a function of the clone bug feature, it just keeps stacking the CCs so if you were unlucky enough that I (randomly) picked one of your packages as initial one, you kept getting appended. Apologies for the noise.
FEDORA-2021-68f1fa8ccb has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-9660787a95 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-9660787a95
Okay, built the package for Fedora 34 and 35.
FEDORA-2021-9660787a95 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-9660787a95` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-9660787a95 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-9660787a95 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.