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:08:00 UTC
[jira] [Updated] (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 updated AVRO-3593:
------------------------------
Description:
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)
was:
We correctly create the {{codec/* }}packages, but they aren't included in the binary distribution.
For release 1.11.1, I'll uploaded the binary artifacts manually from the local build I used to create the release, but they won't be in the [binary artifacts|https://dist.apache.org/repos/dist/release/avro/avro-1.11.1/csharp/] we voted on with the release. This is likely acceptable since an Apache release is for the source, and the uploaded artifacts are considered for convenience (IIUC).
> [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
> Priority: Major
> Fix For: 1.11.1
>
>
> 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)