From patchwork Thu Sep 24 05:34:33 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: 99142 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 AFD52C98304 for ; Thu, 24 Sep 2026 05:34:38 +0000 (UTC) Received: from a27-193.smtp-out.us-west-2.amazonses.com (a27-193.smtp-out.us-west-2.amazonses.com [54.240.27.193]) by mx.groups.io with SMTP id smtpd.msgproc01-g2.1370.1790228074074779015 for ; Wed, 23 Sep 2026 22:34:34 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@yoctoproject.org header.s=lvjh2tk576v2ro5mi6k4dt3mc6wpqbky header.b=Q9rkuvyo; dkim=pass header.i=@amazonses.com header.s=hsbnp7p3ensaochzwyq5wwmceodymuwv header.b=mzyYP3Iu; spf=pass (domain: us-west-2.amazonses.com, ip: 54.240.27.193, mailfrom: 010101a0d1e88a5e-e9a3d072-4565-4da6-a759-78570e71d704-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=1790228073; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date; bh=0td61FU15bgikYJ9hvnaQ56sItNxti3JIa4uR87eSLo=; b=Q9rkuvyoNyXHv2b2ZDBihEC1IYj7zhirWhpZdUqlwB+7yqln8pArKRShIVSTJacX bH/TyrlD6uGC6kJUA4S6KsYl2nw0Udde1L+CzxLxDg+PLY1K8tCP+qRHJIB71+ysLml Jb11l4OYib4KrjPnpKLoMtDmGHDw4OWpOlppXX9o= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=hsbnp7p3ensaochzwyq5wwmceodymuwv; d=amazonses.com; t=1790228073; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date:Feedback-ID; bh=0td61FU15bgikYJ9hvnaQ56sItNxti3JIa4uR87eSLo=; b=mzyYP3Iuhe09XHQ9AR48CGxT0uqxfoJUlSVYD9Kh2GMb3UTzxr7Zqf0zeeNeWSRD Wjx0PlGB+jyDmWI4bAHAsQx8YTpjb7CMOxZHWckkMdtp2Va0mAeThUi/e5ywXIgYGGn OwLaQ3eUAt55RMPa7kpK7FCMEXEtl5/EhtoO3+2o= MIME-Version: 1.0 From: auh@yoctoproject.org To: Trevor Gamblin Cc: openembedded-core@lists.openembedded.org Subject: [AUH] python3-vcs-versioning: upgrading to 2.5.0 SUCCEEDED Message-ID: <010101a0d1e88a5e-e9a3d072-4565-4da6-a759-78570e71d704-000000@us-west-2.amazonses.com> Date: Thu, 24 Sep 2026 05:34:33 +0000 Feedback-ID: ::1.us-west-2.9np3MYPs3fEaOBysGKSlUD4KtcmPijcmS9Az2Hwf7iQ=:AmazonSES X-SES-Outgoing: 2026.09.24-54.240.27.193 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 ; Thu, 24 Sep 2026 05:34:38 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/246564 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 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_` 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 \