public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"ubely@ilbers.de" <ubely@ilbers.de>,
	"amikan@ilbers.de" <amikan@ilbers.de>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>,
	"wzh@ilbers.de" <wzh@ilbers.de>
Subject: Re: [PATCH] meta: Drop Debian Buster support
Date: Thu, 5 Mar 2026 17:02:15 +0000	[thread overview]
Message-ID: <8427526371e4ee0b43ba7f55da57c474199c5d1b.camel@siemens.com> (raw)
In-Reply-To: <c7fc8caa-ad60-43df-beb7-0c4611f6327a@ilbers.de>

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

> 
> Zhihang

-- 
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany

-- 
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/8427526371e4ee0b43ba7f55da57c474199c5d1b.camel%40siemens.com.

  reply	other threads:[~2026-03-05 17:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 14:27 Anton Mikanovich
2024-08-06 14:43 ` 'Jan Kiszka' via isar-users
2024-08-08  7:04 ` Uladzimir Bely
2024-08-08  7:07   ` 'Jan Kiszka' via isar-users
2026-03-05 16:45     ` Zhihang Wei
2026-03-05 17:02       ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-03-06 10:10         ` Zhihang Wei
2026-03-05 17:23       ` 'Jan Kiszka' via isar-users

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=8427526371e4ee0b43ba7f55da57c474199c5d1b.camel@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=ubely@ilbers.de \
    --cc=wzh@ilbers.de \
    /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