From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: M-x list-package fails with error “certificate could not be verified”
Date: Sun, 31 Dec 2017 17:42:21 +0200 [thread overview]
Message-ID: <83fu7qewf6.fsf@gnu.org> (raw)
In-Reply-To: <CAD3zm23QDX_mQ6K1Hbtt522qh3aOUXp19vWGD0P67y6xYvjU1w@mail.gmail.com> (message from York Zhao on Sun, 31 Dec 2017 09:31:08 -0500)
> From: York Zhao <gtdplatform@gmail.com>
> Date: Sun, 31 Dec 2017 09:31:08 -0500
>
> I posted this question on emacs stackexchange (
> https://emacs.stackexchange.com/questions/37805/m-x-list-package-fails-with-error-certificate-could-not-be-verified),
> but haven't got any answer yet. I would really appreciated it if anyone
> could take a look and help.
I cannot reproduce this on my system. Could it be that your
certificate bundle is outdated?
next prev parent reply other threads:[~2017-12-31 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 14:31 M-x list-package fails with error “certificate could not be verified” York Zhao
2017-12-31 15:42 ` Eli Zaretskii [this message]
2017-12-31 18:15 ` York Zhao
2017-12-31 18:28 ` Eli Zaretskii
2018-01-02 3:59 ` York Zhao
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fu7qewf6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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).