| Message ID | 010101a0ae3383f8-4170c7d7-9b47-45f8-bbb1-0835bd0e850e-000000@us-west-2.amazonses.com |
|---|---|
| State | New |
| Headers | show |
| Series | [AUH] barebox-tools: upgrading to 2026.09.0 SUCCEEDED | expand |
diff --git a/meta/recipes-bsp/barebox/barebox-common.inc b/meta/recipes-bsp/barebox/barebox-common.inc index a9f0593e27..d94798193b 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.08.0" +PV = "2026.09.0" SRC_URI = "https://barebox.org/download/barebox-${PV}.tar.bz2" -SRC_URI[sha256sum] = "5b270cbde7f2fc6a78ff6e748eef788bbc04571682e2f2e964cd15a2e009774c" +SRC_URI[sha256sum] = "491b504c8a79b5a4e30c419b824916b7329bad8abfe34987ba066bafa1fbcfc5"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *barebox-tools* to *2026.09.0* has Succeeded. Next steps: - apply the patch: git am 0001-barebox-tools-upgrade-2026.08.0-2026.09.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 a95e5df7d06ab855edca881af16656a6d79374bb Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Thu, 17 Sep 2026 05:27:17 +0000 Subject: [PATCH] barebox-tools: upgrade 2026.08.0 -> 2026.09.0 Source: Documentation/migration-guides/migration-2026.08.0.rst, Documentation/migration-guides/migration-2026.09.0.rst Release v2026.08.0 ================== global.partitions.first_usable_lba removed ------------------------------------------ The ``global.partitions.first_usable_lba`` variable has been removed. Use ``global.partitions.first_partition_offset`` instead. The new variable is a byte offset used by free-space searches for new partitions, for example ``parted mkpart_size``. The default is ``8388608`` bytes (8 MiB). To keep an old configuration, multiply the old ``first_usable_lba`` value by 512. ARCH=arm64 ---------- Use of ``ARCH=arm`` for 64-bit ARM builds is deprecated and now emits a warning. Users should change build scripts to use ``ARCH=arm64`` instead when targetting ARMv8. Removal of deprecated CONFIG_BOOTM_OPTEE ---------------------------------------- The support for late loading of OP-TEE had been deprecated and ultimately removed as it greatly increased the attack surface and was only supported on 32-bit ARM systems. OP-TEE loading is now only supported :ref:`in the prebootloader <optee_early_loading>`. For i.MX6 boards, this can be enabled by enabling ``CONFIG_FIRMWARE_IMX6_OPTEE``. sha1 no longer accepted for secure boot --------------------------------------- FIT images using sha1 are no longer accepted as secure boot images. sha1 has been proven insecure in 2017. --- meta/recipes-bsp/barebox/barebox-common.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)