All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] python3-jsonschema: upgrade 4.7.2 -> 4.9.0
Date: Wed, 3 Aug 2022 16:44:03 +0800	[thread overview]
Message-ID: <1659516246-31185-1-git-send-email-wangmy@fujitsu.com> (raw)

Changelog:
===========
-Fix relative $ref resolution when the base URI is a URN or other scheme (#544).
-pkgutil.resolve_name is now used to retrieve validators provided on the command
 line. This function is only available on 3.9+, so 3.7 and 3.8 (which are still
 supported) now rely on the pkgutil_resolve_name backport package. Note however
 that the CLI itself is due to be deprecated shortly in favor of check-jsonschema.
-best_match no longer traverses into anyOf and oneOf when all of the errors
 within them seem equally applicable. This should lead to clearer error messages
 in some cases where no branches were matched.

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

diff --git a/meta/recipes-devtools/python/python3-jsonschema_4.7.2.bb b/meta/recipes-devtools/python/python3-jsonschema_4.9.0.bb
similarity index 93%
rename from meta/recipes-devtools/python/python3-jsonschema_4.7.2.bb
rename to meta/recipes-devtools/python/python3-jsonschema_4.9.0.bb
index af728ab2d6..66e0affc64 100644
--- a/meta/recipes-devtools/python/python3-jsonschema_4.7.2.bb
+++ b/meta/recipes-devtools/python/python3-jsonschema_4.9.0.bb
@@ -4,7 +4,7 @@ LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://COPYING;md5=7a60a81c146ec25599a3e1dabb8610a8 \
                     file://json/LICENSE;md5=9d4de43111d33570c8fe49b4cb0e01af"
 
-SRC_URI[sha256sum] = "73764f461d61eb97a057c929368610a134d1d1fffd858acfe88864ee94f1f1d3"
+SRC_URI[sha256sum] = "df10e65c8f3687a48e93d0d348ce0ce5f897b5a28e9bbcbbe8f7c7eaf019e850"
 
 inherit pypi python_hatchling
 
-- 
2.25.1



             reply	other threads:[~2022-08-03  8:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03  8:44 Wang Mingyu [this message]
2022-08-03  8:44 ` [OE-core] [PATCH] python3-pip: upgrade 22.1.2 -> 22.2.1 Wang Mingyu
2022-08-03  9:08   ` Alexander Kanavin
2022-08-03  8:44 ` [OE-core] [PATCH] python3-scons: upgrade 4.3.0 -> 4.4.0 Wang Mingyu
2022-08-03  8:44 ` [OE-core] [PATCH] python3-setuptools: upgrade 63.2.0 -> 63.3.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=1659516246-31185-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 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.