From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Khem Raj <raj.khem@gmail.com>, Khem Raj <khem.raj@oss.qualcomm.com>
Subject: [PATCH 4/7] python3-pdm: upgrade 2.26.6 -> 2.26.7
Date: Wed, 15 Apr 2026 22:54:04 -0700 [thread overview]
Message-ID: <20260416055407.795016-4-khem.raj@oss.qualcomm.com> (raw)
In-Reply-To: <20260416055407.795016-1-khem.raj@oss.qualcomm.com>
From: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
---
.../python/{python3-pdm_2.26.6.bb => python3-pdm_2.26.7.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-pdm_2.26.6.bb => python3-pdm_2.26.7.bb} (80%)
diff --git a/meta/recipes-devtools/python/python3-pdm_2.26.6.bb b/meta/recipes-devtools/python/python3-pdm_2.26.7.bb
similarity index 80%
rename from meta/recipes-devtools/python/python3-pdm_2.26.6.bb
rename to meta/recipes-devtools/python/python3-pdm_2.26.7.bb
index 72f6415dbc..5e6cdcb4cf 100644
--- a/meta/recipes-devtools/python/python3-pdm_2.26.6.bb
+++ b/meta/recipes-devtools/python/python3-pdm_2.26.7.bb
@@ -4,7 +4,7 @@ LICENSE = "MIT"
SECTION = "devel/python"
LIC_FILES_CHKSUM = "file://LICENSE;md5=2eb31a2cc1a758c34b499f287dd04ef2"
-SRC_URI[sha256sum] = "771f95b9a484f9eb34dcf8d851be6ff95333e4f3c46189f9004cfd5cc2e925f9"
+SRC_URI[sha256sum] = "0a96a6fb4d60dfeacc1f68bf77efda39503833f6c01866cc8700ea403f0183b7"
inherit pypi python_pdm
next prev parent reply other threads:[~2026-04-16 5:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 5:54 [PATCH 1/7] gn: upgrade to latest revision Khem Raj
2026-04-16 5:54 ` [PATCH 2/7] dos2unix: upgrade 7.5.4 -> 7.5.5 Khem Raj
2026-04-16 5:54 ` [PATCH 3/7] python3-pdm-backend: upgrade 2.4.7 -> 2.4.8 Khem Raj
2026-04-16 5:54 ` Khem Raj [this message]
2026-04-16 5:54 ` [PATCH 5/7] python3-lxml: upgrade 6.0.2 -> 6.0.4 Khem Raj
2026-04-16 5:54 ` [PATCH 6/7] re2c: upgrade 4.4 -> 4.5.1 Khem Raj
2026-04-16 5:54 ` [PATCH 7/7] libmpc: Upgrade to 1.4.0 Khem Raj
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=20260416055407.795016-4-khem.raj@oss.qualcomm.com \
--to=raj.khem@gmail.com \
--cc=khem.raj@oss.qualcomm.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