Bug 1664749

Summary:	Bash completion files should be moved from platform-python-pip to python3-pip
Product:	Red Hat Enterprise Linux 8	Reporter:	Lumír Balhar <lbalhar>
Component:	python-pip	Assignee:	Lumír Balhar <lbalhar>
Status:	CLOSED ERRATA	QA Contact:	Jan Kepler <jkejda>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	cstratak, jkejda, pviktori, torsava
Target Milestone:	rc
Target Release:	8.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 22:24:11 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:
Bug Depends On:	1680786
Bug Blocks:

Description Lumír Balhar 2019-01-09 15:10:34 UTC

After the split of pip to python3-pip and platform-python-pip, bash completion files are still in platform-python-pip but executables are in python3-pip. 

Therefore, Bash completion files should be moved from platform-python-pip to python3-pip to be installed along pip executables.

Version: 9.0.3-13.el8

Upgrade path should be tested for both affected packages.

Comment 2 Lumír Balhar 2019-03-13 14:32:07 UTC

Pull request ready for review: https://src.osci.redhat.com/rpms/python-pip/pull-request/9

I've tested manually that an update of platform-python-pip alone removes bash completion files and an update of both platform-python-pip and python3-pip (which requires platform-python-pip) together keeps files there and just transfers their ownership to python3-pip.

Comment 3 Lumír Balhar 2019-03-28 07:43:34 UTC

Merged and built: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=20752773

Comment 7 errata-xmlrpc 2019-11-05 22:24:11 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-2019:3588