@@ -1,10 +1,10 @@
-From 390a233ed969f82b2ef209b23bfb523e785603f9 Mon Sep 17 00:00:00 2001
+From 4330fe9874ce72026860f96f35faf796e7ea8384 Mon Sep 17 00:00:00 2001
From: Trevor Gamblin <tgamblin@baylibre.com>
Date: Tue, 9 May 2023 10:19:41 -0400
Subject: [PATCH] setup.py: hard-code version
setup.py is pulling the build version from the current date rather than
-a release tag or other predictable method, causing reproducibility
+a release tag or other predictable method, causing reproducibility
issues in builds. Patch this to make reproducible builds work while
discussing this with upstream maintainer (or developing a patch that can
make calver rely on a more standard pyproject.toml solution).
@@ -17,7 +17,7 @@ Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/setup.py b/setup.py
-index 73f6b10..2e27cf1 100644
+index cff2eaf..79c883d 100644
--- a/setup.py
+++ b/setup.py
@@ -42,5 +42,5 @@ setup(
@@ -27,6 +27,3 @@ index 73f6b10..2e27cf1 100644
- version=calver_version(True),
+ version=calver_version("2022.6.26"),
)
-2.40.0
-
similarity index 90%
rename from meta/recipes-devtools/python/python3-calver_2022.6.26.bb
rename to meta/recipes-devtools/python/python3-calver_2025.03.31.bb
@@ -7,7 +7,7 @@ SRC_URI = " \
git://github.com/di/calver;branch=master;protocol=https \
file://0001-setup.py-hard-code-version.patch \
"
-SRCREV = "3268d8acf2c345f32a1c5f08ba25dc67f76cca81"
+SRCREV = "e1f9f3aaa5fc8f3a244e1d479c08340a45c8bfa8"
inherit python_setuptools_build_meta ptest-python-pytest
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *python3-calver* to *2025.03.31* has Succeeded. Next steps: - apply the patch: git am 0001-python3-calver-upgrade-2022.6.26-2025.03.31.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 5c0cc00db027cbb8ef1b122332708d6996ebd38f Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Tue, 1 Apr 2025 08:49:05 +0000 Subject: [PATCH] python3-calver: upgrade 2022.6.26 -> 2025.03.31 --- .../python3-calver/0001-setup.py-hard-code-version.patch | 9 +++------ ...-calver_2022.6.26.bb => python3-calver_2025.03.31.bb} | 2 +- 2 files changed, 4 insertions(+), 7 deletions(-) rename meta/recipes-devtools/python/{python3-calver_2022.6.26.bb => python3-calver_2025.03.31.bb} (90%)