[AUH] barebox-tools: upgrading to 2026.03.0 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe(s) *barebox-tools* to *2026.03.0* has Succeeded.

Next steps:
    - apply the patch: git am 0001-barebox-tools-upgrade-2026.01.0-2026.03.0.patch
    - check the changes to upstream patches and summarize them in the commit message,
    - compile an image that contains the package
    - perform some basic sanity tests
    - amend the patch and sign it off: git commit -s --reset-author --amend
    - send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update failures.
Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-- >8 --
From 438f0f0ffae24211eea1172ab8ab5a734f317b94 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@yoctoproject.org>
Date: Sun, 15 Mar 2026 06:01:23 +0000
Subject: [PATCH] barebox-tools: upgrade 2026.01.0 -> 2026.03.0

---
 meta/recipes-bsp/barebox/barebox-common.inc   |  4 +-
 meta/recipes-bsp/barebox/barebox-tools.bb     |  2 -
 ...x-tools-fix-glibc-2.43-openat2-build.patch | 43 -------------------
 3 files changed, 2 insertions(+), 47 deletions(-)
 delete mode 100644 meta/recipes-bsp/barebox/files/0001-barebox-tools-fix-glibc-2.43-openat2-build.patch

On 15-03-2026 07:11 pm, Auto Upgrade Helper via lists.openembedded.org 
wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> Hello,
>
> this email is a notification from the Auto Upgrade Helper
> that the automatic attempt to upgrade the recipe(s) *barebox-tools* to *2026.03.0* has Succeeded.
>
> Next steps:
>      - apply the patch: git am 0001-barebox-tools-upgrade-2026.01.0-2026.03.0.patch
>      - check the changes to upstream patches and summarize them in the commit message,
>      - compile an image that contains the package
>      - perform some basic sanity tests
>      - amend the patch and sign it off: git commit -s --reset-author --amend
>      - send it to the appropriate mailing list
Hi ,

The recipe currently carries a local patch added for a glibc 2.43 build 
issue (which is anyway dropped in this AUH update).
Will this upgrade be taken automatically, or should we prepare and send 
the upgrade patch?
> Alternatively, if you believe the recipe should not be upgraded at this time,
> you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
> automatic upgrades would no longer be attempted.
>
> Please review the attached files for further information and build/update failures.
> Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
>
> Regards,
> The Upgrade Helper
>
> -- >8 --
>  From 438f0f0ffae24211eea1172ab8ab5a734f317b94 Mon Sep 17 00:00:00 2001
> From: Upgrade Helper <auh@yoctoproject.org>
> Date: Sun, 15 Mar 2026 06:01:23 +0000
> Subject: [PATCH] barebox-tools: upgrade 2026.01.0 -> 2026.03.0
>
> ---
>   meta/recipes-bsp/barebox/barebox-common.inc   |  4 +-
>   meta/recipes-bsp/barebox/barebox-tools.bb     |  2 -
>   ...x-tools-fix-glibc-2.43-openat2-build.patch | 43 -------------------
>   3 files changed, 2 insertions(+), 47 deletions(-)
>   delete mode 100644 meta/recipes-bsp/barebox/files/0001-barebox-tools-fix-glibc-2.43-openat2-build.patch
>
> diff --git a/meta/recipes-bsp/barebox/barebox-common.inc b/meta/recipes-bsp/barebox/barebox-common.inc
> index 14a5ca9709..17cfc25692 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 = "2026.01.0"
> +PV = "2026.03.0"
>   SRC_URI = "https://barebox.org/download/barebox-${PV}.tar.bz2"
> -SRC_URI[sha256sum] = "219283d67c5d2f79bd22915b8a71906531223cb01e6e5b8d1658f299441e4169"
> +SRC_URI[sha256sum] = "760f22ff34ca00539d29826cce07d83210e41ebb51266616c6969b855c099bc2"
> diff --git a/meta/recipes-bsp/barebox/barebox-tools.bb b/meta/recipes-bsp/barebox/barebox-tools.bb
> index 1459f48db2..eb327306d9 100644
> --- a/meta/recipes-bsp/barebox/barebox-tools.bb
> +++ b/meta/recipes-bsp/barebox/barebox-tools.bb
> @@ -2,8 +2,6 @@ SUMMARY = "barebox bootloader tools"
>
>   require barebox-common.inc
>
> -SRC_URI += "file://0001-barebox-tools-fix-glibc-2.43-openat2-build.patch"
> -
>   LICENSE = "GPL-2.0-only"
>
>   DEPENDS = "bison-native flex-native libusb1"
> diff --git a/meta/recipes-bsp/barebox/files/0001-barebox-tools-fix-glibc-2.43-openat2-build.patch b/meta/recipes-bsp/barebox/files/0001-barebox-tools-fix-glibc-2.43-openat2-build.patch
> deleted file mode 100644
> index 2ff7cb82a6..0000000000
> --- a/meta/recipes-bsp/barebox/files/0001-barebox-tools-fix-glibc-2.43-openat2-build.patch
> +++ /dev/null
> @@ -1,43 +0,0 @@
> -barebox-tools: fix build failure with glibc 2.43
> -
> -glibc 2.43 introduces linux/openat2.h through the fcntl include chain
> -(bits/fcntl-linux.h -> linux/openat2.h). This header expects the
> -__u64 type to be defined before inclusion.
> -
> -In barebox scripts/include/linux/types.h the header <fcntl.h> was
> -included before the __u64 typedef, causing build failures such as:
> -
> -  linux/openat2.h:20:9: error: unknown type name '__u64'
> -
> -Move the inclusion of <fcntl.h> after the typedef definitions so that
> -__u64 and related types are defined before linux/openat2.h is parsed.
> -
> -Upstream-Status: Pending
> -
> -Signed-off-by: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
> ----
> -
> - scripts/include/linux/types.h | 3 ++-
> - 1 file changed, 2 insertions(+), 1 deletion(-)
> -
> -diff --git a/scripts/include/linux/types.h b/scripts/include/linux/types.h
> -index 5b01333..33cea19 100644
> ---- a/scripts/include/linux/types.h
> -+++ b/scripts/include/linux/types.h
> -@@ -4,7 +4,6 @@
> - #include <stdbool.h>
> - #include <stddef.h>
> - #include <stdint.h>
> --#include <fcntl.h>
> -
> - typedef uint64_t __u64;
> - typedef int64_t __s64;
> -@@ -15,6 +14,8 @@ typedef int16_t __s16;
> - typedef uint8_t __u8;
> - typedef int8_t __s8;
> -
> -+#include <fcntl.h>
> -+
> - #ifndef __linux__
> - typedef long long loff_t;
> - #endif
> --
> 2.47.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#233128): https://lists.openembedded.org/g/openembedded-core/message/233128
> Mute This Topic: https://lists.openembedded.org/mt/118327905/10244482
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [Hemanth.KumarMD@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

On Mon, 16 Mar 2026 at 12:03, Hemanth Kumar M D via
lists.openembedded.org
<Hemanth.KumarMD=windriver.com@lists.openembedded.org> wrote:
> The recipe currently carries a local patch added for a glibc 2.43 build
> issue (which is anyway dropped in this AUH update).
> Will this upgrade be taken automatically, or should we prepare and send
> the upgrade patch?

You should take the auh patch and follow the instructions above to
re-send it from yourself. AUH patches are not taken automatically, as
they're made by a bot. They're meant as a starting point for anyone
interested in that particular upgrade. Sometimes, resetting the author
to yourself and adding s-o-b, and then saying in commit message that
the removed recipe patch has been merged upstream is all you need to
do (the above update patch seems to be of that kind).

Alex