| Message ID | 010101994d3a1ff4-8ff1d551-b508-48ee-a178-22aa47675443-000000@us-west-2.amazonses.com |
|---|---|
| State | New |
| Headers | show |
| Series | [AUH] libcomps: upgrading to 0.1.23 SUCCEEDED | expand |
diff --git a/meta/recipes-devtools/libcomps/libcomps/0001-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch b/meta/recipes-devtools/libcomps/libcomps/0001-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch index 6fc0a4177f..39d4347493 100644 --- a/meta/recipes-devtools/libcomps/libcomps/0001-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch +++ b/meta/recipes-devtools/libcomps/libcomps/0001-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch @@ -1,4 +1,4 @@ -From 159ad0e19f4c5d7fe357378c00db19c1106e62c4 Mon Sep 17 00:00:00 2001 +From b408fd956fb22be6ba27064f3c4a0b1d67282bba Mon Sep 17 00:00:00 2001 From: Alexander Kanavin <alex.kanavin@gmail.com> Date: Fri, 30 Dec 2016 18:22:09 +0200 Subject: [PATCH] Do not set PYTHON_INSTALL_DIR by running python. diff --git a/meta/recipes-devtools/libcomps/libcomps_0.1.22.bb b/meta/recipes-devtools/libcomps/libcomps_0.1.23.bb similarity index 94% rename from meta/recipes-devtools/libcomps/libcomps_0.1.22.bb rename to meta/recipes-devtools/libcomps/libcomps_0.1.23.bb index 796b78ef65..0a9608297a 100644 --- a/meta/recipes-devtools/libcomps/libcomps_0.1.22.bb +++ b/meta/recipes-devtools/libcomps/libcomps_0.1.23.bb @@ -8,7 +8,7 @@ SRC_URI = "git://github.com/rpm-software-management/libcomps.git;branch=master;t file://0001-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch \ " -SRCREV = "3f0d19b3c3273db4bf0497f08f22317835c1d426" +SRCREV = "e75e85ffd2c7f2a2a96d8eaf45d8dc4f2c73153d" inherit cmake setuptools3-base
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *libcomps* to *0.1.23* has Succeeded. Next steps: - apply the patch: git am 0001-libcomps-upgrade-0.1.22-0.1.23.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 e1d2bcd6b01e70658503573b20e5ea27a5334a8f Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Mon, 15 Sep 2025 07:52:54 +0000 Subject: [PATCH] libcomps: upgrade 0.1.22 -> 0.1.23 --- .../0001-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch | 2 +- .../libcomps/{libcomps_0.1.22.bb => libcomps_0.1.23.bb} | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-devtools/libcomps/{libcomps_0.1.22.bb => libcomps_0.1.23.bb} (94%)