[pkg-gnupg-maint] Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it

Andreas Metzler ametzler at bebt.de
Wed Nov 16 18:32:29 GMT 2022


On 2022-11-16 Daniel Kahn Gillmor <dkg at fifthhorseman.net> wrote:
> On Tue 2022-11-15 18:24:11 +0100, Andreas Metzler wrote:
[...]
> > The main reason was AM_PATH_GPGME's pre-dependency on
> > AM_PATH_GPG_ERROR.  (This also caused the mutt breakage
> > afaict). However Niibe Yutaka has pushed updates for gpg-error.m4 and
> > gpgme.m4 yesterday in upstream git which should fix this.

> Hm, so in terms of upstream git, gpgme has two updates for src/gpgme.m4,
> and libgpg-error has one update to src/gpg-error.m4 that i can see.

> Do you think we should pull those changes into both source packages in
> debian?  or should we wait for (or explicitly encourage) an upstream
> release?

Hello,

Assuming the changes work as advertised (no tests on my side, I will not
have time till weekend) I think both m4 files should be updated in
Debian without waiting for an upstream release. gpgme.m4 is the
important one, the change for gpg-error.m4 is a performance improvement,
avoiding testing for gpgrt twice when both AM_PATH_GPGME (new version) and
AM_PATH_GPG_ERROR (unpatched) are used.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



More information about the pkg-gnupg-maint mailing list