Bug 2123530

Summary:	Filesystem does not own shell completions directories
Product:	Red Hat Enterprise Linux 9	Reporter:	Maxwell G <maxwell>
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, fhrdina, jwboyer
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 07:27:41 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:

Description Maxwell G 2022-09-01 22:55:48 UTC

Description of problem:

Filesystem does not own shell completions directories. Please backport https://pagure.io/filesystem/c/1ab3d19e771134d8a3fed312b91546120d3a3b3e?branch=master which fixes this. Packages that provide shell completions should not have to own the shell completions directories themselves.

Version-Release number of selected component (if applicable):
filesystem-3.16-2.el9.x86_64

Comment 1 Maxwell G 2022-09-01 23:04:50 UTC

Submitted https://gitlab.com/redhat/centos-stream/rpms/filesystem/-/merge_requests/5

Comment 3 Martin Osvald 🛹 2023-08-16 05:20:30 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 4 RHEL Program Management 2023-08-16 06:44:16 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 5 RHEL Program Management 2023-08-16 07:27:41 UTC

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.