Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionTomasz Kepczynski
2020-06-21 14:24:10 UTC
Description of problem:
bash-completion is pulled by python3-lib389 package:
eskel:~# rpm -q --whatrequires bash-completion
python3-lib389-1.4.2.4-8.module_el8.2.0+366+71e3276f.noarch
but looking on the list of the files provided by this package (rpm -ql python3-lib389) there is no indication that it provides any file which may be needed or used by bash-completion package. This breaks bash users' experience as it includes unneeded and often annoying bash completion commands and cannot be easily rectified by an end user (bash-completion needs to be forcefully removed by an administrator).
Version-Release number of selected component (if applicable):
python3-lib389-1.4.2.4-8.module_el8.2.0+366+71e3276f.noarch
How reproducible:
Always
Steps to Reproduce:
dnf module enable idm:DL1
dnf install ipa-server-dns
Actual results:
bash-completion is NOT installed
Expected results:
bash-completion is pulled in unnecessarily
Additional info:
I really don't understand why bash completion is pulled in. As mentioned above there is NO indication this package provides any completions so WHY???
See also bugzilla #1582830
Disclosure: found on CentOS 8.2 (possibly also exists on 8.1). I don't have access to RHEL 8.2 at the moment but if needed can crosscheck this later.
bash-completion is for the Directory Server CLI tools (dsconf, dsctl, dscreate, and dsidm).
In newer versions of 389-ds-base bash-completion is a "Recommends" package via the specfile, it is not a requirement. The current version you are running it is set as a requirement, but that requirement will be removed (changed to "Recommends") in the next 8.2 build. It's already changed in 8.3...
Build tested: 389-ds-base-1.4.3.8-5.module+el8.3.0+7569+08175a8a.x86_64
bash-completion is now recommended, not required:
rpm -q --recommends python3-lib389
bash-completion
It is installed by default if weak dependencies are enabled:
dnf install 389-ds-base -y
...
Installing weak dependencies:
bash-completion noarch 1:2.7-5.el8 rhel8
...
Which can be disabled with
dnf --setopt=install_weak_deps=False install 389-ds-base
Marking as VERIFIED.
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 (389-ds:1.4 bug fix and enhancement 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/RHEA-2020:4695