From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v3 0/6] Imager schroot migration
Date: Mon, 13 Feb 2023 09:40:28 +0200 [thread overview]
Message-ID: <20230213074034.3949-1-amikan@ilbers.de> (raw)
This patchset moves Isar imager from buildchroot to schroot usage as the next
step after moving to sbuild.
Imagers of every target are now running in separate schroot sessions with
independent overlays on top of basic unchanged schroot. Any changes made inside
overlay will be dropped after the usage to keep basic schroot clean.
There are still couple of issues need to be solved before the usage:
- there are no documentaion updates
- repro test case still fails
But now at least fast CI passed ok.
Changes since v2:
- Rebased on next
- Do not keep schroot session open outside tasks
- Get rid of final cleanup code
- Fix sstate test case
- Get back buildchroot removing
Changes since v1:
- Rebased on next and bitbake update
- Fix some build cases
Anton Mikanovich (6):
isar-apt: Move cleanup to postprocessing
imager: Migrate from buildchroot to schroot
imager: Move image types to schroot
imager: Split imager deps between image types
CI: Fix used chroot recipe name
meta: Remove buildchroot
meta-isar/conf/local.conf.sample | 2 +-
meta/classes/buildchroot.bbclass | 71 --------------
meta/classes/image-tools-extension.bbclass | 96 +++++++++++++------
meta/classes/image.bbclass | 35 +++----
meta/classes/imagetypes_vm.bbclass | 9 +-
meta/classes/imagetypes_wic.bbclass | 89 ++++++-----------
meta/classes/isar-events.bbclass | 1 -
meta/classes/rootfs.bbclass | 12 +++
meta/conf/bitbake.conf | 3 -
.../buildchroot/buildchroot-host.bb | 13 ---
.../buildchroot/buildchroot-target.bb | 10 --
.../buildchroot/buildchroot.inc | 73 --------------
.../buildchroot/files/build.sh | 17 ----
.../buildchroot/files/common.sh | 32 -------
.../buildchroot/files/configscript.sh | 15 ---
.../buildchroot/files/deps.sh | 47 ---------
.../sbuild-chroot/sbuild-chroot.inc | 1 +
testsuite/cibase.py | 6 +-
18 files changed, 128 insertions(+), 404 deletions(-)
delete mode 100644 meta/classes/buildchroot.bbclass
delete mode 100644 meta/recipes-devtools/buildchroot/buildchroot-host.bb
delete mode 100644 meta/recipes-devtools/buildchroot/buildchroot-target.bb
delete mode 100644 meta/recipes-devtools/buildchroot/buildchroot.inc
delete mode 100644 meta/recipes-devtools/buildchroot/files/build.sh
delete mode 100644 meta/recipes-devtools/buildchroot/files/common.sh
delete mode 100644 meta/recipes-devtools/buildchroot/files/configscript.sh
delete mode 100644 meta/recipes-devtools/buildchroot/files/deps.sh
--
2.34.1
next reply other threads:[~2023-02-13 7:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 7:40 Anton Mikanovich [this message]
2023-02-13 7:40 ` [PATCH v3 1/6] isar-apt: Move cleanup to postprocessing Anton Mikanovich
2023-02-13 7:40 ` [PATCH v3 2/6] imager: Migrate from buildchroot to schroot Anton Mikanovich
2023-02-13 7:40 ` [PATCH v3 3/6] imager: Move image types " Anton Mikanovich
2023-02-13 7:40 ` [PATCH v3 4/6] imager: Split imager deps between image types Anton Mikanovich
2023-02-13 7:40 ` [PATCH v3 5/6] CI: Fix used chroot recipe name Anton Mikanovich
2023-02-14 9:28 ` Schmidt, Adriaan
2023-02-14 10:30 ` Anton Mikanovich
2023-02-13 7:40 ` [PATCH v3 6/6] meta: Remove buildchroot Anton Mikanovich
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=20230213074034.3949-1-amikan@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.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