From: Leo Famulari <leo@famulari.name>
To: davidpgil@protonmail.com
Cc: 39936@debbugs.gnu.org
Subject: bug#39936: How To Resolve "LC_ALL: cannot change locale (en_US.utf8)"
Date: Wed, 11 Mar 2020 15:05:39 -0400 [thread overview]
Message-ID: <20200311190539.GC26593@jasmine.lan> (raw)
In-Reply-To: <TMXHJK4ivjnh1i4XeUISrxbgZao7EghYYARUXZZnZCeJ57KZ5x2rEDqvoBMlN0FfWROyipVI681ZRmwaguufBhffJXVey0AUoad0crzmdtk=@protonmail.com>
On Thu, Mar 05, 2020 at 08:53:52PM +0000, David Philipe Gil via Bug reports for GNU Guix wrote:
> System: Ubuntu 18.04
> Guix: 1.0.1
>
> Whenever I "guix pull" I see the error "LC_ALL: cannot change locale (en_US.utf8)". I installed "glibc_utf8_locales" and it seems to have had no effect.
>
> In my .profile I am pointing to "/home/username/.guix-profile/lib/locale". Am I missing something?
>
> I have entered "hash guix" as well with no effect.
Is this on the Guix System, or another distro?
Did you check the instructions in the manual section 2.6.1 Locales?
It's likely this error is coming from the guix-daemon, so you'll need to
make sure that GUIX_LOCPATH is set in the environment where the
guix-daemon starts.
On most distros this happens in the systemd unit file with something
like this line in the Service section:
Environment=GUIX_LOCPATH=/var/guix/profiles/per-user/root/guix-profile/lib/locale
next prev parent reply other threads:[~2020-03-11 19:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 20:53 bug#39936: How To Resolve "LC_ALL: cannot change locale (en_US.utf8)" David Philipe Gil via Bug reports for GNU Guix
2020-03-11 19:05 ` Leo Famulari [this message]
2020-03-11 19:55 ` David Philipe Gil via Bug reports for GNU Guix
2020-03-11 22:48 ` Leo Famulari
2020-03-12 12:24 ` David Philipe Gil via Bug reports for GNU Guix
2020-03-12 17:37 ` Leo Famulari
2020-03-12 20:58 ` David Philipe Gil via Bug reports for GNU Guix
2020-03-14 17:27 ` Leo Famulari
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=20200311190539.GC26593@jasmine.lan \
--to=leo@famulari.name \
--cc=39936@debbugs.gnu.org \
--cc=davidpgil@protonmail.com \
/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.