From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Zhihang Wei <wzh@ilbers.de>,
Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] update kas to 5.4
Date: Thu, 2 Jul 2026 17:55:22 +0200 [thread overview]
Message-ID: <91c3413f-17aa-47da-b6fa-f6bf61b2eae7@siemens.com> (raw)
In-Reply-To: <2393d8fe-5a78-4933-a256-37ff2edca5cb@siemens.com>
On 02.07.26 17:29, Jan Kiszka wrote:
> On 01.07.26 11:05, Zhihang Wei wrote:
>> Applied to next, thanks.
>>
>> Zhihang
>>
>> On 6/24/26 15:41, 'Felix Moessbauer' via isar-users wrote:
>>> This is the first release that splits the privileged and rootless
>>> execution modes. By that, the build_system: isar is deprecated and
>>> replaced by isar-privileged / isar-rootless.
>>>
>>> To preserve the old behavior, we change the build system to
>>> isar-privileged.
>>>
>>> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
>>> ---
>>> Dear maintainers,
>>> please also rebuild the test container as this allows us to directly
>>> test the rootless mode in the CI.
>>>
>>> Best regards,
>>> Felix
>>>
>>> .gitlab-ci.yml | 2 +-
>>> Kconfig | 2 +-
>>> kas/isar.yaml | 4 +-
>>> kas/kas-container | 300 +++++++++++++-----------
>>> meta-isar/test/sample_kas_config.yml | 4 +-
>>> meta-isar/test/sample_kas_config_hw.yml | 4 +-
>>> 6 files changed, 169 insertions(+), 147 deletions(-)
>>>
>>> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>>> index d997f73c..0711f200 100644
>>> --- a/.gitlab-ci.yml
>>> +++ b/.gitlab-ci.yml
>>> @@ -1,5 +1,5 @@
>>> default:
>>> - image: ghcr.io/siemens/kas/kas-isar:4.8.2
>>> + image: ghcr.io/siemens/kas/kas-isar:5.4
>>> variables:
>>> GIT_STRATEGY: clone
>>> diff --git a/Kconfig b/Kconfig
>>> index 86a4aac3..8953fbad 100644
>>> --- a/Kconfig
>>> +++ b/Kconfig
>>> @@ -14,7 +14,7 @@ config KAS_INCLUDE_MAIN
>>> config KAS_BUILD_SYSTEM
>>> string
>>> - default "isar"
>>> + default "isar-privileged"
>>> source "kas/machine/Kconfig"
>>> source "kas/distro/Kconfig"
>>> diff --git a/kas/isar.yaml b/kas/isar.yaml
>>> index 16ce8b42..a5194fc8 100644
>>> --- a/kas/isar.yaml
>>> +++ b/kas/isar.yaml
>>> @@ -2,9 +2,9 @@
>>> # Copyright (C) 2023-2024 ilbers GmbH
>>> header:
>>> - version: 14
>>> + version: 23
>
> This is a inconsisent change: All CIP config fragment must be bumped
> version-wise. kas is not yet complaining about that, but that may change.
>
To make my reasoning clearer: If we start to provide config files with
different versions, we signal to users that A) reusing of those files in
downstream projects is possible and B) that mix-and-match for those
files as well as for different kas versions is tested. I don't think
this is manageable.
Felix correctly pointed out to me that we are in kas allowing such
mixes, consolidating the resulting config over the highest version. But
even that may one day change when we have to lift the minimal version in
some future schema revision.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/91c3413f-17aa-47da-b6fa-f6bf61b2eae7%40siemens.com.
prev parent reply other threads:[~2026-07-02 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 13:41 'Felix Moessbauer' via isar-users
2026-07-01 9:05 ` Zhihang Wei
2026-07-02 15:29 ` 'Jan Kiszka' via isar-users
2026-07-02 15:55 ` 'Jan Kiszka' via isar-users [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=91c3413f-17aa-47da-b6fa-f6bf61b2eae7@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=wzh@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