On 2020-02-25 10:04, Harald Dunkel wrote:
> Package: locales
> Version: 2.29-10
> Severity: wishlist
>
> Apparently MacOS 10.15 uses "UTF-8" instead of "C.UTF-8". This
> affects ssh terminal sessions from MacOS to Debian, e.g.
>
> # apt upgrade
> :
> :
> Processing triggers for mime-support (3.64) ...
> Processing triggers for libc-bin (2.29-10) ...
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = (unset),
> LC_ALL = (unset),
> LC_CTYPE = "UTF-8",
> LC_COLLATE = "C",
> LANG = "C"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = (unset),
> LC_ALL = (unset),
> LC_CTYPE = "UTF-8",
> LC_COLLATE = "C",
> LANG = "C"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
>
> The workaround is to run
>
> localedef -i C -f UTF-8 UTF-8
>
> on Debian, but probably others are affected by this problem
> as well. A central solution would be reasonable.
>
> Do you think it would be possible to introduce "UTF-8" as an
> alias for "C.UTF-8"?
MacOS is wrong there. We definitely do no want to introduce such a local
in an uncoordinated way, as it will make things way more difficult to
rollback instead. Have you reported the issue to Apple?
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
