From patchwork Tue Sep 15 05:49:26 2026 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: auh@yoctoproject.org X-Patchwork-Id: 98264 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6307DC982C2 for ; Tue, 15 Sep 2026 05:49:36 +0000 (UTC) Received: from a27-33.smtp-out.us-west-2.amazonses.com (a27-33.smtp-out.us-west-2.amazonses.com [54.240.27.33]) by mx.groups.io with SMTP id smtpd.msgproc01-g2.16957.1789451367828845730 for ; Mon, 14 Sep 2026 22:49:27 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@yoctoproject.org header.s=lvjh2tk576v2ro5mi6k4dt3mc6wpqbky header.b=YCThe8z/; dkim=pass header.i=@amazonses.com header.s=hsbnp7p3ensaochzwyq5wwmceodymuwv header.b=ZNa+0fMp; spf=pass (domain: us-west-2.amazonses.com, ip: 54.240.27.33, mailfrom: 010101a0a39cf1ce-660e44b7-7bdd-4f21-b6df-7afe043994a6-000000@us-west-2.amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=lvjh2tk576v2ro5mi6k4dt3mc6wpqbky; d=yoctoproject.org; t=1789451367; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date; bh=A/eKbItsK6WZADOjI7Jijp3pgrkonaYRGs20EUM1n0o=; b=YCThe8z/ZQ3UDfEcuJXujfo+9+Pn6/y/NQtASG2W7DCt/Y/dFcTFSbvaCRjKpB1Z Atx6BnOr1AAne6JonYQP7CQXHjou74HGHBvHCWTbsRcisGbNnMYadgCAYwaHnd74k2k 9/1z2ZCSMCY3Wdu/QJUyxjuqHmZbFk+MbdEZBrfI= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=hsbnp7p3ensaochzwyq5wwmceodymuwv; d=amazonses.com; t=1789451367; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date:Feedback-ID; bh=A/eKbItsK6WZADOjI7Jijp3pgrkonaYRGs20EUM1n0o=; b=ZNa+0fMpXbxrLqA7mHQyI1WsTP3DA+Lri2Z00navanyjsYuldh3BwYyEHh+3a4wT 8nkQyzYu2EK+4XTIZZa+3XvuvJ+XMZDiNHfbAJSFZYHO/QoKRs4rNTldaPFGoDp0AOY haLhZviJXyK1xzrkTn0AizYIFfyynia/eK6zNVnE= MIME-Version: 1.0 From: auh@yoctoproject.org To: Trevor Gamblin Cc: openembedded-core@lists.openembedded.org Subject: [AUH] python3-setuptools-scm: upgrading to 10.3.2 FAILED Message-ID: <010101a0a39cf1ce-660e44b7-7bdd-4f21-b6df-7afe043994a6-000000@us-west-2.amazonses.com> Date: Tue, 15 Sep 2026 05:49:26 +0000 Feedback-ID: ::1.us-west-2.9np3MYPs3fEaOBysGKSlUD4KtcmPijcmS9Az2Hwf7iQ=:AmazonSES X-SES-Outgoing: 2026.09.15-54.240.27.33 List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Tue, 15 Sep 2026 05:49:36 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/245814 Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *python3-setuptools-scm* to *10.3.2* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-python3-setuptools-scm-upgrade-10.2.3-10.3.2.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 7f108232b164dde8bec89f10756f9a5d8e5bfc22 Mon Sep 17 00:00:00 2001 From: Upgrade Helper Date: Tue, 15 Sep 2026 05:13:29 +0000 Subject: [PATCH] python3-setuptools-scm: upgrade 10.2.3 -> 10.3.2 Source: CHANGELOG.md ## 10.3.2 (2026-09-14) ### Fixed - Stop the command mixins from reordering a project's own ``build_py``, ``egg_info`` or ``bdist_wheel`` MRO. ``ScmVersionFileMixin`` and friends inherited from the corresponding setuptools command, so wrapping a project class built on a disjoint hierarchy -- ``distutils.command.build_py``, or the standalone ``wheel`` package's ``bdist_wheel`` -- placed setuptools' command *ahead* of the project's class. ``setuptools.build_py.run()`` does not delegate any further, so the project's ``run()`` was silently skipped, surfacing as ``error: package directory '...' does not exist``. The mixins now carry no runtime base class and linearise to ``(wrapped, mixin, *project_command.__mro__)``. ([#1531](https://github.com/pypa/setuptools-scm/issues/1531)) - Leave a project's ``cmdclass`` alone when setuptools-scm is installed but not actually inferring a version. ``build_py``, ``egg_info`` and ``bdist_wheel`` are now registered only once version inference has stored data on the distribution -- the precondition for any of the mixins doing something. Previously every project with a ``pyproject.toml`` had its commands wrapped, including projects with no ``[tool.setuptools_scm]`` section at all. Note for projects that *used* to configure setuptools-scm and no longer do: a ``scm_version.json`` left behind in a stale ``*.egg-info`` directory is no longer stripped from built wheels, because the ``bdist_wheel`` mixin that strips it is no longer registered either. Remove the stale ``*.egg-info`` directory. ([#1533](https://github.com/pypa/setuptools-scm/issues/1533)) ## 10.3.1 (2026-09-14) ### Fixed - Require ``vcs-versioning>=2.4.0``. setuptools-scm 10.3.0 declared ``>=2.3.2`` but imports ``vcs_versioning._file_finders.scm_search_known_failed``, which vcs-versioning only gained in 2.4.0, so installing it alongside an older vcs-versioning failed with ``ImportError``. CI now installs setuptools-scm against the oldest vcs-versioning its metadata permits, so the lower bound can no longer go stale unnoticed. ([#1528](https://github.com/pypa/setuptools-scm/issues/1528)) ## 10.3.0 (2026-09-12) ### Deprecated - Emit a ``DeprecationWarning`` when the ``setuptools.file_finders`` entry point is invoked for a project that does not configure setuptools-scm. The entry point will be removed in a future major release. ([#1407](https://github.com/pypa/setuptools-scm/issues/1407)) ### Fixed - Run the `setuptools.file_finders` hook inside a setuptools-scm override context. It previously resolved settings under the `VCS_VERSIONING` prefix only, so documented variables such as `SETUPTOOLS_SCM_SUBPROCESS_TIMEOUT` and `SETUPTOOLS_SCM_HG_COMMAND` were ignored when finding files. When version inference has already run and found no SCM checkout, the `egg_info` mixin now tells the file finders so, rather than letting `walk_revctrl()` re-probe every backend for a repository known to be a [Changelog truncated as it exceeds 3000 characters; the full changelog can be found in an attachment to the AUH email] --- ...etuptools-scm_10.2.3.bb => python3-setuptools-scm_10.3.2.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/python/{python3-setuptools-scm_10.2.3.bb => python3-setuptools-scm_10.3.2.bb} (89%) diff --git a/meta/recipes-devtools/python/python3-setuptools-scm_10.2.3.bb b/meta/recipes-devtools/python/python3-setuptools-scm_10.3.2.bb similarity index 89% rename from meta/recipes-devtools/python/python3-setuptools-scm_10.2.3.bb rename to meta/recipes-devtools/python/python3-setuptools-scm_10.3.2.bb index 0af4bd24f5..30c9483abb 100644 --- a/meta/recipes-devtools/python/python3-setuptools-scm_10.2.3.bb +++ b/meta/recipes-devtools/python/python3-setuptools-scm_10.3.2.bb @@ -6,7 +6,7 @@ argument or in a SCM managed file." LICENSE = "MIT" LIC_FILES_CHKSUM = "file://LICENSE;md5=838c366f69b72c5df05c96dff79b35f2" -SRC_URI[sha256sum] = "f179ed3e2a63cf5823e5ee9aa9ca08386219400443a0553224d72dde3f206b44" +SRC_URI[sha256sum] = "205772a055fcad83a9c6bb533caaa5d864137cdb2bccf41be083bcf43fdda1c1" PYPI_PACKAGE = "setuptools_scm"