Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Major mess with nnimap running latest (today) git pull
Date: Thu, 27 Jul 2017 08:33:08 -0700	[thread overview]
Message-ID: <87wp6tsxmz.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86mv7pnbr3.fsf@local.lan>

Harry Putnam <reader@newsguy.com> writes:

> I've been running versions 26 right along but fell back to 24 a while
> back.  Something I was doing then .. and never returned to v 26.  No
> particular reason.
>
> I noticed it today and switched back to my version 26 from several weeks
> ago.
>
> No problems cropped up.  Things ran just the same in the ways I
> usually use gnus when I used the several weeks old v26 as they did in
> v24. 
>
> I got the idea that I probably needed to update my local git branch of
> emacs and update to the latest.  Upon doing so, I hit some kind of
> mess with nnimap soon as I started gnus.

[...]

> (Seems all my certs are failing)

The problem is almost certainly in gnutls, not nnimap (which hasn't been
updated since January). Gnutls, on the other hand, has had a lot of
tweaks recently. I'd raise this on emacs.help...




  reply	other threads:[~2017-07-27 15:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27 15:24 Harry Putnam
2017-07-27 15:33 ` Eric Abrahamsen [this message]
2017-07-29 15:12   ` Harry Putnam
2017-07-27 15:37 ` Robert Pluim
2017-07-29 14:53   ` Harry Putnam
2017-07-31  7:54     ` Robert Pluim
2017-07-28 14:46 ` Byung-Hee HWANG (황병희, 黃炳熙)
2017-07-29 14:52   ` Harry Putnam
2017-07-29 16:21   ` Harry Putnam
2017-07-30  3:04     ` [Just off topic ...] (was: Re: Major mess with nnimap running latest (today) git pull) Byung-Hee HWANG (황병희, 黃炳熙)
2017-07-29 17:12 ` Major mess with nnimap running latest (today) git pull Harry Putnam

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=87wp6tsxmz.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@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.
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 NNTP newsgroup(s).