From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] python3-pytest-runner: upgrade 5.3.1 -> 6.0.0
Date: Tue, 29 Mar 2022 09:18:24 +0800 [thread overview]
Message-ID: <1648516704-21148-1-git-send-email-wangmy@fujitsu.com> (raw)
Add dependency python3-distutils.
Changelog:
=========
- #49: Dropped workaround for older setuptools versions.
- Require Python 3.7.
- #58: Fixed syntax issue in changelog.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
...-pytest-runner_5.3.1.bb => python3-pytest-runner_6.0.0.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/python/{python3-pytest-runner_5.3.1.bb => python3-pytest-runner_6.0.0.bb} (75%)
diff --git a/meta/recipes-devtools/python/python3-pytest-runner_5.3.1.bb b/meta/recipes-devtools/python/python3-pytest-runner_6.0.0.bb
similarity index 75%
rename from meta/recipes-devtools/python/python3-pytest-runner_5.3.1.bb
rename to meta/recipes-devtools/python/python3-pytest-runner_6.0.0.bb
index 1020b2be26..f7a2c1bb95 100644
--- a/meta/recipes-devtools/python/python3-pytest-runner_5.3.1.bb
+++ b/meta/recipes-devtools/python/python3-pytest-runner_6.0.0.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "https://pypi.org/project/pytest-runner/"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=7a7126e068206290f3fe9f8d6c713ea6"
-SRC_URI[sha256sum] = "0fce5b8dc68760f353979d99fdd6b3ad46330b6b1837e2077a89ebcf204aac91"
+SRC_URI[sha256sum] = "b4d85362ed29b4c348678de797df438f0f0509497ddb8c647096c02a6d87b685"
inherit pypi python_setuptools_build_meta
@@ -11,6 +11,6 @@ DEPENDS += " \
${PYTHON_PN}-setuptools-scm-native"
RDEPENDS:${PN} = "${PYTHON_PN}-py ${PYTHON_PN}-setuptools ${PYTHON_PN}-debugger ${PYTHON_PN}-json \
- ${PYTHON_PN}-io"
+ ${PYTHON_PN}-io ${PYTHON_PN}-distutils"
BBCLASSEXTEND = "native nativesdk"
--
2.25.1
reply other threads:[~2022-03-29 1:18 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=1648516704-21148-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