From: Rasmus Villemoes <ravi@prevas.dk>
To: openembedded-core@lists.openembedded.org
Cc: Yoann Congal <yoann.congal@smile.fr>,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [wrynose][PATCH] image-buildinfo.bbclass: add missing vardeps to buildinfo_target function
Date: Fri, 20 Nov 2026 12:01:54 +0100 [thread overview]
Message-ID: <877bi76a1p.fsf@prevas.dk> (raw)
In-Reply-To: <18E6FCC35BB16260.822248@lists.openembedded.org>
On Wed, Nov 11 2026, "Rasmus Villemoes via openembedded-core" <rasmus.villemoes=prevas.dk@lists.openembedded.org> wrote:
> From: Rasmus Villemoes <ravi@prevas.dk>
>
> Bitbake does see that buildinfo_target depends on the value of
> ${IMAGE_BUILDINFO_VARS} itself. So adding an element to that list does
> cause do_rootfs to run again.
>
> But bitbake does not know that the value is a list of variable names
> whose values are fetched, so changing one of the mentioned variables
> does not guarantee that do_rootfs gets re-run.
>
> Fix that by adding all the ${IMAGE_BUILDINFO_VARS} as [vardeps] for
> buildinfo_target.
>
> Signed-off-by: Rasmus Villemoes <ravi@prevas.dk>
> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> (cherry picked from commit 69543bcbcebef81e2797a0cf5662602876998ca4)
Hi Yoann
Please consider adding this one to the wrynose queue, it is quite
similar to 99cab65285 so I believe it should be eligible.
Thanks,
Rasmus
parent reply other threads:[~2026-11-20 11:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <18E6FCC35BB16260.822248@lists.openembedded.org>]
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=877bi76a1p.fsf@prevas.dk \
--to=ravi@prevas.dk \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=yoann.congal@smile.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.