-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot install cryptography on Fedora 41+, CentOS Stream 10 #11690
Comments
That PR was closed without merging because we had follow up questions before it could be merged and never got a response. Those questions remain, namely: Why RedHat's behavior here is different from upstream's If we can get a clear answer to that question, we can proceed, but from my perspective this is blocked on Red Hat, not us. |
Ah, my bad, I read the discussion wrong in #11328. I do not feel fully qualified to answer, I am just a cryptography user, so by no means an expert on OpenSSL. But I read the change proposal for Fedora and the discussion for a rejected proposal to remove OpenSSL engines. I think that I see what is going on here and I understand this step from maintenance/packaging perspective. First, there were concerns that providers still have issues and prevent full switchover from engines. That prompted another approach (the second accepted proposal), deprecating engines but still keeping them for packages that cannot switch over to providers. So OpenSSL is not built with I would also like to point out that this is not a "Red Hat behavior" or a Red Hat decision. This approach was chosen by Fedora community, during a Fedora Change process and approved by FESCo (Fedora Engineering Steering Committee). CentOS Stream 10 is simply following the Fedora approach as its downstream. |
With that context, I guess we'd be happy to have the PR re-sent. |
Basically the same issue as #11331, result of OpenSSL engine deprecation. Fedora 41 is in beta now and CentOS Stream 10 is starting to be added to various CI tools, so I think this issue is getting more impactful.
Pip will build from source after specifying
--no-binary
or if wheel for an architecture is not available. Upstream cryptography is not installable by pip for s390x and ppc64le architectures on these distributions at all. There was #11328 which was closed without merging even though it looked like it worked and there were no objections. Could it be merged, please?Fedora 41
cryptography
,cffi
,pip
, andsetuptools
you're using
cryptography
pip install --verbose --no-binary :all: cryptography
dnf install gcc libffi-devel openssl-devel rust cargo python3-devel python3-pip pkg-config
pip install --verbose --no-binary :all: cryptography
CentOS Stream 10
cryptography
,cffi
,pip
, andsetuptools
you're using
cryptography
pip install --verbose --no-binary :all: cryptography
dnf install gcc libffi-devel openssl-devel rust-devel cargo python3-devel python3-pip pkg-config
pip install --verbose --no-binary :all: cryptography
The text was updated successfully, but these errors were encountered: