From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: curl, libcurl{4, -devel, -doc}, mingw64-{x86_64, i686}-curl 7.86 (TEST)
Date: Thu, 03 Nov 2022 10:38:13 +0900 [thread overview]
Message-ID: <20221103103809.AB08.50F79699@gmail.com> (raw)
In-Reply-To: <announce.20221101152414.58602-1-Brian.Inglis@SystematicSW.ab.ca>
On Tue, 01 Nov 2022 15:24:14 -0600, Cygwin curl Maintainer
> The following *TEST* packages have been released in the Cygwin distribution:
>
> * curl 7.86
> * libcurl4 7.86
Hi,
Thank you for maintaining the packages
I failed to get https://cygwin.com/index.html by curl:
==========
$ uname -svrmo; cygcheck -c curl libcurl4 libgsasl18 ca-certificates; rm -f index.html; curl -O https://cygwin.com/index.html; ls -l index.html
CYGWIN_NT-10.0-22621 3.3.6-341.x86_64 2022-09-05 11:15 UTC x86_64 Cygwin
Cygwin Package Information
Package Version Status
ca-certificates 2022.2.54-3 OK
curl 7.86.0-1 OK
libcurl4 7.86.0-1 OK
libgsasl18 2.2.0-1 OK
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
ls: cannot access 'index.html': No such file or directory
==========
I don't know whether the result is expeced.
If so, is there any help?
Lem
next prev parent reply other threads:[~2022-11-03 1:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 21:24 Cygwin curl Maintainer
2022-11-02 18:07 ` Achim Gratz
2022-11-03 1:38 ` Lemures Lemniscati [this message]
[not found] ` <Y2MjCqOFZ0PqdN2G@xps13>
2022-11-03 6:43 ` Lemures Lemniscati
2022-11-03 7:36 ` ASSI
2022-11-03 17:48 ` Brian Inglis
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=20221103103809.AB08.50F79699@gmail.com \
--to=lemures.lemniscati@gmail.com \
--cc=cygwin@cygwin.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.
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).