From: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
"Schild, Henning" <henning.schild@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"ibr@ilbers.de" <ibr@ilbers.de>
Subject: Re: [PATCH 0/2] Fix and cover systemd-boot usage in bookworm
Date: Fri, 8 Jul 2022 08:11:20 +0000 [thread overview]
Message-ID: <3c7014aa8e43cef53c82d6d047f31d9ffb014837.camel@siemens.com> (raw)
In-Reply-To: <3861e17a-694a-a9f8-b6ab-4e5b6a2a47a3@ilbers.de>
On Fri, 2022-07-08 at 11:07 +0300, Anton Mikanovich wrote:
> 08.07.2022 10:57, Bezdeka, Florian wrote:
> > Willing to give it a try... But as Henning already mentioned patch 1
> > was lost somewhere...
> It looks like Google Groups issue, because there are all 3 mails on
> maillist.
Nope... It did not make it into my inbox and I can't find it in the
archive (google groups) as well. Coverletter and 2/2 made it.
Please resend.
> Anyway, here are declarations I've used there:
>
> SYSTEMD_BOOTLOADER_INSTALL = "systemd"
> SYSTEMD_BOOTLOADER_INSTALL_debian-bookworm = "systemd-boot"
>
> We can't just use 'systemd < 251 | systemd-boot' syntax in direct apt-get
> install calls, but maybe the way of installing imager deps can be
> rebuild later
> to use more flexible dependencies syntax.
next prev parent reply other threads:[~2022-07-08 8:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 14:18 Anton Mikanovich
2022-07-07 14:18 ` [PATCH 1/2] meta: introduce systemd-boot dependency variable Anton Mikanovich
2022-07-08 8:31 ` Anton Mikanovich
2022-07-08 8:32 ` Anton Mikanovich
2022-07-07 14:18 ` [PATCH 2/2] meta-isar: enable systemd-boot for qemuarm-bookworm Anton Mikanovich
2022-07-08 8:48 ` Henning Schild
2022-07-08 11:04 ` Jan Kiszka
2022-07-12 13:08 ` Anton Mikanovich
2022-07-07 15:50 ` [PATCH 0/2] Fix and cover systemd-boot usage in bookworm Henning Schild
2022-07-08 7:57 ` Bezdeka, Florian
2022-07-08 8:07 ` Anton Mikanovich
2022-07-08 8:11 ` Bezdeka, Florian [this message]
2022-07-08 8:23 ` Bezdeka, Florian
2022-07-08 8:28 ` Anton Mikanovich
2022-07-08 8:49 ` Henning Schild
2022-07-08 8:44 ` Henning Schild
2022-07-08 9:01 ` Baurzhan Ismagulov
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=3c7014aa8e43cef53c82d6d047f31d9ffb014837.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=amikan@ilbers.de \
--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