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

[Andreas Metzler]

On 2022-11-15 Daniel Kahn Gillmor <dkg at fifthhorseman.net> wrote:
[...]
> fwiw, upstream has indicated that gpgrt-config is an "internal"
> interface, so this is not something that should be used explicitly by
> external dependencies.

Hello,

that was my impression also when I looked at it since gpgrt-config does
not work out of the box but needs to be explicitely told where the pc
files can be found.

[...]
> I've reclassified this bug to severity: important because i think that
> we should try to go with the upstream default preferences.  In the event
> that a significant amount of unrelated debian-internal software is
> broken by these change, i'm willing to consider a reversion to the
> changes in libgpg-error, but at the moment the only remaining packages
> i've seen are:

>  rust-libgpg-error-sys
>  rust-libgpgme-sys
>  mutt
[...]

I had started trying to rebuild all packages build-depending on gpgme
last weekend and out of the first 5 at least every other package failed
or lost its gpgme linkage. 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.

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'