Bug 1481618

Summary:	RFE: python 3 package for python-cryptography in EPEL7
Product:	[Fedora] Fedora EPEL	Reporter:	Paul Howarth <paul>
Component:	python-cryptography	Assignee:	Jeremy Cline <jeremy>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	cheimes, itamar, jeremy, mcepl, mcepl, nick, npmccallum, randy, terrycwk1994
Target Milestone:	---	Keywords:	Reopened
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-04-12 09:00:42 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:	1482576, 1482577
Bug Blocks:

Description Paul Howarth 2017-08-15 08:11:45 UTC

The python-paramiko package has been included in RHEL 7.4 (though not on all architectures), version 2.x with a python-cryptography back-end.

There was already a python-paramiko package in EPEL7, version 1.x with a python-crypto back-end, with python2- and python34- sub-packages.

In order to retain full architecture coverage and python 3 support, I would like to bump the EPEL7 python-paramiko package to the same version as the RHEL 7.4 package, but before I can do that I will need a python34 build of python-cryptography in EPEL7.

I see that there's an epel7 branch for python-cryptography but no build done. What's the reason for that? I see that the python-cryptography package in RHEL 7.4 is quite a bit newer than the spec in the epel7 branch.

Would you be willing to support an EPEL7 package with python 3 support?

Comment 1 Jeremy Cline 2017-08-16 13:45:59 UTC

The branch pre-dates my maintainership so I'm not sure why it was never built, but I'm willing to support the Python 3 build in EPEL7 :)

Hopefully I can get to it today.

Comment 2 Paul Howarth 2017-08-16 14:34:33 UTC

That's great :-)

Note that there is a python-cryptography package in RHEL 7.4, but I don't know if it's there for all supported architectures.

If it's only available on some, but not all, architectures, you'd need to follow the guidelines for a limited-arch compatibility package in EPEL, which would be to clone the package from RHEL, prepend "0." to the release, and re-enable python3 support. Hopefully there won't be an issue with missing python3 dependencies in EPEL.

If it's available on all architectures, you have a bit more freedom. You'd be able to choose any version to support, though I think using 1.7.2 as per the RHEL 7.4 python2 package would be a sane choice, and you'd have to disable the python2 package (to avoid conflicting with the RHEL package) and enable just the python3 version. Again, hopefully there won't be an issue with missing python3 dependencies in EPEL.

Comment 3 Jeremy Cline 2017-08-17 19:10:24 UTC

Per the packaging guidelines, we need to go through the review process again and have a new package specifically for the Python 3 builds in EPEL7. I've added them as dependencies to this issue.

Comment 4 Paul Howarth 2018-04-11 08:36:12 UTC

There is now a separate python3-cryptography package in EPEL-7 - see Bug #1482577.

Comment 5 Paul Howarth 2018-04-12 05:51:49 UTC

 Matěj, why did you reopen this?

Comment 6 Matěj Cepl 2018-04-12 08:59:38 UTC

Sorry, I didn't mean to (don't tell me I have reopened by mistake all those hundreds of bugs I meant to add my CC to). Please, close.

Comment 7 Paul Howarth 2018-04-12 09:35:50 UTC

(In reply to Matěj Cepl from comment #6)
> Sorry, I didn't mean to (don't tell me I have reopened by mistake all those
> hundreds of bugs I meant to add my CC to).

I don't think you did. I closed this after you added your Cc: but then it somehow got reopened. I've had lots of notifications about your Cc: changes on other bugs but this was the only one reopened.