public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
	"MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "ubely@ilbers.de" <ubely@ilbers.de>
Subject: Re: [PATCH v2 1/6] meta: Switch to mmdebstrap
Date: Sun, 21 May 2023 08:38:48 +0200	[thread overview]
Message-ID: <5c7eb212-73f9-bd6a-0ddb-1566953854b7@siemens.com> (raw)
In-Reply-To: <9d5aa527-86c7-cd2a-4d07-307cfbeb68ad@ilbers.de>

On 20.05.23 11:23, Anton Mikanovich wrote:
> 20/05/2023 07:50, MOESSBAUER, Felix wrote:
>> Hi,
>>
>> does this solve the issue that we cannot bootstrap ubuntu > focal on a
>> debian < bookworm host? This is currently not supported, as some debs
>> use zstd compression which is only supported from dpkg >= 1.21 on.
>>
>> I hope mmdebstrap can work around this by not relying on the host dpkg,
>> as otherwise very soon bootstrapping from non bookworm hosts will not
>> be possible anymore. However, looking at the dependencies of mmdebstrap
>> I'm not too optimistic about that.
>>
>> PS: This is also another reason to use bookworm as a base for the kas-
>> container (and new ISAR CI).
>>
>> Felix
> 
> Hello Felix,
> I've just tried to build jammy on bullseye host with mmdebstrap and
> unfortunately it has the same issue.
> 

AFAIK, it will take dpkg from bookworm to add zstd support which is
needed for Ubuntu after focal.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux


  reply	other threads:[~2023-05-21  6:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  9:47 [PATCH v2 0/6] Migrate " Anton Mikanovich
2023-05-18  9:47 ` [PATCH v2 1/6] meta: Switch " Anton Mikanovich
2023-05-20  4:50   ` MOESSBAUER, Felix
2023-05-20  9:23     ` Anton Mikanovich
2023-05-21  6:38       ` Jan Kiszka [this message]
2023-05-18  9:47 ` [PATCH v2 2/6] isar-bootstrap: Move preparations to hooks Anton Mikanovich
2023-05-18  9:47 ` [PATCH v2 3/6] isar-bootstrap: Use tar output instead of directory Anton Mikanovich
2023-05-18  9:47 ` [PATCH v2 4/6] user_manual.md: Replace debootstrap with mmdebstrap Anton Mikanovich
2023-05-19  4:55   ` Jan Kiszka
2023-05-19  6:14     ` Anton Mikanovich
2023-05-18  9:47 ` [PATCH v2 5/6] isar-bootstrap: Remove unused code Anton Mikanovich
2023-05-18  9:47 ` [PATCH v2 6/6] CI: Install mmdebstrap Anton Mikanovich
2023-05-19  4:57 ` [PATCH v2 0/6] Migrate to mmdebstrap Jan Kiszka
2023-05-19  6:13   ` Anton Mikanovich
2023-05-19 12:55     ` 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=5c7eb212-73f9-bd6a-0ddb-1566953854b7@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=felix.moessbauer@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