unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: "J.P." <jp@neverwas.me>
Cc: Kai Tetzlaff <emacs+bug@tetzco.de>, 58985@debbugs.gnu.org
Subject: bug#58985: 29.0.50; Gnus setup broken by commit 2cf9e699ef0fc43a4eadaf00a1ed2f876765c64d
Date: Thu, 24 Nov 2022 15:38:02 +0000	[thread overview]
Message-ID: <87ilj4uzvp.fsf@gmail.com> (raw)
In-Reply-To: <87fse8wg4g.fsf@neverwas.me> (J. P.'s message of "Thu, 24 Nov 2022 07:01:51 -0800")

"J.P." <jp@neverwas.me> writes:

> If we were actually gonna try and debug this, I'd probably ask you for
> the names of the affected items in your ~/.password-store and the query
> params passed to `auth-source-search' and maybe also whatever's printed
> to *Messages* when a query is performed with `auth-source-debug' turned
> on.

The affected item is, I believe, ~/.password-store/local-gmail:imap.gpg
and likely also ~/.password-store/smtp.gmail.com:465.gpg.  When I set
auth-source-debug to t, these lines appeared in *Messages*

auth-source-pass: final result: nil
auth-source-search: found 0 results (max 1) matching (:max 1 :host ("local-gmail" "localhost") :port ("imap" "imap" "143") :user "joaotavora@gmail.com" :require (:user :secret) :create t)
auth-source-pass: final result: nil
auth-source-search: CREATED 0 results (max 1) matching (:max 1 :host ("local-gmail" "localhost") :port ("imap" "imap" "143") :user "joaotavora@gmail.com" :require (:user :secret) :create t)
Opening nnimap server on local-gmail...failed: 

> However, I think it's probably best to forgo all that and do what I was
> leaning toward from the outset, and that's keeping the new behavior off
> by default in Emacs 29. It's looking liable to cause too much churn for
> too many folks [1]. Thus, unless anyone objects or has anything else to
> add, I will do this in the next 24 hours or so. Apologies again for the
> disruption and the time spent bisecting.

No problem, and thanks for understanding.  I think it is indeed better
if you make this opt-in. I can then opt into it and help you debug the
root cause.  But in the meantime, my email won't be broken :-)

João





  reply	other threads:[~2022-11-24 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 10:31 bug#59538: 29.0.50; Gnus setup broken by commit 2cf9e699ef0fc43a4eadaf00a1ed2f876765c64d João Távora
2022-11-24 15:01 ` bug#58985: " J.P.
2022-11-24 15:38   ` João Távora [this message]
2022-11-25 14:23     ` J.P.
2024-02-21 21:25 ` bug#59538: " Jakub Ječmínek via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-21 22:04   ` João Távora
2024-02-21 22:20     ` Jakub Ječmínek via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87ilj4uzvp.fsf@gmail.com \
    --to=joaotavora@gmail.com \
    --cc=58985@debbugs.gnu.org \
    --cc=emacs+bug@tetzco.de \
    --cc=jp@neverwas.me \
    /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).