From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH v6 0/8] Migrate to mmdebstrap
Date: Wed, 1 Nov 2023 11:58:22 +0200 [thread overview]
Message-ID: <98513029-408d-4209-87b9-908c8c16454c@ilbers.de> (raw)
In-Reply-To: <f22e113e-59a9-49b2-af00-825c6a5a2c7c@siemens.com>
27/10/2023 18:36, Jan Kiszka wrote:
> No other regressions known? Or do we need an option to select the
> bootstrap variant, at least for some transition period?
There are no other regressions found so far, so I think loosing
oldoldstrable
build host support is not a big issue.
Bootstrap variant selection will require a lot of effort and can cause
issues
by itself. And it probably can be done only with huge code duplication
just like
we had it with buildchroot + sbuild prevoiusly.
> BTW, the series seems to be a bit misordered, given that it first
> switched to mmdebstrap and only after that fixes related issues. Is that
> unavoidable?
Right, it looks not really nice. Will rearrange some patches and resend.
> Jan
prev parent reply other threads:[~2023-11-01 9:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 6:23 Anton Mikanovich
2023-10-24 6:23 ` [PATCH v6 1/8] meta: Switch " Anton Mikanovich
2023-10-24 6:23 ` [PATCH v6 2/8] meta: Preinstall apt for Ubuntu and RPi targets Anton Mikanovich
2023-10-24 6:23 ` [PATCH v6 3/8] isar-bootstrap: Move preparations to hooks Anton Mikanovich
2023-10-24 6:23 ` [PATCH v6 4/8] isar-bootstrap: Use tar output instead of directory Anton Mikanovich
2023-10-24 6:23 ` [PATCH v6 5/8] user_manual.md: Replace debootstrap with mmdebstrap Anton Mikanovich
2023-10-24 6:23 ` [PATCH v6 6/8] user_manual.md: Update minimal host requirements Anton Mikanovich
2023-10-24 6:23 ` [PATCH v6 7/8] isar-bootstrap: Remove unused code Anton Mikanovich
2023-10-24 6:23 ` [PATCH v6 8/8] meta: Fix missing dpkg available Anton Mikanovich
2023-10-27 15:36 ` [PATCH v6 0/8] Migrate to mmdebstrap Jan Kiszka
2023-11-01 9:58 ` Anton Mikanovich [this message]
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=98513029-408d-4209-87b9-908c8c16454c@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