Re: update on GPG kys in Savannah

[Ineiev]

On Mon, May 17, 2021 at 12:12:45PM +0000, Ineiev wrote:
> On Thu, Apr 15, 2021 at 10:38:04AM +0000, Ineiev wrote:
> > 
> > Recently, Savannah has changed the way how release GPG
> > keys are published, the Information for GNU maintainers
> > needs an update like follows.

Updated patch: a newline was missing after @item on line 1646.

Index: maintain.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.280
diff -U 2 -r1.280 maintain.texi
--- maintain.texi       23 Aug 2020 22:01:44 -0000      1.280
+++ maintain.texi       25 Jun 2021 07:16:17 -0000
@@ -1616,22 +1616,8 @@
 @enumerate
 @item
-Create an account for yourself at @url{https://savannah.gnu.org}, if
-you don't already have one.  By the way, this is also needed to
-maintain the web pages at @url{https://www.gnu.org} for your project
-(@pxref{Web Pages}).
-
-@item
-In the @samp{My Account Conf} page on @code{savannah}, upload the GPG
-key (in ASCII-armored format) that you will use to sign your packages.
-If you haven't created one before, you can do so with the command
-@code{gpg --gen-key} (you can accept and/or confirm the default
-answers to its questions).  Then, to get the ASCII-armored version,
-run @samp{gpg --export --armor @var{your_key_id}}.
-
-Optional but recommended: Send your key to a GPG public key server:
-@code{gpg --keyserver keys.gnupg.net --send-keys @var{keyid}}, where
-@var{keyid} is the eight hex digits reported by @code{gpg
---list-public-keys} on the @code{pub} line before the date.  For full
-information about GPG, see @url{https://www.gnu.org/software/gpg}.
+Create an account for yourself at @url{https://savannah.gnu.org},
+and register your package there, if you haven't already done that.
+By the way, this is also needed to maintain the web pages at
+@url{https://www.gnu.org} for your project (@pxref{Web Pages}).

 @item
@@ -1657,4 +1643,16 @@
 ASCII armored copies of GPG keys for any individuals listed in (3).
 @end enumerate
+
+@item
+Publish the concatenated ASCII armored copies of your GPG key
+with the GPG keys listed in the previous step in the @samp{GPG Keys Used
+for Releases} area of the @samp{Public info} of the Savannah group
+of your package.
+
+Optional but recommended: Send your keys to a GPG public key server:
+@code{gpg --keyserver keys.gnupg.net --send-keys @var{keyid}...}, where
+@var{keyid} is the eight hex digits reported by @code{gpg
+--list-public-keys} on the @code{pub} line before the date.  For full
+information about GPG, see @url{https://www.gnu.org/software/gpg}.
 @end enumerate

signature.asc
Description: PGP signature