public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: "Moessbauer, Felix" <felix.moessbauer@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
	"ibr@ilbers.de" <ibr@ilbers.de>,
	"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: Re: [PATCH v4 1/2] run imager in buildchroot-host on cross
Date: Thu, 15 Sep 2022 18:43:25 +0300	[thread overview]
Message-ID: <738f3380-8bce-b249-dcd8-46ec68eb1994@ilbers.de> (raw)
In-Reply-To: <20220915130605.016e14f5@md1za8fc.ad001.siemens.net>

15.09.2022 14:06, Henning Schild wrote:
> Please take bullseye, not stretch. When we drop stretch we would
> silently drop the cross/wic/compression test.

Bullseye don't have any issues with SDK building, when stretch really do.
This is what Felix just asked and this is what my reply about.


  reply	other threads:[~2022-09-15 15:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 20:21 [PATCH v4 0/2] use xz and gzip on host (outside chroot) Felix Moessbauer
2022-09-14 20:21 ` [PATCH v4 1/2] run imager in buildchroot-host on cross Felix Moessbauer
2022-09-15  9:14   ` Anton Mikanovich
2022-09-15  9:35     ` Moessbauer, Felix
2022-09-15 10:45       ` Anton Mikanovich
2022-09-15 11:04         ` Moessbauer, Felix
2022-09-15 11:06         ` Henning Schild
2022-09-15 15:43           ` Anton Mikanovich [this message]
2022-09-15 11:08         ` Henning Schild
2022-09-15 15:44           ` Anton Mikanovich
2022-09-15 17:08             ` Moessbauer, Felix
2022-09-16  7:41               ` Anton Mikanovich
2022-09-14 20:21 ` [PATCH v4 2/2] add wic.xz image to qemuarm64-bookworm Felix Moessbauer

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=738f3380-8bce-b249-dcd8-46ec68eb1994@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=adriaan.schmidt@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=ibr@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    /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