docs: Update release signing key.

The release artifacts are now signed by Efraim, not Ludo.

* doc/guix-cookbook.texi: Switch gpg url to codeberg, mention Efraim's key.
* doc/guix.texi: Likewise.

Change-Id: Iae667796b6978cdd4a44f73990da7b9599ab509c
Fixes: #5946
Signed-off-by: Rutherther <rutherther@ditigal.xyz>
Merges: #6213

2 files changed, 6 insertions, 6 deletions

diff --git a/doc/guix-cookbook.texi b/doc/guix-cookbook.texi
index 73b1e16b241..ffadd32c3de 100644
--- a/doc/guix-cookbook.texi
+++ b/doc/guix-cookbook.texi
@@ -3256,8 +3256,8 @@ your Linode Summary section.) Now you can run the "install guix from
 
 @example
 sudo apt-get install gpg
-wget https://sv.gnu.org/people/viewgpg.php?user_id=15145 -qO - | gpg --import -
-wget https://git.savannah.gnu.org/cgit/guix.git/plain/etc/guix-install.sh
+wget https://codeberg.org/efraim.gpg -qO - | gpg --import -
+wget https://guix.gnu.org/guix-install.sh
 chmod +x guix-install.sh
 ./guix-install.sh
 guix pull
@@ -3436,7 +3436,7 @@ Now you can run the "install guix from @pxref{Binary Installation,,,
 guix, GNU Guix}" steps:
 
 @example
-wget https://git.savannah.gnu.org/cgit/guix.git/plain/etc/guix-install.sh
+wget https://guix.gnu.org/guix-install.sh
 chmod +x guix-install.sh
 ./guix-install.sh
 guix pull
diff --git a/doc/guix.texi b/doc/guix.texi
index 6a7a9f8c35e..b2ff12dcb11 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -10,8 +10,8 @@
 @include version.texi
 
 @c Identifier of the OpenPGP key used to sign tarballs and such.
-@set OPENPGP-SIGNING-KEY-ID 3CE464558A84FDC69DB40CFB090B11993D9AEBB5
-@set OPENPGP-SIGNING-KEY-URL https://sv.gnu.org/people/viewgpg.php?user_id=15145
+@set OPENPGP-SIGNING-KEY-ID A28BF40C3E551372662D14F741AAE7DCCA3D8351
+@set OPENPGP-SIGNING-KEY-URL https://codeberg.org/efraim.gpg
 
 @c Base URL for downloads.
 @set BASE-URL https://ftpmirror.gnu.org/gnu/guix
@@ -14858,7 +14858,7 @@ provided through NuGet's v3 API at @code{api.nuget.org} and includes
 most relevant information, including package dependencies.
 There are some caveats, however.  The metadata does not always include
 repository information, in which case the importer attempts to extract
-it from the symbol package (@file{.snupkg}) if available. 
+it from the symbol package (@file{.snupkg}) if available.
 Additionally, dependencies are grouped by target framework in NuGet,
 but the importer flattens all dependency groups into a single list.