DEPLOY.md - add GPG Troubleshooting #2560
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added troubleshooting tips for two problems I run into and had troubles fixing. The cause of the former is mentioned elsewhere in the docs but when you run into it, a Troubleshooting section is the natural place to look for solution. The latter is caused by inconsistent/unclear docs that mention `lein deploy clojars` but either do not have clojars explicitly in the repositories (because it is baked in, I assume) or have it under "releases". Perhaps some clarification could be made there as well. However we should certainly demonstrate how to make gpg auth work with `lein deploy clojars` since that is what e.g. the tutorial uses.
| `lein deploy` fails with _gpg: decryption failed: No secret key_ | ||
| Likely your secret key is protected by a passphrase, which lein cannot | ||
| ask for (yet). Run `gpg --quiet --batch --decrypt ~/.lein/credentials.clj.gpg` | ||
| to verify that you can decrpyt the credentials and to cache the passphrase |
Collaborator
There was a problem hiding this comment.
Suggested change
| to verify that you can decrpyt the credentials and to cache the passphrase | |
| to verify that you can decrypt the credentials and to cache the passphrase |
|
|
||
| #### Troubleshooting | ||
|
|
||
| `lein deploy` fails with _gpg: decryption failed: No secret key_ |
Collaborator
There was a problem hiding this comment.
Can you add some delineation between the problem and solution? Either a newline or a . or a - or something else which separates the two.
Author
|
Thank you, I will when I get back from Easter holiday.
…On Thu, Apr 18, 2019, 3:10 AM Daniel Compton ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In doc/DEPLOY.md
<#2560 (comment)>
:
> @@ -175,6 +175,21 @@ Note to windows users: Be sure to download the full version of
select GPA for installation. You then need to run
`gpg-connect-agent /bye` from the command line before starting lein.
+#### Troubleshooting
+
+`lein deploy` fails with _gpg: decryption failed: No secret key_
+Likely your secret key is protected by a passphrase, which lein cannot
+ask for (yet). Run `gpg --quiet --batch --decrypt ~/.lein/credentials.clj.gpg`
+to verify that you can decrpyt the credentials and to cache the passphrase
⬇️ Suggested change
-to verify that you can decrpyt the credentials and to cache the passphrase
+to verify that you can decrypt the credentials and to cache the passphrase
------------------------------
In doc/DEPLOY.md
<#2560 (comment)>
:
> @@ -175,6 +175,21 @@ Note to windows users: Be sure to download the full version of
select GPA for installation. You then need to run
`gpg-connect-agent /bye` from the command line before starting lein.
+#### Troubleshooting
+
+`lein deploy` fails with _gpg: decryption failed: No secret key_
Can you add some delineation between the problem and solution? Either a
newline or a . or a - or something else which separates the two.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2560 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEYSPWO3BAMVUMMY3FHJ6LPQ7C77ANCNFSM4HGRAJYA>
.
|
Collaborator
|
Passing by … are you aware of the documentation at doc/GPG.md? That file has a ‘troubleshooting’ section, and there is some overlap with the changes proposed here. I think these could better be consolidated in one place. |
cmc49ers23
approved these changes
Apr 16, 2025
cmc49ers23
approved these changes
Apr 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added troubleshooting tips for two problems I run into and had troubles fixing. The cause of the former is mentioned elsewhere in the docs but when you run into it, a Troubleshooting section is the natural place to look for solution. The latter is caused by inconsistent/unclear docs that mention
lein deploy clojarsbut either do not have clojars explicitly in the repositories (because it is baked in, I assume) or have it under "releases". Perhaps some clarification could be made there as well. However we should certainly demonstrate how to make gpg auth work withlein deploy clojarssince that is what e.g. the tutorial uses.