Bug 1705259

Summary: Make bash completion compatible with rh-dotnet22 packages
Product: dotNET Reporter: Omair Majid <omajid>
Component: rh-dotnet21Assignee: Omair Majid <omajid>
Status: CLOSED ERRATA QA Contact: Radka Gustavsson <rjanekov>
Severity: unspecified Docs Contact: Les Williams <lwilliam>
Priority: unspecified    
Version: 2.1CC: bodavis, dbhole, kanderso, rwagner
Target Milestone: ga   
Target Release: 2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rh-dotnet21-dotnet-2.1.507-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-15 21:54:39 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 Omair Majid 2019-05-01 20:20:02 UTC 
The two different software collections that both ship .NET Core 2.x include different versions of incompatible files for bash completion. Both need to install the bash completion file to /usr/share/bash-completion/completions/dotnet. This is not an SCL-specific path, but a general system path.

To make this work, both SCLs need to ship an identical copy of this file. Otherwise it's not possible to install them both side-by-size.

Thankfully, this is easy enough to fix: we can just take the latest bash completion file from upstream and make sure both SCLs use the exact same file. There haven't been any backwards-incompatible changes to this file in the last few years: https://github.com/dotnet/cli/commits/master/scripts/register-completions.bash

(As a bonus, the latest upstream version of the bash completion file contains additional fixes we pushed to fix some issues)
Comment 5 errata-xmlrpc 2019-05-15 21:54:39 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/RHSA-2019:1236