From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Tim Orling <ticotimo@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 00/18] Move python3-pytest to oe-core
Date: Mon, 30 Nov 2020 21:36:57 +0000 [thread overview]
Message-ID: <59e03e67690a8811cca94b2f1cea684da85c2807.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1606536874.git.timothy.t.orling@linux.intel.com>
On Fri, 2020-11-27 at 20:24 -0800, Tim Orling wrote:
> From: Tim Orling <timothy.t.orling@linux.intel.com>
>
> We are increasingly needing pytest in oe-core, so it is time to move it
> from meta-python.
>
> This series first imports the recipes -- as-is -- from meta-python.
> Second, the maintainers.inc is updated to add myself as maintainer for all
> the new recipes.
> Third, the two recipes that have stable updates are updated to their
> latest releases.
> Finally, a fix caught during ptest runs is added for RDEPENDS for
> pytest.
>
> This was built on 'nodistro' with only openembedded-core and tested on
> qemux86-64. All the new recipes that have ptests pass all tests.
That series was an easier one to test and merge :)
Thanks Tim!
Cheers,
Richard
prev parent reply other threads:[~2020-11-30 21:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 4:24 [PATCH 00/18] Move python3-pytest to oe-core Tim Orling
2020-11-28 4:24 ` [PATCH 01/18] python3-atomicwrites: move from meta-python Tim Orling
2020-11-28 4:24 ` [PATCH 02/18] python3-attrs: " Tim Orling
2020-11-28 4:24 ` [PATCH 03/18] python3-iniconfig: " Tim Orling
2020-11-28 4:24 ` [PATCH 04/18] python3-more-itertools: " Tim Orling
2020-11-28 4:24 ` [PATCH 05/18] python3-pathlib2: " Tim Orling
2020-11-28 4:24 ` [PATCH 06/18] python3-toml: " Tim Orling
2020-11-28 4:24 ` [PATCH 07/18] python3-py: " Tim Orling
2020-11-28 4:24 ` [PATCH 08/18] python3-setuptools-scm: " Tim Orling
2020-11-28 4:24 ` [PATCH 09/18] python3-packaging: " Tim Orling
2020-11-28 4:24 ` [PATCH 10/18] python3-wcwidth: " Tim Orling
2020-11-28 4:24 ` [PATCH 11/18] python3-zipp: " Tim Orling
2020-11-28 4:24 ` [PATCH 12/18] python3-importlib-metadata: " Tim Orling
2020-11-28 4:24 ` [PATCH 13/18] python3-pluggy: " Tim Orling
2020-11-28 4:24 ` [PATCH 14/18] python3-pytest: " Tim Orling
2020-11-28 4:24 ` [PATCH 15/18] maintainers.inc: add self for new pytest packages Tim Orling
2020-11-28 4:24 ` [PATCH 16/18] python3-more-itertools: upgrade 8.5.0 -> 8.6.0 Tim Orling
2020-11-28 4:24 ` [PATCH 17/18] python3-importlib-metadata: upgrade 2.0.0 to 3.1.0 Tim Orling
2020-11-28 4:24 ` [PATCH 18/18] python3-pytest: RDEPENDS on python3-toml Tim Orling
2020-11-28 7:31 ` [OE-core] [PATCH 00/18] Move python3-pytest to oe-core Khem Raj
2020-11-30 3:52 ` akuster
2020-11-30 21:36 ` Richard Purdie [this message]
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=59e03e67690a8811cca94b2f1cea684da85c2807.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ticotimo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox