unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@gmail.com
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 31339@debbugs.gnu.org, Eric Hanchrow <eric.hanchrow@gmail.com>
Subject: bug#31339: 25.3.50; package-list-packages does not provide useful error when gnutls-cli is missing
Date: Mon, 13 May 2019 16:02:58 -0400	[thread overview]
Message-ID: <85zhnqw2a5.fsf@gmail.com> (raw)
In-Reply-To: <877eauuouq.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Mon, 13 May 2019 15:38:21 -0400")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Glenn Morris <rgm@gnu.org> writes:
>
>> Does an end-user who does not compile Emacs themselves receive any
>> notification about avoiding tls.el?
>
> Hm...  It's in lisp/obsolete.

Note: it wasn't when Glenn posted that.  See Bug#31457 "27.0.50; Move
starttls.el and tls.el to lisp/obsolete/".

> Does Emacs have a general method to warn
> about requiring files in that directory?

Emacs does warn about requiring files from obsolete.  Users loading
tls.el will now get this in *Messages*:

    Package tls is obsolete!

It's not super visible though, opening a connection with tls.el produces
several other messages too, so it looks something like this:

    Opening TLS connection to ‘example.com’...
    Opening TLS connection with ‘gnutls-cli --x509cafile /etc/ssl/certs/ca-certificates.crt -p 443 example.com’...
    Package tls is obsolete!
    Opening TLS connection with ‘gnutls-cli --x509cafile /etc/ssl/certs/ca-certificates.crt -p 443 example.com’...done
    Opening TLS connection to ‘example.com’...done





  parent reply	other threads:[~2019-05-13 20:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02  2:33 bug#31339: 25.3.50; package-list-packages does not provide useful error when gnutls-cli is missing Eric Hanchrow
2018-05-02 14:52 ` Eli Zaretskii
2018-05-02 22:12   ` Glenn Morris
2019-05-13 19:38     ` Lars Ingebrigtsen
2019-05-13 20:00       ` Glenn Morris
2019-05-13 20:11         ` Lars Ingebrigtsen
2019-05-13 20:02       ` npostavs [this message]
2019-09-15  1:06 ` Stefan Kangas

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=85zhnqw2a5.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=31339@debbugs.gnu.org \
    --cc=eric.hanchrow@gmail.com \
    --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).