public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "srinuvasan.a via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: ubely@ilbers.de, Srinuvasan A <srinuvasan.a@siemens.com>
Subject: [PATCH 2/2] meta-isar/test: update refspec to commit/branch
Date: Mon, 24 Mar 2025 12:38:33 +0530	[thread overview]
Message-ID: <20250324070833.2280190-2-srinuvasan.a@siemens.com> (raw)
In-Reply-To: <20250324070833.2280190-1-srinuvasan.a@siemens.com>

From: Srinuvasan A <srinuvasan.a@siemens.com>

kas-container 3.3 or above version not support refspec key instead it uses
the commit/branch, hence dropping the refspec.

Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
---
 CONTRIBUTING.md                         | 4 ++--
 meta-isar/test/sample_kas_config.yml    | 4 ++--
 meta-isar/test/sample_kas_config_hw.yml | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f932417b..e70e36c9 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -83,12 +83,12 @@ Plan merges to `master` so that both fit the two-week window; short extensions s
     git clone https://github.com/siemens/kas
     cat > kas.yml <<EOF
     header:
-      version: 12
+      version: 14
       build_system: isar
     repos:
       isar:
         url: "http://github.com:/ilbers/isar"
-        refspec: master
+        branch: master
         layers:
           meta:
           meta-isar:
diff --git a/meta-isar/test/sample_kas_config.yml b/meta-isar/test/sample_kas_config.yml
index e7635af8..f9b72d82 100644
--- a/meta-isar/test/sample_kas_config.yml
+++ b/meta-isar/test/sample_kas_config.yml
@@ -1,5 +1,5 @@
 header:
-  version: 11
+  version: 14
 
 build_system: isar
 
@@ -9,7 +9,7 @@ target: mc:qemuarm64-bullseye:isar-image-ci
 repos:
   isar:
     url: "https://github.com/ilbers/isar.git"
-    refspec: next
+    branch: next
     layers:
       meta:
       meta-isar:
diff --git a/meta-isar/test/sample_kas_config_hw.yml b/meta-isar/test/sample_kas_config_hw.yml
index 69afc9c3..37c7bb31 100644
--- a/meta-isar/test/sample_kas_config_hw.yml
+++ b/meta-isar/test/sample_kas_config_hw.yml
@@ -1,5 +1,5 @@
 header:
-  version: 11
+  version: 14
 
 build_system: isar
 
@@ -9,7 +9,7 @@ target: mc:rpi-arm-v7-bullseye:isar-image-ci
 repos:
   isar:
     url: "https://github.com/ilbers/isar.git"
-    refspec: next
+    branch: next
     layers:
       meta:
       meta-isar:
-- 
2.34.1

-- 
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/20250324070833.2280190-2-srinuvasan.a%40siemens.com.

  reply	other threads:[~2025-03-24  7:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24  7:08 [PATCH 1/2] kas/kas-container: update kas-container to version 4.7 srinuvasan.a via isar-users
2025-03-24  7:08 ` srinuvasan.a via isar-users [this message]
2025-03-24 10:12   ` [PATCH 2/2] meta-isar/test: update refspec to commit/branch 'MOESSBAUER, Felix' via isar-users
2025-04-01 12:43 ` [PATCH 1/2] kas/kas-container: update kas-container to version 4.7 Uladzimir Bely

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=20250324070833.2280190-2-srinuvasan.a@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=srinuvasan.a@siemens.com \
    --cc=ubely@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