From: "'Clara Kowalsky' via isar-users" <isar-users@googlegroups.com>
To: Anton Mikanovich <amikan@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 0/4] BitBake update in Isar - part 1
Date: Wed, 4 Nov 2026 10:46:54 +0100 [thread overview]
Message-ID: <2ce9f35b-efb4-4487-bd57-4ff4d7eb34fa@siemens.com> (raw)
In-Reply-To: <419696e8-cda9-4cec-803a-e3ac5386d1ba@ilbers.de>
On 11/4/26 10:32, Anton Mikanovich wrote:
> Hello Clara,
>
> Bitbake was not updated for a long time for the reason.
> Newer Bitbake releases are using "valid_signals" call which was
> introduced in
> Python 3.8, but Isar still support building Buster with Python 3.7 only.
>
> Did you fix Buster compatibility somehow?
Yes, I fixed the Buster issue where WIC ran inside Buster's imaging
chroot and imported BitBake. I have a commit that moves WIC to the build
host's Python and leaves only imaging utilities in the chroot. I tested
it extensively in the testsuite for Buster and newer targets + newest
BitBake.
Regarding these first patches, I wanted to get some feedback on those
first before sending the rest of the patches to not have too many
changes at once.
Clara
>
> 04.11.2026 11:22, 'Clara Kowalsky' via isar-users wrote:
>> These are first commits for preparing the update of BitBake in Isar.
>> Currently, BitBake v2.8.0 is used, which is very outdated. The goal is
>> to update to v2.20.0, which is the latest release.
>>
>> Clara Kowalsky (4):
>> base: replace BitBake's outdated persist_data
>> isar-events: preserve cleanup for default multiconfig
>> isar-events: close /proc/mounts after cleanup
>> meta: migrate fetcher references to bb.fetch
>>
>> meta/classes-global/base.bbclass | 39 +++++---
>> meta/classes-global/isar-events.bbclass | 48 +++++----
>> meta/classes-global/sstate.bbclass | 14 +--
>> meta/classes-recipe/bootstrap.bbclass | 4 +-
>> meta/classes-recipe/dpkg-base.bbclass | 6 +-
>> meta/classes-recipe/dpkg.bbclass | 2 +-
>> meta/conf/bitbake.conf | 6 +-
>> meta/lib/aptsrc_fetcher.py | 8 +-
>> meta/lib/container_fetcher.py | 12 +--
>> meta/lib/oe/patch.py | 10 +-
>> meta/recipes-devtools/base-apt/base-apt.bb | 2 +-
>> testsuite/unittests/test_build_uuid.py | 107 +++++++++++++++++++++
>> 12 files changed, 188 insertions(+), 70 deletions(-)
>> create mode 100644 testsuite/unittests/test_build_uuid.py
>>
>
--
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/2ce9f35b-efb4-4487-bd57-4ff4d7eb34fa%40siemens.com.
next prev parent reply other threads:[~2026-11-04 9:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 9:22 'Clara Kowalsky' via isar-users
2026-11-04 9:22 ` [PATCH 1/4] base: replace BitBake's outdated persist_data 'Clara Kowalsky' via isar-users
2026-11-04 9:22 ` [PATCH 2/4] isar-events: preserve cleanup for default multiconfig 'Clara Kowalsky' via isar-users
2026-11-04 9:22 ` [PATCH 3/4] isar-events: close /proc/mounts after cleanup 'Clara Kowalsky' via isar-users
2026-11-04 9:22 ` [PATCH 4/4] meta: migrate fetcher references to bb.fetch 'Clara Kowalsky' via isar-users
2026-11-04 9:32 ` [PATCH 0/4] BitBake update in Isar - part 1 Anton Mikanovich
2026-11-04 9:46 ` 'Clara Kowalsky' via isar-users [this message]
2026-11-04 13:14 ` 'Moessbauer, Felix' 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=2ce9f35b-efb4-4487-bd57-4ff4d7eb34fa@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=clara.kowalsky@siemens.com \
/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