CI: force-reinstall cryptography from source for the linux binaries

The moto S3 test server install already pulls in the cryptography
manylinux wheel, so a plain "pip install --no-binary cryptography"
kept that wheel (statically linked OpenSSL) and the dynamic libcrypto
check failed.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
Thomas Waldmann
2026-09-27 15:53:44 +02:00
co-authored by Claude Opus 5.5
parent bce686de68
commit 001b59cde5
+3 -1
View File
@@ -323,7 +323,9 @@ jobs:
run: |
set -euxo pipefail
rustc --version
pip install --no-binary cryptography cryptography
# --force-reinstall: the moto S3 test server install above already pulled in the
# cryptography wheel, without it pip would just keep that one.
pip install --force-reinstall --no-binary cryptography cryptography
# check that the extension links the system OpenSSL dynamically and
# loads the same version as the system's openssl program
rust_ext=$(python -c 'import cryptography.hazmat.bindings._rust as m; print(m.__file__)')