Bug 2148292

Summary:	Drop dependency on xorg-x11-font-utils
Product:	Red Hat Enterprise Linux 9	Reporter:	Peter Hutterer <peter.hutterer>
Component:	xorg-x11-server	Assignee:	Peter Hutterer <peter.hutterer>
Status:	CLOSED ERRATA	QA Contact:	Tomas Pelka <tpelka>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.1	CC:	tpelka
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	xorg-x11-server-1.20.11-13.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-09 07:38:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2142931

Description Peter Hutterer 2022-11-24 22:32:15 UTC

This bug was initially created as a copy of Bug #2145088

I am copying this bug because: 



The xserver build currently requires xorg-x11-font-utils. But the only reason it does is by calling some m4 macros that are provided by that package. And those again just resolve to: adding a --with-fontrootdir to configure and defaulting (eventually) to /usr/share/fonts/X11.

The macros also allow per-font subdirectory configuration but no-one needs this (e.g. this is not available in upstream's meson.build files where those subdirectories are hardcoded).

A better approach here would be to simply handle that configure flag ourselves, hardcoding the subdirectories and dropping the need for xorg-x11-font-utils.

There's little impact for Fedora. One package during the build is arguably meh and xorg-x11-font-utils cannot be removed until the legacy fonts are dropped. It has more advantages on RHEL though where we can drop that package.

This affects e.g. tigervnc since that will no longer require that package either.

Comment 5 errata-xmlrpc 2023-05-09 07:38:36 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: xorg-x11-server security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:2248