Re: How to make results of “localedef” survive “dpkg-reconfigure locales”?

[Thorsten Schöning]

Guten Tag Tom H,
am Montag, 25. Februar 2019 um 16:43 schrieben Sie:

> localedef --no-archive -f CP1252 -i /usr/share/i18n/locales/de_DE
> /usr/lib/locale/de_DE.CP1252

Doesn't change a thing: Because "output" already has been a path
before, "localedef" behaved like "--no-archive" has been provided as
well already. A directory is created with the generated locale-files
and nothing is added to the archive. So additionally adding
"--no-archive" doesn't make any difference in my case.

If I neither provide an output path nor "--no-archive", the generated
locale is added to the archive as documented and Postgres fails as
well. Pretty much the same behaviour like with using "dpkg-reconfigure
locales" only, as if the locale simply was not (properly) available
(somewhere).

There's one difference, though: "dpkg-reconfigure locales" doesn't
recognize that the locale added to the archive using "localedef" has
been added at all. While "localedef --list-archive" does list it as
available, much like it lists all others added by "dpkg-reconfigure
locales" only.

That again fits exactly to my described behavior that,
dpkg-reconfigure deletes my locale-files in a folder simply because it
doesn't know about them for some reason.

The only thing allowing me to get Postgres to succeed instantly
currently is using "localedef" with an output path.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail: Thorsten.Schoening at AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow