From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 0/6] Migrate to mmdebstrap
Date: Fri, 19 May 2023 09:13:43 +0300 [thread overview]
Message-ID: <077e3130-9db2-103e-442e-360133e8d825@ilbers.de> (raw)
In-Reply-To: <166ba2b7-35e0-fd95-dd97-6c4782a16227@siemens.com>
19/05/2023 07:57, Jan Kiszka wrote:
> On 18.05.23 11:47, Anton Mikanovich wrote:
>> Switch Isar from debootstrap to mmdebstrap.
>> It makes isar-bootstrap target ~10% faster on both cross and native rootfs
>> types. Also mmdebstrap support using SOURCE_DATE_EPOCH for images reproducibly
>> out of the box. But the main advantage is an ability to remove sudo for
>> debootstrapping later on.
>> This change brakes Debian Buster support as host distro.
> Where is this last aspect described in the patches?
>
> Jan
Hello Jan,
It's all about the usage of mmdebstrap itself: buster version of the
package is
too old to have all the features already used in isar-bootstrap recipe.
next prev parent reply other threads:[~2023-05-19 6:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 9:47 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
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 [this message]
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=077e3130-9db2-103e-442e-360133e8d825@ilbers.de \
--to=amikan@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