From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: "Moessbauer,
Felix (FT RPD CED OES-DE)" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"Schmidt,
Adriaan (FT RPD CED EDC-DE)" <adriaan.schmidt@siemens.com>,
"Gylstorff,
Quirin (FT RPD CED OES-DE)" <quirin.gylstorff@siemens.com>
Subject: Re: [PATCH] image-tools-extension: Limit IMAGER_BUILD_DEPS to do_image_tools task
Date: Thu, 16 Oct 2025 17:58:49 +0200 [thread overview]
Message-ID: <cd3ee231-1b18-4a06-8f61-cc3fcbb5103b@siemens.com> (raw)
In-Reply-To: <336625dcdad7e66cd9798300b845cfac336b5a8d.camel@siemens.com>
On 16.10.25 16:41, Moessbauer, Felix (FT RPD CED OES-DE) wrote:
> 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 "...").
>
This happened to bite me today as well - only fair. I'm debugging it
right now.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
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/cd3ee231-1b18-4a06-8f61-cc3fcbb5103b%40siemens.com.
prev parent reply other threads:[~2025-10-16 15:59 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
2025-10-16 15:58 ` 'Jan Kiszka' via isar-users [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=cd3ee231-1b18-4a06-8f61-cc3fcbb5103b@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