From: Wang Mingyu < wangmy@fujitsu.com>
To: openembedded-core@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH 08/17] python3-packaging: upgrade 25.0 -> 26.0
Date: Mon, 26 Jan 2026 20:35:07 +0800 [thread overview]
Message-ID: <20260126123517.1020-8-wangmy@fujitsu.com> (raw)
In-Reply-To: <20260126123517.1020-1-wangmy@fujitsu.com>
From: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../{python3-packaging_25.0.bb => python3-packaging_26.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-packaging_25.0.bb => python3-packaging_26.0.bb} (93%)
diff --git a/meta/recipes-devtools/python/python3-packaging_25.0.bb b/meta/recipes-devtools/python/python3-packaging_26.0.bb
similarity index 93%
rename from meta/recipes-devtools/python/python3-packaging_25.0.bb
rename to meta/recipes-devtools/python/python3-packaging_26.0.bb
index 9cb5c68f58..cadf913db8 100644
--- a/meta/recipes-devtools/python/python3-packaging_25.0.bb
+++ b/meta/recipes-devtools/python/python3-packaging_26.0.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "https://github.com/pypa/packaging"
LICENSE = "Apache-2.0 | BSD-2-Clause"
LIC_FILES_CHKSUM = "file://LICENSE;md5=faadaedca9251a90b205c9167578ce91"
-SRC_URI[sha256sum] = "d443872c98d677bf60f6a1f2f8c1cb748e8fe762d2bf9d3148b5599295b0fc4f"
+SRC_URI[sha256sum] = "00243ae351a257117b6a241061796684b084ed1c516a08c48a3f7e147a9d80b4"
SRC_URI += "file://run-ptest.in"
--
2.43.0
next prev parent reply other threads:[~2026-01-26 12:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 12:35 [OE-core] [PATCH 01/17] bind: upgrade 9.20.17 -> 9.20.18 Wang Mingyu
2026-01-26 12:35 ` [OE-core] [PATCH 02/17] harfbuzz: upgrade 12.3.0 -> 12.3.1 Wang Mingyu
2026-01-26 12:35 ` [OE-core] [PATCH 03/17] meson: upgrade 1.10.0 -> 1.10.1 Wang Mingyu
2026-01-26 12:35 ` [OE-core] [PATCH 04/17] p11-kit: upgrade 0.25.10 -> 0.26.1 Wang Mingyu
2026-01-26 12:35 ` [OE-core] [PATCH 05/17] python3-hypothesis: upgrade 6.149.0 -> 6.150.3 Wang Mingyu
2026-01-26 12:35 ` [OE-core] [PATCH 06/17] python3-markdown: upgrade 3.10 -> 3.10.1 Wang Mingyu
2026-01-26 12:35 ` [OE-core] [PATCH 07/17] python3-meson-python: upgrade 0.18.0 -> 0.19.0 Wang Mingyu
2026-01-26 12:35 ` Wang Mingyu [this message]
2026-01-28 7:08 ` [OE-core] [PATCH 08/17] python3-packaging: upgrade 25.0 -> 26.0 Mathieu Dubois-Briand
2026-01-26 12:35 ` [OE-core] [PATCH 09/17] python3-pdm: upgrade 2.26.4 -> 2.26.6 Wang Mingyu
2026-01-26 12:35 ` [OE-core] [PATCH 10/17] python3-poetry-core: upgrade 2.2.1 -> 2.3.0 Wang Mingyu
2026-01-29 12:51 ` Paul Barker
2026-01-26 12:35 ` [OE-core] [PATCH 11/17] python3-pyasn1: upgrade 0.6.1 -> 0.6.2 Wang Mingyu
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=20260126123517.1020-8-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