From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6750639733816164352 X-Received: by 2002:a5d:6a02:: with SMTP id m2mr4602998wru.304.1571762181077; Tue, 22 Oct 2019 09:36:21 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:adf:9d8c:: with SMTP id p12ls9525555wre.1.gmail; Tue, 22 Oct 2019 09:36:20 -0700 (PDT) X-Google-Smtp-Source: APXvYqy968Wft6h3nmvxJXQiezgnkFycGobg+Z9TstCeKFqA+Y0GDpX4jL+MjZjRl4gHzet8ZsR/ X-Received: by 2002:adf:fec3:: with SMTP id q3mr4293588wrs.343.1571762180573; Tue, 22 Oct 2019 09:36:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571762180; cv=none; d=google.com; s=arc-20160816; b=n8Bv+pqVJBi8OBsO5iYSsL0H7vYVCeuBhGSjbWUOy+CzIhif1mUFCrJmPxDrwKBAyC M0Cgbh0/wTgUSOO9ueQTXKiqJNGpmRN6P/pMTrqrxmn62ddvI9DepNXhYfTU432cWBZI OR2+buNdcCUNYdd1Rmarnm71PY3T/gNeZtPcUBq3TtIR+rMjwZ116zutJ8kYxkKIlKRM 1t1e8VVmBSCFLTDAssICTeugvVTbyTHD2gTKUjLsXh2+Z3gG3p7oWeoRMaT02XeM2v+R 1x6VwGqrFPID//g848swh3pzN3InTWIlaML4W+foS+3blhHUk64gBSKTSAp5nOTfFfTV NFNg== 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:cc:to:from:date; bh=HR6WcmlEZ/5TQeZAP1QTRW40tBtEKjLUq7jJGH7PLek=; b=kodi6O9b3ZhBrp0CT7thk8c2lMbrsjbBHFU9w22cs/vk97fx457Q5lg+BAErOdJL9l xgDN22g4j9rGSHBK9aKvbzEZ8p7CHNpBT01Cxko/OLsYMPGmM6Ci0C2gkG1LtwvTb08r 1ZXp7Gc+UeNUAvCKFhUiqUtmxpH9F6dxeWGmUbgv100EXHR0tTfYyOdcGHMFDYYm49av I33ABr1o5PmG4CR1ANPkvwJEAEc0I6g3afeYSziNHhM2rIGdwV1x7X4SXDQpB1Q52Y0v HW7oqBh5XzI1+h8JlWN2k6m0dy2gFFWKPhIBT6DYuNafNj87wfxOYXWz6XDx+0Jlg37i u0tg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 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 david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id q3si63456wrp.5.2019.10.22.09.36.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Oct 2019 09:36:20 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x9MGaK4B003465 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 22 Oct 2019 18:36:20 +0200 Received: from md1za8fc.ad001.siemens.net ([139.25.69.254]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x9MGaKtC019029; Tue, 22 Oct 2019 18:36:20 +0200 Date: Tue, 22 Oct 2019 18:36:19 +0200 From: Henning Schild To: "[ext] Gylstorff Quirin" Cc: Subject: Re: [PATCH v2] meta: rootfs: Fix manifest generation Message-ID: <20191022183619.4ecc0033@md1za8fc.ad001.siemens.net> In-Reply-To: <28666b08-fc78-8ad3-083b-f94a345b98ce@siemens.com> References: <20191022144930.3458-1-Vijaikumar_Kangarajan@mentor.com> <20191022145336.3873-1-Vijaikumar_Kangarajan@mentor.com> <28666b08-fc78-8ad3-083b-f94a345b98ce@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: /IT5jROHaPY9 Am Tue, 22 Oct 2019 18:28:57 +0200 schrieb "[ext] Gylstorff Quirin" : > On 10/22/19 4:53 PM, vijaikumar.kanagarajan@gmail.com wrote: > > From: Vijai Kumar K > > > > finalize-rootfs task removes qemu-*-static. It is needed for > > rootfs_generate_manifest to work when HOST_ARCH != DISTRO_ARCH. > > > > Make sure a proper chroot environment is available when > > generating manifest. > > > > Signed-off-by: Vijai Kumar K > > --- > > Changes in v2: > > - Updated commit message. > > > > meta/classes/rootfs.bbclass | 20 ++++++++++---------- > > 1 file changed, 10 insertions(+), 10 deletions(-) > > > > diff --git a/meta/classes/rootfs.bbclass > > b/meta/classes/rootfs.bbclass index da66b3f..1da27ff 100644 > > --- a/meta/classes/rootfs.bbclass > > +++ b/meta/classes/rootfs.bbclass > > @@ -9,8 +9,8 @@ ROOTFS_PACKAGES ?= "" > > # available features are: > > # 'deploy-package-cache' - copy the package cache > > ${WORKDIR}/apt_cache # 'clean-package-cache' - delete package cache > > from rootfs -# 'finalize-rootfs' - delete files needed to chroot > > into the rootfs # 'generate-manifest' - generate a package manifest > > of the rootfs into ${ROOTFS_MANIFEST_DEPLOY_DIR} +# > > 'finalize-rootfs' - delete files needed to chroot into the rootfs > > ROOTFS_FEATURES ?= "" > > ROOTFS_APT_ARGS="install --yes -o Debug::pkgProblemResolver=yes" > > @@ -185,6 +185,15 @@ rootfs_postprocess_clean_package_cache() { > > sudo rm -rf "${ROOTFSDIR}/var/lib/apt/lists/"* > > } > > > > +ROOTFS_POSTPROCESS_COMMAND += > > "${@bb.utils.contains('ROOTFS_FEATURES', 'generate-manifest', > > 'rootfs_generate_manifest', '', d)}" +rootfs_generate_manifest () { > > + mkdir -p ${ROOTFS_MANIFEST_DEPLOY_DIR} > > + sudo -E chroot --userspec=$(id -u):$(id -g) '${ROOTFSDIR}' \ > > + dpkg-query -W -f \ > > + > > '${source:Package}|${source:Version}|${binary:Package}|${Version}\n' > > > \ > > + ${ROOTFS_MANIFEST_DEPLOY_DIR}/"${PF}".manifest > > +} > > + > > ROOTFS_POSTPROCESS_COMMAND += > > "${@bb.utils.contains('ROOTFS_FEATURES', 'finalize-rootfs', > > 'rootfs_postprocess_finalize', '', d)}" > > rootfs_postprocess_finalize() { sudo -s <<'EOSUDO' @@ -223,15 > > +232,6 @@ rootfs_postprocess_finalize() { EOSUDO > > } > > > > Is it possible to add a guard to finalize to check that it is the > last command in ROOTFS_POSTPROCESS_COMMAND. > > > -ROOTFS_POSTPROCESS_COMMAND += > > "${@bb.utils.contains('ROOTFS_FEATURES', 'generate-manifest', > > 'rootfs_generate_manifest', '', d)}" -rootfs_generate_manifest () { > > - mkdir -p ${ROOTFS_MANIFEST_DEPLOY_DIR} > > - sudo -E chroot --userspec=$(id -u):$(id -g) '${ROOTFSDIR}' \ > > - dpkg-query -W -f \ > > - > > '${source:Package}|${source:Version}|${binary:Package}|${Version}\n' > > > \ > > - ${ROOTFS_MANIFEST_DEPLOY_DIR}/"${PF}".manifest > > -} > > - > > do_rootfs_postprocess[vardeps] = "${ROOTFS_POSTPROCESS_COMMAND}" > > python do_rootfs_postprocess() { > > # Take care that its correctly mounted: > > > > Thanks. > > This should have been found in the CI build. > Is the CrossBuild not part of the CI configuration? Not sure whether i can see which args ci_build.sh was called with, but i quickly found a failing build of next in the CI. For those who have access: http://isar-build.org:8080/job/isar_next/488/console >> chroot: failed to run command 'dpkg-query': No such file or directory ... that is the missing qemu ... >> ERROR: mc:qemuarm64-stretch:isar-image-base-1.0-r0 >> do_rootfs_postprocess: Function failed: rootfs_generate_manifest >> (log file is located >> at /workspace/build/isar_next/488/build/tmp/work/debian-stretch-arm64/isar-image-base-qemuarm64-ext4-img/1.0-r0/temp/log.do_rootfs_postprocess.23077) Henning > Quirin >