From: <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [oe] [meta-python] [PATCH] python3-cmake: upgrade 3.26.1 -> 3.26.3
Date: Mon, 17 Apr 2023 14:46:29 +0800 [thread overview]
Message-ID: <1681713993-18603-1-git-send-email-wangmy@fujitsu.com> (raw)
From: Wang Mingyu <wangmy@fujitsu.com>
Changelog:
==========
update pre-commit hooks (#350, #353)
bump pypa/gh-action-pypi-publish from 1.8.3 to 1.8.5
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../python/{python3-cmake_3.26.1.bb => python3-cmake_3.26.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-cmake_3.26.1.bb => python3-cmake_3.26.3.bb} (90%)
diff --git a/meta-python/recipes-devtools/python/python3-cmake_3.26.1.bb b/meta-python/recipes-devtools/python/python3-cmake_3.26.3.bb
similarity index 90%
rename from meta-python/recipes-devtools/python/python3-cmake_3.26.1.bb
rename to meta-python/recipes-devtools/python/python3-cmake_3.26.3.bb
index f95e2eab0..8e924acd3 100644
--- a/meta-python/recipes-devtools/python/python3-cmake_3.26.1.bb
+++ b/meta-python/recipes-devtools/python/python3-cmake_3.26.3.bb
@@ -11,7 +11,7 @@ PYPI_PACKAGE = "cmake"
PYPI_ARCHIVE_NAME_PREFIX = "pypi-"
inherit pypi python_setuptools_build_meta
-SRC_URI[sha256sum] = "4e0eb3c03dcf2d459f78d96cc85f7482476aeb1ae5ada65150b1db35c0f70cc7"
+SRC_URI[sha256sum] = "b54cde1f1c0573321b22382bd2ffaf5d08f65188572d128cd4867fb9669723c5"
SRC_URI += " \
file://CMakeLists.txt \
--
2.34.1
next reply other threads:[~2023-04-17 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 6:46 wangmy [this message]
2023-04-17 6:46 ` [oe] [meta-python] [PATCH] python3-croniter: upgrade 1.3.8 -> 1.3.14 wangmy
2023-04-17 6:46 ` [oe] [meta-python] [PATCH] python3-diskcache: upgrade 5.4.0 -> 5.5.1 wangmy
2023-04-17 6:46 ` [oe] [meta-python] [PATCH] python3-elementpath: upgrade 4.1.0 -> 4.1.1 wangmy
2023-04-17 6:46 ` [oe] [meta-python] [PATCH] python3-google-api-python-client: upgrade 2.84.0 -> 2.85.0 wangmy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1681713993-18603-1-git-send-email-wangmy@fujitsu.com \
--to=wangmy@fujitsu.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox