From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50983@debbugs.gnu.org, Rudi C <rudiwillalwaysloveyou@gmail.com>
Subject: bug#50983: 28.0.50; [REGRESSION, BUG] Display bugs with uncommon characters
Date: Sun, 03 Oct 2021 11:11:23 +0200 [thread overview]
Message-ID: <874k9ytqv8.fsf@gnus.org> (raw)
In-Reply-To: <83lf3aac5w.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 03 Oct 2021 08:51:39 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> P.S. The site which you use to post the files is problematic: its
> certificate is expired or invalid, and at least on one of my systems
> wget said the TLS handshake failed, perhaps for the same reason.
It's not expired, but if you're getting messages saying that it is, it
probably means that your wget is too old. It's due to the Let's Encrypt
meltdown on October 1st. Here's one of the many, many threads about it;
basically you have to delete the X3 certificate:
https://stackoverflow.com/questions/69387175/git-for-windows-ssl-certificate-problem-certificate-has-expired
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-03 9:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 22:50 bug#50983: 28.0.50; [REGRESSION, BUG] Display bugs with uncommon characters Rudi C
2021-10-03 5:51 ` Eli Zaretskii
2021-10-03 6:47 ` Rudi C
2021-10-03 9:01 ` Eli Zaretskii
2021-10-03 9:11 ` Lars Ingebrigtsen [this message]
2021-10-03 9:54 ` Alan Third
2021-10-03 10:04 ` Eli Zaretskii
2021-10-03 10:24 ` Alan Third
2021-10-03 10:49 ` Eli Zaretskii
2021-10-03 11:26 ` Alan Third
2021-10-03 12:02 ` Eli Zaretskii
2021-10-03 12:54 ` Alan Third
2021-10-03 14:48 ` Eli Zaretskii
2021-10-03 11:00 ` Rudi C
2021-10-03 11:11 ` Eli Zaretskii
2021-10-04 8:05 ` Rudi C
2021-10-04 12:40 ` Eli Zaretskii
2021-10-04 13:50 ` Eli Zaretskii
2022-09-04 21:37 ` Lars Ingebrigtsen
2021-10-03 9:08 ` Lars Ingebrigtsen
2021-10-03 10:48 ` Rudi C
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=874k9ytqv8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50983@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rudiwillalwaysloveyou@gmail.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.
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).