From: wangmy@fujitsu.com
To: openembedded-devel@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [oe] [meta-python] [PATCH] python3-coverage: upgrade 7.2.6 -> 7.2.7
Date: Wed, 31 May 2023 15:40:07 +0800 [thread overview]
Message-ID: <1685518820-20028-9-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1685518820-20028-1-git-send-email-wangmy@fujitsu.com>
From: Wang Mingyu <wangmy@fujitsu.com>
Changelog:
=========
- Fix: reverted a change from 6.4.3 that helped Cython, but also increased the
size of data files when using dynamic contexts, as described in the now-fixed
issue 1586. The problem is now avoided due to a recent change (issue 1538).
- Wheels are now provided for CPython 3.12.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../{python3-coverage_7.2.6.bb => python3-coverage_7.2.7.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-coverage_7.2.6.bb => python3-coverage_7.2.7.bb} (84%)
diff --git a/meta-python/recipes-devtools/python/python3-coverage_7.2.6.bb b/meta-python/recipes-devtools/python/python3-coverage_7.2.7.bb
similarity index 84%
rename from meta-python/recipes-devtools/python/python3-coverage_7.2.6.bb
rename to meta-python/recipes-devtools/python/python3-coverage_7.2.7.bb
index b13384cd2..f625996ba 100644
--- a/meta-python/recipes-devtools/python/python3-coverage_7.2.6.bb
+++ b/meta-python/recipes-devtools/python/python3-coverage_7.2.7.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "https://coverage.readthedocs.io"
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=2ee41112a44fe7014dce33e26468ba93"
-SRC_URI[sha256sum] = "2025f913f2edb0272ef15d00b1f335ff8908c921c8eb2013536fcaf61f5a683d"
+SRC_URI[sha256sum] = "924d94291ca674905fe9481f12294eb11f2d3d3fd1adb20314ba89e94f44ed59"
inherit pypi setuptools3
--
2.34.1
next prev parent reply other threads:[~2023-05-31 7:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 7:39 [oe] [meta-oe] [PATCH] ctags: upgrade 6.0.20230521.0 -> 6.0.20230528.0 wangmy
2023-05-31 7:40 ` [oe] [meta-gnome] [PATCH] eog: upgrade 44.1 -> 44.2 wangmy
2023-05-31 7:40 ` [oe] [meta-gnome] [PATCH] nautilus: " wangmy
2023-05-31 7:40 ` [oe] [meta-gnome] [PATCH] evolution-data-server: upgrade 3.48.1 -> 3.48.2 wangmy
2023-05-31 7:40 ` [oe] [meta-oe] [PATCH] flatbuffers: upgrade 23.1.4 -> 23.3.56 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-asgiref: upgrade 3.7.1 -> 3.7.2 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-bitarray: upgrade 2.7.3 -> 2.7.4 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-cachetools: upgrade 5.3.0 -> 5.3.1 wangmy
2023-05-31 7:40 ` wangmy [this message]
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-croniter: upgrade 1.3.14 -> 1.3.15 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-deprecated: upgrade 1.2.13 -> 1.2.14 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-google-api-python-client: upgrade 2.86.0 -> 2.87.0 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-google-auth: upgrade 2.18.1 -> 2.19.0 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-imageio: upgrade 2.29.0 -> 2.30.0 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-license-expression: upgrade 30.1.0 -> 30.1.1 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-lru-dict: upgrade 1.1.8 -> 1.2.0 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-paramiko: upgrade 3.1.0 -> 3.2.0 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-pint: upgrade 0.21 -> 0.22 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-protobuf: upgrade 4.23.1 -> 4.23.2 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-xlsxwriter: upgrade 3.1.1 -> 3.1.2 wangmy
2023-05-31 7:40 ` [oe] [meta-python] [PATCH] python3-zeroconf: upgrade 0.62.0 -> 0.63.0 wangmy
2023-05-31 7:40 ` [oe] [meta-oe] [PATCH] xterm: upgrade 380 -> 381 wangmy
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=1685518820-20028-9-git-send-email-wangmy@fujitsu.com \
--to=wangmy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).