Bug 1951345 - xorg-x11-font-utils: Conflicts line in new subpackages does not conflict correctly
Summary: xorg-x11-font-utils: Conflicts line in new subpackages does not conflict corr...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-font-utils
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F34FinalFreezeException 1932731
TreeView+ depends on / blocked
 
Reported: 2021-04-20 01:45 UTC by Peter Hutterer
Modified: 2021-04-20 22:42 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-20 22:42:56 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Peter Hutterer 2021-04-20 01:45:35 UTC 
After the deaggregation (#1932731) some individually split packages use the following:

  Conflicts:  xorg-x11-font-utils <= 7.5-50

This line is incorrect, without %{?dist} it does not match against the actual EVR of 7.7-50.fc34. Packages with this tag do not correctly conflict the xorg-x11-server-utils package, causing conflicts on update.

This affects bdftopcf, fonttosfnt and mkfontscale, this bug is to be used for the update of these packages.
Comment 1 Fedora Update System 2021-04-20 01:46:02 UTC 
FEDORA-2021-ea9f5e2fce has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ea9f5e2fce
Comment 2 Peter Hutterer 2021-04-20 01:47:20 UTC 
Proposing as F34 Freeze Exception

The update here is trivial, it just fixes the Conflicts line in all packages to avoid install errors due to conflicting file lists.
Comment 3 Adam Williamson 2021-04-20 21:25:16 UTC 
+3 in https://pagure.io/fedora-qa/blocker-review/issue/366 , marking accepted.
Comment 4 Fedora Update System 2021-04-20 22:42:56 UTC 
FEDORA-2021-ea9f5e2fce has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.