On Thu, 2020-05-21 at 10:34 -0500, Joshua Watt wrote:
> The commits 910ffaf5be ("pyelftools: Import from meta-python") and
> a96f815c53 ("pycryptodome: Import from meta-python") moved recipes
> from
> meta-python to oe-core. In order for this to be communicated with
> users,
> bump the LAYERVERSION so that meta-python can key of it in its
> LAYERDEPENDS.
> 
> Signed-off-by: Joshua Watt <jpewhac...@gmail.com>
> ---
>  meta/conf/layer.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
> index da93d64e0a..098ef12ac6 100644
> --- a/meta/conf/layer.conf
> +++ b/meta/conf/layer.conf
> @@ -11,7 +11,7 @@ LAYERSERIES_CORENAMES = "dunfell gatesgarth"
>  
>  # This should only be incremented on significant changes that will
>  # cause compatibility issues with other layers
> -LAYERVERSION_core = "11"
> +LAYERVERSION_core = "12"
>  LAYERSERIES_COMPAT_core = "gatesgarth"

I'm trying to work out if/where this helps. It can certainly help the
case where meta-oe is updated and core isn't as you can get an error.
Where you perhaps don't get one is where you update core but not meta-
oe.

Its almost as if you want core to error if meta-oe is too old too.

Cheers,

Richard



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#138544): 
https://lists.openembedded.org/g/openembedded-core/message/138544
Mute This Topic: https://lists.openembedded.org/mt/74378015/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to