public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Schild, Henning" <henning.schild@siemens.com>
Cc: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
	"ibr@ilbers.de" <ibr@ilbers.de>,
	"Moessbauer, Felix" <felix.moessbauer@siemens.com>
Subject: Re: [PATCH v2 0/2] bump bitbake and wic for python 3.10 support
Date: Fri, 22 Apr 2022 08:15:22 +0000	[thread overview]
Message-ID: <0a9f7251f578913b77f02e25fde17d16e031f867.camel@siemens.com> (raw)
In-Reply-To: <b2b06875-b928-1ac7-9fb8-89ec0813e534@ilbers.de>

On Fri, 2022-04-22 at 10:59 +0300, Anton Mikanovich wrote:
> 21.04.2022 11:52, Henning Schild wrote:
> > 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 (2):
> >    bitbake: Update to 1.50.5 release
> >    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 +-
> >   .../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 ++-
> >   31 files changed, 320 insertions(+), 109 deletions(-)
> 
> Thanks for update, python issue is really fixed now, but it brakes 
> qemu386 targets booting in QEMU:
> 
> 00:46:00 [   34.424136] blk_update_request: I/O error, dev fd0, sector 0
> 00:46:00 [   34.428049] floppy: error -5 while reading block 0
> 00:46:00 [   34.508133] blk_update_request: I/O error, dev fd0, sector 0
> 00:46:00 [   34.512050] floppy: error -5 while reading block 0
> 00:46:00 Gave up waiting for root file system device.  Common problems:
> 00:46:00  - Boot args (cat /proc/cmdline)
> 00:46:00    - Check rootdelay= (did the system wait long enough?)
> 00:46:00  - Missing modules (cat /proc/modules; ls /dev)
> 00:46:00 ALERT!  PARTLABEL=platform does not exist.  Dropping to a shell!
> 00:46:00 (initramfs)
> 

Might be upstream commit [1] which Henning pulled in now.

Adding Adriaan as author of this commit to CC. I have no idea why this
should break exactly this image...

[1] https://github.com/openembedded/openembedded-core/commit/2fb247c5ecf057bb96649a3c0234794b4991c050

Regards,
Florian


  reply	other threads:[~2022-04-22  8:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21  8:52 Henning Schild
2022-04-21  8:52 ` [PATCH v2 1/2] bitbake: Update to 1.50.5 release Henning Schild
2022-04-21  8:52 ` [PATCH v2 2/2] wic: Update to the latest revision Henning Schild
2022-04-21  9:02   ` Henning Schild
2022-04-22  7:59 ` [PATCH v2 0/2] bump bitbake and wic for python 3.10 support Anton Mikanovich
2022-04-22  8:15   ` Bezdeka, Florian [this message]
2022-04-22  8:26     ` Henning Schild
2022-04-22  8:52       ` Henning Schild
2022-04-22  9:54         ` Henning Schild
2022-04-22  8:27   ` Henning Schild
2022-04-22  8:57     ` 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=0a9f7251f578913b77f02e25fde17d16e031f867.camel@siemens.com \
    --to=florian.bezdeka@siemens.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=ibr@ilbers.de \
    --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