From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Certificate verification failure, cannot fetch some distfiles
Date: Fri, 28 May 2021 09:21:21 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31161@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
New issue by newbluemoon on void-packages repository
https://github.com/void-linux/void-packages/issues/31161
Description:
When trying to fetch the distfiles for `sonic-visualiser` and `vamp-plugin-sdk` there is a certificate verification failure:
```
=> sonic-visualiser-4.3_1: fetching distfile 'sonic-visualiser-4.3.tar.gz'...
Certificate verification failed for /jurisdictionC=GB/businessCategory=Government Entity/serialNumber=1989-08-02/C=GB/ST=Tower Hamlets/L=Bethnal Green/O=Queen Mary University of London/CN=code.soundsoftware.ac.uk
SSL_connect returned 1
https://code.soundsoftware.ac.uk/attachments/download/2786/sonic-visualiser-4.3.tar.gz: Operation not permitted
=> ERROR: sonic-visualiser-4.3_1: failed to fetch sonic-visualiser-4.3.tar.gz.
```
```
=> vamp-plugin-sdk-2.10.0_1: fetching distfile 'vamp-plugin-sdk-2.10.0.tar.gz'...
Certificate verification failed for /jurisdictionC=GB/businessCategory=Government Entity/serialNumber=1989-08-02/C=GB/ST=Tower Hamlets/L=Bethnal Green/O=Queen Mary University of London/CN=code.soundsoftware.ac.uk
SSL_connect returned 1
https://code.soundsoftware.ac.uk/attachments/download/2691/vamp-plugin-sdk-2.10.0.tar.gz: Operation not permitted
=> ERROR: vamp-plugin-sdk-2.10.0_1: failed to fetch vamp-plugin-sdk-2.10.0.tar.gz.
```
It seems there is a problem with `code.soundsoftware.ac.uk`. However, the files can be downloaded without error using firefox or chromium. So the issue might lie with `ca-certificates`.
next reply other threads:[~2021-05-28 7:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 7:21 newbluemoon [this message]
2021-06-10 2:22 ` ericonr
2021-07-02 16:06 ` RossComputerGuy
2021-07-03 0:57 ` RossComputerGuy
2021-07-03 0:57 ` RossComputerGuy
2021-07-03 1:02 ` ericonr
2021-07-03 1:31 ` RossComputerGuy
2021-07-03 6:55 ` RossComputerGuy
2021-07-17 2:11 ` ericonr
2021-07-18 0:49 ` sgn
2021-07-18 0:50 ` sgn
2021-07-18 1:01 ` sgn
2021-07-19 13:22 ` sgn
2021-07-19 16:02 ` ericonr
2021-07-21 9:35 ` sgn
2021-07-21 9:37 ` sgn
2021-07-21 13:31 ` newbluemoon
2021-07-21 13:34 ` leahneukirchen
2021-07-21 13:41 ` newbluemoon
2021-07-21 13:48 ` newbluemoon
2022-05-20 2:12 ` github-actions
2022-06-04 2:08 ` [ISSUE] [CLOSED] " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31161@inbox.vuxu.org \
--to=newbluemoon@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).