From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Zhihang Wei <wzh@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] CI: Update kas version to include bwrap for GitLab CI
Date: Thu, 11 Dec 2025 17:38:26 +0100 [thread overview]
Message-ID: <222ff01e-5bd6-4473-86d2-b766a7b719a2@siemens.com> (raw)
In-Reply-To: <6dcdbb73-841f-49e5-9e28-8f283483d315@ilbers.de>
On 11.12.25 17:14, Zhihang Wei wrote:
>
>
> On 12/9/25 10:44, Zhihang Wei wrote:
>>
>> On 12/9/25 00:13, Jan Kiszka wrote:
>>> On 08.12.25 17:46, Zhihang Wei wrote:
>>>> Signed-off-by: Zhihang Wei<wzh@ilbers.de>
>>>> ---
>>>> .gitlab-ci.yml | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>>>> index b5faa11a..1a7abcb8 100644
>>>> --- a/.gitlab-ci.yml
>>>> +++ b/.gitlab-ci.yml
>>>> @@ -1,5 +1,5 @@
>>>> default:
>>>> - image: ghcr.io/siemens/kas/kas-isar:4.4
>>>> + image: ghcr.io/siemens/kas/kas-isar:4.8
>>>> variables:
>>>> GIT_STRATEGY: clone
>>>> @@ -26,7 +26,7 @@ variables:
>>>> .docker-isar: &docker-isar
>>>> - image: ghcr.io/ilbers/docker-isar:4.4
>>>> + image: ghcr.io/ilbers/docker-isar:4.8
>>>> .use-default-image:
>>> Any reason to stay on 4.x? 5.0 had some issue with isar, but 5.1 is out
>>> and should be fine.
>>>
>>> Jan
>>>
>> Let me try 5.1 as well.
>>
>> Zhihang
>>
> With 5.1 it is complaining "|E: Unable to locate package sbuild-build-
> depends-main-dummy|". I don't have time to analyze this but would like
> to have 4.8 first so we can share the failure log on GitLab directly.
>
That's the sbuild bug that was recently fixed, backported, but not yet
released to the container in 5.1. You need to use the bookworm based
container in the meantime. Adjust kas-container accordingly.
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/222ff01e-5bd6-4473-86d2-b766a7b719a2%40siemens.com.
next prev parent reply other threads:[~2025-12-11 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 16:46 Zhihang Wei
2025-12-08 23:13 ` 'Jan Kiszka' via isar-users
2025-12-09 9:44 ` Zhihang Wei
2025-12-11 16:14 ` Zhihang Wei
2025-12-11 16:38 ` 'Jan Kiszka' via isar-users [this message]
2025-12-11 16:16 ` Zhihang Wei
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=222ff01e-5bd6-4473-86d2-b766a7b719a2@siemens.com \
--to=isar-users@googlegroups.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