public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: wangmy@fujitsu.com
To: openembedded-core@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH 15/22] python3-idna: upgrade 3.7 -> 3.8
Date: Tue,  3 Sep 2024 16:32:52 +0800	[thread overview]
Message-ID: <1725352379-20334-15-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1725352379-20334-1-git-send-email-wangmy@fujitsu.com>

From: Wang Mingyu <wangmy@fujitsu.com>

Changelog:
==========
- Fix regression where IDNAError exception was not being produced for certain inputs.
- Add support for Python 3.13, drop support for Python 3.5 as it is no longer testable.
- Documentation improvements
- Updates to package testing using Github actions

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

diff --git a/meta/recipes-devtools/python/python3-idna_3.7.bb b/meta/recipes-devtools/python/python3-idna_3.8.bb
similarity index 84%
rename from meta/recipes-devtools/python/python3-idna_3.7.bb
rename to meta/recipes-devtools/python/python3-idna_3.8.bb
index 713e803d03..95c3c8cc44 100644
--- a/meta/recipes-devtools/python/python3-idna_3.7.bb
+++ b/meta/recipes-devtools/python/python3-idna_3.8.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "https://github.com/kjd/idna"
 LICENSE = "BSD-3-Clause & Python-2.0 & Unicode-TOU"
 LIC_FILES_CHKSUM = "file://LICENSE.md;md5=204c0612e40a4dd46012a78d02c80fb1"
 
-SRC_URI[sha256sum] = "028ff3aadf0609c1fd278d8ea3089299412a7a8b9bd005dd08b9f8285bcb5cfc"
+SRC_URI[sha256sum] = "d838c2c0ed6fced7693d5e8ab8e734d5f8fda53a039c0164afb0b82e771e3603"
 
 SRC_URI += "file://run-ptest"
 
-- 
2.34.1



  parent reply	other threads:[~2024-09-03  8:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03  8:32 [OE-core] [PATCH 01/22] acpica: upgrade 20240322 -> 20240827 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 02/22] cairo: upgrade 1.18.0 -> 1.18.2 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 03/22] dhcpcd: upgrade 10.0.8 -> 10.0.10 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 04/22] diffoscope: upgrade 276 -> 277 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 05/22] ell: upgrade 0.67 -> 0.68 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 06/22] json-glib: upgrade 1.8.0 -> 1.10.0 wangmy
2024-09-03 21:51   ` Richard Purdie
2024-09-04  1:25     ` Mingyu Wang (Fujitsu)
2024-09-04  7:49       ` Richard Purdie
2024-09-11  0:57         ` Mingyu Wang (Fujitsu)
2024-09-11 10:21           ` Alexander Kanavin
2024-09-04  2:21   ` Yi Zhao
2024-09-03  8:32 ` [OE-core] [PATCH 07/22] libdrm: upgrade 2.4.122 -> 2.4.123 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 08/22] libsoup: upgrade 3.4.4 -> 3.6.0 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 09/22] liburcu: upgrade 0.14.0 -> 0.14.1 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 10/22] lttng-tools: upgrade 2.13.13 -> 2.13.14 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 11/22] mc: upgrade 4.8.31 -> 4.8.32 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 12/22] nghttp2: upgrade 1.62.1 -> 1.63.0 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 13/22] ofono: upgrade 2.9 -> 2.10 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 14/22] python3-certifi: upgrade 2024.7.4 -> 2024.8.30 wangmy
2024-09-03  8:32 ` wangmy [this message]
2024-09-03  8:32 ` [OE-core] [PATCH 16/22] python3-maturin: upgrade 1.7.0 -> 1.7.1 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 17/22] python3-pbr: upgrade 6.0.0 -> 6.1.0 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 18/22] python3-websockets: upgrade 12.0 -> 13.0.1 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 19/22] python3-zipp: upgrade 3.20.0 -> 3.20.1 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 20/22] taglib: upgrade 2.0.1 -> 2.0.2 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 21/22] wayland-protocols: upgrade 1.36 -> 1.37 wangmy
2024-09-03  8:32 ` [OE-core] [PATCH 22/22] wayland: upgrade 1.23.0 -> 1.23.1 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=1725352379-20334-15-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