On 2023-11-01 Vincent Lefevre <vinc...@vinc17.net> wrote: > On 2023-11-01 18:39:24 +0100, Andreas Metzler wrote: > > I am closing this since afaict this is a solved issue and I do not see > > any TODOs on the gpgme side. > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=gpgme-config-transition;users=pkg-gnupg-ma...@lists.alioth.debian.org > > has shrunk to 4 open bugs, three of them with patches (undead packages?) > > and I am going to close the fourth one myself since it seems to have > > been fixed upstream and has been fixed in Debian by a uploading this > > version.
> Yes, this was at least fixed in Mutt. I'm not aware of any new issue > in other software, and as there were no new comments since last year, > I assume that this has been fixed everywhere (or no-one cares). Thank god I can provide the more like explanation that the gnupg maintainer team held their promise and diagnosed, tracked, provided patches for and if necessary NMUed the affected packages. cu Andreas
