This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2123530 - Filesystem does not own shell completions directories
Summary: Filesystem does not own shell completions directories
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: filesystem
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Martin Osvald 🛹
QA Contact: František Hrdina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-01 22:55 UTC by Maxwell G
Modified: 2023-08-16 07:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-16 07:27:41 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Pagure filesystem c 1ab3d19e771134d8a3fed312b91546120d3a3b3e?branch=master 0 None None None 2022-09-01 22:55:48 UTC
Fedora Pagure filesystem pull-request 7 0 None None None 2022-09-01 22:55:48 UTC
Gitlab redhat/centos-stream/rpms filesystem merge_requests 5 0 None opened Own zsh and fish completions directories (rhbz#2123530). 2022-09-01 23:04:49 UTC
Red Hat Issue Tracker   RHEL-1338 0 None Migrated None 2023-08-16 06:45:24 UTC
Red Hat Issue Tracker RHELPLAN-133069 0 None None None 2022-09-01 22:59:23 UTC

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 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.


Note You need to log in before you can comment on or make changes to this bug.