[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#59538: 29.0.50; Gnus setup broken by commit 2cf9e699ef0fc43a4eadaf00
From: |
João Távora |
Subject: |
bug#59538: 29.0.50; Gnus setup broken by commit 2cf9e699ef0fc43a4eadaf00a1ed2f876765c64d |
Date: |
Wed, 21 Feb 2024 22:04:57 +0000 |
On Wed, Feb 21, 2024 at 9:25 PM Jakub Ječmínek <kuba@kubajecminek.cz> wrote:
>
> João Távora <joaotavora@gmail.com> writes:
> > Hi Maintainers,
> >
> > Commit 2cf9e699ef0fc43a4eadaf00a1ed2f876765c64d breaks my Gnus setup.
> >
> > Author: F. Jason Park <jp@neverwas.me>
> > Date: Tue Nov 1 22:46:24 2022 -0700
> >
> > Make auth-source-pass behave more like other backends
> >
> > I've reached this conclusion through 'git bisect'. I.e. the commit which
> > immediately precedes it is not broken.
> >
> > I haven't investigated why, but I do use 'pass' (www.passwordstore.org) to
> > (require 'auth-source)
> > (auth-source-pass-enable)
> > (setq auth-sources '(password-store)) ;; don't use anything else
> >
> > store my passwords securely.
> >
> > This is my pass-related setup, which is pretty simple:
> >
> > After the commit, M-x gnus is unable to connect to my local imap server.
> > There
> > is very little debug information.
>
> Hello João,
> thanks for the bug report! I wasn't able to reproduce your issue on
> current master. Do you still experience the same problem?
>
> I started emacs with the -Q option, evaluated this snippet:
>
> (require 'auth-source)
> (auth-source-pass-enable)
> (setq auth-sources '(password-store))
>
> and configured gnus-select-method. Credentials were successfully
> decrypted and Gnus was able to connect without any issues. If you happen
> to have the same issue, can you evaluate this snippet and confirm that
> your pass entry is in the list? Thanks.
>
> (let ((hostname "gmail")
> (user "username@gmail.com")
> (port 993))
> (auth-source-pass--generate-entry-suffixes hostname user port))
>
> --
> Kuba Ječmínek (http://kubajecminek.cz)
This seems to be a perfect duplicate of bug#58985 (not sure why two bugs
were created back then). Anyway, that bug was promptly addressed and
fixed by J.P. as described here.
https://lists.gnu.org/archive/html/bug-gnu-emacs/2022-11/msg02133.html
João