From: Henning Schild <henning.schild@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Florian Bezdeka <florian.bezdeka@siemens.com>,
Felix Moessbauer <felix.moessbauer@siemens.com>,
Henning Schild <henning.schild@siemens.com>
Subject: [PATCH v3 0/3] bump bitbake and wic for python 3.10 support
Date: Fri, 22 Apr 2022 11:05:59 +0200 [thread overview]
Message-ID: <20220422090602.21666-1-henning.schild@siemens.com> (raw)
diff to v2:
add p2 before wic bump
debian bookworm switched to python 3.10 recently, our versions of
bitbake and wic both have some issues with that new interpreter. All
these issues have been fixes in bitbake and OE, so all we need to do is
update the two tools in our tree.
v1 was send as "[PATCH] bitbake: Update to 1.50.5 release", which is p1
here, only later i found that wic also needs a bump to v2 added p2
If this series is applied we do not need "[PATCH] wic-img: use
python3.9 in bookworm", in case this one is applied before it should be
reverted after the version bumps.
Henning Schild (3):
bitbake: Update to 1.50.5 release
wic: align our fork of common.wks.inc with wic version we carry
wic: Update to the latest revision
bitbake/lib/bb/cache.py | 3 +-
bitbake/lib/bb/cooker.py | 30 +++++++-
bitbake/lib/bb/data_smart.py | 4 +-
bitbake/lib/bb/fetch2/__init__.py | 4 +
bitbake/lib/bb/fetch2/perforce.py | 2 +-
bitbake/lib/bb/fetch2/wget.py | 2 +-
bitbake/lib/bb/persist_data.py | 5 +-
bitbake/lib/bb/process.py | 2 +-
bitbake/lib/bb/runqueue.py | 34 ++++----
bitbake/lib/bb/server/process.py | 2 +-
bitbake/lib/bb/tests/fetch.py | 35 +++++----
bitbake/lib/bb/utils.py | 13 +++-
bitbake/lib/hashserv/server.py | 4 +-
bitbake/lib/toaster/tests/builds/buildtest.py | 2 +-
.../lib/wic/canned-wks/common-isar.wks.inc | 2 +-
.../wic/plugins/source/bootimg-efi-isar.py | 77 ++++++++++++++++---
.../wic/plugins/source/bootimg-pcbios-isar.py | 6 +-
scripts/lib/wic/canned-wks/common.wks.inc | 2 +-
scripts/lib/wic/canned-wks/directdisk-gpt.wks | 2 +-
scripts/lib/wic/canned-wks/mkefidisk.wks | 2 +-
scripts/lib/wic/engine.py | 6 +-
scripts/lib/wic/help.py | 10 ++-
scripts/lib/wic/ksparser.py | 8 +-
scripts/lib/wic/misc.py | 4 +-
scripts/lib/wic/partition.py | 25 ++++--
scripts/lib/wic/pluginbase.py | 8 +-
scripts/lib/wic/plugins/imager/direct.py | 11 ++-
scripts/lib/wic/plugins/source/bootimg-efi.py | 74 +++++++++++++++---
.../lib/wic/plugins/source/bootimg-pcbios.py | 6 +-
scripts/lib/wic/plugins/source/rawcopy.py | 35 ++++++++-
scripts/lib/wic/plugins/source/rootfs.py | 2 +-
scripts/wic | 9 ++-
32 files changed, 321 insertions(+), 110 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-22 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 9:05 Henning Schild [this message]
2022-04-22 9:06 ` [PATCH v3 1/3] bitbake: Update to 1.50.5 release Henning Schild
2022-04-22 9:06 ` [PATCH v3 2/3] wic: align our fork of common.wks.inc with wic version we carry Henning Schild
2022-04-22 9:06 ` [PATCH v3 3/3] wic: Update to the latest revision Henning Schild
2022-04-22 9:57 ` [PATCH v3 0/3] bump bitbake and wic for python 3.10 support Anton Mikanovich
2022-04-22 10:28 ` Henning Schild
2022-04-23 5:08 ` Anton Mikanovich
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=20220422090602.21666-1-henning.schild@siemens.com \
--to=henning.schild@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.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