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?
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.
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.
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.
There is now a separate python3-cryptography package in EPEL-7 - see Bug #1482577.
Matěj, why did you reopen this?
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.
(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.