unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sebastian Boehm <sebastian@sometimesfood.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 54096@debbugs.gnu.org
Subject: bug#54096: 27.2; Error retrieving package descriptions when TLS 1.3 is used (macOS)
Date: Tue, 22 Feb 2022 15:27:16 +0100	[thread overview]
Message-ID: <CAPNHJwEWPN4St7QezhdSq3jPk_74zBe3U5hL_i=eEuuRg2jkkA@mail.gmail.com> (raw)
In-Reply-To: <87wnhnau75.fsf@gnus.org>

Hi Lars,

On Tue, 22 Feb 2022 at 14:48, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> There aren't going to be any further Emacs 27 releases

I did not know that. Sorry for the noise, then.

> if this has been fixed for Emacs 28, I'm not sure there's anything to be done on the Emacs side here?  Did you have something in particular in mind?

No, I'm perfectly fine with a WONTFIX resolution. I'll just keep using
the workaround on macOS until Emacs 28 is out, then.

I just re-tested Emacs 28 to make sure this issue does not affect
Emacs 28 and as far as I can tell, no version other than 27.2 seems to
be affected.

I don't have a great dev setup on this particular machine, so I tested
the following packages from http://emacsformacosx.com:

- Emacs-26.3-universal.dmg
- Emacs-27.1-1-universal.dmg
- Emacs-pretest-28.0.90-universal.dmg
- Emacs-pretest-28.0.91-universal.dmg
- Emacs-2022-02-22_00-09-13-dfd76688beac1d99a9cdcfe375e0a125cb039b8f-universal

All of these are working just as expected for me.

Thank you for your help!

Best,
Sebastian





  reply	other threads:[~2022-02-22 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 18:12 bug#54096: 27.2; Error retrieving package descriptions when TLS 1.3 is used (macOS) Sebastian Boehm
2022-02-22 13:48 ` Lars Ingebrigtsen
2022-02-22 14:27   ` Sebastian Boehm [this message]
2022-02-23 12:11     ` Lars Ingebrigtsen

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='CAPNHJwEWPN4St7QezhdSq3jPk_74zBe3U5hL_i=eEuuRg2jkkA@mail.gmail.com' \
    --to=sebastian@sometimesfood.org \
    --cc=54096@debbugs.gnu.org \
    --cc=larsi@gnus.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.
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).