public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <ankur.tyagi85@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][whinlatter][PATCH] barebox/barebox-tools: upgrade 2025.09.0 -> 2025.09.3
Date: Wed, 15 Apr 2026 23:05:05 +0200	[thread overview]
Message-ID: <DHU1874ATB71.203BIG61AS590@smile.fr> (raw)
In-Reply-To: <20260408000932.10450-1-ankur.tyagi85@gmail.com>

On Wed Apr 8, 2026 at 2:09 AM CEST, Ankur Tyagi via lists.openembedded.org wrote:
> From: Ankur Tyagi <ankur.tyagi85@gmail.com>
>
> 2025.09.3
> ---------
> Fixed FIT image vulnerability
> https://lore.barebox.org/barebox/abljJRMecNdejSD0@pengutronix.de/
>
> Changelog:
> https://github.com/barebox/barebox/compare/v2025.09.2...v2025.09.3
>
> 2025.09.2
> ---------
> Changelog:
> https://github.com/barebox/barebox/compare/v2025.09.1...v2025.09.2
>
> 2025.09.1
> ---------
> This stable release is specifically targeted at whinlatter which is
> currently at v2025.09.0
> https://lore.barebox.org/barebox/aUkaSKDePHF8__LB@pengutronix.de/
>
> Changelog:
> https://github.com/barebox/barebox/compare/v2025.09.0...v2025.09.1
>
> Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>

I'm a bit torn on this one. Because on one hand, this looks like a
proper stable branch (and I appreciate the effort), but on the other
hand, there are changes that I find too risky:
For example:
* API Change: https://github.com/barebox/barebox/commit/5e9f709b2b56bd9689e174572ef2af59b9fed5d2
* New feature: https://github.com/barebox/barebox/compare/v2025.09.0...v2025.09.3#diff-2dd6d3e4c91931c982f091155a47dd8d03e26731f8d59b112e938508fe12255aR1

Thoughts?

In the meantime, I will keep it in my branch for awareness.

> ---
>  meta/recipes-bsp/barebox/barebox-common.inc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-bsp/barebox/barebox-common.inc b/meta/recipes-bsp/barebox/barebox-common.inc
> index e41d0858fd..91865b4d44 100644
> --- a/meta/recipes-bsp/barebox/barebox-common.inc
> +++ b/meta/recipes-bsp/barebox/barebox-common.inc
> @@ -3,6 +3,6 @@ SECTION = "bootloaders"
>  
>  LIC_FILES_CHKSUM = "file://COPYING;md5=f5125d13e000b9ca1f0d3364286c4192"
>  
> -PV = "2025.09.0"
> +PV = "2025.09.3"
>  SRC_URI = "https://barebox.org/download/barebox-${PV}.tar.bz2"
> -SRC_URI[sha256sum] = "7df1aa47bb7bf1763a729137ac773e69a4052812af094475d739fc63a9295f0d"
> +SRC_URI[sha256sum] = "e87eb863cbe45e4f5af8930825c8f6e20c02b82451e9e1125ea1c73c1fb49a87"


-- 
Yoann Congal
Smile ECS



  reply	other threads:[~2026-04-15 21:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08  0:09 [OE-core][whinlatter][PATCH] barebox/barebox-tools: upgrade 2025.09.0 -> 2025.09.3 ankur.tyagi85
2026-04-15 21:05 ` Yoann Congal [this message]
2026-04-16 11:34   ` Ahmad Fatoum
2026-04-16 13:40     ` Yoann Congal
2026-04-16 15:45       ` Ahmad Fatoum

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=DHU1874ATB71.203BIG61AS590@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=ankur.tyagi85@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox