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] python3-scons: upgrade 4.3.0 -> 4.4.0
Date: Wed, 3 Aug 2022 16:44:05 +0800	[thread overview]
Message-ID: <1659516246-31185-3-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1659516246-31185-1-git-send-email-wangmy@fujitsu.com>

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

diff --git a/meta/recipes-devtools/python/python3-scons_4.3.0.bb b/meta/recipes-devtools/python/python3-scons_4.4.0.bb
similarity index 90%
rename from meta/recipes-devtools/python/python3-scons_4.3.0.bb
rename to meta/recipes-devtools/python/python3-scons_4.4.0.bb
index ae91d980fe..ad1149597f 100644
--- a/meta/recipes-devtools/python/python3-scons_4.3.0.bb
+++ b/meta/recipes-devtools/python/python3-scons_4.4.0.bb
@@ -5,7 +5,7 @@ LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=d903b0b8027f461402bac9b5169b36f7"
 
 SRC_URI += " file://0001-Fix-man-page-installation.patch"
-SRC_URI[sha256sum] = "d47081587e3675cc168f1f54f0d74a69b328a2fc90ec4feb85f728677419b879"
+SRC_URI[sha256sum] = "7703c4e9d2200b4854a31800c1dbd4587e1fa86e75f58795c740bcfa7eca7eaa"
 
 PYPI_PACKAGE = "SCons"
 
-- 
2.25.1



  parent reply	other threads:[~2022-08-03  8:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03  8:44 [OE-core] [PATCH] python3-jsonschema: upgrade 4.7.2 -> 4.9.0 Wang Mingyu
2022-08-03  8:44 ` [OE-core] [PATCH] python3-pip: upgrade 22.1.2 -> 22.2.1 Wang Mingyu
2022-08-03  9:08   ` Alexander Kanavin
2022-08-03  8:44 ` Wang Mingyu [this message]
2022-08-03  8:44 ` [OE-core] [PATCH] python3-setuptools: upgrade 63.2.0 -> 63.3.0 Wang Mingyu

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=1659516246-31185-3-git-send-email-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