From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 08/20] python3-pdm: upgrade 2.29.1 -> 2.29.2
Date: Mon, 21 Sep 2026 08:06:44 +0100 [thread overview]
Message-ID: <20260921070656.521680-8-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <20260921070656.521680-1-richard.purdie@linuxfoundation.org>
- Fix writing lock files specified as bare relative filenames with `pdm lock --lockfile`.
- Preserve local paths containing spaces and their extras and environment markers when importing requirements files.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
.../python/{python3-pdm_2.29.1.bb => python3-pdm_2.29.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-pdm_2.29.1.bb => python3-pdm_2.29.2.bb} (80%)
diff --git a/meta/recipes-devtools/python/python3-pdm_2.29.1.bb b/meta/recipes-devtools/python/python3-pdm_2.29.2.bb
similarity index 80%
rename from meta/recipes-devtools/python/python3-pdm_2.29.1.bb
rename to meta/recipes-devtools/python/python3-pdm_2.29.2.bb
index 4520e677ee5..83e9508612d 100644
--- a/meta/recipes-devtools/python/python3-pdm_2.29.1.bb
+++ b/meta/recipes-devtools/python/python3-pdm_2.29.2.bb
@@ -4,7 +4,7 @@ LICENSE = "MIT"
SECTION = "devel/python"
LIC_FILES_CHKSUM = "file://LICENSE;md5=2eb31a2cc1a758c34b499f287dd04ef2"
-SRC_URI[sha256sum] = "6bb5d893d301edb2b83d46042039634bf36c96c57cc7edad22a59521a41df9f8"
+SRC_URI[sha256sum] = "bad9705e9482e7d877a53380ff25273b01e9c1d313ee6ce7b215a6562a9d8bdd"
inherit pypi python_pdm
next prev parent reply other threads:[~2026-09-21 7:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 7:06 [PATCH 01/20] ffmpeg: upgrade 9.0.1 -> 9.0.2 Richard Purdie
2026-09-21 7:06 ` [PATCH 02/20] librsvg: upgrade 2.63.0 -> 2.63.2 Richard Purdie
2026-09-21 7:06 ` [PATCH 03/20] python3-dtschema: upgrade 2026.6 -> 2026.9 Richard Purdie
2026-09-21 7:23 ` Patchtest results for " patchtest
2026-09-21 7:06 ` [PATCH 04/20] python3-uv-build: upgrade 0.12.13 -> 0.12.17 Richard Purdie
2026-09-21 7:06 ` [PATCH 05/20] xxhash: upgrade 0.8.3 -> 0.8.4 Richard Purdie
2026-09-21 7:23 ` Patchtest results for " patchtest
2026-09-21 7:06 ` [PATCH 06/20] python3-hatchling: upgrade 1.32.0 -> 1.32.3 Richard Purdie
2026-09-21 7:06 ` [PATCH 07/20] python3-idna: upgrade 3.19 -> 3.20 Richard Purdie
2026-09-21 7:06 ` Richard Purdie [this message]
2026-09-21 7:06 ` [PATCH 09/20] python3-wcwidth: upgrade 0.8.3 -> 0.8.4 Richard Purdie
2026-09-21 7:06 ` [PATCH 10/20] barebox-tools: upgrade 2026.08.0 -> 2026.09.0 Richard Purdie
2026-09-21 7:06 ` [PATCH 11/20] bind: upgrade 9.20.27 -> 9.20.29 Richard Purdie
2026-09-21 7:06 ` [PATCH 12/20] mesa: upgrade 26.2.2 -> 26.2.3 Richard Purdie
2026-09-21 7:06 ` [PATCH 13/20] python3-pdm-build-locked: upgrade 0.3.7 -> 0.3.8 Richard Purdie
2026-09-21 7:06 ` [PATCH 14/20] python3-vcs-versioning: upgrade 2.4.0 -> 2.4.1 Richard Purdie
2026-09-21 7:06 ` [PATCH 15/20] fastfloat: upgrade 8.2.10 -> 8.3.0 Richard Purdie
2026-09-21 7:06 ` [PATCH 16/20] ppp: upgrade 2.5.3 -> 2.5.4 Richard Purdie
2026-09-21 7:06 ` [PATCH 17/20] python3-urllib3: upgrade 2.7.0 -> 2.8.0 Richard Purdie
2026-09-21 7:06 ` [PATCH 18/20] ruby: upgrade 4.0.6 -> 4.0.7 Richard Purdie
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=20260921070656.521680-8-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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