public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 2/3] meta: Set LAYERSERIES_* variables
Date: Wed, 7 Nov 2018 17:20:11 +0100	[thread overview]
Message-ID: <0a15ced9-20ff-2fc8-b2c1-b87829ede99f@siemens.com> (raw)
In-Reply-To: <20181107160955.23426-3-mosipov@ilbers.de>

On 07.11.18 17:09, Maxim Yu. Osipov wrote:
> Fix warnings after update to the latest bitbake.
> 
> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
> ---
>   meta-isar/conf/layer.conf | 1 +
>   meta/conf/layer.conf      | 5 ++++-
>   2 files changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/meta-isar/conf/layer.conf b/meta-isar/conf/layer.conf
> index 4aa1cf1..b4b90c1 100644
> --- a/meta-isar/conf/layer.conf
> +++ b/meta-isar/conf/layer.conf
> @@ -14,6 +14,7 @@ BBFILE_PRIORITY_isar = "5"
>   # This should only be incremented on significant changes that will
>   # cause compatibility issues with other layers
>   LAYERVERSION_isar = "3"
> +LAYERSERIES_COMPAT_isar = "sumo"
>   
>   LAYERDIR_isar = "${LAYERDIR}"
>   
> diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
> index ab6ae8e..6fefca6 100644
> --- a/meta/conf/layer.conf
> +++ b/meta/conf/layer.conf
> @@ -11,8 +11,11 @@ BBFILE_COLLECTIONS += "core"
>   BBFILE_PATTERN_core = "^${LAYERDIR}/"
>   BBFILE_PRIORITY_core = "5"
>   
> +LAYERSERIES_CORENAMES = "sumo"
> +
>   # This should only be incremented on significant changes that will
>   # cause compatibility issues with other layers
> -LAYERVERSION_core = "1"
> +LAYERVERSION_core = "11"
> +LAYERSERIES_COMPAT_core = "sumo"
>   
>   LAYERDIR_core = "${LAYERDIR}"
> 

That looks... weird. Does bitbake now actually have Yocto release names encoded???

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-11-07 16:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 16:09 [PATCH 0/3] bitbake upstream update and eliminate no-gpg-check option usage Maxim Yu. Osipov
2018-11-07 16:09 ` [PATCH 1/3] Update bitbake from the upstream Maxim Yu. Osipov
2018-11-07 17:58   ` Henning Schild
2018-11-08  9:08     ` Maxim Yu. Osipov
2018-11-07 16:09 ` [PATCH 2/3] meta: Set LAYERSERIES_* variables Maxim Yu. Osipov
2018-11-07 16:20   ` Jan Kiszka [this message]
2018-11-07 16:39     ` Maxim Yu. Osipov
2018-11-07 16:41       ` Jan Kiszka
2018-11-07 17:24         ` Maxim Yu. Osipov
2018-11-07 17:26           ` Jan Kiszka
2018-11-07 16:09 ` [PATCH 3/3] isar-bootstrap: Eliminate no-gpg-check option usage Maxim Yu. Osipov
2018-11-07 17:38   ` Henning Schild
2018-11-08  7:57     ` Maxim Yu. Osipov
2018-11-12  9:30   ` Maxim Yu. Osipov
2018-11-27  9:43   ` Henning Schild
2018-11-27 10:15     ` Maxim Yu. Osipov
2018-12-03 11:49   ` Maxim Yu. Osipov
2018-12-03 12:52     ` Jan Kiszka

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=0a15ced9-20ff-2fc8-b2c1-b87829ede99f@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=mosipov@ilbers.de \
    /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