On 4/8/18 5:54 PM, Georg Faerber wrote: > Hi, > > On 18-04-08 17:29:17, Daniele Nicolodi wrote: >> On 08/04/2018 17:10, Mattia Rizzolo wrote: >>> On Sun, Apr 08, 2018 at 04:41:32PM -0600, Daniele Nicolodi wrote: >>>> I just tried to upload a package to mentors.debian.net and it got >>>> rejected because is is signed with an ed25519 key: >>>> >>>> gpg: Signature made So 08 Apr 2018 22:00:14 UTC using ? key ID C18A4F7D >>>> gpg: Can't check signature: unknown pubkey algorithm >>>> >>>> I guess the infrastructure has not been upgraded to GnuPG 2. >>> >>> Yes, when we upgraded the host 1,5 months ago we tried also moving >>> to gpg2, but that wasn't as straightforward as we'd hoped… So, we've >>> installed gnupg1 and changed the binary used. >>> >>> Patches welcome, as usual :) >> >> I can look into that. What code needs to be patched? > > Have a look at [1] to begin with.
At a first look that code can be updated to use pgpme and do not call out to a gpg binary. I'll give it a try. Just to be sure, is the code supposed to be run with the libraries in stable? Cheers, Dan
