From: Chris Marusich <cmmarusich@gmail.com>
To: Dave Love <fx@gnu.org>
Cc: 25136@debbugs.gnu.org
Subject: bug#25136: locale confusion
Date: Thu, 08 Dec 2016 22:46:21 -0800 [thread overview]
Message-ID: <87a8c5sipu.fsf@gmail.com> (raw)
In-Reply-To: <87y3zq7cqx.fsf@pc102091.liv.ac.uk> (Dave Love's message of "Thu, 08 Dec 2016 13:48:38 +0000")
[-- Attachment #1: Type: text/plain, Size: 2302 bytes --]
Dave Love <fx@gnu.org> writes:
> I followed the instructions for getting locales working in
> "(guix)Application Setup" to no effect initially. I'm running over
> RHEL6, if that's relevant, and I have:
>
> $ locale
> LANG=en_GB.UTF-8
> LC_CTYPE="en_GB.UTF-8"
> LC_NUMERIC="en_GB.UTF-8"
> LC_TIME="en_GB.UTF-8"
> LC_COLLATE="en_GB.UTF-8"
> LC_MONETARY="en_GB.UTF-8"
> LC_MESSAGES="en_GB.UTF-8"
> LC_PAPER="en_GB.UTF-8"
> LC_NAME="en_GB.UTF-8"
> LC_ADDRESS="en_GB.UTF-8"
> LC_TELEPHONE="en_GB.UTF-8"
> LC_MEASUREMENT="en_GB.UTF-8"
> LC_IDENTIFICATION="en_GB.UTF-8"
> LC_ALL=
> $ export -p | grep GUIX
> declare -x GUIX_LOCPATH="/home/dlove/.guix-profile/lib/locale"
> $ find $GUIX_LOCPATH -name en_GB.UTF-8
> /home/dlove/.guix-profile/lib/locale/2.24/en_GB.UTF-8
>
> but saw this (note the warning):
>
> $ guix --version
> warning: failed to install locale: Invalid argument
> guix (GNU Guix) 20161208.12
> Copyright (C) 2016 the Guix authors
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> strace showed it looking in "locale/2.23", not "locale/2.24", despite
> the environment.
Did /home/dlove/.guix-profile/lib/locale contain a "2.23" directory? If
not, then perhaps that's why the warning was emitted.
> "guix" there was from the /usr/local/bin link suggested by the
> installation instructions. After a "guix package -i guix" (to the same
> version of guix, but now in .guix-profile), I don't get the warning but
> I wonder why that should have made a difference and why the environment
> seems to be ignored.
After "guix package -i guix", does the warning still show up when you
invoke "/usr/local/bin/guix"? If so, then perhaps the reason is that
the "guix" program installed in root's profile was compiled against a
different version of glibc (2.23, I guess) than the one in your profile.
I wonder if perhaps this is the kind of problem described in "(guix)
Locales", specifically the following:
https://www.gnu.org/software/guix/manual/html_node/Locales.html#Locale-Data-Compatibility-Considerations
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2016-12-09 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 13:48 bug#25136: locale confusion Dave Love
2016-12-08 20:08 ` Leo Famulari
2016-12-12 13:40 ` Dave Love
2016-12-09 6:46 ` Chris Marusich [this message]
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=87a8c5sipu.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=25136@debbugs.gnu.org \
--cc=fx@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).