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.
Description of problem:
User is creating a GPG key to commit in his repo. When he try to create a GPG key the "error: error No pinentry" error is reported.
To solve this issue:
Adding RPM pinentry in file devspaces/context/setup.sh.
Context is presented here: https://issues.redhat.com/browse/CRW-7895
Thank you for your help!
Steps to Reproduce
Launch the workspace: Ansible
then run ;
gpg --gen-key
After entering your name and e-mail you will have the error:
gpg: agent_genkey failed: No pinentry
Key generation failed: No pinentry
Actual results:
gpg creation results in following error:
gpg: key D79: error sending to agent: No pinentry
gpg: error building skey array: No pinentry
gpg: error reading 'myprivatekeys.asc': No pinentry
gpg: import from 'myprivatekeys.asc' failed: No pinentry
Expected results:
GPG key creation should proceed