Description of problem: python3-crypto is a dependency of a package I maintain that I need to add to epel8. Please branch and build it for epel8. Additional info: If you add me (or the Python SIG) as a maintainer I'd be happy to take care of this myself.
Given that pycrypto is dead upstream and has been for a few years now, is there no way that you could use pycryptodomex instead? https://pycryptodome.readthedocs.io/en/latest/src/introduction.html https://pycryptodome.readthedocs.io/en/latest/src/vs_pycrypto.html https://github.com/rthalley/dnspython/issues/271 https://src.fedoraproject.org/rpms/python-pycryptodomex
It's not my choice, that's the upstream dependency. I'll open an issue upstream to request they migrate from pycrypto to pycryptodomex. Going that route will require getting pycryptodomex added to epel6. If it's dead upstream, why hasn't it been retired in Fedora? I feel like if this is valid to be in Fedora (i.e. a popular dependency) then it's valid for epel8.
It'll be retired in Fedora when nothing is left depending on it. In the meantime, I backport security fixes from pycryptodome. However, Fedora releases have a much shorter lifetime than EPEL, so I'm reluctant to bring into EPEL something that's already dead. I'm willing to help getting pycryptodomex into EPEL-6 if the current maintainer doesn't want to do it themselves.
That's a fair point, thanks for the clarification. I think I've sorted out the changes necessary to port nova-agent, it wasn't too bad. https://github.com/Rackspace-DOT/nova-agent/pull/77 If you can go ahead and add pycryptodomex it epel6 it would be greatly appreciated.
I just requested pycryptodomex for el6 in bug 1759730.