unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Salim Khatib <saleemkhatib22@gmail.com>
Cc: 27126@debbugs.gnu.org
Subject: bug#27126: gnutls+emacs
Date: Tue, 30 May 2017 20:09:28 -0400	[thread overview]
Message-ID: <kkr2z5rio7.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <fe13de50-a44b-78f6-b7bc-7e5dc10f3e65@gmail.com> (Salim Khatib's message of "Mon, 29 May 2017 00:38:24 +0300")

Salim Khatib wrote:

> I think there is a bug with gnutls-cli 3.4.10 with Emacs 24.5.1 since
> every time I write :
> M-x list-packages an error message come up 'gnutls.c [0] error: ......
> TLS connection terminated'

Could you try the Emacs 25.2 release, please?





  reply	other threads:[~2017-05-31  0:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-28 21:38 bug#27126: gnutls+emacs Salim Khatib
2017-05-31  0:09 ` Glenn Morris [this message]
2017-05-31  8:34   ` saleem khatib

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=kkr2z5rio7.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=27126@debbugs.gnu.org \
    --cc=saleemkhatib22@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).