From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH v5 0/9] Imager schroot migration
Date: Thu, 13 Jul 2023 16:33:00 +0300 [thread overview]
Message-ID: <ac32f4f5984c029a68f75547882862bf84d82815.camel@ilbers.de> (raw)
In-Reply-To: <20230531111236.104373-1-amikan@ilbers.de>
On Wed, 2023-05-31 at 14:12 +0300, Anton Mikanovich wrote:
> 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.
>
> Changes since v4:
> - Rebased on next
> - Add RECIPE-API-CHANGELOG entry
> - Remove unused mounts from dpkg-gbp
>
> Changes since v3:
> - Rebased on next
> - Fixed full CI build issues
> - Add documentation updates
> - Fix task name in CI
> - Some code cleanup
>
> 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 (9):
> 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
> dpkg-gbp: Remove unused mounts
> doc: Update chroot documentation
> RECIPE-API-CHANGELOG.md: Describe imager changes
>
> RECIPE-API-CHANGELOG.md | 20 ++++
> doc/offline.md | 2 +-
> doc/technical_overview.md | 107 +++++++++-------
> --
> doc/user_manual.md | 53 +++++----
> meta-isar/conf/local.conf.sample | 2 +-
> meta/classes/buildchroot.bbclass | 59 ----------
> meta/classes/crossvars.bbclass | 6 -
> meta/classes/deb-dl-dir.bbclass | 4 +-
> meta/classes/dpkg-gbp.bbclass | 2 -
> meta/classes/image-tools-extension.bbclass | 99 +++++++++++-----
> 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 +
> scripts/contrib/convert-overrides.py | 2 +-
> testsuite/cibase.py | 8 +-
> 26 files changed, 238 insertions(+), 483 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
>
Before sendingv6 of the patchset, we would like to propose a patchset
for meta-iot2050 that makes it compatible with new schroot-based
imager. The patchset relays on SBUILD_FLAVOR feature that was recently
added in isar.
The WIP patchset for meta-iot2050 can be found at
https://github.com/WiseLord/meta-iot2050/commits/master
For now I don't send it as a pull request since p1 "Update isar
revision to next" will be changed later since meta-iot2050 is temporary
not compatible with recent isar 'next'. This is due to missing patch
https://groups.google.com/g/isar-users/c/Sfd2fYMLXxg that is going to
be merged soon.
prev parent reply other threads:[~2023-07-13 13:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 11:12 Anton Mikanovich
2023-05-31 11:12 ` [PATCH v5 1/9] isar-apt: Move cleanup to postprocessing Anton Mikanovich
2023-05-31 11:12 ` [PATCH v5 2/9] imager: Migrate from buildchroot to schroot Anton Mikanovich
2023-05-31 11:12 ` [PATCH v5 3/9] imager: Move image types " Anton Mikanovich
2023-05-31 11:12 ` [PATCH v5 4/9] imager: Split imager deps between image types Anton Mikanovich
2023-05-31 11:12 ` [PATCH v5 5/9] CI: Fix used chroot recipe name Anton Mikanovich
2023-05-31 11:12 ` [PATCH v5 6/9] meta: Remove buildchroot Anton Mikanovich
2023-05-31 11:12 ` [PATCH v5 7/9] dpkg-gbp: Remove unused mounts Anton Mikanovich
2023-05-31 11:12 ` [PATCH v5 8/9] doc: Update chroot documentation Anton Mikanovich
2023-05-31 11:12 ` [PATCH v5 9/9] RECIPE-API-CHANGELOG.md: Describe imager changes Anton Mikanovich
2023-07-13 13:33 ` Uladzimir Bely [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=ac32f4f5984c029a68f75547882862bf84d82815.camel@ilbers.de \
--to=ubely@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