public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
	"quirin.gylstorff@siemens.com" <quirin.gylstorff@siemens.com>
Subject: Re: [PATCH] image-tools-extension: Limit IMAGER_BUILD_DEPS to do_image_tools task
Date: Thu, 16 Oct 2025 14:41:25 +0000	[thread overview]
Message-ID: <336625dcdad7e66cd9798300b845cfac336b5a8d.camel@siemens.com> (raw)
In-Reply-To: <143fcb5c-c8bb-4292-8cf8-760fa366020f@siemens.com>

On Sun, 2025-08-17 at 18:20 +0200, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> There is no reason to let the rootfs_install task wait for imager build
> dependencies. This also avoid rebuilding the rootfs if only an imager
> dependency was updated.

Hi, this patch breaks the swupdate (:swu) image type in isar-cip-core.

While I was not able to locate the root cause, I checked that the
swupdate.inc correctly appends the needed dependencies to
IMAGER_BUILD_DEPS:swu. Also, I saw that the packages never appear in
do_image_tools[depends]. Where they get lost remains unclear.

To debug this, I recommend to just look at the dependency graph
(bitbake -g cip-core-image, grep task-depends.dot "...").

Best regards,
Felix

> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>  meta/classes/image-tools-extension.bbclass | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/classes/image-tools-extension.bbclass b/meta/classes/image-tools-extension.bbclass
> index e8ace8f5..5e248f2e 100644
> --- a/meta/classes/image-tools-extension.bbclass
> +++ b/meta/classes/image-tools-extension.bbclass
> @@ -1,5 +1,5 @@
>  # This software is a part of ISAR.
> -# Copyright (C) Siemens AG, 2019
> +# Copyright (C) Siemens AG, 2019-2024
>  #
>  # SPDX-License-Identifier: MIT
>  #
> @@ -9,7 +9,11 @@ inherit sbuild
>  
>  IMAGER_INSTALL ??= ""
>  IMAGER_BUILD_DEPS ??= ""
> -DEPENDS += "${IMAGER_BUILD_DEPS}"
> +
> +python() {
> +    for dep in d.getVar('IMAGER_BUILD_DEPS').split():
> +        d.appendVarFlag('do_image_tools', 'depends', ' ' + dep + ':do_deploy_deb')
> +}
>  
>  SCHROOT_MOUNTS = "${WORKDIR}:${PP_WORK} ${IMAGE_ROOTFS}:${PP_ROOTFS} ${DEPLOY_DIR_IMAGE}:${PP_DEPLOY}"
>  SCHROOT_MOUNTS += "${REPO_ISAR_DIR}/${DISTRO}:/isar-apt"
> -- 
> 2.43.0
> 
> -- 
> You received this message because you are subscribed to the Google Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/isar-users/143fcb5c-c8bb-4292-8cf8-760fa366020f%40siemens.com.

-- 
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/336625dcdad7e66cd9798300b845cfac336b5a8d.camel%40siemens.com.

  parent reply	other threads:[~2025-10-16 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-17 16:20 'Jan Kiszka' via isar-users
2025-09-12  9:16 ` Anton Mikanovich
2025-10-16 14:41 ` 'MOESSBAUER, Felix' via isar-users [this message]
2025-10-16 15:58   ` 'Jan Kiszka' via isar-users

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=336625dcdad7e66cd9798300b845cfac336b5a8d.camel@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=quirin.gylstorff@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