Nils Gillmann <n...@n0.is> writes: > Alex Vong transcribed 1.1K bytes: >> l...@gnu.org (Ludovic Courtès) writes: >> >> > Hi Alex, >> > >> > Alex Vong <alexvong1...@gmail.com> skribis: >> > >> >> l...@gnu.org (Ludovic Courtès) writes: >> > >> > [...] >> > >> >>> I’ve added you to the group on Savannah, so you now have commit access. >> >>> >> >>> Please upload the OpenPGP key you will use to sign commits to Savannah, >> >>> and reply with a message signed with this key. >> >>> >> >> I receive the following error message when I test my uploaded openpgp >> >> key: >> > >> > By “uploading”, I meant you have to manually paste the ASCII-armored >> > output to the Savannah web interface; there’s no key server there. >> > >> Yes, I am using a ECC key. Does it work with Savannah? > > At the moment? Not at all. > I've had this discussion with the savannah admin, they expected to > update their gnupg at earliest sometime in 2019. > > If you have added the ECC key already it might happen that your > key won't work at all after a correction, so you need to contact > the admin anyway (so that they can fix your key/account). > Thanks everyone for the help! I've pushed my 1st commit as c991806a7d9817c8c204dfd0813144aa0ea96c57. This is the first time I ever push to a repo not own by myself!
Besides, you can follow this bug report[0] for ECC key support in Savannah (I'm unaware that Nils previously had discussion with the admin as well). >> > HTH! >> > >> > Ludo’. [0]: https://savannah.gnu.org/support/?109583
signature.asc
Description: PGP signature
