wangyum commented on code in PR #54:
URL: https://github.com/apache/spark-docker/pull/54#discussion_r1300873405


##########
tools/template.py:
##########
@@ -28,6 +28,8 @@
     "3.3.1": "86727D43E73A415F67A0B1A14E68B3E6CD473653",
     # issuer "[email protected]"
     "3.3.2": "C56349D886F2B01F8CAE794C653C2301FEA493EE",
+    # issuer "[email protected]"
+    "3.3.3": "F6468A4FF8377B4F1C07BC2AA077F928A0BF68D8",

Review Comment:
   It seems can't add keys from `hkps://keys.openpgp.org`:
   ```
   #19 21.44 + gpg --keyserver hkps://keys.openpgp.org --recv-key 
F6468A4FF8377B4F1C07BC2AA077F928A0BF68D8
   #19 21.49 gpg: keybox '/tmp/tmp.0eI3yRt1g0/pubring.kbx' created
   #19 22.59 gpg: key A077F928A0BF68D8: new key but contains no user ID - 
skipped
   #19 22.59 gpg: Total number processed: 1
   #19 22.59 gpg:           w/o user IDs: 1
   #19 22.59 + gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 
F6468A4FF8377B4F1C07BC2AA077F928A0BF68D8
   #19 23.27 gpg: /tmp/tmp.0eI3yRt1g0/trustdb.gpg: trustdb created
   #19 23.28 gpg: key A077F928A0BF68D8: public key "Yuming Wang (CODE SIGNING 
KEY) <[email protected]>" imported
   #19 23.37 gpg: Total number processed: 1
   #19 23.37 gpg:               imported: 1
   #19 23.38 + gpg --batch --verify spark.tgz.asc spark.tgz
   #19 29.95 gpg: Signature made Fri 04 Aug 2023 04:18:57 PM UTC
   #19 29.95 gpg:                using RSA key 
F6468A4FF8377B4F1C07BC2AA077F928A0BF68D8
   #19 29.95 gpg:                issuer "[email protected]"
   #19 29.98 gpg: Good signature from "Yuming Wang (CODE SIGNING KEY) 
<[email protected]>" [unknown]
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to