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.5.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-vcs-versioning-upgrade-2.4.0-2.5.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 45150f15abe163ed7f1d174e11838f76feb1eafb Mon Sep 17 00:00:00 2001
From: Upgrade Helper <[email protected]>
Date: Thu, 24 Sep 2026 05:21:20 +0000
Subject: [PATCH] python3-vcs-versioning: upgrade 2.4.0 -> 2.5.0
## 2.5.0 (2026-09-23)
### Added
- Add `discover_file_workdir()`, which finds the checkout a project sits in for
the purpose of listing files. `discover_workdir()` answers which checkout
defines the version, scoped by `root` and `search_parent_directories`; which
files a project ships is a separate question, and a project in a subdirectory
of a checkout still ships that checkout's files. ([#1543]( ))
### Fixed
- Accept the `tool` keyword in `_version_missing()` again. setuptools-scm 10.1.0
through 10.2.3 pass it and allow any `vcs-versioning<3`; since 2.4.1 removed
it,
a build without a detectable version failed with
`TypeError: _version_missing() got an unexpected keyword argument 'tool'`
instead of the `LookupError` that says how to set a version. The keyword is
ignored; the tool is taken from the configuration's environment. ([#1550]( ))
## 2.4.1 (2026-09-16)
### Fixed
- The error raised when a `.jj/` directory is found but `jj` is not installed
now names the environment variables that actually disable jj discovery
(`SETUPTOOLS_SCM_DISABLE_JJ=1` / `VCS_VERSIONING_DISABLE_JJ=1`) instead of an
unprefixed `DISABLE_JJ=1`, which was never read. ([#1537]( ))
- The "unable to detect version" error now names the environment variables the
running integration actually reads. It previously suggested
`SETUPTOOLS_SCM_PRETEND_VERSION_FOR_${NORMALIZED_DIST_NAME}` unconditionally,
which is not read by `vcs-versioning` on its own (or by any other integrator),
and it named setuptools-scm as the failing tool regardless of which one ran.
When the distribution name is known the suggested variable is spelled out in
full. When it is not, the generic variables are suggested instead, with a note
that the per-distribution `..._FOR_<DIST>` form needs a dist name to match --
the previous message offered a `${NORMALIZED_DIST_NAME}` template that could
never be filled in. ([#1539]( ))
- Warn when file discovery is suppressed while a VCS marker sits in the
project directory. `scm_search_known_failed()` means an integrator already
looked and found no checkout, so a `.git`, `.hg` or `.jj` right there
contradicts it and the artifact is about to lose every tracked file. That
combination was the signature of the pretend-version regression and stayed
invisible for three releases. Parent directories are not searched, since an
unpacked sdist inside an unrelated checkout is the case the suppression
exists for, and roots listed in `IGNORE_VCS_ROOTS` are skipped. ([#1540]( ))
### Miscellaneous
- Environment variable names are now built in one place (`env_var_name` /
`EnvReader.candidate_names`), shared by the lookup in `EnvReader.read` and by
every error message that suggests a variable, so a message cannot name a
variable the lookup would not honour.
The "repository found in a parent directory" error no longer offers a
`get_version(relative_to=...)` call to integrators that do not ship one; the
remaining options are renumbered instead. ([#1539]( ))
---
...-vcs-versioning_2.4.0.bb => python3-vcs-versioning_2.5.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-vcs-versioning_2.4.0.bb =>
python3-vcs-versioning_2.5.0.bb} (91%)
diff --git a/meta/recipes-devtools/python/python3-vcs-versioning_2.4.0.bb
b/meta/recipes-devtools/python/python3-vcs-versioning_2.5.0.bb
similarity index 91%
rename from meta/recipes-devtools/python/python3-vcs-versioning_2.4.0.bb
rename to meta/recipes-devtools/python/python3-vcs-versioning_2.5.0.bb
index e66a7ce7b0..16e009c16d 100644
--- a/meta/recipes-devtools/python/python3-vcs-versioning_2.4.0.bb
+++ b/meta/recipes-devtools/python/python3-vcs-versioning_2.5.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] =
"cc4b66c02ae4cfb51e843910024f7142464c3391bb1f7e04608578b45046891b"
+SRC_URI[sha256sum] =
"956a796e31f80fe714d219d6d1df15a6bf247d10f6d851bf4b98279d0a42da55"
SRC_URI += "\
file://run-ptest \
--
2.47.1
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: FILELIST: directory renamed /usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info -> /usr/lib/python3.14/site-packages/vcs_versioning-2.5.0.dist-info, directory renamed /usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info/licenses -> /usr/lib/python3.14/site-packages/vcs_versioning-2.5.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.4.0.dist-info moved to /usr/lib/python3.14/site-packages/vcs_versioning-2.5.0.dist-info Changes to packages/x86_64-linux/python3-vcs-versioning-native (sysroot): /usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info moved to /usr/lib/python3.14/site-packages/vcs_versioning-2.5.0.dist-info
0001-python3-vcs-versioning-upgrade-2.4.0-2.5.0.patch
Description: Binary data
packages/x86-64-v3-poky-linux/python3-vcs-versioning: PV changed from "2.4.0" to "2.5.0" 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.4.0.tar.gz file://run-ptest" to "https://files.pythonhosted.org/packages/source/v/vcs_versioning/vcs_versioning-2.5.0.tar.gz file://run-ptest" packages/x86-64-v3-poky-linux/python3-vcs-versioning: PKGV changed from 2.4.0 [default] to 2.5.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-dbg: PV changed from "2.4.0" to "2.5.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-dbg: PKGV changed from 2.4.0 [default] to 2.5.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-dev: PV changed from "2.4.0" to "2.5.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-dev: PKGV changed from 2.4.0 [default] to 2.5.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-doc: PV changed from "2.4.0" to "2.5.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-doc: PKGV changed from 2.4.0 [default] to 2.5.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-locale: PV changed from "2.4.0" to "2.5.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-locale: PKGV changed from 2.4.0 [default] to 2.5.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-ptest: PKGSIZE changed from 299016 to 311194 (+4%) packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-ptest: PV changed from "2.4.0" to "2.5.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-ptest: PKGV changed from 2.4.0 [default] to 2.5.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-src: PV changed from "2.4.0" to "2.5.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-src: PKGV changed from 2.4.0 [default] to 2.5.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-staticdev: PV changed from "2.4.0" to "2.5.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-staticdev: PKGV changed from 2.4.0 [default] to 2.5.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: FILELIST: directory renamed /usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info -> /usr/lib/python3.14/site-packages/vcs_versioning-2.5.0.dist-info, directory renamed /usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info/licenses -> /usr/lib/python3.14/site-packages/vcs_versioning-2.5.0.dist-info/licenses packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: PKGSIZE changed from 815292 to 831820 (+2%) packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: PV changed from "2.4.0" to "2.5.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: PKGV changed from 2.4.0 [default] to 2.5.0 [default] Changes to packages/x86-64-v3-poky-linux/python3-vcs-versioning (sysroot): /usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info moved to /usr/lib/python3.14/site-packages/vcs_versioning-2.5.0.dist-info Changes to packages/x86_64-linux/python3-vcs-versioning-native (sysroot): /usr/lib/python3.14/site-packages/vcs_versioning-2.4.0.dist-info moved to /usr/lib/python3.14/site-packages/vcs_versioning-2.5.0.dist-info
## 2.5.0 (2026-09-23)
### Added
- Add `discover_file_workdir()`, which finds the checkout a project sits in for
the purpose of listing files. `discover_workdir()` answers which checkout
defines the version, scoped by `root` and `search_parent_directories`; which
files a project ships is a separate question, and a project in a subdirectory
of a checkout still ships that checkout's files. ([#1543]( ))
### Fixed
- Accept the `tool` keyword in `_version_missing()` again. setuptools-scm 10.1.0
through 10.2.3 pass it and allow any `vcs-versioning<3`; since 2.4.1 removed
it,
a build without a detectable version failed with
`TypeError: _version_missing() got an unexpected keyword argument 'tool'`
instead of the `LookupError` that says how to set a version. The keyword is
ignored; the tool is taken from the configuration's environment. ([#1550]( ))
## 2.4.1 (2026-09-16)
### Fixed
- The error raised when a `.jj/` directory is found but `jj` is not installed
now names the environment variables that actually disable jj discovery
(`SETUPTOOLS_SCM_DISABLE_JJ=1` / `VCS_VERSIONING_DISABLE_JJ=1`) instead of an
unprefixed `DISABLE_JJ=1`, which was never read. ([#1537]( ))
- The "unable to detect version" error now names the environment variables the
running integration actually reads. It previously suggested
`SETUPTOOLS_SCM_PRETEND_VERSION_FOR_${NORMALIZED_DIST_NAME}` unconditionally,
which is not read by `vcs-versioning` on its own (or by any other integrator),
and it named setuptools-scm as the failing tool regardless of which one ran.
When the distribution name is known the suggested variable is spelled out in
full. When it is not, the generic variables are suggested instead, with a note
that the per-distribution `..._FOR_<DIST>` form needs a dist name to match --
the previous message offered a `${NORMALIZED_DIST_NAME}` template that could
never be filled in. ([#1539]( ))
- Warn when file discovery is suppressed while a VCS marker sits in the
project directory. `scm_search_known_failed()` means an integrator already
looked and found no checkout, so a `.git`, `.hg` or `.jj` right there
contradicts it and the artifact is about to lose every tracked file. That
combination was the signature of the pretend-version regression and stayed
invisible for three releases. Parent directories are not searched, since an
unpacked sdist inside an unrelated checkout is the case the suppression
exists for, and roots listed in `IGNORE_VCS_ROOTS` are skipped. ([#1540]( ))
### Miscellaneous
- Environment variable names are now built in one place (`env_var_name` /
`EnvReader.candidate_names`), shared by the lookup in `EnvReader.read` and by
every error message that suggests a variable, so a message cannot name a
variable the lookup would not honour.
The "repository found in a parent directory" error no longer offers a
`get_version(relative_to=...)` call to integrators that do not ship one; the
remaining options are renumbered instead. ([#1539]( ))
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#246564): https://lists.openembedded.org/g/openembedded-core/message/246564 Mute This Topic: https://lists.openembedded.org/mt/121405567/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
