From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 33603@debbugs.gnu.org
Subject: bug#33603: Invalid hash for NSS-Certs
Date: Tue, 15 Jan 2019 13:57:55 +0100 [thread overview]
Message-ID: <87d0oy13jg.fsf@gnu.org> (raw)
In-Reply-To: <87imyqqzpk.fsf@gmail.com> (Maxim Cournoyer's message of "Tue, 15 Jan 2019 00:03:51 -0500")
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> Hello!
>
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
> [...]
>
>>> It's a rather old install (late 2016 -- but kept up-to-date, of course
>>> :-)) so there might be remnants from the past? How could I verify in
>>> which locale the guix-daemon is running?
>>
>> You could check /proc/$(pidof guix-daemon)/environ for variables like
>> ‘LC_ALL’. And of course, you can see if ‘guix substitute’ emits the
>> infamous “can’t install locale” message. :-)
>>
>> Regardless, I think ‘guix substitute’ should ideally be
>> locale-insensitive, or it should error out rather than produce files
>> with the wrong names.
>
> The only environment variable(s?) defined for the guix-daemon process on
> that machine is:
>
> $ pidof guix-daemon
> 270
>
> sudo cat /proc/270/environ
> GUIX_LOCPATH=/gnu/store/94k5w17z54w25lgp90czdqfv9m4hwzhq-glibc-utf8-locales-2.28/lib/localeLC_ALL=en_US.utf8
This is perfect (see commit 7e4bc215098f334bc2a11737f2665dd4992fc2da,
which gave you this, fixing the issue we’re talking about on GuixSD.)
So I don’t think this machine has any problem. Perhaps nss-certs was
installed before the fix above?
> I'm not familiar with this systemfs structure, but shouldn't there be a
> newline before the LC_ALL=en_US.utf8 variable assignment?
No, there are actually newlines, try:
cat /proc/270/environ | xargs -0 echo
HTH,
Ludo’.
next prev parent reply other threads:[~2019-01-15 12:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 19:58 bug#33603: Invalid hash for NSS-Certs Brett Gilio
2018-12-05 11:47 ` Ludovic Courtès
2019-01-08 16:24 ` maxim.cournoyer
2019-01-11 8:19 ` Ludovic Courtès
2019-01-14 2:33 ` Maxim Cournoyer
2019-01-14 8:48 ` Ludovic Courtès
2019-01-15 5:03 ` Maxim Cournoyer
2019-01-15 12:57 ` Ludovic Courtès [this message]
2019-01-18 4:59 ` Maxim Cournoyer
2019-01-18 16:53 ` Ludovic Courtès
2019-01-19 3:32 ` Maxim Cournoyer
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=87d0oy13jg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33603@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.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 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).