unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Rustom Mody <rustompmody@gmail.com>
Cc: 21145@debbugs.gnu.org, bruce.connor.am@gmail.com
Subject: bug#21145: 24.4; package update gives tls errors
Date: Tue, 28 Jul 2015 18:34:03 +0300	[thread overview]
Message-ID: <83fv48xpn8.fsf@gnu.org> (raw)
In-Reply-To: <CAJ+TeodVkBmF8+wypf6pMRBJ9vctmsCFZTuJSdhAEXzhPs6rEA@mail.gmail.com>

> From: Rustom Mody <rustompmody@gmail.com>
> Date: Tue, 28 Jul 2015 19:24:53 +0530
> Cc: Eli Zaretskii <eliz@gnu.org>, 21145@debbugs.gnu.org
> 
> In the spirit of Artur's 'uneducated guess' I too found this described
> all over with no solutions.
> So my uneducated response was to inform that the problem seems to
> remain and now closer to
> emacs-core as package moves there.

GnuTLS is not part of Emacs.  If on your platform it is part of the
Emacs package, that is a decision of whoever packages Emacs on that
system.  Nevertheless, GnuTLS is a separate project developed outside
of Emacs; Emacs just uses it.

> If Eli feels that my reporting it to gnutls will help I'll try doing
> it; but frankly Ive no frigging clue what gnutls is and think that
> its *users* (viz emacs-devs) should report.

GnuTLS is a library, its home page is here:

  http://www.gnutls.org/

and its bug reporting address is bugs@gnutls.org.

> Still...
> If you (Eli) want me to report it I'll try doing so

Yes, please.  I cannot report a problem I can't reproduce, because I
will be unable to answer any questions GnuTLS developers might wish to
ask me.





  reply	other threads:[~2015-07-28 15:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28  2:59 bug#21145: 24.4; package update gives tls errors Rustom Mody
2015-07-28 10:12 ` Eli Zaretskii
2015-07-28 11:21   ` Rustom Mody
2015-07-28 11:38     ` Eli Zaretskii
2015-07-28 13:15       ` Artur Malabarba
2015-07-28 13:54         ` Rustom Mody
2015-07-28 15:34           ` Eli Zaretskii [this message]
2015-07-28 17:08             ` Rustom Mody
2015-11-05 18:51         ` Ted Zlatanov
2016-02-05  7:15           ` 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=83fv48xpn8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21145@debbugs.gnu.org \
    --cc=bruce.connor.am@gmail.com \
    --cc=rustompmody@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).