Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add FAQ for "no pinentry" issue #118

Merged
merged 1 commit into from
Sep 10, 2024
Merged

Add FAQ for "no pinentry" issue #118

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions src/site/fml/faq.fml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,5 +43,16 @@ under the License.
</p>
</answer>
</faq>
<faq id="no-pinentry">
<question>Why am I getting "gpg: signing failed: No pinentry" while releasing?</question>
<answer>
<p>
When plugin used in combination with <a href="https://maven.apache.org/maven-release/maven-release-plugin/">Maven Release Plugin</a>
the GPG signing will happen in "batch mode". This implies that you must either use GPG passphrase passed in
via environment variable (preferred on systems like CI systems are), or, if on Workstation, using primed
gpg-agent is needed. Read more here about <a href="usage.html#sign-artifacts-with-gnupg">GPG Agent priming</a>.
</p>
</answer>
</faq>
</part>
</faqs>