From: Rustom Mody <rustompmody@gmail.com>
To: bruce.connor.am@gmail.com
Cc: 21145@debbugs.gnu.org
Subject: bug#21145: 24.4; package update gives tls errors
Date: Tue, 28 Jul 2015 19:24:53 +0530 [thread overview]
Message-ID: <CAJ+TeodVkBmF8+wypf6pMRBJ9vctmsCFZTuJSdhAEXzhPs6rEA@mail.gmail.com> (raw)
In-Reply-To: <CAAdUY-LmptPH1FOXSKtbJkXerB0NCnsOxUug8sGecChrAepNmQ@mail.gmail.com>
On Tue, Jul 28, 2015 at 6:45 PM, Artur Malabarba
<bruce.connor.am@gmail.com> wrote:
>>> > I cannot reproduce this on my system (not on Ubuntu) with the same
>>> > version of GnuTLS. I get a listing of packages, including those from
>>> > marmalade, as expected.
>
> I can reproduce the message under different contexts at work. And I've
> received numerous reports about that on another package of mine. My
> uneducated guess is that it's something in GnuTLS, and not something
> Emacs can solve.
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.
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.
Still...
If you (Eli) want me to report it I'll try doing so
next prev parent reply other threads:[~2015-07-28 13:54 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 [this message]
2015-07-28 15:34 ` Eli Zaretskii
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=CAJ+TeodVkBmF8+wypf6pMRBJ9vctmsCFZTuJSdhAEXzhPs6rEA@mail.gmail.com \
--to=rustompmody@gmail.com \
--cc=21145@debbugs.gnu.org \
--cc=bruce.connor.am@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).