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