From mboxrd@z Thu Jan  1 00:00:00 1970
Delivery-date: Mon, 09 Dec 2024 09:43:14 +0100
Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104])
	by lore.white.stw.pengutronix.de with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <rauc-bounces+lore=lore.pengutronix.de@pengutronix.de>)
	id 1tKZMH-005u32-26
	for lore@lore.pengutronix.de;
	Mon, 09 Dec 2024 09:43:14 +0100
Received: from localhost ([127.0.0.1] helo=metis.whiteo.stw.pengutronix.de)
	by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92)
	(envelope-from <rauc-bounces@pengutronix.de>)
	id 1tKZMH-0002kW-P6; Mon, 09 Dec 2024 09:43:13 +0100
Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2])
 by metis.whiteo.stw.pengutronix.de with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92)
 (envelope-from <jlu@pengutronix.de>)
 id 1tKZM7-0002kL-KI; Mon, 09 Dec 2024 09:43:03 +0100
Received: from ptz.office.stw.pengutronix.de ([2a0a:edc0:0:900:1d::77])
 by drehscheibe.grey.stw.pengutronix.de with esmtps (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96)
 (envelope-from <jlu@pengutronix.de>) id 1tKZM6-002Tlv-1U;
 Mon, 09 Dec 2024 09:43:03 +0100
Received: from localhost ([127.0.0.1])
 by ptz.office.stw.pengutronix.de with esmtp (Exim 4.96)
 (envelope-from <jlu@pengutronix.de>) id 1tKZM7-0007Kd-07;
 Mon, 09 Dec 2024 09:43:03 +0100
Message-ID: <dce5a82b6f1cd9a5b15908c3af216b83f88ca864.camel@pengutronix.de>
To: Brian Hutchinson <b.hutchman@gmail.com>, rauc@pengutronix.de
Date: Mon, 09 Dec 2024 09:43:02 +0100
In-Reply-To: <CAFZh4h9tu5WLxbAnA76iZ0+R5B1Oog89xeMN4-gWuBch7OPVSQ@mail.gmail.com>
References: <CAFZh4h9tu5WLxbAnA76iZ0+R5B1Oog89xeMN4-gWuBch7OPVSQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.2 (by Flathub.org) 
MIME-Version: 1.0
Subject: Re: [RAUC] Is it possible to change the [system]compatible= string
 after it has already been set/flashed?
X-BeenThere: rauc@pengutronix.de
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RAUC Project - Discussion List <rauc.pengutronix.de>
List-Unsubscribe: <https://metis.pengutronix.de/mailman/options/rauc>,
 <mailto:rauc-request@pengutronix.de?subject=unsubscribe>
List-Archive: <https://metis.pengutronix.de/mailman/private/rauc/>
List-Post: <mailto:rauc@pengutronix.de>
List-Help: <mailto:rauc-request@pengutronix.de?subject=help>
List-Subscribe: <https://metis.pengutronix.de/mailman/listinfo/rauc>,
 <mailto:rauc-request@pengutronix.de?subject=subscribe>
From: =?utf-8?q?Jan_L=C3=BCbbe_via_RAUC?= <rauc@pengutronix.de>
Reply-To: Jan =?ISO-8859-1?Q?L=FCbbe?= <jlu@pengutronix.de>
Sender: "RAUC" <rauc-bounces@pengutronix.de>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: rauc-bounces@pengutronix.de
X-SA-Exim-Scanned: No (on metis.whiteo.stw.pengutronix.de); SAEximRunCond expanded to false

Hi again,

On Thu, 2024-12-05 at 22:38 -0500, Brian Hutchinson via RAUC wrote:
> This almost feels like the intermediate update that's necessary with
> changing rauc versions ...

Enrico pointed me to this part.

Updating RAUC versions normally does *not* require an intermediate
update. An intermediate update is only needed if you explicitly create
bundles which use new features:
https://rauc.readthedocs.io/en/latest/basic.html#forward-and-backward-compa=
tibility

Regards,
Jan
--=20
Pengutronix e.K.                        |                             |
Steuerwalder Str. 21                    | https://www.pengutronix.de/ |
31137 Hildesheim, Germany               | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686        | Fax:   +49-5121-206917-5555 |