From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 17135@debbugs.gnu.org, "Douglas F. Calvert" <dfc@douglasfcalvert.net>
Subject: bug#17135: 24.3; SSL certificate expired for elpa.gnu.org
Date: Sat, 29 Mar 2014 16:25:55 -0400 [thread overview]
Message-ID: <mksiq0vjjg.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvlhvsx0hs.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Sat, 29 Mar 2014 15:35:37 -0400")
Stefan Monnier wrote:
> Could someone take care of that? I'm sure it's not hard to do, but
> I have no idea what I'd have to do to fix it, or even where to look.
I think you need to ask sysadmin@gnu to get a new cert.
next prev parent reply other threads:[~2014-03-29 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 23:25 bug#17135: 24.3; SSL certificate expired for elpa.gnu.org Douglas F. Calvert
2014-03-29 19:35 ` Stefan Monnier
2014-03-29 20:25 ` Glenn Morris [this message]
2014-04-10 23:30 ` Glenn Morris
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=mksiq0vjjg.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=17135@debbugs.gnu.org \
--cc=dfc@douglasfcalvert.net \
--cc=monnier@IRO.UMontreal.CA \
/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/emacs.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).