From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] python3-attrs: upgrade 21.4.0 -> 22.1.0
Date: Wed, 3 Aug 2022 16:40:27 +0800 [thread overview]
Message-ID: <1659516030-31123-1-git-send-email-wangmy@fujitsu.com> (raw)
License-Update: add "and the attrs contributors" to Copyright
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../{python3-attrs_21.4.0.bb => python3-attrs_22.1.0.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/python/{python3-attrs_21.4.0.bb => python3-attrs_22.1.0.bb} (68%)
diff --git a/meta/recipes-devtools/python/python3-attrs_21.4.0.bb b/meta/recipes-devtools/python/python3-attrs_22.1.0.bb
similarity index 68%
rename from meta/recipes-devtools/python/python3-attrs_21.4.0.bb
rename to meta/recipes-devtools/python/python3-attrs_22.1.0.bb
index 1839ce6245..ba07ac71e3 100644
--- a/meta/recipes-devtools/python/python3-attrs_21.4.0.bb
+++ b/meta/recipes-devtools/python/python3-attrs_22.1.0.bb
@@ -1,9 +1,9 @@
DESCRIPTION = "Classes Without Boilerplate"
HOMEPAGE = "http://www.attrs.org/"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=d4ab25949a73fe7d4fdee93bcbdbf8ff"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=5e55731824cf9205cfabeab9a0600887"
-SRC_URI[sha256sum] = "626ba8234211db98e869df76230a137c4c40a12d72445c45d5f5b716f076e2fd"
+SRC_URI[sha256sum] = "29adc2665447e5191d0e7c568fde78b21f9672d344281d0c6e1ab085429b22b6"
inherit pypi python_setuptools_build_meta
--
2.25.1
next reply other threads:[~2022-08-03 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 8:40 Wang Mingyu [this message]
2022-08-03 8:40 ` [OE-core] [PATCH] python3-cython: upgrade 0.29.30 -> 0.29.32 Wang Mingyu
2022-08-03 8:40 ` [OE-core] [PATCH] python3-dbusmock: upgrade 0.28.1 -> 0.28.4 Wang Mingyu
2022-08-03 8:40 ` [OE-core] [PATCH] python3-hatchling: upgrade 1.5.0 -> 1.6.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=1659516030-31123-1-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