From: Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
To: guile-user@gnu.org
Subject: Re: Re: Using GUIX
Date: Wed, 19 Dec 2018 09:06:05 +0100 [thread overview]
Message-ID: <f142e6a1-b293-0b25-ba75-30655697cab4@gmail.com> (raw)
In-Reply-To: <mailman.133.1545152425.18875.guile-user@gnu.org>
Hello,
On 18.12.18 18:00, guile-user-request@gnu.org wrote:
> ------------------------------
>
> Message: 3
> Date: Tue, 18 Dec 2018 20:59:05 +0800
> From: iyzsong@member.fsf.org (=?utf-8?B?5a6L5paH5q2m?=)
> To: Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
> Cc: Guile User <guile-user@gnu.org>
> Subject: Re: Using GUIX
> Message-ID: <874lbb0z52.fsf@member.fsf.org>
> Content-Type: text/plain; charset=utf-8
>
> Zelphir Kaltstahl <zelphirkaltstahl@gmail.com> writes:
>
>> Hello Guile Users,
>>
>> I recently managed to install GUIX package manager. Now I always get the
>> following warning, when I install any package:
>>
>> guix package -i hello
>> guix package: warning: Consider running 'guix pull' followed by
>> 'guix package -u' to get up-to-date packages and security updates.
>>
>> The following package will be upgraded:
>> hello 2.10 ? 2.10 /gnu/store/md2plii4g5sk66wg9cgwc964l3xwhrm9-hello-2.10
>>
>> substitute: guile: warning: failed to install locale
>> substitute: hint: Consider installing the `glibc-utf8-locales' or `glibc-locales' package and
>> substitute: defining `GUIX_LOCPATH', along these lines:
>> substitute:
>> substitute: guix package -i glibc-utf8-locales
>> substitute: export GUIX_LOCPATH="$HOME/.guix-profile/lib/locale"
>> substitute:
>> substitute: See the "Application Setup" section in the manual, for more info.
>> substitute:
>> substitute:
>> nothing to be done
>>
>> I already installed both, glibc-utf8-locales and glibc-locales, but the
>> warning remains.
>>
> Hello, I think you need to install the 'glibc-utf8-locales' as the
> 'root' user, and then restart the 'guix-daemon' service. The locale
> warning coming from the 'substitute' program spawned by the
> 'guix-daemon', whose environment variables are controlled by the system
> service manager, which set GUIX_LOCPATH to root's profile by default.
Here is what I tried:
$ ps -fel|grep guix
shows:
4 S root 1118 1 0 80 0 - 2208 poll_s 08:37 ? 00:00:00 /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon --build-users-group=guixbuild
0 S root 7892 5848 0 80 0 - 4134 pipe_w 08:59 pts/0 00:00:00 grep --color=auto guix
So there is something running, but I could not find a restart parameter in:
$ /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon --help
I also already rebooted multiple times (really shutdown the machine and
then start it again by pressing the power button and carrying it around
separated from power source) between the GUIX installation and now. How
would I restart that daemon and would that have any effect, having
already rebooted multiple times?
Thanks for everyone's help so far!
Oh and I saw the message about the mailing lists. I think I should take
this question over there : )
Zelphir
next parent reply other threads:[~2018-12-19 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.133.1545152425.18875.guile-user@gnu.org>
2018-12-19 8:06 ` Zelphir Kaltstahl [this message]
2018-12-19 17:55 ` Re: Using GUIX 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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f142e6a1-b293-0b25-ba75-30655697cab4@gmail.com \
--to=zelphirkaltstahl@gmail.com \
--cc=guile-user@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.
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).