public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "Bezdeka, Florian" <florian.bezdeka@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "amikan@ilbers.de" <amikan@ilbers.de>,
	"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
	"Schild, Henning" <henning.schild@siemens.com>
Subject: RE: [PATCH 0/3] systemd-boot: Locate imager deps in buildchroot
Date: Fri, 12 Aug 2022 07:17:47 +0000	[thread overview]
Message-ID: <AM9PR10MB4869B65EEC4BE97F3890536689679@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <1e4409a8f97d815fde31fb87d9104f519e0eb3b8.camel@siemens.com>

> -----Original Message-----
> From: Bezdeka, Florian (T CED SES-DE) <florian.bezdeka@siemens.com>
> Sent: Friday, August 12, 2022 9:08 AM
> To: isar-users@googlegroups.com; Moessbauer, Felix (T CED SES-DE)
> <felix.moessbauer@siemens.com>
> Cc: amikan@ilbers.de; Kiszka, Jan (T CED) <jan.kiszka@siemens.com>; Schild,
> Henning (T CED SES-DE) <henning.schild@siemens.com>
> Subject: Re: [PATCH 0/3] systemd-boot: Locate imager deps in buildchroot
> 
> On Fri, 2022-08-12 at 08:50 +0200, Felix Moessbauer wrote:
> > This patch reworks the logic how we create images with systemd-boot:
> > Instead of installing the systemd-boot dependency into the target
> > image, we install it in the buildchroot, leveraging the IMAGER_INSTALL
> > infrastructure.
> 
> For some reasion 2/3 didn't make it into my inbox but it's on the list.
> Just in case someone else is missing a patch.
> 
> IMHO patches 2 and 3 should be squashed together to stay bisectable.

Both patches have a one-to-one relation to another patch from [1].
That's why I separated them, but I have no problem with squashing.

> 
> I hope that was tested with Debian testing as well. Testing was the reason for
> the change last time.

This has been tested on Debian testing, as well as a Debian bullseye layer where all system-* packages come from backports.
I can also confirm that the systemd-boot package is no longer installed in the image.

But I would be happy if more people could give this series a test.

Felix

[1] https://groups.google.com/g/isar-users/c/AM9L31ugDco/m/A9UVRL1cAgAJ

> 
> Florian
> 
> >
> > This has the following advantages:
> >
> > - smaller images: The systemd-boot package is no longer installed into
> > the image
> > - unified imager logic with OE
> >
> > Best regards,
> > Felix
> >
> > Felix Moessbauer (3):
> >   wic: locate systemd-boot efi files in buildchroot
> >   Rework imager support for systemd-boot
> >   Install systemd-boot into buildchroot for qemuarm
> >
> >  meta-isar/conf/multiconfig/qemuarm-bookworm.conf        | 2 +-
> >  meta/conf/distro/debian-common.conf                     | 6 +++---
> >  meta/scripts/lib/wic/plugins/source/bootimg-efi-isar.py | 6 +++---
> >  3 files changed, 7 insertions(+), 7 deletions(-)
> >
> > --
> > 2.30.2
> >


  reply	other threads:[~2022-08-12  7:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12  6:50 Felix Moessbauer
2022-08-12  6:50 ` [PATCH 1/3] wic: locate systemd-boot efi files " Felix Moessbauer
2022-08-22 11:47   ` Henning Schild
2022-08-30  8:23     ` Moessbauer, Felix
2022-08-30 15:06       ` Henning Schild
2022-08-12  6:50 ` [PATCH 2/3] Rework imager support for systemd-boot Felix Moessbauer
2022-08-12  6:50 ` [PATCH 3/3] Install systemd-boot into buildchroot for qemuarm Felix Moessbauer
2022-08-12  7:08 ` [PATCH 0/3] systemd-boot: Locate imager deps in buildchroot Bezdeka, Florian
2022-08-12  7:17   ` Moessbauer, Felix [this message]
2022-08-22 11:55 ` 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=AM9PR10MB4869B65EEC4BE97F3890536689679@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
    --to=felix.moessbauer@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=florian.bezdeka@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