On Tue, Jul 15, 2025 at 03:39:26PM -0600, Karl Berry wrote: > On https://savannah.gnu.org/project/admin/editgroupinfo.php > there is a block to "Update your keys in this input area" about updating > the GPG keys for a project. (I suggest adding "GPG" before "keys" in > that title to avoid anyone thinking it's about ssh keys.) > > When adding a new key, is it necessary to upload the whole keyring > including all the old keys? Or will uploading the new key by itself > suffice, and Savannah will automatically merge it in?
Savannah doesn't merge keys, it will serve what was last time uploaded; so maintainers can remove things like expired signatures, outdated user IDs and so on. > Whatever the answer is, I suggest stating it on the page. Right now, the > fact that the input textarea includes all the keys sort of implies that > it should be all the keys, while the text "Insert *your* (ASCII) public > keys here" (my emphasis) sort of implies it can just be the new key. Thank you, I'll clarify the texts. > And, if it has to be all the keys, it would be nice to link to > instructions for how to do it, that is, how to add a key to a .keyring > file independent of one's own personal ~/.gnupg stuff. Personally I > don't have the foggiest. All my attempts to run commands that operate > independently of ~/.gnupg have failed, so I've had to resort to > --homedir. Maybe that is indeed the only way. I don't know. --thanks, karl. I'll write some directions in Savannah sviki. Basically, `cat new-key.asc >> .keyring` will work.
signature.asc
Description: PGP signature
