From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: "Yu, Mingli" <mingli.yu@eng.windriver.com>,
tim.orling@konsulko.com, Ross Burton <ross.burton@arm.com>,
openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-python][kirkstone][PATCH 2/3] python3-pyyaml-include: switch to pytest --automake
Date: Tue, 30 Apr 2024 16:05:43 +0800 [thread overview]
Message-ID: <ef4e1549-d7be-48f1-a2e5-03bdf25464fb@windriver.com> (raw)
In-Reply-To: <CA+chaQe=-D2t+T9j9=cppJLJZufhKuTiUuqDH0eC6+aCsbdt-w@mail.gmail.com>
On 4/30/24 15:45, Martin Jansa wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Tue, Apr 30, 2024 at 9:28 AM Yu, Mingli <mingli.yu@windriver.com> wrote:
>>
>>
>>
>> On 4/30/24 15:16, Martin Jansa wrote:
>>> CAUTION: This email comes from a non Wind River email account!
>>> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>>>
>>> On Wed, Mar 27, 2024 at 8:16 AM Yu, Mingli <mingli.yu@eng.windriver.com> wrote:
>>>>
>>>> From: Tim Orling <ticotimo@gmail.com>
>>>>
>>>> * Also replace ${PYTHON_PN} with python3
>>>>
>>>> Signed-off-by: Tim Orling <tim.orling@konsulko.com>
>>>> Signed-off-by: Khem Raj <raj.khem@gmail.com>
>>>> (cherry picked from commit 182f31a182f6572a3538b875cec7ee761e2da1e6)
>>>> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
>>> ...
>>>> diff --git a/meta-python/recipes-devtools/python/python3-pyyaml-include_1.3.2.bb b/meta-python/recipes-devtools/python/python3-pyyaml-include_1.3.2.bb
>>>> index 9bfaa2194..3a5bd99a7 100644
>>>> --- a/meta-python/recipes-devtools/python/python3-pyyaml-include_1.3.2.bb
>>>> +++ b/meta-python/recipes-devtools/python/python3-pyyaml-include_1.3.2.bb
>>>> @@ -2,7 +2,7 @@ SUMMARY = "Extending PyYAML with a custom constructor for including YAML files w
>>>> HOMEPAGE = "https://github.com/tanbro/pyyaml-include"
>>>> LICENSE = "GPL-3.0-only"
>>>> LIC_FILES_CHKSUM = "file://LICENSE;md5=d32239bcb673463ab874e80d47fae504"
>>>> -DEPENDS += "${PYTHON_PN}-setuptools-scm-native"
>>>> +DEPENDS += "python3-setuptools-scm-native"
>>>> SRCREV = "36b6975aa8fc7a6cbf37de40aa2ed6d996b2f7be"
>>>>
>>>> SRC_URI = " \
>>>> @@ -20,9 +20,10 @@ do_install_ptest() {
>>>> }
>>>>
>>>> RDEPENDS:${PN} += " \
>>>> - ${PYTHON_PN}-pyyaml \
>>>> + python3-pyyaml \
>>>> "
>>>> RDEPENDS:${PN}-ptest += " \
>>>> - ${PYTHON_PN}-pytest \
>>>> + python3-pytest \
>>>> + python3-unittest-automake-output \
>>>> "
>>>
>>> This was now merged to meta-oe kirkstone, but the
>>> python3-unittest-automake-output isn't available in oe-core kirkstone,
>>> causing:
>>> ERROR: Nothing RPROVIDES 'python3-unittest-automake-output' (but
>>> meta-oe/meta-python/recipes-devtools/python/python3-pyyaml-include_1.4.1.bb
>>> RDEPENDS on or otherwise requires it)
>>>
>>> python3-unittest-automake-output was added to oe-core in mickledore:
>>>
>>> openembedded-core $ git log --oneline --
>>> ./meta/recipes-devtools/python/python3-unittest-automake-output_0.1.bb
>>> db0e82135c python3-unittest-automake-output: upgrade to 0.2
>>> 961e4f3fc7 python3-unittest-automake-output: add new recipe for ptest
>>> integration
>>>
>>> Please revert this (if the newer python3-pyyaml-include works without
>>> this change) or add python3-unittest-automake-output to kirkstone as
>>> well.
>>
>> The python3-pyyaml-include did works without
>> python3-unittest-automake-output, but the python3-pyyaml-include ptest
>> needs python3-unittest-automake-output and I also sent the patch to
>> oe-core(kirkstone)[1].
>>
>> [1]
>> https://lore.kernel.org/all/20240327072236.2221619-1-mingli.yu@windriver.com/T/#mda91919809cf156aba24f099bef65142067cd318
>
> [1] was rejected by Steve, so what's the plan now?
Is it okay to add python3-unittest-automake-output in
meta-openembedded/meta-python(kirkstone)? If okay, I will send the patch
then.
Thanks,
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#110193): https://lists.openembedded.org/g/openembedded-devel/message/110193
> Mute This Topic: https://lists.openembedded.org/mt/105173183/3618448
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [mingli.yu@eng.windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2024-04-30 8:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 7:16 [meta-python][kirkstone][PATCH 1/3] python3-pyyaml-include: add initial recipe for version 1.3.2 mingli.yu
2024-03-27 7:16 ` [meta-python][kirkstone][PATCH 2/3] python3-pyyaml-include: switch to pytest --automake mingli.yu
2024-04-30 7:16 ` [oe] " Martin Jansa
2024-04-30 7:28 ` Yu, Mingli
2024-04-30 7:45 ` Martin Jansa
2024-04-30 8:05 ` Yu, Mingli [this message]
2024-04-30 8:53 ` [meta-python][kirkstone][PATCH] python3-pyyaml-include: Drop " mingli.yu
[not found] ` <17CB02D3AC5ADA82.26557@lists.openembedded.org>
2024-05-16 3:37 ` [oe] " Yu, Mingli
2024-03-27 7:16 ` [meta-python][kirkstone][PATCH 3/3] python3-pyyaml-include: Upgrade 1.3.2 -> 1.4.1 mingli.yu
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=ef4e1549-d7be-48f1-a2e5-03bdf25464fb@windriver.com \
--to=mingli.yu@windriver.com \
--cc=martin.jansa@gmail.com \
--cc=mingli.yu@eng.windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=ross.burton@arm.com \
--cc=tim.orling@konsulko.com \
/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.