From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev <cip-dev@lists.cip-project.org>
Subject: [isar-cip-core][PATCH] Update isar revision
Date: Thu, 13 Mar 2025 10:53:58 +0100 [thread overview]
Message-ID: <fa747ccb-9f57-4da8-907c-65618a94164e@siemens.com> (raw)
From: Jan Kiszka <jan.kiszka@siemens.com>
Allows to drop the local patch.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
...op-no-longer-needed-and-now-broken-r.patch | 32 -------------------
kas-cip.yml | 6 +---
2 files changed, 1 insertion(+), 37 deletions(-)
delete mode 100644 isar-patches/0001-sbuild-chroot-Drop-no-longer-needed-and-now-broken-r.patch
diff --git a/isar-patches/0001-sbuild-chroot-Drop-no-longer-needed-and-now-broken-r.patch b/isar-patches/0001-sbuild-chroot-Drop-no-longer-needed-and-now-broken-r.patch
deleted file mode 100644
index fc4f6bd6..00000000
--- a/isar-patches/0001-sbuild-chroot-Drop-no-longer-needed-and-now-broken-r.patch
+++ /dev/null
@@ -1,32 +0,0 @@
-From 5dc3f7d755b5adf447b419816002076bed21b8e1 Mon Sep 17 00:00:00 2001
-From: Jan Kiszka <jan.kiszka@siemens.com>
-Date: Mon, 24 Feb 2025 21:25:49 +0100
-Subject: [PATCH] sbuild-chroot: Drop no longer needed and now broken riscv64
- special case
-
-This was forgotten while cleaning up for trixie in 735dc16c1e. However,
-it continued to work - until these days. Fix the riscv64 build by simply
-dropping the obsolete package list.
-
-Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
----
- meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb | 6 ------
- 1 file changed, 6 deletions(-)
-
-diff --git a/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb b/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
-index 255d6937..3f0888d8 100644
---- a/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
-+++ b/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
-@@ -18,9 +18,3 @@ SBUILD_CHROOT_PREINSTALL ?= " \
- crossbuild-essential-${DISTRO_ARCH} \
- apt-utils \
- "
--
--SBUILD_CHROOT_PREINSTALL:riscv64 ?= " \
-- ${SBUILD_CHROOT_PREINSTALL_COMMON} \
-- gcc-riscv64-linux-gnu \
-- g++-riscv64-linux-gnu \
-- dpkg-cross"
---
-2.43.0
-
diff --git a/kas-cip.yml b/kas-cip.yml
index 16e54d63..cffc4f16 100644
--- a/kas-cip.yml
+++ b/kas-cip.yml
@@ -22,13 +22,9 @@ repos:
isar:
url: https://github.com/ilbers/isar.git
- commit: b5f7aef4e4fd26d852f8b09e545d5ade551224df
+ commit: d46adc844a74ba55c4b9521b7d7da9b5a47b489e
layers:
meta:
- patches:
- 01:
- path: isar-patches/0001-sbuild-chroot-Drop-no-longer-needed-and-now-broken-r.patch
- repo: cip-core
bblayers_conf_header:
standard: |
--
2.43.0
--
Siemens AG, Foundational Technologies
Linux Expert Center
next reply other threads:[~2025-03-13 9:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 9:53 Jan Kiszka [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-28 18:22 [isar-cip-core][PATCH] Update Isar revision Jan Kiszka
2025-12-16 14:50 [isar-cip-core][PATCH] Update isar revision Jan Kiszka
2025-12-01 8:05 Jan Kiszka
2025-07-28 13:40 Jan Kiszka
2025-07-03 12:17 Jan Kiszka
2025-02-14 11:01 Jan Kiszka
2025-02-14 13:33 ` Jan Kiszka
2025-01-30 13:17 Jan Kiszka
2025-02-03 17:06 ` Jan Kiszka
2024-12-06 9:48 Jan Kiszka
2024-12-06 12:38 ` Adithya.Balakumar
2024-12-06 12:44 ` Jan Kiszka
2024-12-06 12:56 ` Adithya.Balakumar
2024-11-13 17:32 Jan Kiszka
2024-10-19 7:12 Jan Kiszka
2024-05-28 8:21 Jan Kiszka
2023-03-13 13:48 [isar-cip-core][PATCH] Update Isar revision 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=fa747ccb-9f57-4da8-907c-65618a94164e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.org \
/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