From: Ted Zlatanov <tzz@lifelogs.com>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: Yagnesh Raghava Yakkala <hi@yagnesh.org>, 19346@debbugs.gnu.org
Subject: bug#19346: 25.0.50; url-http-parse-headers: Symbol's function definition is void: gnutls-available-p
Date: Thu, 11 Dec 2014 11:08:45 -0500 [thread overview]
Message-ID: <m27fxynp82.fsf@lifelogs.com> (raw)
In-Reply-To: <m3h9x2mb5l.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 11 Dec 2014 16:57:58 +0100")
On Thu, 11 Dec 2014 16:57:58 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Yagnesh Raghava Yakkala <hi@yagnesh.org> writes:
>> while reading news from gnus I get above error.
>>
>> backtrace.
>>
>> ╭─────
>> │Debugger entered--Lisp error: (void-function gnutls-available-p)
>> │ gnutls-available-p()
>> │ url-http-parse-headers()
LMI> I've now pushed a fix for this.
Your fix uses `fboundp'. Should we make `gnutls-available-p' always
defined to return nil, to simplify this in the future?
Ted
next prev parent reply other threads:[~2014-12-11 16:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 10:57 bug#19346: 25.0.50; url-http-parse-headers: Symbol's function definition is void: gnutls-available-p Yagnesh Raghava Yakkala
2014-12-11 15:57 ` Lars Magne Ingebrigtsen
2014-12-11 16:08 ` Ted Zlatanov [this message]
2014-12-11 16:16 ` Lars Magne Ingebrigtsen
2014-12-11 18:00 ` Eli Zaretskii
2014-12-11 19:16 ` Stefan Monnier
2014-12-11 19:48 ` Ted Zlatanov
2014-12-11 21:03 ` Eli Zaretskii
2014-12-11 22:58 ` Ted Zlatanov
2014-12-12 0:02 ` Stefan Monnier
2014-12-12 0:21 ` Ted Zlatanov
2014-12-12 1:33 ` Stefan Monnier
2014-12-12 7:58 ` Eli Zaretskii
2014-12-12 14:40 ` Stefan Monnier
2014-12-12 14:54 ` Eli Zaretskii
2014-12-12 16:39 ` Stefan Monnier
2014-12-12 19:04 ` Eli Zaretskii
2014-12-12 21:56 ` Stefan Monnier
2014-12-13 7:43 ` Eli Zaretskii
2014-12-13 14:21 ` Stefan Monnier
2014-12-13 15:20 ` Eli Zaretskii
2014-12-12 13:19 ` Ted Zlatanov
2014-12-12 14:47 ` Stefan Monnier
2014-12-12 7:49 ` Eli Zaretskii
2014-12-12 14:42 ` Stefan Monnier
2014-12-12 14:55 ` Eli Zaretskii
2014-12-12 16:33 ` Stefan Monnier
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=m27fxynp82.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=19346@debbugs.gnu.org \
--cc=hi@yagnesh.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).