public inbox for openembedded-core@lists.openembedded.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-pytest-subtests: upgrade 0.6.0 -> 0.7.0
Date: Tue, 29 Mar 2022 09:26:55 +0800	[thread overview]
Message-ID: <1648517215-21272-1-git-send-email-wangmy@fujitsu.com> (raw)

Changelog:
=========
Fixed support for pytest 7.0, and pytest>=7.0 is now required.

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 ...ytest-subtests_0.6.0.bb => python3-pytest-subtests_0.7.0.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-pytest-subtests_0.6.0.bb => python3-pytest-subtests_0.7.0.bb} (86%)

diff --git a/meta/recipes-devtools/python/python3-pytest-subtests_0.6.0.bb b/meta/recipes-devtools/python/python3-pytest-subtests_0.7.0.bb
similarity index 86%
rename from meta/recipes-devtools/python/python3-pytest-subtests_0.6.0.bb
rename to meta/recipes-devtools/python/python3-pytest-subtests_0.7.0.bb
index 5e4847b8d9..060a6ff6cf 100644
--- a/meta/recipes-devtools/python/python3-pytest-subtests_0.6.0.bb
+++ b/meta/recipes-devtools/python/python3-pytest-subtests_0.7.0.bb
@@ -7,7 +7,7 @@ BUGTRACKER = "https://github.com/pytest-dev/pytest-subtests/issues"
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=242b4e17fa287dcf7aef372f6bc3dcb1"
 
-SRC_URI[sha256sum] = "3ebd306a8dcf75133f1742f288c82f36426ebcf8a132d4ee89782d20e84fc13a"
+SRC_URI[sha256sum] = "95c44c77e3fbede9848bb88ca90b384815fcba8090ef9a9f55659ab163b1681c"
 
 inherit pypi setuptools3
 
-- 
2.25.1



                 reply	other threads:[~2022-03-29  1:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1648517215-21272-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox