all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 29147@debbugs.gnu.org, tzz@lifelogs.com, juri@linkov.net
Subject: bug#29147: 27.0.50; gnutls-available-p broken
Date: Sun, 05 Nov 2017 17:29:22 +0200	[thread overview]
Message-ID: <838tfku4kt.fsf@gnu.org> (raw)
In-Reply-To: <87inepvvum.fsf@gmail.com> (message from Robert Pluim on Sun, 05 Nov 2017 11:54:57 +0100)

> From: Robert Pluim <rpluim@gmail.com>
> Date: Sun, 05 Nov 2017 11:54:57 +0100
> Cc: 29147@debbugs.gnu.org, Ted Zlatanov <tzz@lifelogs.com>
> 
> Juri Linkov <juri@linkov.net> writes:
> 
> > The Emacs GnuTLS manual says that gnutls-available-p returns t
> > if GnuTLS is available, but really it returns nil, and I don't see
> > how gnutls-available-p is supposed to return a non-nil value
> > when HAVE_GNUTLS is defined, but HAVE_GNUTLS3 is not.
> 
> Its docstring says:
> 
>     gnutls-available-p is a built-in function in `C source code'.
> 
>     (gnutls-available-p)
> 
>     Return list of capabilities if GnuTLS is available in this instance of Emacs.
> 
> I see that the info documentation says it returns t, so that needs
> fixing.

Not just the documentation, the code as well needs fixing.

> Your point about HAVE_GNUTLS3 is valid, that's true as of commit
> 583995c62dd424775dda33d5134ce04bee2ae685. Ted, was that intentional?

I cannot see how this could be intentional, because it makes it
impossible to distinguish between GnuTLS 2.x and no GnuTLS at all.  So
I fixed this on the release branch.

If Juri (or someone else) has GnuTLS 2.x, please test and close the
bug if it is indeed fixed.

Thanks.





  reply	other threads:[~2017-11-05 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04 21:53 bug#29147: 27.0.50; gnutls-available-p broken Juri Linkov
2017-11-05 10:54 ` Robert Pluim
2017-11-05 15:29   ` Eli Zaretskii [this message]
2017-11-06 21:35     ` Juri Linkov

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838tfku4kt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=29147@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=rpluim@gmail.com \
    --cc=tzz@lifelogs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.