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] python3-cryptography-vectors: upgrade 41.0.1 -> 41.0.2
Date: Mon, 17 Jul 2023 17:10:17 +0800	[thread overview]
Message-ID: <1689585025-23731-11-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1689585025-23731-1-git-send-email-wangmy@fujitsu.com>

From: Wang Mingyu <wangmy@fujitsu.com>

Changelog:
==========
-Fixed bugs in creating and parsing SSH certificates where critical options
 with values were handled incorrectly. Certificates are now created correctly
 and parsing accepts correct values as well as the previously generated
 invalid forms with a warning. In the next release, support for parsing these
 invalid forms will be removed.

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

diff --git a/meta/recipes-devtools/python/python3-cryptography-vectors_41.0.1.bb b/meta/recipes-devtools/python/python3-cryptography-vectors_41.0.2.bb
similarity index 91%
rename from meta/recipes-devtools/python/python3-cryptography-vectors_41.0.1.bb
rename to meta/recipes-devtools/python/python3-cryptography-vectors_41.0.2.bb
index 016620e710..52f2c35315 100644
--- a/meta/recipes-devtools/python/python3-cryptography-vectors_41.0.1.bb
+++ b/meta/recipes-devtools/python/python3-cryptography-vectors_41.0.2.bb
@@ -9,7 +9,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=8c3617db4fb6fae01f1d253ab91511e4 \
 # NOTE: Make sure to keep this recipe at the same version as python3-cryptography
 #       Upgrade both recipes at the same time
 
-SRC_URI[sha256sum] = "23b08c39777ec7b2774a11f945d1746301b1e88ecff2e5326d7f50ea0f42d580"
+SRC_URI[sha256sum] = "028dff94a8522ca818b11295ff12df55f348f33a193c0597ddfe8239e53d1582"
 
 PYPI_PACKAGE = "cryptography_vectors"
 
-- 
2.34.1



  parent reply	other threads:[~2023-07-17  9:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17  9:10 [OE-core] [PATCH] harfbuzz: upgrade 7.3.0 -> 8.0.1 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] libproxy: upgrade 0.5.2 -> 0.5.3 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] libva: upgrade 2.18.0 -> 2.19.0 wangmy
2023-07-18  6:55   ` Mittal, Anuj
2023-07-17  9:10 ` [OE-core] [PATCH] nghttp2: upgrade 1.54.0 -> 1.55.1 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] debianutils: upgrade 5.7 -> 5.8 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] glib-2.0: upgrade 2.76.3 -> 2.76.4 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] python3-pip: upgrade 23.1.2 -> 23.2 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] python3-zipp: upgrade 3.15.0 -> 3.16.2 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] opkg: upgrade 0.6.1 -> 0.6.2 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] opkg-utils: upgrade 0.5.0 " wangmy
2023-07-17  9:10 ` wangmy [this message]
2023-07-17  9:31   ` [OE-core] [PATCH] python3-cryptography-vectors: upgrade 41.0.1 -> 41.0.2 Tim Orling
2023-07-17  9:10 ` [OE-core] [PATCH] python3-editables: upgrade 0.3 -> 0.4 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] python3-git: upgrade 3.1.31 -> 3.1.32 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] python3-hypothesis: upgrade 6.80.0 -> 6.81.2 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] python3-importlib-metadata: upgrade 6.7.0 -> 6.8.0 wangmy
2023-07-17 10:10   ` Tim Orling
2023-07-17  9:10 ` [OE-core] [PATCH] python3-jsonschema: upgrade 4.17.3 -> 4.18.3 wangmy
2023-07-19 22:50   ` Alexandre Belloni
2023-07-17  9:10 ` [OE-core] [PATCH] python3-numpy: upgrade 1.25.0 -> 1.25.1 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] python3-typing-extensions: upgrade 4.7.0 -> 4.7.1 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] repo: upgrade 2.34.1 -> 2.35 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=1689585025-23731-11-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