[AUH] python3-setuptools-scm: upgrading to 10.3.2 FAILED

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 <auh@yoctoproject.org>
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%)