all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: "Josh Holland" <josh@inv.alid.pw>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 37662@debbugs.gnu.org
Subject: bug#37662: substitution failure of nss-certs
Date: Wed, 16 Oct 2019 01:20:02 +0530	[thread overview]
Message-ID: <cu7eezdn5zp.fsf@systemreboot.net> (raw)
In-Reply-To: <877e55an15.fsf@inv.alid.pw>

[-- Attachment #1: Type: text/plain, Size: 684 bytes --]


Josh Holland <josh@inv.alid.pw> writes:

> Ludovic Courtès <ludo@gnu.org> writes:
>> I suppose the error here is because you’re daemon is missing its UTF-8
>> locales.
>>
>> This could be because you upgraded the daemon but did not upgrade the
>> ‘glibc-utf8-locales’ or ‘glibc-locales’ you installed as root, no?
>
> It's possible - I rarely do anything with the root profile, and wasn't
> even aware that I had to keep it up to date.  Should I have to `guix
> pull` and `guix upgrade` it regularly, as well as my user profile?

I install glibc-locales as a system-wide package in my operating-system
configuration. Perhaps that's what Ludo meant to say.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-10-15 19:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 14:18 bug#37662: substitution failure of nss-certs Josh Holland
2019-10-10 14:31 ` Ludovic Courtès
2019-10-15 18:20   ` Josh Holland
2019-10-15 19:50     ` Arun Isaac [this message]
2019-10-16 17:21       ` Josh Holland
2019-10-17  5:07       ` Ben Sturmfels
2019-10-17  9:13         ` Ludovic Courtès
2019-10-16 20:34     ` Ludovic Courtès
2019-10-16 22:25       ` Josh Holland
2019-10-17  0:31         ` Bengt Richter
2019-10-17  9:08         ` Ludovic Courtès
2019-10-17 10:28           ` Josh Holland
2019-10-17 12:05             ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cu7eezdn5zp.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=37662@debbugs.gnu.org \
    --cc=josh@inv.alid.pw \
    --cc=ludo@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 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.