Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe(s) *python3-vcs-versioning* to 
*2.4.0* has Succeeded.

Next steps:
    - apply the patch: git am 
0001-python3-vcs-versioning-upgrade-2.3.4-2.4.0.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 8e9c7b4238086925e620dd5574e93fa943ef2066 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <[email protected]>
Date: Mon, 14 Sep 2026 05:26:43 +0000
Subject: [PATCH] python3-vcs-versioning: upgrade 2.3.4 -> 2.4.0

Source: CHANGELOG.md

## 2.4.0 (2026-09-12)

### Added

- Add `scm.git.distance_scope` and `scm.git.distance_count`, restricting the 
distance count to the commits that touch a monorepo project (and optionally 
further shared directories) instead of every commit in the repository. Counting 
uses `--full-history` by default, or `--first-parent`; git's default history 
simplification is not offered because it can make the distance shrink across a 
merge. Git only. ([#1056](https://github.com/pypa/setuptools-scm/issues/1056))

### Fixed

- Select file finders by the VCS marker their entry point is named for (`.git`, 
`.hg`, `.jj`) instead of running every backend's command in turn. A tree with 
no VCS marker -- an unpacked sdist, say -- now spawns no subprocess at all, so 
a slow `hg` on `PATH` can no longer fail an unrelated build.

  The finders also survive a subprocess timeout: `subprocess.TimeoutExpired` 
was uncaught and aborted the build, and is now treated like any other failed 
probe. ([#1212](https://github.com/pypa/setuptools-scm/issues/1212))
- Prefer the fallback metadata nearest the project directory. A 
`.git_archival.txt` or `PKG-INFO` at the VCS root no longer shadows a monorepo 
project's own, which silently produced the root project's version. 
([#1522](https://github.com/pypa/setuptools-scm/issues/1522))
---
 ...-vcs-versioning_2.3.4.bb => python3-vcs-versioning_2.4.0.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-vcs-versioning_2.3.4.bb => 
python3-vcs-versioning_2.4.0.bb} (91%)

diff --git a/meta/recipes-devtools/python/python3-vcs-versioning_2.3.4.bb 
b/meta/recipes-devtools/python/python3-vcs-versioning_2.4.0.bb
similarity index 91%
rename from meta/recipes-devtools/python/python3-vcs-versioning_2.3.4.bb
rename to meta/recipes-devtools/python/python3-vcs-versioning_2.4.0.bb
index e358c722d7..e66a7ce7b0 100644
--- a/meta/recipes-devtools/python/python3-vcs-versioning_2.3.4.bb
+++ b/meta/recipes-devtools/python/python3-vcs-versioning_2.4.0.bb
@@ -5,7 +5,7 @@ library that can be used independently of setuptools."
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=c9b06ad2ebd7e2e82d34b3caf353e7d5"
 
-SRC_URI[sha256sum] = 
"f3443da15a34a32755b04324e33c6166add300c7661f45902225190c9337f711"
+SRC_URI[sha256sum] = 
"cc4b66c02ae4cfb51e843910024f7142464c3391bb1f7e04608578b45046891b"
 
 SRC_URI += "\
     file://run-ptest \
-- 
2.47.1

packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-ptest:
 FILELIST: added 
"/usr/lib/python3-vcs-versioning/ptest/testing_vcs/test_git_distance_scope.py"
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: 
FILELIST: directory renamed 
/usr/lib/python3.14/site-packages/vcs_versioning-2.3.4.dist-info -> 
/usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info, directory 
renamed 
/usr/lib/python3.14/site-packages/vcs_versioning-2.3.4.dist-info/licenses -> 
/usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info/licenses
Changes to packages/x86-64-v3-poky-linux/python3-vcs-versioning (sysroot):
  /usr/lib/python3.14/site-packages/vcs_versioning-2.3.4.dist-info moved to 
/usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info
Changes to packages/x86_64-linux/python3-vcs-versioning-native (sysroot):
  /usr/lib/python3.14/site-packages/vcs_versioning-2.3.4.dist-info moved to 
/usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info
packages/x86-64-v3-poky-linux/python3-vcs-versioning: PV changed from "2.3.4" 
to "2.4.0"
packages/x86-64-v3-poky-linux/python3-vcs-versioning: PKGV changed from 2.3.4 
[default] to 2.4.0 [default]
packages/x86-64-v3-poky-linux/python3-vcs-versioning: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/v/vcs_versioning/vcs_versioning-2.3.4.tar.gz
 file://run-ptest" to 
"https://files.pythonhosted.org/packages/source/v/vcs_versioning/vcs_versioning-2.4.0.tar.gz
 file://run-ptest"
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-dbg:
 PV changed from "2.3.4" to "2.4.0"
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-dbg:
 PKGV changed from 2.3.4 [default] to 2.4.0 [default]
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-dev:
 PV changed from "2.3.4" to "2.4.0"
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-dev:
 PKGV changed from 2.3.4 [default] to 2.4.0 [default]
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-doc:
 PV changed from "2.3.4" to "2.4.0"
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-doc:
 PKGV changed from 2.3.4 [default] to 2.4.0 [default]
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-locale:
 PV changed from "2.3.4" to "2.4.0"
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-locale:
 PKGV changed from 2.3.4 [default] to 2.4.0 [default]
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-ptest:
 PKGSIZE changed from 278380 to 299016 (+7%)
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-ptest:
 FILELIST: added 
"/usr/lib/python3-vcs-versioning/ptest/testing_vcs/test_git_distance_scope.py"
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-ptest:
 PV changed from "2.3.4" to "2.4.0"
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-ptest:
 PKGV changed from 2.3.4 [default] to 2.4.0 [default]
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-src:
 PV changed from "2.3.4" to "2.4.0"
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-src:
 PKGV changed from 2.3.4 [default] to 2.4.0 [default]
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-staticdev:
 PV changed from "2.3.4" to "2.4.0"
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-staticdev:
 PKGV changed from 2.3.4 [default] to 2.4.0 [default]
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: 
PKGSIZE changed from 777583 to 815292 (+5%)
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: 
FILELIST: directory renamed 
/usr/lib/python3.14/site-packages/vcs_versioning-2.3.4.dist-info -> 
/usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info, directory 
renamed 
/usr/lib/python3.14/site-packages/vcs_versioning-2.3.4.dist-info/licenses -> 
/usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info/licenses
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: PV 
changed from "2.3.4" to "2.4.0"
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: 
PKGV changed from 2.3.4 [default] to 2.4.0 [default]
Changes to packages/x86-64-v3-poky-linux/python3-vcs-versioning (sysroot):
  /usr/lib/python3.14/site-packages/vcs_versioning-2.3.4.dist-info moved to 
/usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info
Changes to packages/x86_64-linux/python3-vcs-versioning-native (sysroot):
  /usr/lib/python3.14/site-packages/vcs_versioning-2.3.4.dist-info moved to 
/usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info

Attachment: 0001-python3-vcs-versioning-upgrade-2.3.4-2.4.0.patch
Description: Binary data

Changelog for python3-vcs-versioning: 2.3.4 -> 2.4.0
Source: CHANGELOG.md

## 2.4.0 (2026-09-12)

### Added

- Add `scm.git.distance_scope` and `scm.git.distance_count`, restricting the 
distance count to the commits that touch a monorepo project (and optionally 
further shared directories) instead of every commit in the repository. Counting 
uses `--full-history` by default, or `--first-parent`; git's default history 
simplification is not offered because it can make the distance shrink across a 
merge. Git only. ([#1056](https://github.com/pypa/setuptools-scm/issues/1056))

### Fixed

- Select file finders by the VCS marker their entry point is named for (`.git`, 
`.hg`, `.jj`) instead of running every backend's command in turn. A tree with 
no VCS marker -- an unpacked sdist, say -- now spawns no subprocess at all, so 
a slow `hg` on `PATH` can no longer fail an unrelated build.

  The finders also survive a subprocess timeout: `subprocess.TimeoutExpired` 
was uncaught and aborted the build, and is now treated like any other failed 
probe. ([#1212](https://github.com/pypa/setuptools-scm/issues/1212))
- Prefer the fallback metadata nearest the project directory. A 
`.git_archival.txt` or `PKG-INFO` at the VCS root no longer shadows a monorepo 
project's own, which silently produced the root project's version. 
([#1522](https://github.com/pypa/setuptools-scm/issues/1522))
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#245755): 
https://lists.openembedded.org/g/openembedded-core/message/245755
Mute This Topic: https://lists.openembedded.org/mt/121238071/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to