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: upgrade 7.1.2 -> 7.1.3
Date: Mon, 5 Sep 2022 17:06:21 +0800	[thread overview]
Message-ID: <1662368782-32326-3-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1662368782-32326-1-git-send-email-wangmy@fujitsu.com>

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

diff --git a/meta/recipes-devtools/python/python3-pytest_7.1.2.bb b/meta/recipes-devtools/python/python3-pytest_7.1.3.bb
similarity index 93%
rename from meta/recipes-devtools/python/python3-pytest_7.1.2.bb
rename to meta/recipes-devtools/python/python3-pytest_7.1.3.bb
index c642d9a232..373f7f35fa 100644
--- a/meta/recipes-devtools/python/python3-pytest_7.1.2.bb
+++ b/meta/recipes-devtools/python/python3-pytest_7.1.3.bb
@@ -5,7 +5,7 @@ DESCRIPTION = "The pytest framework makes it easy to write small tests, yet scal
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=bd27e41b6550fe0fc45356d1d81ee37c"
 
-SRC_URI[sha256sum] = "a06a0425453864a270bc45e71f783330a7428defb4230fb5e6a731fde06ecd45"
+SRC_URI[sha256sum] = "4f365fec2dff9c1162f834d9f18af1ba13062db0c708bf7b946f8a5c76180c39"
 
 DEPENDS += "python3-setuptools-scm-native"
 
-- 
2.25.1



  parent reply	other threads:[~2022-09-05  9:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05  9:06 [OE-core] [PATCH] python3-mako: upgrade 1.2.1 -> 1.2.2 Wang Mingyu
2022-09-05  9:06 ` [OE-core] [PATCH] python3-pathspec: upgrade 0.9.0 -> 0.10.1 Wang Mingyu
2022-09-05  9:06 ` Wang Mingyu [this message]
2022-09-05  9:06 ` [OE-core] [PATCH] vala: upgrade 0.56.2 -> 0.56.3 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=1662368782-32326-3-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