On 07.03.22 11:09, Srinuvasan Arjunan wrote:

On Mon, Mar 7, 2022 at 3:11 PM Jan Kiszka <jan.kiszka@...
<mailto:jan.kiszka@...>> wrote:

On 07.03.22 10:34, Srinuvasan A wrote:
> From: Srinuvasan A <srinuvasan_a@...
<mailto:srinuvasan_a@...>>
>
> Update to kas 3.0.
>
> Signed-off-by: Srinuvasan A <srinuvasan_a@...
<mailto:srinuvasan_a@...>>
> ---
>  .gitlab-ci.yml | 2 +-
>  README.md      | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index c06c783..f573da6 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -1,4 +1,4 @@
> -image: ghcr.io/siemens/kas/kas-isar:2.6.2
<http://ghcr.io/siemens/kas/kas-isar:2.6.2>
> +image: ghcr.io/siemens/kas/kas-isar:3.0
<http://ghcr.io/siemens/kas/kas-isar:3.0>
> 
>  variables:
>    GIT_STRATEGY: clone
> diff --git a/README.md b/README.md
> index f7cb86e..fc4ddbf 100644
> --- a/README.md
> +++ b/README.md
> @@ -12,7 +12,7 @@ from scratch.
> 
>  Install `kas-container` from the [kas
project](https://github.com/siemens/kas
<https://github.com/siemens/kas>):
> 
> -    wget
https://raw.githubusercontent.com/siemens/kas/2.6.2/kas-container
<https://raw.githubusercontent.com/siemens/kas/2.6.2/kas-container>
> +    wget
https://raw.githubusercontent.com/siemens/kas/3.0/kas-container
<https://raw.githubusercontent.com/siemens/kas/3.0/kas-container>
>      chmod a+x kas-container
> 
>  Furthermore, install docker and make sure you have required
permissions to

Please test before you submit: We have an open issue with kas-isar:3.0.


  I did a build and verified the pipeline in KAS github, It seems okay,
but when i trigger the build i was able to see some logs related to sbuild
Adding user `builder' to group `sbuild' ...
Adding user builder to group sbuild
Done.

# Setup tasks for sudo users:

# BUILD
# HOME directory in chroot, user:sbuild, 0770 perms, from
# passwd/group copying to chroot, filtered
# Maybe source 50sbuild, or move into common location.

Next, copy the example sbuildrc file to the home directory of each user and
set the variables for your system:

  cp /usr/share/doc/sbuild/examples/example.sbuildrc /builder/.sbuildrc

Now try a build:

  cd /path/to/source
  sbuild-update -ud <distribution>
  (or "sbuild-apt <distribution> apt-get -f install"
       first if the chroot is broken)
  sbuild -d <distribution> <package>_<version>
 
 Might be i missed the open issue things

That warning is just a cosmetic issue, but I plan to fix it with 3.0.1
this week. The actual issue was (now fixed in next) that swupdate images
did not build. CI would have revealed it as well, but I happened to
notice this already on Friday during EFI Boot Guard experiments.

Jan

--
Siemens AG, Technology
Competence Center Embedded Linux