emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#38586: closed (Can not obtain gpg keys for binary install)


From: GNU bug Tracking System
Subject: bug#38586: closed (Can not obtain gpg keys for binary install)
Date: Thu, 12 Dec 2019 23:44:02 +0000

Your message dated Fri, 13 Dec 2019 00:43:31 +0100
with message-id <87sglphzz0.fsf@nckx>
and subject line Re: bug#38586: Can not obtain gpg keys for binary install
has caused the debbugs.gnu.org bug report #38586,
regarding Can not obtain gpg keys for binary install
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
38586: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=38586
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Can not obtain gpg keys for binary install Date: Thu, 12 Dec 2019 23:43:31 +0100
Also when trying to install via binary, I am not able to obtain the gpg keys (see picture below)
image.png

--- End Message ---
--- Begin Message --- Subject: Re: bug#38586: Can not obtain gpg keys for binary install Date: Fri, 13 Dec 2019 00:43:31 +0100
dalanicolai 写道:
Also when trying to install via binary, I am not able to obtain the gpg
keys (see picture below)
[image: image.png]

I assume you copy and pasted these URLs from the ‘Binary Installation’ section of the manual. And the text explicitly states:

 1. Download the binary tarball from
    ‘https://ftp.gnu.org/gnu/guix/guix-binary-0.0-git.SYSTEM.tar.xz’,
where SYSTEM is ‘x86_64-linux’ for an ‘x86_64’ machine already
    running the kernel Linux, and so on.

Indeed:

λ curl https://ftp.gnu.org/gnu/guix/guix-binary-1.0.1.x86_64-linux.tar.xz.sig
 -----BEGIN PGP SIGNATURE-----
 iQIzBAABCAAdFiEEPORkVYqE/cadtAz7CQsRmT2a67UFAlzhwOcACgkQCQsRmT2a
 67VRIg//QrxO5Qip+p5l+SmcvffgWVRR76bpxm7eE8tovwXxMMH3hU9Mqi5DNQ/X
 pE8/CbJkt4VEx0Y2ozlxwkBA1n3PwLd49/ouJXxcipNw3kFw0g1F+yv5KjSsDi+F
 kgjJ59u9w5oaMYo5s54f2WI0y9USxoq/2GT1Xi29MSG4A7PEXzWvJUuobNnCvTYQ
 vJ+QnqVBzcNRBWhrM7l7WP6L8qw1QfWVLfaH/SLLh2Nh4db5cTkYVOTSIwFYAUCi
 KKtcy9FAYOQsuQAX3KfSgWAx/G2iCx2D4WGf2ij8hEn8dZguB4L+YOtSnRxIPrtP
 x6ZKfawMUi5wfP0sF+jgTsnVZiPtqh5LDLmyy+fCTfVledWfugJgkXxoOLW8Oonf
 nzSPWmCNS/ITSKKmzCiIptJtStvZQ1ZUpAF3xcajAb1zor7i7XlMeLb0Dvtg7Icb
 dErAbrra648aA8ZOCpXK/thF3MZDyId5QVxKqkLhyr4oT4Pw3drr4WvFDCUs51Um
 jY4xiOug6yeog/Ip+D7661dX628ZquAmSHCR+Sih48nIeZIXDepNPNf/pLMYSPYi
 fSmS0ac3WTnBCW7Y5x3sQPb1kFDoz3a2OxHPusMSC4N8KhrS3Au+ZImdtL+LGxfq
 jtbuxXWSnzNru3MXPfyV/OfWaphY3L64KDKjAiSTnFv+QoecgYI=
 =V6yd
 -----END PGP SIGNATURE-----

Thanks,

T G-R

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]