You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Ryan Skraba (Jira)" <ji...@apache.org> on 2022/07/31 17:09:00 UTC

[jira] [Assigned] (AVRO-3593) [build] Signing artifacts in docker fails with "no pinentry"

     [ https://issues.apache.org/jira/browse/AVRO-3593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan Skraba reassigned AVRO-3593:
---------------------------------

    Assignee: Ryan Skraba

> [build] Signing artifacts in docker fails with "no pinentry"
> ------------------------------------------------------------
>
>                 Key: AVRO-3593
>                 URL: https://issues.apache.org/jira/browse/AVRO-3593
>             Project: Apache Avro
>          Issue Type: New Feature
>    Affects Versions: 1.11.1
>            Reporter: Ryan Skraba
>            Assignee: Ryan Skraba
>            Priority: Major
>             Fix For: 1.12.0
>
>
> It's difficult to sign artifacts in docker, both for specifying the correct GPG key to use (if more than one is installed), and because of the following error message:
> {{gpg: signing failed: No pinentry}}
> The solution is to sign the files outside of the docker, or to use the ubertool with the following changes to the build command: 
> {{gpg --local-user=B0CCBDD6 --batch --pinentry-mode loopback --passphrase "$password" ...}}
> (note that {{B0CCBDD6}} refers to my GPG public key: https://people.apache.org/keys/committer/rskraba.asc)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)