* Daniel Kahn Gillmor [2022-11-23 08:24]:
Thanks for confirming! It'd be great to clear the decks for the gpgme
transition, so please let me know if you'd like me to NMU neomutt with
that patch, or if you have any plans for a release any time soon.
I'm not part of the Mutt maintainer team, unf
Hi Timo--
On Tue 2022-11-22 15:58:21 +0100, Timo Röhling wrote:
> I have built neomutt with your patch and can confirm that the GPGme
> integration works as expected.
Thanks for confirming! It'd be great to clear the decks for the gpgme
transition, so please let me know if you'd like me to NMU n
Hi Daniel,
* Daniel Kahn Gillmor [2022-11-21 19:24]:
The attached patch appears to fix things for me so that neomutt builds
successfully against libgpgme-dev 1.18.0-3, though i don't know enough
about how to adequately test neomutt to be confident in the results (i
don't use neomutt myself).
I
Control: tags 1023767 + patch
On Wed 2022-11-09 22:04:00 +0100, Timo Röhling wrote:
> neomutt fails to build with the recent libgpgme-dev update that dropped
> the gpgme-config executable.
>
> https://github.com/neomutt/neomutt/pull/3555 fixes the problem, but does
> not apply cleanly to the neomu
Source: neomutt
Version: 20220429+dfsg1-4
Severity: serious
Tags: ftbfs fixed-upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainers,
neomutt fails to build with the recent libgpgme-dev update that dropped
the gpgme-config executable.
https://github.com/neomutt/neomutt/pull/3
5 matches
Mail list logo
