From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6719774909718855680 X-Received: by 2002:a2e:9dc1:: with SMTP id x1mr2074332ljj.0.1565103349570; Tue, 06 Aug 2019 07:55:49 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:b601:: with SMTP id r1ls9889080ljn.3.gmail; Tue, 06 Aug 2019 07:55:49 -0700 (PDT) X-Google-Smtp-Source: APXvYqx42/Kcir3kiQ3Hz8+QbqDEdSowrVd3zbtRpPUOvWSIUZvK58gBaeIuPAUKe52H71ZvpP01 X-Received: by 2002:a2e:7f05:: with SMTP id a5mr1997447ljd.190.1565103349106; Tue, 06 Aug 2019 07:55:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565103349; cv=none; d=google.com; s=arc-20160816; b=qlwQSfaK7ydInefwirik1az715ZECHuZooqbUy98+sIIGS1sDQoS+LktVwWA5MJoIi bVxCS6ooq/W7IYJ9ttyNp+S/FHiKnOGQgAGiHxQQ1Vnzvud3Bi6ZFw7XhwPjPIdRklPy 3dcYAZCnjL9QjdDB/1KfTlkg/go+bgp/gwC+a8slXa3/656/ux9m0GmoR04lCqr8IVpb nscN7NoHhrTU3Apt/KFRFynfVZohvInoS8vZ4iQu4jfzY8pL7Gll/lYtxdrMtvE7Poed DCk0768hyFzrrDp2Qv/ARMW8SX/IMECB4uLeYFvcqeCkXxTi0sBpSGbcDYyRbeMbcrls 6Ubg== 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:subject:to:from:date; bh=YX29jCJwjsEmSqucBb+vTG5JY+VdeNnQDZ83v30f/U8=; b=IENROR6rn9t4VmxtR8AoLf4V+GRsT3ojGmG8KRi4fCVS6BHkd6dbo0l8iA7jJ1bzAl nLrr9VhMNjg9EboScpDjgTCEbu2lcKi+7BNvJ8HWO8WD6p1Luv6F7YG1WNqo9/j68QD4 A3LNk/0KLT/w3arAiCQRONBQB72dvKIhgKGv8lE7sxsddewvsKweBl8vrUFiqjuXVmM8 y15hWk0jKUB0LE9WI8GZHcXIETAAvhKwwgylmeuWqfxO89Kmc39ZhsI0d65EGEYWkIQg D/SCwIL9njCddCl8lSzt5iT3BL1H8U5pDbeExxMR/AOK4nb6ji82SzeraLittYQ2Wk0G ubVw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from lizzard.sbs.de (lizzard.sbs.de. [194.138.37.39]) by gmr-mx.google.com with ESMTPS id q7si1536653lji.5.2019.08.06.07.55.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Aug 2019 07:55:49 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.39 as permitted sender) client-ip=194.138.37.39; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id x76EtmnM027027 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 6 Aug 2019 16:55:48 +0200 Received: from md1za8fc.ad001.siemens.net ([139.25.0.27]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x76EtmcD018800 for ; Tue, 6 Aug 2019 16:55:48 +0200 Date: Tue, 6 Aug 2019 16:55:47 +0200 From: Henning Schild To: isar-users Subject: Re: [PATCH 1/3] doc: make buster the new default suite Message-ID: <20190806165547.05c6d461@md1za8fc.ad001.siemens.net> In-Reply-To: <20190806145437.8195-1-henning.schild@siemens.com> References: <20190806145437.8195-1-henning.schild@siemens.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: lDZuwvaYM0d4 Somehow the v2 is missing ... sorry. Diff to v1 is just the author. Henning Am Tue, 6 Aug 2019 16:54:35 +0200 schrieb Henning Schild : > From: Henning Schild > > Buster is the new stable release. Mention it in the docs to clearly > state that we support it. And tell users to choose it for their next > image. > > Signed-off-by: Henning Schild > --- > doc/user_manual.md | 38 > +++++++++++++++++------------------ meta-isar/conf/conf-notes.txt | > 4 ++-- 2 files changed, 21 insertions(+), 21 deletions(-) > > diff --git a/doc/user_manual.md b/doc/user_manual.md > index ed181aa..a301740 100644 > --- a/doc/user_manual.md > +++ b/doc/user_manual.md > @@ -128,22 +128,22 @@ e.g.: > > ``` > MACHINE ??= "qemuarm" > -DISTRO ??= "debian-stretch" > +DISTRO ??= "debian-buster" > DISTRO_ARCH ??= "armhf" > ``` > > Then, call `bitbake` with image names, e.g.: > > ``` > -bitbake multiconfig:qemuarm-stretch:isar-image-base \ > - multiconfig:qemuarm-stretch:isar-image-debug > +bitbake multiconfig:qemuarm-buster:isar-image-base \ > + multiconfig:qemuarm-buster:isar-image-debug > ``` > > The following images are created: > > ``` > -tmp/deploy/images/qemuarm/isar-image-base-qemuarm-debian-stretch.ext4.img > -tmp/deploy/images/qemuarm/isar-image-debug-qemuarm-debian-stretch.ext4.img > +tmp/deploy/images/qemuarm/isar-image-base-qemuarm-debian-buster.ext4.img > +tmp/deploy/images/qemuarm/isar-image-debug-qemuarm-debian-buster.ext4.img > ``` > > ### Building Target Images for Multiple Configurations > @@ -197,9 +197,9 @@ tmp/deploy/images/rpi/isar-image-base.rpi-sdimg > A bootable disk image is generated if you set IMAGE_TYPE to > 'wic-img'. Behind the scenes a tool called `wic` is used to assemble > the images. It is controlled by a `.wks` file which you can choose > with changing WKS_FILE. Some examples in the tree use that feature > already. ``` # Generate an image for the `i386` target architecture > - $ bitbake multiconfig:qemui386-stretch:isar-image-base > + $ bitbake multiconfig:qemui386-buster:isar-image-base > # Similarly, for the `amd64` target architecture, in this case EFI > - $ bitbake multiconfig:qemuamd64-stretch:isar-image-base > + $ bitbake multiconfig:qemuamd64-buster:isar-image-base > ``` > > Variables may be used in `.wks.in` files; Isar will expand them and > generate a regular `.wks` file before generating the disk image using > `wic`. @@ -212,9 +212,9 @@ enough to allow images to be testable > under `qemu`. ``` > # AMD64 image, EFI > -qemu-system-x86_64 -m 256M -nographic -bios > edk2/Build/OvmfX64/RELEASE_*/FV/OVMF.fd -hda > tmp/deploy/images/qemuamd64/isar-image-base-debian-stretch-qemuamd64.wic.img > +qemu-system-x86_64 -m 256M -nographic -bios > edk2/Build/OvmfX64/RELEASE_*/FV/OVMF.fd -hda > tmp/deploy/images/qemuamd64/isar-image-base-debian-buster-qemuamd64.wic.img > # i386 image -qemu-system-i386 -m 256M -nographic -hda > tmp/deploy/images/qemui386/isar-image-base-debian-stretch-qemui386.wic.img > +qemu-system-i386 -m 256M -nographic -hda > tmp/deploy/images/qemui386/isar-image-base-debian-buster-qemui386.wic.img > ``` --- @@ -303,7 +303,7 @@ following variables define the default > configuration to build for: > - `DISTRO_ARCH` - The Debian architecture to build for (e.g., > `armhf`). > If BitBake is called with multiconfig targets (e.g., > -`multiconfig:qemuarm-stretch:isar-image-base`), the following > variable defines +`multiconfig:qemuarm-buster:isar-image-base`), the > following variable defines all supported configurations: > > - `BBMULTICONFIG` - The list of the complete configuration > definition files. @@ -708,7 +708,7 @@ One may chroot into the SDK and > install required target packages with the help o > - Trigger creation of SDK root filesystem > > ``` > -bitbake -c do_populate_sdk > multiconfig:qemuarm-stretch:isar-image-base +bitbake -c > do_populate_sdk multiconfig:qemuarm-buster:isar-image-base ``` > > - Mount the following directories in chroot by passing resulting > rootfs as an argument to the script `mount_chroot.sh`: @@ -726,14 > +726,14 @@ mount devtmpfs $1/dev -t devtmpfs -o mode=0755,nosuid > mount devpts $1/dev/pts -t devpts -o gid=5,mode=620 mount > tmpfs $1/dev/shm -t tmpfs -o rw,seclabel,nosuid,nodev > -$ sudo > scripts/mount_chroot.sh ../build/tmp/deploy/images/qemuarm/sdk-debian-stretch-armhf > +$ sudo > scripts/mount_chroot.sh ../build/tmp/deploy/images/qemuarm/sdk-debian-buster-armhf > ``` > - chroot to isar SDK rootfs: > > ``` > -$ sudo chroot > build/tmp/deploy/images/qemuarm/sdk-debian-stretch-armhf +$ sudo > chroot build/tmp/deploy/images/qemuarm/sdk-debian-buster-armhf ``` > - Check that cross toolchains are installed > > @@ -790,7 +790,7 @@ BASE_REPO_KEY = > "file://"' > - Trigger creation of local apt caching Debian packages during > image generation. > ``` > -bitbake -c cache_base_repo > multiconfig:qemuarm-stretch:isar-image-base +bitbake -c > cache_base_repo multiconfig:qemuarm-buster:isar-image-base ``` > > - Set `ISAR_USE_CACHED_BASE_REPO` in `conf/local.conf`: > @@ -809,7 +809,7 @@ sudo rm -rf tmp > - Trigger again generation of image (now using local caching repo): > > ``` > -bitbake multiconfig:qemuarm-stretch:isar-image-base > +bitbake multiconfig:qemuarm-buster:isar-image-base > ``` > > ### Limitation > @@ -830,10 +830,10 @@ Add a new sources list entry to fetch the > package from, i.e. include a new apt s > Add docker-ce from arm64: > > -Create a new layer containing `conf/distro/docker-stretch.list` with > the following content: +Create a new layer containing > `conf/distro/docker-buster.list` with the following content: > ``` > -deb [arch=arm64] https://download.docker.com/linux/debian > stretch stable +deb [arch=arm64] > https://download.docker.com/linux/debian buster stable > ``` > Include the layer in your project. > @@ -843,11 +843,11 @@ To the local.conf add: > ``` > IMAGE_PREINSTALL += "docker-ce" > THIRD_PARTY_APT_KEYS_append = " > https://download.docker.com/linux/debian/gpg;md5sum=1afae06b34a13c1b3d9cb61a26285a15" > -DISTRO_APT_SOURCES_append = " conf/distro/docker-stretch.list" > +DISTRO_APT_SOURCES_append = " conf/distro/docker-buster.list" ``` > > And build the corresponding image target: > > ``` > -bitbake multiconfig:qemuarm64-stretch:isar-image-base > +bitbake multiconfig:qemuarm64-buster:isar-image-base > ``` > diff --git a/meta-isar/conf/conf-notes.txt > b/meta-isar/conf/conf-notes.txt index ae9611e..74df97c 100644 > --- a/meta-isar/conf/conf-notes.txt > +++ b/meta-isar/conf/conf-notes.txt > @@ -1,4 +1,4 @@ > Common targets are: > - multiconfig:qemuarm-stretch:isar-image-base > - multiconfig:qemuamd64-stretch:isar-image-base > + multiconfig:qemuarm-buster:isar-image-base > + multiconfig:qemuamd64-buster:isar-image-base > multiconfig:rpi-stretch:isar-image-base