To: ['Joshua Watt ', 'Joshua Watt '] To: openembedded-core@lists.openembedded.org Subject: [AUH] python3-pycryptodome,python3-pycryptodomex: upgrading to 4.0.0,3.24.1 FAILED Attachments: /srv/pokybuild/yocto-worker/auh/build/build/upgrade-helper/20261015050057/all/python3-pycryptodome,python3-pycryptodomex/python3-pycryptodomex-changelog.txt /srv/pokybuild/yocto-worker/auh/build/build/upgrade-helper/20261015050057/all/python3-pycryptodome,python3-pycryptodomex/python3-pycryptodome-changelog.txt /srv/pokybuild/yocto-worker/auh/build/build/upgrade-helper/20261015050057/all/python3-pycryptodome,python3-pycryptodomex/0001-python3-pycryptodome-python3-pycryptodomex-upgrade-3.patch /srv/pokybuild/yocto-worker/auh/build/build/upgrade-helper/20261015050057/all/python3-pycryptodome,python3-pycryptodomex/bitbake-output-qemux86-64.txt Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *python3-pycryptodome,python3-pycryptodomex* to *4.0.0,3.24.1* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-python3-pycryptodome-python3-pycryptodomex-upgrade-3.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 e9832c4f1f262c86300e72e9616eb339b5f14338 Mon Sep 17 00:00:00 2001 From: Upgrade Helper Date: Thu, 15 Oct 2026 05:09:53 +0000 Subject: [PATCH] python3-pycryptodome,python3-pycryptodomex: upgrade 3.23.0 -> 4.0.0,3.23.0 -> 3.24.1 4.0.0 (14 October 2026) Breaking changes ---------------- Deprecations ------------ Resolved issues --------------- New features ------------ 3.24.1 (11 October 2026) Resolved issues --------------- 3.24.0 (4 October 2026) New features --------------- Resolved issues --------------- Other changes ------------- 3.24.1 (11 October 2026) Resolved issues --------------- 3.24.0 (4 October 2026) New features --------------- Resolved issues --------------- Other changes ------------- --- ....23.0.bb => python3-pycryptodome_4.0.0.bb} | 26 ++++++++++++++++++- ...3.0.bb => python3-pycryptodomex_3.24.1.bb} | 2 +- 2 files changed, 26 insertions(+), 2 deletions(-) rename meta/recipes-devtools/python/{python3-pycryptodome_3.23.0.bb => python3-pycryptodome_4.0.0.bb} (11%) rename meta/recipes-devtools/python/{python3-pycryptodomex_3.23.0.bb => python3-pycryptodomex_3.24.1.bb} (76%) diff --git a/meta/recipes-devtools/python/python3-pycryptodome_3.23.0.bb b/meta/recipes-devtools/python/python3-pycryptodome_4.0.0.bb similarity index 11% rename from meta/recipes-devtools/python/python3-pycryptodome_3.23.0.bb rename to meta/recipes-devtools/python/python3-pycryptodome_4.0.0.bb index 1b2a5edd38..cc3bf81e90 100644 --- a/meta/recipes-devtools/python/python3-pycryptodome_3.23.0.bb +++ b/meta/recipes-devtools/python/python3-pycryptodome_4.0.0.bb @@ -1,6 +1,30 @@ +# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'. +# The following is the difference between the old and the new license text. +# Please update the LICENSE value if needed, and summarize the changes in +# the commit message via 'License-Update:' tag. +# (example: 'License-Update: copyright years updated.') +# +# The changes: +# +# --- LICENSE.rst +# +++ LICENSE.rst +# @@ -3,6 +3,10 @@ +# +# In either case, there are minimal if no restrictions on the redistribution, +# modification and usage of the software. +# + +# +Files that do not include the license text refer to it with an SPDX tag: +# +``SPDX-License-Identifier: BSD-2-Clause`` for the BSD license below +# +(``SPDX-FileCopyrightText`` gives the copyright notice). +# +# Public domain +# ============= +# +# + require python-pycryptodome.inc inherit python_setuptools_build_meta -SRC_URI[sha256sum] = "447700a657182d60338bab09fdb27518f8856aecd80ae4c6bdddb67ff5da44ef" +SRC_URI[sha256sum] = "4ad4dd220fa22f99f5832847ccaea5bee39f140b8e4ea1a29aa77dc969c6490c" CVE_PRODUCT = "pycryptodome:pycryptodome" diff --git a/meta/recipes-devtools/python/python3-pycryptodomex_3.23.0.bb b/meta/recipes-devtools/python/python3-pycryptodomex_3.24.1.bb similarity index 76% rename from meta/recipes-devtools/python/python3-pycryptodomex_3.23.0.bb rename to meta/recipes-devtools/python/python3-pycryptodomex_3.24.1.bb index e2120d9972..b24e047a19 100644 --- a/meta/recipes-devtools/python/python3-pycryptodomex_3.23.0.bb +++ b/meta/recipes-devtools/python/python3-pycryptodomex_3.24.1.bb @@ -1,7 +1,7 @@ require python-pycryptodome.inc inherit python_setuptools_build_meta -SRC_URI[sha256sum] = "71909758f010c82bc99b0abf4ea12012c98962fbf0583c2164f8b84533c2e4da" +SRC_URI[sha256sum] = "09081666ffc599976c0b8b29caf2cf82212c0f05bed233c8f8ed53e4f6e1d356" CVE_PRODUCT = "pycryptodome:pycryptodome pycryptodome:pycryptodomex" -- 2.47.1