python3-cryptography-vectors: upgrade 41.0.4 -> 41.0.5
PATCH 1/1 python3-cryptography-vectors: upgrade 41.0.4 -> 41.0.5
From: Wang Mingyu <[email protected]>
Changelog:
=============
Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 3.1.4. Added a function to support an upcoming pyOpenSSL release.
Signed-off-by Wang Mingyu <[email protected]>
---
...vectors_41.0.4.bb => python3-cryptography-vectors_41.0.5.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-cryptography-vectors_41.0.4.bb => python3-cryptography-vectors_41.0.5.bb} (91%)meta/recipes-devtools/python/python3-cryptography-vectors_41.0.5.bb renamed from meta/recipes-devtools/python/python3-cryptography-vectors_41.0.4.bb +1 -1
@@ -9,7 +9,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=8c3617db4fb6fae01f1d253ab91511e4 \ # NOTE: Make sure to keep this recipe at the same version as python3-cryptography # Upgrade both recipes at the same time -SRC_URI[sha256sum] = "440af2813ea7aeb52181ec651a36d9ae8f0976e8b3a62b411a800fe6fa57a19e" +SRC_URI[sha256sum] = "75e82aea2982729312af735adb2983f347bb21fff88ad5dda3673ed70e1d1caf" PYPI_PACKAGE = "cryptography_vectors"
Signature · 1 line
2.34.1
Quoted 2 lines · wangmy
# NOTE: Make sure to keep this recipe at the same version as python3-cryptography
# Upgrade both recipes at the same time
Please note this comment - there does not seem to be an upgrade of python3-cryptography in your patch set, and it would be even better to squash both updates together into a single commit.
Alex