public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Wang Mingyu < wangmy@fujitsu.com>
To: openembedded-core@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH 13/17] python3-pyparsing: upgrade 3.3.1 -> 3.3.2
Date: Mon, 26 Jan 2026 20:38:40 +0800	[thread overview]
Message-ID: <20260126123844.1052-2-wangmy@fujitsu.com> (raw)
In-Reply-To: <20260126123844.1052-1-wangmy@fujitsu.com>

From: Wang Mingyu <wangmy@fujitsu.com>

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 .../{python3-pyparsing_3.3.1.bb => python3-pyparsing_3.3.2.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-pyparsing_3.3.1.bb => python3-pyparsing_3.3.2.bb} (90%)

diff --git a/meta/recipes-devtools/python/python3-pyparsing_3.3.1.bb b/meta/recipes-devtools/python/python3-pyparsing_3.3.2.bb
similarity index 90%
rename from meta/recipes-devtools/python/python3-pyparsing_3.3.1.bb
rename to meta/recipes-devtools/python/python3-pyparsing_3.3.2.bb
index 37d5b192bc..2565751f28 100644
--- a/meta/recipes-devtools/python/python3-pyparsing_3.3.1.bb
+++ b/meta/recipes-devtools/python/python3-pyparsing_3.3.2.bb
@@ -10,7 +10,7 @@ BUGTRACKER = "https://github.com/pyparsing/pyparsing/issues"
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=9c8a9625037eff2407f8456010875183"
 
-SRC_URI[sha256sum] = "47fad0f17ac1e2cad3de3b458570fbc9b03560aa029ed5e16ee5554da9a2251c"
+SRC_URI[sha256sum] = "c777f4d763f140633dcb6d8a3eda953bf7a214dc4eff598413c070bcdc117cbc"
 
 inherit pypi python_flit_core
 
-- 
2.43.0



  reply	other threads:[~2026-01-26 12:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 12:38 [OE-core] [PATCH 12/17] python3-pycparser: upgrade 2.23 -> 3.0 Wang Mingyu
2026-01-26 12:38 ` Wang Mingyu [this message]
2026-01-26 12:38 ` [OE-core] [PATCH 14/17] python3-sphinx-rtd-theme: upgrade 3.0.2 -> 3.1.0 Wang Mingyu
2026-01-26 12:38 ` [OE-core] [PATCH 15/17] python3-uv-build: upgrade 0.9.18 -> 0.9.26 Wang Mingyu
2026-01-26 12:38 ` [OE-core] [PATCH 16/17] python3-wheel: upgrade 0.46.1 -> 0.46.3 Wang Mingyu
2026-01-28 16:44   ` Mathieu Dubois-Briand
2026-01-29  8:06     ` Mingyu Wang (Fujitsu)
2026-02-03  9:09     ` Mingyu Wang (Fujitsu)
2026-02-03  9:13     ` Mingyu Wang (Fujitsu)
2026-02-09 13:57       ` Alexander Kanavin
2026-01-26 12:38 ` [OE-core] [PATCH 17/17] python3-yamllint: upgrade 1.37.1 -> 1.38.0 Wang Mingyu
2026-01-27 15:42 ` [OE-core] [PATCH 12/17] python3-pycparser: upgrade 2.23 -> 3.0 Mathieu Dubois-Briand

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=20260126123844.1052-2-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