You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/07/31 16:51:00 UTC
[jira] [Work logged] (AVRO-3592) [build] Signing artifacts in docker fails with "no pinentry"
[ https://issues.apache.org/jira/browse/AVRO-3592?focusedWorklogId=796712&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796712 ]
ASF GitHub Bot logged work on AVRO-3592:
----------------------------------------
Author: ASF GitHub Bot
Created on: 31/Jul/22 16:50
Start Date: 31/Jul/22 16:50
Worklog Time Spent: 10m
Work Description: RyanSkraba opened a new pull request, #1796:
URL: https://github.com/apache/avro/pull/1796
Add the `codec/` packages to the C# distribution. Note that these are missing from the Avro 1.11.1 binary release but uploaded to nuget.org from the same build.
### Jira
- [X] My PR addresses AVRO-3592
### Tests
- [X] My PR does not need testing for this extremely good reason: manually building
### Commits
- [X] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "[How to write a good git commit message](https://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
Issue Time Tracking
-------------------
Worklog Id: (was: 796712)
Remaining Estimate: 0h
Time Spent: 10m
> [build] Signing artifacts in docker fails with "no pinentry"
> ------------------------------------------------------------
>
> Key: AVRO-3592
> URL: https://issues.apache.org/jira/browse/AVRO-3592
> Project: Apache Avro
> Issue Type: New Feature
> Reporter: Ryan Skraba
> Assignee: Ryan Skraba
> Priority: Minor
> Fix For: 1.12.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)