Bug#1023601: [pkg-gnupg-maint] Bug#1023601: Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it
On Tue 2022-11-15 18:24:11 +0100, Andreas Metzler wrote: > 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. I believe you, but that's disappointing, because it suggests that debian's CI tests are still lacking -- the only things that are showing up as a potential blocker on https://tracker.debian.org/pkg/gpgme1.0 (via automated testing) are the rust bindings :( > 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? I appreciate your looking into this, Andreas! --dkg signature.asc Description: PGP signature
Bug#1023601: Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it
On 2022-11-15 Daniel Kahn Gillmor 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'
