On 2017-11-05 21:14, Elena ``of Valhalla'' wrote: > It is true, however, that debian is migrating towards gnupg2, so if you > (or anybody else) don't want to be stuck with both versions for another > release what I can do is to provide a backport of the version currently > in testing, as that one has gone back to use gpg as the gpgbinary.
Yes, please backport! > (A note to myself, so that I don't forget about it: before uploading the > backport I need to check that it does not break gajim and act > appropriately if it does.) Gajim 0.16.6-1.1 in stable still embeds its own copy of python-gnugp. Not good, but good in this case. Gajim 0.16.8-3~bpo9+1 in stretch-backports explicitely uses 'gpg1', but if a newer python-gnupg were in backports, we could just depend on python-gnupg >= 0.4.1 what is done in testing anyway. I can upload as soon as your backport passes bpo-NEW.
signature.asc
Description: PGP signature