From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 33678@debbugs.gnu.org
Subject: bug#33678: Locale problems
Date: Sat, 8 Dec 2018 23:59:06 +0100 [thread overview]
Message-ID: <20181208225906.bqlagnuzxnrgqqlq@pelzflorian.localdomain> (raw)
In-Reply-To: <20181208223551.2ad9c226@scratchpost.org>
On Sat, Dec 08, 2018 at 10:35:51PM +0100, Danny Milosavljevic wrote:
> 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
Is this only on foreign distros? I cannot reproduce this in a Guix VM.
These errors occurred for me on the foreign distro Debian also for
Debian commands like localectl because the locale command was taken
from a glibc in root’s guix profile. I uninstalled the glibc package
and now Debian’s locale commands work again. `strace locale` made it
seem like the directory for the de_DE.UTF-8 locale was never checked
by the locale program, only de_DE.utf8 and others, which apparently
are not what Debian uses.
Regards,
Florian
next prev parent reply other threads:[~2018-12-08 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 21:35 bug#33678: Locale problems Danny Milosavljevic
2018-12-08 22:35 ` Danny Milosavljevic
2018-12-08 22:56 ` Marius Bakke
2018-12-08 22:59 ` pelzflorian (Florian Pelz) [this message]
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=20181208225906.bqlagnuzxnrgqqlq@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=33678@debbugs.gnu.org \
--cc=dannym@scratchpost.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).