"Darshit Shah" writes:
> I don't have push access to gnulib, so could you please push it for me?
I ended up pushing the patch below. There are several considerations
here:
* We want the OpenPGP Key identifier to be mentioned in the e-mail, it
provides a strong hash-based coupling between
On Sun, Mar 13, 2022, at 09:10, Simon Josefsson wrote:
> Darshit Shah writes:
>
>> + --gpg-keyring-url=URLURL pointing to the GnuPG Keyring containing
>> +the key used to sign the tarballs
> ...
>> If that command fails because you don't have the
Darshit Shah writes:
> + --gpg-keyring-url=URLURL pointing to the GnuPG Keyring containing
> +the key used to sign the tarballs
...
> If that command fails because you don't have the required public key,
> then run this command to import it:
>
> -
Okay, I decided to take the easy way out and wrote this patch instead. The URL
was too long and ugly in the --help output, so I'm glad to remove it from
there.
-- >8 --
* build-aux/announce-gen: The default SKS Keyserver pool for GnuPG Keys was
deprecated and has been offline since the middle
Sorry,
I just realized a glaring error in this patch. The $gpg_keyring_url variable is
not used at all. Instead the Savannah URL is hardcoded in the announce email.
My Perl is not good enough to immediately know how to force a lazy evaluation
of the variable in order to get the project name at
* build-aux/announce-gen: The default SKS Keyserver pool for GnuPG Keys was
deprecated and has been offline since the middle of 2021. The default
keyserver: keys.gnupg.net was just a mirror of the SKS Pool and is thus
offline as well. Instead, use the Release Keyring on Savannah to list the
GnuPG
