Bug 1596017

Summary:	infra: install python3-devel everywhere
Product:	[Community] GlusterFS	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, kkeithle, nigelb
Target Milestone:	---
Target Release:	---
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:	2018-07-02 12:31:47 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 Kaleb KEITHLEY 2018-06-28 04:52:36 UTC

Description of problem:

$Summary.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Nigel Babu 2018-06-28 10:22:30 UTC

While installing python3 isn't a problem, getting that working for el7/el6 stuff that run inside a mock is going to be more challenging to impossible EL7 does not have appropriate amount of python3 support without using SCL or EPEL. So now we need to make a call on how we handle this.

Comment 2 Niels de Vos 2018-06-28 10:38:36 UTC

At least CentOS 6 and 7 packages are expected to keep working fine with the standard Python (2) in the distribution. I am not sure of the requirement to move *everything* to Python3.

Kaleb, could you be a little more specific and explain the need for it?

Comment 3 Nigel Babu 2018-06-28 11:03:15 UTC

Kaleb is doing this correctly as per Fedora packaging guidelines (see https://fedoraproject.org/wiki/Packaging:Python). You cannot simply use python anymore. You have to specify python2 or python3 including in the shebang for all scripts. This is going to cause interesting problems for the EL6/EL7 world.

The only way I can see this work is if we make sure we're compatible with python3 with tooling, but actually run all our stuff on python2 until such a time that there is an EL7 which ships python3 packages in base.