similarity index 95%
rename from meta-python/recipes-devtools/python/python3-m2crypto_0.39.0.bb
rename to meta-python/recipes-devtools/python/python3-m2crypto_0.40.1.bb
@@ -11,7 +11,7 @@ SRC_URI += "file://0001-setup.py-link-in-sysroot-not-in-host-directories.patch \
file://avoid-host-contamination.patch \
file://0001-setup.py-address-openssl-3.x-build-issue.patch \
"
-SRC_URI[sha256sum] = "24c0f471358b8b19ad4c8aa9da12e868030b65c1fdb3279d006df60c9501338a"
+SRC_URI[sha256sum] = "bbfd113ec55708c05816252a4f09e4237df4f3bbfc8171cbbc33057d257bbb30"
PYPI_PACKAGE = "M2Crypto"
inherit pypi siteinfo setuptools3
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-m2crypto* to *0.40.1* has Succeeded. Next steps: - apply the patch: git am 0001-python3-m2crypto-upgrade-0.39.0-0.40.1.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -- >8 -- From b39c1a7d0c38ff2ff518644f5b626d9eef556bef Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Fri, 3 Nov 2023 22:41:15 +0000 Subject: [PATCH] python3-m2crypto: upgrade 0.39.0 -> 0.40.1 --- .../{python3-m2crypto_0.39.0.bb => python3-m2crypto_0.40.1.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta-python/recipes-devtools/python/{python3-m2crypto_0.39.0.bb => python3-m2crypto_0.40.1.bb} (95%)