On 2022-11-08 Vincent Lefevre <vinc...@vinc17.net> wrote: > On 2022-11-07 13:36:30 +0100, Vincent Lefevre wrote: > > The removal of gpgme-config due to > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348 > > > > breaks the build of software relying on it, such as Mutt: [...] > Actually gpgrt-config can be used instead of gpgme-config. But > this requires changes in existing code, possibly non trivial, > as now done for Mutt:
> https://gitlab.com/muttmua/mutt/-/issues/430 > (not yet in Debian). > So before gpgme-config gets removed (which is a *recent* upstream > change), you should make sure that existing code based on it has > been updated. Hello Vincent, Disclaimer: I am not in uploaders of gpg packaging but follow the list. We were aware that some breakage was to be expected (a little bit late, though), and will provide help/assistance (quoting Daniel 1023601: "this might cause knock-on effects for projects that themselves think they should be dependent on gpgme-config, but i'll try to sort those through as well.") I do not think the bug severity is correct. It does not break any binary packages, i.e. it fits "a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone." One might argue that the combination of this gpgme version with unbuildable packages is not releaseable and up with serious. 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'