Bug 1270295 - dnf bash-completion is a bit flaky
dnf bash-completion is a bit flaky
Product: Fedora
Classification: Fedora
Component: dnf (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Martin Kutlak
Fedora Extras Quality Assurance
: Reopened, Triaged, UserExperience
Depends On:
  Show dependency treegraph
Reported: 2015-10-09 10:19 EDT by Davide Repetto
Modified: 2017-08-09 04:07 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 14:10:05 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Davide Repetto 2015-10-09 10:19:40 EDT
Description of problem:
The bash-completion of dnf does not always work properly. I will give a few examples here:

- "dnf list pe<TAB>" is not auto-completed while "dnf list available pe<TAB>" works as expected.

- "dnf -y ..." is never completed whatever follows

- "dnf install abc<TAB>" is autocompleted but the completion also shows packages that are already installed, while "dnf remove abc<TAB>" appears to work correctly. That is, it proposes only packages that are installed.

- When new repos are added (eg. a copr has just been enabled) the bash-completion is not aware about their presence until dnf somehow populates the cache. For which incidentally a simple "dnf makecache" is not sufficient and a "--refresh" needs to be specified.

Version-Release number of selected component:

How reproducible:
Consistently, with the provided examples.
Comment 1 Honza Silhan 2015-10-13 10:30:22 EDT
Thanks for the report.

Could that be improved, Igor?

Otherwise it could be fixed by argcomplete integration.
Comment 2 Christopher Tubbs 2016-05-24 01:02:21 EDT
This appears to be duplicate of bz#1227980
Comment 3 Fedora Admin XMLRPC Client 2016-07-08 05:30:19 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 4 Fedora End Of Life 2016-07-19 14:10:05 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 5 Fedora End Of Life 2017-07-25 15:21:04 EDT
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

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