From: "Nicolas Dechesne" <nicolas.dechesne@linaro.org>
To: akuster808@gmail.com, openembedded-devel@lists.openembedded.org
Cc: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Subject: [PATCH 0/5] Various fixes for YP compatible
Date: Tue, 20 Jul 2021 18:30:47 +0200 [thread overview]
Message-ID: <20210720163052.11295-1-nicolas.dechesne@linaro.org> (raw)
There are some pending requests for YP compatible for layers which
depend on meta-oe, meta-python and meta-networking. In dunfell, these
layers do not PASS the yocto-check-layer compatibility script. With
these patches applied, I am able to get this:
INFO: Summary of results:
INFO:
INFO: meta-networking ... PASS
INFO: meta-python ... PASS
INFO: meta-oe ... PASS
Khem Raj (1):
libdevmapper,lvm2: Do not inherit license
Nicolas Dechesne (4):
python3-markupsafe: remove recipe
python3-jinja2: remove recipe
python3-{pyyaml,cython,pyparsing}: move from meta-python to meta-oe
ostree: Do not check for meta-python
.../recipes-devtools/python/python-cython.inc | 0
.../python/python3-cython_0.29.14.bb | 0
.../python/python3-pyparsing_2.4.6.bb | 0
.../python/python3-pyyaml_5.3.1.bb | 0
.../recipes-extended/ostree/ostree_2020.3.bb | 2 +-
meta-oe/recipes-support/lvm2/lvm2.inc | 5 +--
.../python/python3-jinja2/run-ptest | 3 --
.../python/python3-jinja2_2.11.2.bb | 43 -------------------
.../python/python3-markupsafe/run-ptest | 3 --
.../python/python3-markupsafe_1.1.1.bb | 2 -
10 files changed, 3 insertions(+), 55 deletions(-)
rename {meta-python => meta-oe}/recipes-devtools/python/python-cython.inc (100%)
rename {meta-python => meta-oe}/recipes-devtools/python/python3-cython_0.29.14.bb (100%)
rename {meta-python => meta-oe}/recipes-devtools/python/python3-pyparsing_2.4.6.bb (100%)
rename {meta-python => meta-oe}/recipes-devtools/python/python3-pyyaml_5.3.1.bb (100%)
delete mode 100644 meta-python/recipes-devtools/python/python3-jinja2/run-ptest
delete mode 100644 meta-python/recipes-devtools/python/python3-jinja2_2.11.2.bb
delete mode 100644 meta-python/recipes-devtools/python/python3-markupsafe/run-ptest
delete mode 100644 meta-python/recipes-devtools/python/python3-markupsafe_1.1.1.bb
--
2.29.2
next reply other threads:[~2021-07-20 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 16:30 Nicolas Dechesne [this message]
2021-07-20 16:30 ` [PATCH 1/5] libdevmapper,lvm2: Do not inherit license Nicolas Dechesne
2021-07-20 16:30 ` [PATCH 2/5] python3-markupsafe: remove recipe Nicolas Dechesne
2021-07-20 16:30 ` [PATCH 3/5] python3-jinja2: " Nicolas Dechesne
2021-07-20 16:30 ` [PATCH 4/5] python3-{pyyaml,cython,pyparsing}: move from meta-python to meta-oe Nicolas Dechesne
2021-07-20 16:30 ` [PATCH 5/5] ostree: Do not check for meta-python Nicolas Dechesne
2021-07-20 16:32 ` [PATCH 0/5] Various fixes for YP compatible Nicolas Dechesne
2021-07-25 22:40 ` Armin Kuster
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=20210720163052.11295-1-nicolas.dechesne@linaro.org \
--to=nicolas.dechesne@linaro.org \
--cc=akuster808@gmail.com \
--cc=openembedded-devel@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 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.