From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: c4droid <c4droid@foxmail.com>
Cc: help-guix@gnu.org
Subject: Re: pypi import certs issues
Date: Mon, 08 May 2023 08:12:30 -0400 [thread overview]
Message-ID: <87fs87vx75.fsf@gmail.com> (raw)
In-Reply-To: <tencent_1B75B8FEFA1069692584DED061B7088F7505@qq.com> (c4droid@foxmail.com's message of "Mon, 8 May 2023 23:55:06 +0800")
Hi,
c4droid <c4droid@foxmail.com> writes:
> Hi, Maxim
>
> On Sun, May 07, 2023 at 09:18:25PM -0400, Maxim Cournoyer wrote:
>> Hi,
>>
>> c4droid <c4droid@foxmail.com> writes:
>>
>> > Hi, Guix!
>> >
>> > on commit dc5430c9dc20ee53441995d9a89a90b0a86aeed3 pypi import has
>> > issues:
>> >
>> > Backtrace:
>> > In ice-9/eval.scm:
>> > 619:8 19 (_ #(#(#<directory (guile-user) 7fb1cb718c80>)))
>> > In guix/ui.scm:
>> > 2300:7 18 (run-guix . _)
>> > 2263:10 17 (run-guix-command _ . _)
>> > In guix/scripts/import.scm:
>> > 89:11 16 (guix-import . _)
>> > In ice-9/boot-9.scm:
>> > 1752:10 15 (with-exception-handler _ _ #:unwind? _ # _)
>> > In guix/scripts/import/pypi.scm:
>> > 97:21 14 (_)
>> > In guix/import/utils.scm:
>> > 638:27 13 (recursive-import "pwntools" #:repo->guix-package _ # . #)
>> > 630:33 12 (lookup-node "pwntools" #f)
>> > In guix/memoization.scm:
>> > 98:0 11 (mproc "pwntools" #:version #f #:repo->guix-package #<…> …)
>> > In unknown file:
>> > 10 (_ #<procedure 7fb1c7d05a20 at guix/memoization.scm:17…> …)
>> > In guix/import/pypi.scm:
>> > 495:21 9 (_ "pwntools" #:version _)
>> > 126:10 8 (pypi-fetch _)
>> > In ice-9/exceptions.scm:
>> > 406:15 7 (json-fetch _ #:http-fetch _ #:headers _)
>> > In ice-9/boot-9.scm:
>> > 1752:10 6 (with-exception-handler _ _ #:unwind? _ # _)
>> > In guix/import/json.scm:
>> > 53:19 5 (_)
>> > In guix/http-client.scm:
>> > 107:28 4 (http-fetch _ #:port _ #:text? _ #:buffered? _ # _ # _ # …)
>> > In guix/build/download.scm:
>> > 468:4 3 (open-connection-for-uri _ #:timeout _ # _)
>> > 360:6 2 (tls-wrap #<closed: file 7fb1c7a3ce00> _ # _)
>> > In ice-9/boot-9.scm:
>> > 1685:16 1 (raise-exception _ #:continuable? _)
>> > 1683:16 0 (raise-exception _ #:continuable? _)
>> >
>> > ice-9/boot-9.scm:1683:16: In procedure raise-exception:
>> > X.509 certificate of 'pypi.org' could not be verified:
>> > revocation-data-superseded
>> > invalid
>> >
>> > I found a old discuss in
>> > https://lists.gnu.org/archive/html/guix-devel/2018-03/msg00247.html,
>> > but set SSL_CERTS_DIR to /etc/ssl/certs don't working.
>>
>> [...]
>>
>> Do you have nss-certs installed in your operating system declaration (on
>> Guix System) ?
>>
>> Not sure if it could help, but I just updated nss-certs to 3.88.1, up
>> from 3.85, so pulling and reconfiguring your system may help.
>
> I tried to update nss-certs, after reconfiguring system still report this.
At least we've ironed out that. I'm out of ideas for now :-/.
Hopefully a TLS certs expert jumps in.
--
Thanks,
Maxim
prev parent reply other threads:[~2023-05-08 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 17:23 pypi import certs issues c4droid
2023-05-08 1:18 ` Maxim Cournoyer
2023-05-08 15:35 ` c4droid
2023-05-08 15:55 ` c4droid
2023-05-08 11:55 ` James R. Haigh (+ML.GNU.Guix subaddress)
2023-05-09 0:55 ` c4droid
2023-05-09 13:51 ` pypi import certs issues caused by clock synchronisation issue [fixed] James R. Haigh (+ML.GNU.Guix subaddress)
2023-05-10 7:28 ` c4droid
2023-05-08 12:12 ` Maxim Cournoyer [this message]
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=87fs87vx75.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=c4droid@foxmail.com \
--cc=help-guix@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).