From: henning.schild@siemens.com
To: isar-users@googlegroups.com
Cc: Uladzimir Bely <ubely@ilbers.de>,
Henning Schild <henning.schild@siemens.com>
Subject: [PATCH] CI: pin down the kas container version we use in CI
Date: Thu, 10 Feb 2022 13:33:49 +0100 [thread overview]
Message-ID: <20220210123349.24789-1-henning.schild@siemens.com> (raw)
In-Reply-To: <20220127104544.13077-1-ubely@ilbers.de>
That is a very good idea anyhow, even though it will need regular
version bumping and cause some work.
But right now we are doing it to work around a problem in debian 11.
In Debian >= bullseye 'dpkg-deb --show --showformat' is currently broken
in case of requesting virtual fields like 'source:<FieldName>'.
This makes function 'debsrc_download' broken, so build fails when
ISAR_USE_CACHED_BASE_REPO is enabled in local.conf
The regression came with the fix for bug #972580 in Debian.
The issue is reported to Debian bugtracker as bug #1004372.
Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
.gitlab-ci.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 1693a8ab4037..37882efa1f18 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -1,4 +1,4 @@
-image: ghcr.io/siemens/kas/kas-isar:latest
+image: ghcr.io/siemens/kas/kas-isar:2.6.3
variables:
GIT_STRATEGY: clone
--
2.34.1
next prev parent reply other threads:[~2022-02-10 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 10:45 [PATCH] deb-dl-dir: Use dpkg-deb --field in debsrc_download Uladzimir Bely
2022-01-31 8:49 ` Uladzimir Bely
2022-02-10 12:25 ` Henning Schild
2022-02-10 16:55 ` Uladzimir Bely
2022-02-11 13:10 ` Henning Schild
2022-02-10 12:33 ` henning.schild [this message]
2022-02-23 7:25 ` [PATCH] CI: pin down the kas container version we use in CI Anton Mikanovich
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=20220210123349.24789-1-henning.schild@siemens.com \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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