To: ['Trevor Gamblin '] To: openembedded-core@lists.openembedded.org Subject: [AUH] python3-vcs-versioning: upgrading to 2.3.2 SUCCEEDED Attachments: /srv/pokybuild/yocto-worker/auh/build/build/upgrade-helper/20260902050054/all/python3-vcs-versioning/buildhistory-diff-full.txt /srv/pokybuild/yocto-worker/auh/build/build/upgrade-helper/20260902050054/all/python3-vcs-versioning/python3-vcs-versioning-changelog.txt /srv/pokybuild/yocto-worker/auh/build/build/upgrade-helper/20260902050054/all/python3-vcs-versioning/0001-python3-vcs-versioning-upgrade-2.3.1-2.3.2.patch /srv/pokybuild/yocto-worker/auh/build/build/upgrade-helper/20260902050054/all/python3-vcs-versioning/buildhistory-diff.txt 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.3.2* has Succeeded. Next steps: - apply the patch: git am 0001-python3-vcs-versioning-upgrade-2.3.1-2.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 96da56b1aa705084ef62e167ceeaa1ff233d9e1a Mon Sep 17 00:00:00 2001 From: Upgrade Helper Date: Wed, 2 Sep 2026 05:23:34 +0000 Subject: [PATCH] python3-vcs-versioning: upgrade 2.3.1 -> 2.3.2 Source: CHANGELOG.md ## 2.3.2 (2026-09-01) ### Fixed - Register the `pkginfo` workdir discovery factory in vcs-versioning itself. `PKG-INFO` is standard sdist metadata, not a setuptools artifact, but its factory was only registered by setuptools-scm -- so a standalone vcs-versioning install could not infer a version from an sdist. This broke sdist builds for non-setuptools backends, e.g. meson-python calling `python -m vcs_versioning` from `project()`. Fallback workdir candidates are now ordered by how much metadata they carry (egg-info, then archival, then `PKG-INFO`) instead of by entry point iteration order, so a setuptools built sdist keeps using its `scm_version.json` now that the two factories ship from different distributions. ([#1507](https://github.com/pypa/setuptools-scm/issues/1507)) ### Miscellaneous - Stop shipping a per-package `uv.lock` in the sdist. It could not be generated correctly whenever `setuptools-scm` required an unreleased `vcs-versioning`, which broke the release proposal workflow. ([#1509](https://github.com/pypa/setuptools-scm/issues/1509)) --- ...-vcs-versioning_2.3.1.bb => python3-vcs-versioning_2.3.2.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/python/{python3-vcs-versioning_2.3.1.bb => python3-vcs-versioning_2.3.2.bb} (91%) diff --git a/meta/recipes-devtools/python/python3-vcs-versioning_2.3.1.bb b/meta/recipes-devtools/python/python3-vcs-versioning_2.3.2.bb similarity index 91% rename from meta/recipes-devtools/python/python3-vcs-versioning_2.3.1.bb rename to meta/recipes-devtools/python/python3-vcs-versioning_2.3.2.bb index 1800475dff..57ea6a9227 100644 --- a/meta/recipes-devtools/python/python3-vcs-versioning_2.3.1.bb +++ b/meta/recipes-devtools/python/python3-vcs-versioning_2.3.2.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] = "806635bd0ea653c96af98a70624be758d408a989f2cd0b390e63474d99f96b63" +SRC_URI[sha256sum] = "24abddff97aecf44cf3fec727eae8d76d9c6f70f5acb39afc41f824d69f2aac5" SRC_URI += "\ file://run-ptest \ -- 2.47.1