Bug 1400223 - bash-completion for umount doesn't work
Summary: bash-completion for umount doesn't work
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: bash-completion
Version: 7.4
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Siteshwar Vashisht
QA Contact: Karel Volný
URL:
Whiteboard:
Depends On:
Blocks: 1716963 1719445
TreeView+ depends on / blocked
 
Reported: 2016-11-30 17:21 UTC by Daniel
Modified: 2020-03-31 19:48 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 19:48:14 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1069 0 None None None 2020-03-31 19:48:18 UTC

Description Daniel 2016-11-30 17:21:39 UTC 
bash completion for umount doesn't work

looking at the bash-completion script for umount, i see 

if [[ $OSTYPE == *linux* ]]; then
    . "$BASH_SOURCE.linux"
    return
fi

which tries to source /usr/share/bash-completion/completions/umount.linux

but that file does not exist.

I see it exists on the github page for bash-completion... so I am not sure how it went missing in rhel.
Comment 2 Siteshwar Vashisht 2017-02-14 11:49:04 UTC 
umount.linux is intentionally removed from being included in the package. I am still not sure why it is not included, because umount command is listed in the RFE at https://bugzilla.redhat.com/show_bug.cgi?id=810343#c15

The source package for bash-completion has a file 'script_list' that contains list of files that are not included in final package.
Comment 4 Siteshwar Vashisht 2017-02-14 11:51:27 UTC 
I have modified script_list file to include 'umount.linux' and done a test build at https://copr.fedorainfracloud.org/coprs/svashisht/bash-completion/package/bash-completion/
Comment 6 Daniel 2017-11-28 14:11:20 UTC 
Another dumb simple bug fix that still isn't finished. What is the hold up? Do people not use the command line any more? I don't understand how other people haven't complained about this...
Comment 7 Kamil Dudka 2017-11-28 14:25:53 UTC 
Updates in RHEL are driven by requests of our customers.  If you are a customer of Red Hat, please contact product support and let them know about this bug.
Comment 9 Daniel Arena 2019-07-31 17:25:47 UTC 
(In reply to Kamil Dudka from comment #7)
> Updates in RHEL are driven by requests of our customers.  If you are a
> customer of Red Hat, please contact product support and let them know about
> this bug.

I am now a paying customer with both RHEL subscriptions and a RHEL Developer Support (Professional) subscription. I contacted support but it doesn't seem to have helped, I just keep getting told they are "negotiating the SLA for next update for 1 more month."... for over 4 months now.
Comment 10 Siteshwar Vashisht 2019-08-01 10:36:13 UTC 
> I am now a paying customer with both RHEL subscriptions and a RHEL Developer Support (Professional) subscription. I contacted support but it doesn't seem to have helped, I just keep getting told they are "negotiating the SLA for next update for 1 more month."... for over 4 months now.

I will consider fixing this in RHEL 7.8.
Comment 17 errata-xmlrpc 2020-03-31 19:48:14 UTC 
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, 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/RHBA-2020:1069
Note You need to log in before you can comment on or make changes to this bug.