From: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
To: openembedded-core@lists.openembedded.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Subject: [PATCH] python3-shacl2code: upgrade 1.2.0 -> 1.3.2
Date: Wed, 02 Sep 2026 14:21:17 +0200 [thread overview]
Message-ID: <20260902-mathieu-python3-shacl2code-1-3-2-v1-1-765805e89a5c@bootlin.com> (raw)
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
---
.../python/{python3-shacl2code_1.2.0.bb => python3-shacl2code_1.3.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3-shacl2code_1.2.0.bb b/meta/recipes-devtools/python/python3-shacl2code_1.3.2.bb
similarity index 81%
rename from meta/recipes-devtools/python/python3-shacl2code_1.2.0.bb
rename to meta/recipes-devtools/python/python3-shacl2code_1.3.2.bb
index 6956aad6189c..f43f49f1f092 100644
--- a/meta/recipes-devtools/python/python3-shacl2code_1.2.0.bb
+++ b/meta/recipes-devtools/python/python3-shacl2code_1.3.2.bb
@@ -5,7 +5,7 @@ LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=0582f358628f299f29c23bf5fb2f73c9"
PYPI_PACKAGE = "shacl2code"
-SRC_URI[sha256sum] = "92c5bb633b232bb914699157b3e79796aaf1672f22c0cac0cc633f353aa8a398"
+SRC_URI[sha256sum] = "2dd0b7a4fd50958d0783764da6ca9ede1805ccdd22b6bed3afbf89136e8962be"
inherit pypi python_hatchling
---
base-commit: dcd8e6d6703e2d5baf82f0b2e846d977c0c5844f
change-id: 20260902-mathieu-python3-shacl2code-1-3-2-92b717c09bbc
Best regards,
--
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
next reply other threads:[~2026-09-02 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 12:21 Mathieu Dubois-Briand [this message]
2026-09-02 12:31 ` Patchtest results for [PATCH] python3-shacl2code: upgrade 1.2.0 -> 1.3.2 patchtest
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=20260902-mathieu-python3-shacl2code-1-3-2-v1-1-765805e89a5c@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.