Re: bookworm/sid: new interactive system locale setting on first boot

[Henning Schild <henning.schild@siemens.com>]

Am Thu, 20 Oct 2022 13:11:44 +0200
schrieb "Schaffner, Tobias (T CED SES-DE)"
<tobias.schaffner@siemens.com>:

> On 20.10.22 12:54, Schild, Henning (T CED SES-DE) wrote:
> 
> > I think for the time being we want to just disable it via the
> > cmdline. It is unexpected and breaks non-interactive booting.
> > 
> > But looking at what that thing can do ... it seems valuable to keep
> > it in mind. It in fact does 3 key things which we kind of want to
> > do in any isar image as well. (and it can do more we also might
> > want)
> > - hostname (part of almost every layer i know)
> > - rootpw (part of isar core)
> > - locales (part of isar core)
> > 
> > Maybe we can eventually use it for these purposes and drop our
> > implementations.
> > 
> > But back to the question on locale.conf. Generating that might also
> > be an option. Here i would suggest to see where it comes from in a
> > debian installed with the debian installer, if it is generated
> > together with locale.gen and friends ... yes we likely want to
> > generate it in the extension and solve the problem that way. Also
> > have a look at the reconfigure scripts that we cater for, and how
> > they changed with that more recent systemd.
> > 
> > Henning  
> 
> I would suggest to provide the locale.conf even if we disable
> systemd-firstboot via the command line. Other packages might rely on
> a the new file as firstboot ensures that it will be present on
> bookworm.

Yes simply follow any change that came in the reconfigure scripts and
the installer should be the way to go. The patch you did send looks
like you already had a look at the debconf stuff.

Henning