From: chee.yang.lee@intel.com
To: openembedded-core@lists.openembedded.org
Subject: [kirkstone][PATCH 6/7] python3-urllib3: upgrade 1.26.14 -> 1.26.15
Date: Fri, 13 Oct 2023 19:09:40 +0800 [thread overview]
Message-ID: <20231013110941.2223228-6-chee.yang.lee@intel.com> (raw)
In-Reply-To: <20231013110941.2223228-1-chee.yang.lee@intel.com>
From: Wang Mingyu <wangmy@fujitsu.com>
Changelog:
==========
* Fix socket timeout value when "HTTPConnection" is reused ('#2645 <https://github.com/urllib3/urllib3/issues/2645>'__)
* Remove "!" character from the unreserved characters in IPv6 Zone ID parsing
('#2899 <https://github.com/urllib3/urllib3/issues/2899>'__)
* Fix IDNA handling of '\x80' byte ('#2901 <https://github.com/urllib3/urllib3/issues/2901>'__)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 8e062efbac29a81831c3060bcae601dc533d65dd)
Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com>
---
.../{python3-urllib3_1.26.14.bb => python3-urllib3_1.26.15.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-urllib3_1.26.14.bb => python3-urllib3_1.26.15.bb} (86%)
diff --git a/meta/recipes-devtools/python/python3-urllib3_1.26.14.bb b/meta/recipes-devtools/python/python3-urllib3_1.26.15.bb
similarity index 86%
rename from meta/recipes-devtools/python/python3-urllib3_1.26.14.bb
rename to meta/recipes-devtools/python/python3-urllib3_1.26.15.bb
index f35a141df26..d2de7c4c022 100644
--- a/meta/recipes-devtools/python/python3-urllib3_1.26.14.bb
+++ b/meta/recipes-devtools/python/python3-urllib3_1.26.15.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "https://github.com/shazow/urllib3"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=c2823cb995439c984fd62a973d79815c"
-SRC_URI[sha256sum] = "076907bf8fd355cde77728471316625a4d2f7e713c125f51953bb5b3eecf4f72"
+SRC_URI[sha256sum] = "8a388717b9476f934a21484e8c8e61875ab60644d29b9b39e11e4b9dc1c6b305"
inherit pypi setuptools3
--
2.37.3
next prev parent reply other threads:[~2023-10-13 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 11:09 [kirkstone][PATCH 1/7] python3-urllib3: upgrade 1.26.9 -> 1.26.10 chee.yang.lee
2023-10-13 11:09 ` [kirkstone][PATCH 2/7] python3-urllib3: upgrade 1.26.10 -> 1.26.11 chee.yang.lee
2023-10-13 11:09 ` [kirkstone][PATCH 3/7] python3-urllib3: upgrade 1.26.11 -> 1.26.12 chee.yang.lee
2023-10-13 11:09 ` [kirkstone][PATCH 4/7] python3-urllib3: upgrade 1.26.12 -> 1.26.13 chee.yang.lee
2023-10-13 11:09 ` [kirkstone][PATCH 5/7] python3-urllib3: upgrade 1.26.13 -> 1.26.14 chee.yang.lee
2023-10-13 11:09 ` chee.yang.lee [this message]
2023-10-13 11:09 ` [kirkstone][PATCH 7/7] python3-urllib3: 1.26.15 -> 1.26.17 chee.yang.lee
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=20231013110941.2223228-6-chee.yang.lee@intel.com \
--to=chee.yang.lee@intel.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 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.