Re: [PATCH v3 0/7] Migrate to mmdebstrap

[Jan Kiszka <jan.kiszka@siemens.com>]

On 20.06.23 12:00, Uladzimir Bely wrote:
> On Tue, 2023-06-20 at 07:30 +0200, Jan Kiszka wrote:
>> On 31.05.23 12:10, 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.
>>>
>>> Changes since v2:
>>> - Rebase on next
>>> - Fix commit messages
>>> - Update host requirements
>>>
>>> Changes since v1:
>>> - Move mmdebstrap tmpdir to workdir
>>> - Fix kas building
>>> - Improve mounts cleanup
>>>
>>> Anton Mikanovich (5):
>>>   isar-bootstrap: Move preparations to hooks
>>>   isar-bootstrap: Use tar output instead of directory
>>>   user_manual.md: Replace debootstrap with mmdebstrap
>>>   user_manual.md: Update minimal host requirements
>>>   isar-bootstrap: Remove unused code
>>>
>>> Uladzimir Bely (2):
>>>   meta: Switch to mmdebstrap
>>>   CI: Install mmdebstrap
>>>
>>>  doc/user_manual.md                            |  41 +--
>>>  meta-isar/conf/distro/ubuntu-common.inc       |   4 -
>>>  meta/classes/rootfs.bbclass                   |  11 +-
>>>  .../isar-bootstrap/isar-bootstrap.inc         | 274 ++++++++------
>>> ----
>>>  scripts/ci_build.sh                           |   6 +
>>>  5 files changed, 152 insertions(+), 184 deletions(-)
>>>
>>
>> Is this now settled? Asking as I'm planning to release kas 4.0 with
>> the
>> dependencies in patch 7 resolved these days, and I'd like to see this
>> targeting the final version of this feature.
>>
>> Jan
>>
> 
> We are currently upgrading our interlnal CI and need to run more jobs
> before merging it.
> 
> But anyway, if mmdebstrap (and other packages mentioned in patch 3) is
> preinstalled in kas 4.0 image, it would be nice.

You can already check that by using kas-isar:next which contains [1].

Jan

[1] https://github.com/siemens/kas/commit/9110175839729cd5dbd3047e7a52e6bd43786ecc

-- 
Siemens AG, Technology
Competence Center Embedded Linux