diff options
| author |   Nicolas Dechesne <nicolas.dechesne@linaro.org> | 2021-07-20 18:30:51 +0200 |
|---|---|---|
| committer |   Armin Kuster <akuster808@gmail.com> | 2021-07-25 13:36:16 -0700 |
| commit | d34d040fdaf199cee2a956b09a448aa8d9aa8fe9 (patch) | |
| tree | af806fd4788c52c7df685cd6f33be5bc3ed92766 /meta-networking/recipes-support | |
| parent | 8bdc78483115e12943f0946c8e863d4a70ef7168 (diff) | |
| download | meta-openembedded-d34d040fdaf199cee2a956b09a448aa8d9aa8fe9.tar.gz | |
python3-{pyyaml,cython,pyparsing}: move from meta-python to meta-oe
This specific statement in ostree recipe breaks the YP compatible
status (yocto-check-layer):
RDEPENDS_${PN}-ptest += " \
...
${@bb.utils.contains('BBFILE_COLLECTIONS', 'meta-python', 'python3-pyyaml', '', d)} \
...
"
Recently python3-pyyaml was moved to OE-core (0a8600f9cec0), and the
ostree recipe was fixed with:
b9ede0cb182a (python3-pyyaml: Do not check for meta-python)
In dunfell, moving python3-pyyaml to OE-core is not a great idea, but
moving it from meta-python to meta-oe allows us to fix ostree YP
compatible issue. Since meta-python depends on meta-oe, it should not
be a change with any visible effect.
python3-cython and python3-pyparsing are collateral damages since they are
dependency for python3-pyyaml, so needed to be moved too.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Diffstat (limited to 'meta-networking/recipes-support')
0 files changed, 0 insertions, 0 deletions