From: Edouard KLEIN <edouardklein@gmail.com>
To: quiliro@fsfla.org
Cc: help-guix@gnu.org
Subject: Re: warning: failed to install locale
Date: Thu, 17 Jan 2019 22:05:12 +0100 [thread overview]
Message-ID: <CANiMCTM4pNHX7T816=RqXraUR7A8y9+fWySM6+Gjbv8RW-akYQ@mail.gmail.com> (raw)
In-Reply-To: <2d571a602d342564a6d0b042437c6a4e@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
I had the same problem, which was solved by installing glibc-utf8-locales
in root's profile and adding the export line to root's ~/.profile, which
fits Ricardo's explanations.
Le jeu. 17 janv. 2019 à 21:56, Quiliro Ordonez <quiliro@riseup.net> a
écrit :
> Thank you for this straightforward answer Ricardo. I post some insights
> below.
>
> El 2019-01-17 09:24, Ricardo Wurmus escribió:
> > This is in your environment. But what about the daemon’s environment?
> > It is not started in your environment where GUIX_LOCPATH is set. How do
> > you start the daemon? If it’s via systemd you may want to look at the
> > service file to see where GUIX_LOCPATH points.
>
> In fact:
> echo $GUIX_LOCPATH
> gives no output as root (which runs the Guix daemon, presumably).
>
> Where is the service file supposed to be and how to include GUIX_LOCPATH
> in it?
>
> I also ran the script to install Guix. Perhaps this script should do all
> the setup.
>
>
[-- Attachment #2: Type: text/html, Size: 1269 bytes --]
next prev parent reply other threads:[~2019-01-17 21:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 18:11 warning: failed to install locale Giovanni Biscuolo
2019-01-17 13:31 ` zimoun
2019-01-17 13:39 ` Ricardo Wurmus
2019-01-17 14:18 ` zimoun
2019-01-17 14:24 ` Ricardo Wurmus
2019-01-17 16:27 ` zimoun
2019-01-17 20:56 ` Quiliro Ordonez
2019-01-17 21:05 ` Edouard KLEIN [this message]
2019-01-18 10:13 ` zimoun
2019-01-18 15:51 ` Quiliro Ordonez
2019-01-18 10:35 ` Giovanni Biscuolo
2019-01-18 10:59 ` zimoun
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANiMCTM4pNHX7T816=RqXraUR7A8y9+fWySM6+Gjbv8RW-akYQ@mail.gmail.com' \
--to=edouardklein@gmail.com \
--cc=help-guix@gnu.org \
--cc=quiliro@fsfla.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.