Bug 2104350

Summary:	Nothing owns /usr/share/X11/fonts
Product:	Red Hat Enterprise Linux 9	Reporter:	Orion Poplawski <orion>
Component:	filesystem	Assignee:	Martin Osvald 🛹 <mosvald>
Status:	CLOSED MIGRATED	QA Contact:	František Hrdina <fhrdina>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, carl, davide, fhrdina, jwboyer, mark, ndegraef, pasik, peter.hutterer
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-16 10:59:54 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:	2107447
Bug Blocks:	1914423, 2104335

Description Orion Poplawski 2022-07-06 03:08:52 UTC

Description of problem:

With the exclusion of xorg-x11-font-utils it seems that nothing own /usr/share/X11/fonts:

rpm -qf /usr/share/X11/fonts
file /usr/share/X11/fonts is not owned by any package

dnf repoquery --whatprovides /usr/share/X11/fonts

returns nothing

Comment 1 Peter Hutterer 2022-07-14 05:23:43 UTC

Hmm, indeed, this is a result of the splitout from xorg-x11-font-utils which previously was, effectively, always pulled in through dependencies. Is there any immediate functionality impact here though?

I'm wondering, this should probably go into filesystem.rpm.

Comment 2 Orion Poplawski 2022-07-14 19:15:44 UTC

No immediate functionality impact - though I guess you can get some permission oddness in rare cases.  More of a "correctness" issue.  filesystem already owns /usr/share/X11 so that seems a reasonable solution.

Comment 3 Niels De Graef 2022-11-16 12:23:19 UTC

This probably needs a similar solution to bug 2107447, so moving to the same component as that one

Comment 4 Niels De Graef 2022-11-16 12:26:39 UTC

*** Bug 2059773 has been marked as a duplicate of this bug. ***

Comment 6 Martin Osvald 🛹 2023-08-16 05:07:00 UTC

This bug has been scheduled for migration to Jira (https://issues.redhat.com).

Please, let me know if you face any problems once it is done (Jira login creation, etc.).

Comment 7 RHEL Program Management 2023-08-16 06:43:49 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 8 Martin Osvald 🛹 2023-08-16 11:17:24 UTC

Copy&pasting the below text from other BZ which got closed automatically after migration as it contains useful info (apparently this one got stuck at comment 7):

~~~
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue
Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to
the new issue location. The issue key will have an icon of 2 footprints next to
it, and begin with "RHEL-" followed by an integer.  You can also find this
issue by visiting https://issues.redhat.com/issues/?jql= and searching the
"Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an
issue by sending mail to rh-issues.
~~~