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.2.0 -> 21.4.0
Date: Mon, 3 Jan 2022 14:36:01 +0800 [thread overview]
Message-ID: <1641191763-41666-1-git-send-email-wangmy@fujitsu.com> (raw)
Changelog:
=========
Bugs fixed for this release (https://github.com/python-attrs/attrs/pull/####)
Fixed the test suite on PyPy3.8 where cloudpickle does not work. #892
Fixed coverage report for projects that use attrs and don't set a --source. #895, #896
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../python/{python3-attrs_21.2.0.bb => python3-attrs_21.4.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-attrs_21.2.0.bb => python3-attrs_21.4.0.bb} (82%)
diff --git a/meta/recipes-devtools/python/python3-attrs_21.2.0.bb b/meta/recipes-devtools/python/python3-attrs_21.4.0.bb
similarity index 82%
rename from meta/recipes-devtools/python/python3-attrs_21.2.0.bb
rename to meta/recipes-devtools/python/python3-attrs_21.4.0.bb
index d52237f267..d1dde29d37 100644
--- a/meta/recipes-devtools/python/python3-attrs_21.2.0.bb
+++ b/meta/recipes-devtools/python/python3-attrs_21.4.0.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "http://www.attrs.org/"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=d4ab25949a73fe7d4fdee93bcbdbf8ff"
-SRC_URI[sha256sum] = "ef6aaac3ca6cd92904cdd0d83f629a15f18053ec84e6432106f7a4d04ae4f5fb"
+SRC_URI[sha256sum] = "626ba8234211db98e869df76230a137c4c40a12d72445c45d5f5b716f076e2fd"
inherit pypi setuptools3
--
2.25.1
next reply other threads:[~2022-01-03 6:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 6:36 Wang Mingyu [this message]
2022-01-03 6:36 ` [OE-core] [PATCH] python3-setuptools: upgrade 59.5.0 -> 60.2.0 Wang Mingyu
2022-01-03 6:36 ` [OE-core] [PATCH] python3-zipp: upgrade 3.6.0 -> 3.7.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=1641191763-41666-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