From: Danny Milosavljevic <dannym@scratchpost.org>
To: 33678@debbugs.gnu.org
Subject: bug#33678: Locale problems
Date: Sat, 8 Dec 2018 22:35:51 +0100 [thread overview]
Message-ID: <20181208223551.2ad9c226@scratchpost.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
Can we do something against the locale problems that keep showing up
when updating?
Right now, after a half-finished update from guix master (half-finished because
once any package build breaks, the entire update will stop), I cannot use any
Umlauts because "xterm -u8" stops working as it should:
$ xterm -u8
Warning: locale not supported by C library, locale unchanged
$
Why does this keep happening? Shouldn't the functional nature and modularity
of Guix keep using the old locales where those make sense and the new locales
where those make sense?
Environment:
$ locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
POSIX
$ echo $LC_ALL
de_DE.utf8
$ echo $LANG
en_US.utf8
$ echo $GUIX_LOCPATH
/run/current-system/locale
$ ls $GUIX_LOCPATH/2.28/en_US.utf8/
LC_ADDRESS LC_IDENTIFICATION LC_MONETARY LC_PAPER
LC_COLLATE LC_MEASUREMENT LC_NAME LC_TELEPHONE
LC_CTYPE LC_MESSAGES LC_NUMERIC LC_TIME
$ ls xxx
ls: Zugriff auf 'xxx' nicht möglich: Datei oder Verzeichnis nicht gefunden
$
^^ Note: Message is in German, as it should. I left in the mangled Umlauts
for documentation purposes.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-12-08 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 21:35 Danny Milosavljevic [this message]
2018-12-08 22:35 ` bug#33678: Locale problems Danny Milosavljevic
2018-12-08 22:56 ` Marius Bakke
2018-12-08 22:59 ` pelzflorian (Florian Pelz)
2018-12-08 23:35 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181208223551.2ad9c226@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=33678@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).