Re: [PATCH] meta: Drop Debian Buster support

[Zhihang Wei <wzh@ilbers.de>]

On 3/5/26 18:02, MOESSBAUER, Felix wrote:
> On Thu, 2026-03-05 at 17:45 +0100, Zhihang Wei wrote:
>> On 8/8/24 09:07, 'Jan Kiszka' via isar-users wrote:
>>> On 08.08.24 09:04, Uladzimir Bely wrote:
>>>> On Tue, 2024-08-06 at 17:27 +0300, Anton Mikanovich wrote:
>>>>> As Debian Buster became EOL from 30th June 2024, remove its support
>>>>> as
>>>>> target and host distro in Isar.
>>>>> Update documentation to be aligned with those changes.
>>>>>
>>>>> Signed-off-by: Anton Mikanovich<amikan@ilbers.de>
>>>>> ---
>>>>>
>>>> It would be better not to remove buster efi/pcbios boot tests but
>>>> change them to bookworm.
>>>>
>>> As pointed out, it would be better to NOT remove buster at all because
>>> it is still alive. Reduce testing, and if we can build buster with
>>> bookworm host, host removal is fine as well. But buster images may still
>>> live and be built.
>>>
>>> Jan
>>>
>> What should we do about Buster support now?
>>
>> With da17d920 we patched BitBake to keep it compatible with Debian
>> Buster. BitBake 2.8 requires Python ≥ 3.8, but Debian Buster only
>> provides Python 3.7.3.
>>
>> This patch is required not only when building on a Buster host, but
>> also when building Buster targets. In do_image_wic, BitBake chroots
>> into the target rootfs to create the image. The Python version from
>> Buster rootfs is used.
> Oops... I missed that wic is executed inside the chroot. We can try to
> apply the same patch and hope that code path requiring 3.8 is traversed
> (as before).
>
> But it is anyways rather suboptimal to execute wic inside the chroot.
> Changing this is out of scope for now, but with the current design we
> either can't safely update bitbake (even a stable branch) or we will
> lose distro support from time to time.
>
>> Felix's patchset "Update bitbake to 2.8.1" reverts the patches to
>> BitBake and updates BitBake from 2.8.0 to 2.8.1. This would remove our
>> current workaround for Buster compatibility.
> Does the CI pass if we just re-apply your patch?
> We definitely need bitbake 2.8.1 to support Python 3.14, so eventually
> we have to update.
>
> Felix
I'll move the discussion to the "Update bitbake to 2.8.1" thread.

Zhihang

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/a70a979f-9a70-4212-92ce-88f2415c486c%40ilbers.de.