All of lore.kernel.org
 help / color / mirror / Atom feed
From: XU Huan <xuhuan.fnst@fujitsu.com>
To: <openembedded-devel@lists.openembedded.org>
Cc: Xu Huan <xuhuan.fnst@fujitsu.com>
Subject: [oe] [meta-python] [PATCH] python3-mypy: upgrade 0.960 -> 0.961
Date: Fri, 17 Jun 2022 09:33:30 +0800	[thread overview]
Message-ID: <1655429612-19310-1-git-send-email-xuhuan.fnst@fujitsu.com> (raw)

From: Xu Huan <xuhuan.fnst@fujitsu.com>

Signed-off-by: Xu Huan <xuhuan.fnst@fujitsu.com>
---
 .../python/{python3-mypy_0.960.bb => python3-mypy_0.961.bb}     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta-python/recipes-devtools/python/{python3-mypy_0.960.bb => python3-mypy_0.961.bb} (86%)

diff --git a/meta-python/recipes-devtools/python/python3-mypy_0.960.bb b/meta-python/recipes-devtools/python/python3-mypy_0.961.bb
similarity index 86%
rename from meta-python/recipes-devtools/python/python3-mypy_0.960.bb
rename to meta-python/recipes-devtools/python/python3-mypy_0.961.bb
index 5d99b6468..02f7cce4c 100644
--- a/meta-python/recipes-devtools/python/python3-mypy_0.960.bb
+++ b/meta-python/recipes-devtools/python/python3-mypy_0.961.bb
@@ -7,7 +7,7 @@ PYPI_PACKAGE = "mypy"
 
 inherit pypi python_setuptools_build_meta
 
-SRC_URI[sha256sum] = "d4fccf04c1acf750babd74252e0f2db6bd2ac3aa8fe960797d9f3ef41cf2bfd4"
+SRC_URI[sha256sum] = "f730d56cb924d371c26b8eaddeea3cc07d78ff51c521c6d04899ac6904b75492"
 
 BBCLASSEXTEND = "native"
 
-- 
2.25.1



             reply	other threads:[~2022-06-17  1:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  1:33 XU Huan [this message]
2022-06-17  1:33 ` [oe] [meta-python] [PATCH] python3-pylint: upgrade 2.13.9 -> 2.14.1 XU Huan
2022-06-20  3:54   ` akuster808
2022-06-17  1:33 ` [oe] [meta-python] [PATCH] python3-smbus2: upgrade 0.4.1 -> 0.4.2 XU Huan

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=1655429612-19310-1-git-send-email-xuhuan.fnst@fujitsu.com \
    --to=xuhuan.fnst@fujitsu.com \
    --cc=openembedded-devel@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 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.