From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7032253102499561472 X-Received: by 2002:a19:484b:: with SMTP id v72mr45720772lfa.338.1638970833695; Wed, 08 Dec 2021 05:40:33 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:651c:1251:: with SMTP id h17ls341344ljh.6.gmail; Wed, 08 Dec 2021 05:40:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJyIEzhCCUPlp+TulkU9drBailzirTi2qKlZaYRsa91ooZLq2RM5kv9JL7nRMh3o3ivdzKUP X-Received: by 2002:a2e:8702:: with SMTP id m2mr46111489lji.55.1638970832345; Wed, 08 Dec 2021 05:40:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1638970832; cv=none; d=google.com; s=arc-20160816; b=F26mgZeGZWjkQw8vzLWp7wSlMM7/SBJO/fSadpiRQv3wWQ8qqq3b5pc3R1bowYqb/K c13GMs2uhjYm5CFcv//jf2Eve21bzQuvDnGLg5YbmXITY4W7t26Iv7dKrrqgxI1MxqjO +69wgNnN5lMkmr446QkkWP38o9bKguP27VBPr0HN0DWTrkSf95rBgQdMf+49fGd+Rw/A 8MU83vxnGi3wr8jGKUc7bE4NqVsZWvQAbSK9odt+me9raAW8Jq3nR066cNvDpC0rZh32 /QUof1nzfxRoXY1X5/rQx5dCo/DiHGRGNK+ZIyG2swHgbRPWMI/53B+UhpldQdORbZlN N/2g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from; bh=aM+mxxS3mBoxyoa8ZXDwkmqQhKifhCJVzB42rlUK2Sc=; b=T3PWQU0rLcNTt4iyPrW5TUopRfAes/4KpaGGOpqbGkngYBPGKbojbPGYNO6DN2Lm21 0McnQpScyqgZWZcYxSc0vSQxujbHBS54rDK3TygGofSDM9v7hGnWC8fguvyikxds7dFp PtVm8NcpqiEaTe8Mk7FkHn3qrTGltKFaO/9A3nvwliehC3CVCWDC/p8UsqpZvoAefk8T OlR1vGroHOvV92DadYNw8Fh3YLiKoGFUVaGH0JJ72Ip3LfGbcIdvD3Deuq18I0cv1net J20uqjSv4Fb2lFeVwG5Em+z5EwKuY//+XDc3TYSPYWBbweevGl9kr/qimSmGhWgOh9fI 2qow== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id i12si192807lfr.7.2021.12.08.05.40.32 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Wed, 08 Dec 2021 05:40:32 -0800 (PST) Received-SPF: pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Received: from hp.localnet (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id 1B8DeTVb010099 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 8 Dec 2021 14:40:30 +0100 From: Uladzimir Bely To: isar-users@googlegroups.com Cc: Uladzimir Bely Subject: Re: [PATCH v3 00/20] Sbuild/Schroot migration Date: Wed, 08 Dec 2021 16:40:28 +0300 Message-ID: <1978289.YKUYFuaPT4@hp> In-Reply-To: <20211208130544.15133-1-ubely@ilbers.de> References: <20211208130544.15133-1-ubely@ilbers.de> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: ORPKGg5OgY6X In mail from =D1=81=D1=80=D0=B5=D0=B4=D0=B0, 8 =D0=B4=D0=B5=D0=BA=D0=B0=D0= =B1=D1=80=D1=8F 2021 =D0=B3. 16:05:24 +03 user Uladzimir Bely wrote: > This is a patchset showing how sbuild/schroot tools can be integrated > into Isar build system. >=20 > Base schroot image is created with sbuild-chroot-target (or > sbuild-chroot-host in case of cross-build) recipe. These images are based > on isar-bootstrap ones, but include some build-related stuff preinstalled. >=20 > To use this changes you need to have sbuild and schroot installed and > configured. Current user should be added to sbuild group. >=20 > If 'kas-container' is used, it should be modified to support sbuild: > - /var/lib/schroot/union/overlay should be externally mounted (-v option) > - export KAS_IMAGE_VERSION=3D2.6.2-sbuild > - export KAS_CONTAINER_IMAGE_PATH=3Dghcr.io/wiselord > Here I uploaded a docker image that has preinstalled software (sbuild, > schroot, etc) required to run sbuild. Later, the changes might be > included in official kas docker images. >=20 > If 'gitlab' is used, the similar changes are required: > - 'image: ghcr.io/wiselord/kas-isar:2.6.2-sbuild' in .gitlab-ci.yml > - external dir for schroot overlay should also be specified in > /etc/gitlab-runner/config.toml: > volumes =3D ["/path/to/overlay:/var/lib/schroot/union/overlay"] >=20 > The patchset was tested with 'meta-iot2050' and 'xenomai-images' > downstreams. Some patches are required for these downstreams, > appropriate pull requests will be created soon. >=20 > Changes since v2: > - patches reworked/squashed for easier reading and understanding > - fixed building foreigh architectures with kas-docker > - implemented support of ccache > - fixed devshell and devshell_nodeps > Changes since v1: > - parallel builds with different BUILD_DIR are supported > - parallel multiconfig targets in one build are supported > - per-task schroot configuration in /etc/schroot/ is now used > - patchset now passes Jenkins CI (so patches changes RFC =3D> PATCH) >=20 > Current limitations: > - parallel building of several packages requires more free space in > comparison with buildchroot-based architecture. This happens due > the sbuild architecture which uses some basic layer (common for all > packages) and per-package separate layer (where builddeps are downloaded > and installed). >=20 > For experiments, the code can be taken from Isar 'ubely/sbuild' branch. > This is a dev branch, so sometimes it can be force-pushed when some > fixes are applied of rebased to 'next' branch. >=20 > First 9 patches (1..9) - are just preparation patches. With them, Isar wi= ll > continue using buildchroot-based architecture. So, potentially, > they can be merged as a subseries. >=20 > Remaining 11 patches (10..20) represent a sbuild-related changes. >=20 > Anton Mikanovich (10): > template: Make templates passthrough > linux-module: Do not use shell environment > u-boot: Do not use shell environment > trusted-firmware: Do not use shell environment > optee-os: Do not use shell environment > kselftest: Do not use shell environment > linux-mainline: Move cfg fragment test to debian/rules > dpkg: Build packages with sbuild > sbuild: Introduce environment variables export API > linux-custom: Prepare kernel config inside sbuild >=20 > Uladzimir Bely (10): > dpkg-gbp: Use separate command to export tarball > dpkg-gbp: Use host tools for dsc preparation > sbuild: Add recipes for host and target rootfs to run sbuild > sbuild: Introduce a class for another build method > dpkg: Remove builddeps install task. > dpkg-base: Switch devshell to use schroot > dpkg-base: Switch apt_fetch and apt_unpack to use schroot > dpkg-base: Cleanup from buildchroot parts. > doc: Add sbuild-related documentation > sbuild: add ccache support >=20 > doc/user_manual.md | 22 ++- > .../optee-os/optee-os-stm32mp15x_3.11.0.bb | 2 +- > .../linux/linux-mainline_5.4.70.bb | 16 +- > meta/classes/dpkg-base.bbclass | 98 ++++------ > meta/classes/dpkg-gbp.bbclass | 26 +-- > meta/classes/dpkg.bbclass | 53 ++--- > meta/classes/sbuild.bbclass | 184 ++++++++++++++++++ > meta/classes/template.bbclass | 7 +- > meta/conf/bitbake.conf | 2 + > .../files/debian/{rules =3D> rules.tmpl} | 4 +- > meta/recipes-bsp/optee-os/optee-os-custom.inc | 9 +- > .../files/debian/{rules =3D> rules.tmpl} | 4 +- > .../trusted-firmware-a-custom.inc | 9 +- > .../u-boot/files/debian/{rules =3D> rules.tmpl} | 2 +- > meta/recipes-bsp/u-boot/u-boot-custom.inc | 9 +- > .../sbuild-chroot/sbuild-chroot-host.bb | 13 ++ > .../sbuild-chroot/sbuild-chroot-target.bb | 10 + > .../sbuild-chroot/sbuild-chroot.inc | 39 ++++ > .../kselftest/files/{rules =3D> rules.tmpl} | 0 > meta/recipes-kernel/kselftest/kselftest.inc | 21 +- > .../linux-module/files/debian/rules | 37 ---- > .../linux-module/files/debian/rules.tmpl | 52 +++++ > meta/recipes-kernel/linux-module/module.inc | 19 +- > meta/recipes-kernel/linux/linux-custom.inc | 7 +- > 24 files changed, 437 insertions(+), 208 deletions(-) > create mode 100644 meta/classes/sbuild.bbclass > rename meta/recipes-bsp/optee-os/files/debian/{rules =3D> rules.tmpl} (7= 5%) > rename meta/recipes-bsp/trusted-firmware-a/files/debian/{rules =3D> > rules.tmpl} (77%) rename meta/recipes-bsp/u-boot/files/debian/{rules =3D> > rules.tmpl} (94%) create mode 100644 > meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb create mode > 100644 meta/recipes-devtools/sbuild-chroot/sbuild-chroot-target.bb create > mode 100644 meta/recipes-devtools/sbuild-chroot/sbuild-chroot.inc rename > meta/recipes-kernel/kselftest/files/{rules =3D> rules.tmpl} (100%) delete > mode 100755 meta/recipes-kernel/linux-module/files/debian/rules create mo= de > 100755 meta/recipes-kernel/linux-module/files/debian/rules.tmpl Just a question: Does 'xenomai-images' and 'meta-iot2050' have their own=20 maillists where I could send the changes to work with isar-based sbuild? I= =20 just found a maillist for 'kas', but not for these projects. =2D-=20 Uladzimir Bely Promwad Ltd. External service provider of ilbers GmbH Maria-Merian-Str. 8 85521 Ottobrunn, Germany +49 (89) 122 67 24-0 Commercial register Munich, HRB 214197 General Manager: Baurzhan Ismagulov