From: "Ludovic Courtès" <ludo@gnu.org>
To: Ben Sturmfels <ben@stumbles.id.au>
Cc: 37662@debbugs.gnu.org, Josh Holland <josh@inv.alid.pw>
Subject: bug#37662: substitution failure of nss-certs
Date: Thu, 17 Oct 2019 11:13:26 +0200 [thread overview]
Message-ID: <87eezbrayx.fsf@gnu.org> (raw)
In-Reply-To: <611eb65b-6b21-3a03-2dc7-c3bebb7a6328@stumbles.id.au> (Ben Sturmfels's message of "Thu, 17 Oct 2019 16:07:37 +1100")
Hi,
Ben Sturmfels <ben@stumbles.id.au> skribis:
> On 16/10/19 06:50, Arun Isaac wrote:
>>
>> 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.
>
> Hi Ludo, is it best to install glibc-locales or glibc-utf8-locales in
> the operating system configuration as Arun suggests?
It’s best to install none of these. :-)
On Guix System, the mechanism is more fine-grained: the admin declares
precisely the locales they want in the ‘locale’ and ‘locale-definitions’
fields, and only those get installed. See
<https://guix.gnu.org/manual/devel/en/html_node/Locales.html>.
> I hit the same issue doing a reconfigure on Guix System after not having
> these locales either in user, root or system profiles (though I'm unsure
> whether root and system are the same thing).
This is probably due to the switch to glibc 2.29: your system now
provides locales for glibc 2.29 only, but if you have binaries linked
against 2.28, they need 2.28 locale data.
To do that, add ‘glibc-2.28’ to the ‘locale-libcs’ field:
<https://guix.gnu.org/manual/devel/en/html_node/Locales.html#Locale-Data-Compatibility-Considerations>.
(Normally ‘guix pull --news’ mentioned it when you upgraded.)
Perhaps on we should just add the current and previous glibc to
‘locale-libcs’ by default.
HTH!
Ludo’.
next prev parent reply other threads:[~2019-10-17 9:14 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
2019-10-16 17:21 ` Josh Holland
2019-10-17 5:07 ` Ben Sturmfels
2019-10-17 9:13 ` Ludovic Courtès [this message]
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
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=87eezbrayx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37662@debbugs.gnu.org \
--cc=ben@stumbles.id.au \
--cc=josh@inv.alid.pw \
/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).