From: Anton Mikanovich <amikan@ilbers.de>
To: "T. Schaffner" <tobias.schaffner@siemens.com>,
isar-users@googlegroups.com
Cc: florian.bezdeka@siemens.com, quirin.gylstorff@siemens.com
Subject: Re: [PATCH 2/2] Warn if systemd-firstboot misses configurations
Date: Tue, 22 Nov 2022 13:04:13 +0300 [thread overview]
Message-ID: <08d391d5-cb8c-4a49-826d-51b69cd7ef07@ilbers.de> (raw)
In-Reply-To: <20221119182031.2005807-3-tobias.schaffner@siemens.com>
19.11.2022 21:20, T. Schaffner wrote
> From: Tobias Schaffner <tobias.schaffner@siemens.com>
>
> systemd-firstboot checks the existence of different system configurations
> like locale or hostname. Debian packages may trust that these configurations
> are in the location that systemd-firstboot enforced.
>
> Warn the user in the image postproc step if systemd-firstboot misses any
> configurations in the image.
>
> Signed-off-by: Tobias Schaffner <tobias.schaffner@siemens.com>
If we have a warning here, do we really need to mask the service in p1?
User should fix the reason but not hide it, and masking can be optional just
in case there are no other ways.
next prev parent reply other threads:[~2022-11-22 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 18:20 [PATCH 0/2] Mask systemd-firstboot T. Schaffner
2022-11-19 18:20 ` [PATCH 1/2] " T. Schaffner
2022-11-19 18:20 ` [PATCH 2/2] Warn if systemd-firstboot misses configurations T. Schaffner
2022-11-22 10:04 ` Anton Mikanovich [this message]
2022-11-22 10:24 ` Florian Bezdeka
2023-02-23 11:43 ` Uladzimir Bely
2023-02-24 11:36 ` Schaffner, Tobias
2023-02-27 4:39 ` [PATCH 0/2] Mask systemd-firstboot Uladzimir Bely
2023-02-27 12:23 ` Cedric Hombourger
2023-02-27 12:37 ` Jan Kiszka
2023-02-27 12:53 ` Uladzimir Bely
2023-02-27 12:55 ` 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=08d391d5-cb8c-4a49-826d-51b69cd7ef07@ilbers.de \
--to=amikan@ilbers.de \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=quirin.gylstorff@siemens.com \
--cc=tobias.schaffner@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