From: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"Moessbauer, Felix" <felix.moessbauer@siemens.com>,
"Schild, Henning" <henning.schild@siemens.com>
Subject: Warning: bookworm support broken due to systemd packet split
Date: Wed, 6 Jul 2022 08:54:11 +0000 [thread overview]
Message-ID: <f21333903f94967c59f580a2ed557978d60a8774.camel@siemens.com> (raw)
Hi all,
when trying to update one of my internal targets from Debian bullseye
to bookworm I was surprised that the build was failing with the
following wic failure:
| Traceback (most recent call last):
| File "/work/isar/scripts/wic", line 547, in <module>
| sys.exit(main(sys.argv[1:]))
| File "/work/isar/scripts/wic", line 542, in main
| return hlp.invoke_subcommand(args, parser, hlp.wic_help_usage, subcommands)
| File "/work/isar/scripts/lib/wic/help.py", line 83, in invoke_subcommand
| subcmd[0](args, usage)
| File "/work/isar/scripts/wic", line 222, in wic_create_subcommand
| engine.wic_create(wks_file, rootfs_dir, bootimg_dir, kernel_dir,
| File "/work/isar/scripts/lib/wic/engine.py", line 190, in wic_create
| plugin.do_create()
| File "/work/isar/scripts/lib/wic/plugins/imager/direct.py", line 98, in do_create
| self.create()
| File "/work/isar/scripts/lib/wic/plugins/imager/direct.py", line 182, in create
| self._image.prepare(self)
| File "/work/isar/scripts/lib/wic/plugins/imager/direct.py", line 360, in prepare
| part.prepare(imager, imager.workdir, imager.oe_builddir,
| File "/work/isar/scripts/lib/wic/partition.py", line 183, in prepare
| plugin.do_prepare_partition(self, srcparams_dict, creator,
| File "/work/isar/meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py", line 419, in do_prepare_partition
| for mod in [x for x in os.listdir(kernel_dir) if x.startswith("systemd-")]:
| FileNotFoundError: [Errno 2] No such file or directory: '/build/tmp/work/debian-bookworm-amd64/talker-qemuamd64/1.0-r0/rootfs/usr/lib/systemd/boot/efi/'
It turns out that the systemd package is now split into different
packages, so the systemd-boot stuff that we use in the ISAR wic plugin
was moved into the systemd-boot-efi packet. With that we now have
additional dependencies. The systemd-boot stuff is no longer installed
"automatically".Debian changelog:
systemd (251.2-3) unstable; urgency=medium
systemd-boot has been split into a separate package.
This new systemd-boot package will not be installed automatically on
upgrades. If you are using systemd-boot, please install this new
package manually.
The default boot loader in Debian is grub2. If you have not set up
systemd-boot manually, no action is required on your side.
-- Michael Biebl <biebl@debian.org> Wed, 08 Jun 2022 21:49:47 +0200
Why does the ISAR CI system not report that? We should really make sure
that Debian testing / bookworm is tested properly.
How to fix that? Similar to the SYSLINUX_BOOTLOADER_INSTALL stuff but
with IMAGE_PREINSTALL instead of IMAGER_INSTALL? It's a combination of
distribution (package name) and machine configuration (WKS file
selection).
Best regards,
Florian
next reply other threads:[~2022-07-06 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 8:54 Bezdeka, Florian [this message]
2022-07-06 9:07 ` Baurzhan Ismagulov
2022-07-06 9:10 ` Henning Schild
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=f21333903f94967c59f580a2ed557978d60a8774.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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