From: Jan Kiszka <jan.kiszka@siemens.com>
To: Jonas Reindl <jonas.reindl@kilobaser.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: Rapios Wic Image
Date: Thu, 10 Mar 2022 08:30:15 +0100 [thread overview]
Message-ID: <15b94400-524a-55fc-2441-a99231878256@siemens.com> (raw)
In-Reply-To: <8b0abbf9-0be1-f112-4a2d-893fd29ce9cf@kilobaser.com>
On 09.03.22 19:57, Jonas Reindl wrote:
> Hey everyone,
>
> I'm currently trying to build a raspios image as "wic-img" and get a
> python import error.
>
> kas-version: 3.0.2
>
> isar-version: 0.8
>
> I'm using kas-container to build the images with multiconfig for that.
>
> ```
>
> MACHINE ?= "rpi-arm"
> DISTRO ?= "raspios-bullseye"
>
> IMAGE_FSTYPES = "wic-img"
>
> ```
>
> Error:
>
> Exception: bb.process.ExecutionError: Execution of
> '/build/tmp/work/raspios-bullseye-armhf/my-image-base-rpi-arm-wic-img/1.0-r0/temp/run.generate_wic_image.285'
> failed with exit code 1:
> Traceback (most recent call last):
> File "/work/layers/isar/scripts/wic", line 27, in <module>
> from distutils import spawn
> ImportError: cannot import name 'spawn' from 'distutils'
> (/usr/lib/python3.9/distutils/__init__.py)
> WARNING: exit code 1 from a shell command.
>
> If I enter the build environment with the kas shell and execute python3
> I'm able to import spawn. I also rebuild the docker container to
> explicitly include python3-distutils. Maybe I misunderstood something,
> but I don't know how I should further debug that.
kas-isar:3.0.2 container python3-distutils already. So that is not the
issue. It may rather come from some missing
WIC_IMAGER_INSTALL += "python3-distutils"
for your raspios-bullseye distro config. Compare that to regular
debian-bullseye.conf - or include that if it fits.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-03-10 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 18:57 Jonas Reindl
2022-03-10 7:30 ` Jan Kiszka [this message]
2022-03-10 8:04 ` Henning Schild
2022-03-14 13:59 ` Jonas Reindl
2022-03-14 14:58 ` Jan Kiszka
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=15b94400-524a-55fc-2441-a99231878256@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jonas.reindl@kilobaser.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