From: yash.shinde.oss.dev@gmail.com
To: openembedded-core@lists.openembedded.org
Cc: Yash Shinde <Yash.Shinde.oss.dev@gmail.com>
Subject: [PATCH 2/3] python3-scons: upgrade 4.11.0 -> 4.11.1
Date: Thu, 27 Aug 2026 12:50:09 +0530 [thread overview]
Message-ID: <20260827072010.394532-2-Yash.Shinde.oss.dev@gmail.com> (raw)
In-Reply-To: <20260827072010.394532-1-Yash.Shinde.oss.dev@gmail.com>
From: Yash Shinde <Yash.Shinde.oss.dev@gmail.com>
https://scons.org/scons-4111-is-available.html
https://github.com/SCons/scons/compare/4.11.0...4.11.1
Signed-off-by: Yash Shinde <Yash.Shinde.oss.dev@gmail.com>
---
.../python/{python3-scons_4.11.0.bb => python3-scons_4.11.1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-scons_4.11.0.bb => python3-scons_4.11.1.bb} (88%)
diff --git a/meta/recipes-devtools/python/python3-scons_4.11.0.bb b/meta/recipes-devtools/python/python3-scons_4.11.1.bb
similarity index 88%
rename from meta/recipes-devtools/python/python3-scons_4.11.0.bb
rename to meta/recipes-devtools/python/python3-scons_4.11.1.bb
index 585cad271c..c1c56856c6 100644
--- a/meta/recipes-devtools/python/python3-scons_4.11.0.bb
+++ b/meta/recipes-devtools/python/python3-scons_4.11.1.bb
@@ -4,7 +4,7 @@ SECTION = "devel/python"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=d903b0b8027f461402bac9b5169b36f7"
-SRC_URI[sha256sum] = "5ba48f9e2eb6b9178cabdc9893792418e6970c84f43f4b027e4468e20616a89c"
+SRC_URI[sha256sum] = "4210d1a80a62e986029208117991b6347ccaaaab37b67463a3ff31ee065dc487"
inherit pypi python_setuptools_build_meta
next prev parent reply other threads:[~2026-08-27 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 7:20 [PATCH 1/3] python3-click: upgrade 8.4.2 -> 8.5.0 yash.shinde.oss.dev
2026-08-27 7:20 ` yash.shinde.oss.dev [this message]
2026-08-27 7:20 ` [PATCH 3/3] python3-websockets: upgrade 17.0.1 -> 17.1 yash.shinde.oss.dev
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=20260827072010.394532-2-Yash.Shinde.oss.dev@gmail.com \
--to=yash.shinde.oss.dev@gmail.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