* Re: [yocto-patches] [meta-rockchip][PATCH] rauc-conf: set arch to machine
[not found] <1828187512D580A8.767@lists.yoctoproject.org>
@ 2025-02-28 13:30 ` Trevor Woerner
0 siblings, 0 replies; 2+ messages in thread
From: Trevor Woerner @ 2025-02-28 13:30 UTC (permalink / raw)
To: yocto-patches
On Thu 2025-02-27 @ 09:55:29 AM, Trevor Woerner via lists.yoctoproject.org wrote:
> Since this bbappend is modifying the rauc config file with a MACHINE-specific
> search-and-replace, the architecture setting of the package needs to be
> MACHINE-specific as well. Otherwise if multiple images are built for the same
> SoC, the sstate mechanism will use the first-built SoC copy of the
> rauc/system.conf file, which may or may not match this device's MACHINE
> setting.
>
> At runtime this leads to compatible mismatch issues:
>
> # rauc install <bundle>
> ...
> LastError: Compatible mismatch: Expected 'nanopi-r2s' but bundle manifest has 'rock-pi-e'
>
> These errors can be worked around by using the "--ignore-compatible" cmdline
> switch to the "rauc install" command. Or can be fixed by updating the
> on-device /etc/rauc/system.conf file and restarting the rauc.service systemd
> service unit. This patch, however, is the more correct, build-time, fix,
> rather than having to fix the issue at run-time.
>
> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> ---
> .../rk-rauc-demo/recipes-core/rauc/rauc-conf.bbappend | 2 ++
> 1 file changed, 2 insertions(+)
Applied to meta-rockchip; branches: master, and scarthgap
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [yocto-patches] [meta-rockchip][PATCH] rauc-conf: set arch to machine
2025-02-27 14:55 Trevor Woerner
@ 2025-02-28 13:46 ` Quentin Schulz
0 siblings, 0 replies; 2+ messages in thread
From: Quentin Schulz @ 2025-02-28 13:46 UTC (permalink / raw)
To: yocto-patches
Hi Trevor,
On 2/27/25 3:55 PM, Trevor Woerner via lists.yoctoproject.org wrote:
> Since this bbappend is modifying the rauc config file with a MACHINE-specific
> search-and-replace, the architecture setting of the package needs to be
> MACHINE-specific as well. Otherwise if multiple images are built for the same
> SoC, the sstate mechanism will use the first-built SoC copy of the
> rauc/system.conf file, which may or may not match this device's MACHINE
> setting.
>
> At runtime this leads to compatible mismatch issues:
>
> # rauc install <bundle>
> ...
> LastError: Compatible mismatch: Expected 'nanopi-r2s' but bundle manifest has 'rock-pi-e'
>
Uuuuuuuuh, that sounds very odd. The sstate-cache should be invalidated
because MACHINE differs in the do_install:prepend:rk-rauc-demo task no?
Can you check if MACHINE makes it to the sstate-cache? It could be that
somehow BitBake doesn't detect it should be monitoring changes for
MACHINE and invalidate the cache for that?
I guess we could also add MACHINE to do_install[vardeps] only when
rk-rauc-demo feature is selected?
In any case, making the package MACHINE_ARCH specific is the good thing
to do, though... maybe we want to make it happen only when rk-rauc-demo
feature is enabled otherwise including this layer even for non-Rockchip
machines (or when rk-rauc-demo feature is not selected) will still make
the package machine-specific?
Cheers,
Quentin
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-02-28 13:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1828187512D580A8.767@lists.yoctoproject.org>
2025-02-28 13:30 ` [yocto-patches] [meta-rockchip][PATCH] rauc-conf: set arch to machine Trevor Woerner
2025-02-27 14:55 Trevor Woerner
2025-02-28 13:46 ` [yocto-patches] " Quentin Schulz
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.