All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: yocto-patches@lists.yoctoproject.org
Subject: Re: [yocto-patches] [meta-rockchip][PATCH] rauc-conf: set arch to machine
Date: Fri, 28 Feb 2025 08:30:28 -0500	[thread overview]
Message-ID: <20250228133028.GA1093@localhost> (raw)
In-Reply-To: <1828187512D580A8.767@lists.yoctoproject.org>

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


       reply	other threads:[~2025-02-28 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1828187512D580A8.767@lists.yoctoproject.org>
2025-02-28 13:30 ` Trevor Woerner [this message]
2025-02-27 14:55 [meta-rockchip][PATCH] rauc-conf: set arch to machine Trevor Woerner
2025-02-28 13:46 ` [yocto-patches] " Quentin Schulz

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=20250228133028.GA1093@localhost \
    --to=twoerner@gmail.com \
    --cc=yocto-patches@lists.yoctoproject.org \
    /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.