[
https://issues.apache.org/jira/browse/HADOOP-15590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yongjun Zhang updated HADOOP-15590:
-----------------------------------
Attachment: HADOOP-15590.001.patch
> Use gpg2 and add set GPG_AGENT_INFO for hadoop release
> ------------------------------------------------------
>
> Key: HADOOP-15590
> URL: https://issues.apache.org/jira/browse/HADOOP-15590
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Yongjun Zhang
> Assignee: Yongjun Zhang
> Priority: Major
> Attachments: HADOOP-15590.001.patch
>
>
> When doing 3.0.3 release, by running command
> dev-support/bin/create-release --asfrelease --docker --dockercache
> documented in
> https://wiki.apache.org/hadoop/HowToRelease
> I hit the following problems:
> 1.
> {quote}
> starting gpg agent ERROR: Unable to launch or acquire gpg-agent. Disable
> signing.
> {quote}
> The script expect GPG_AGENT_INFO env being set with needed info by the
> gpg-agent. However, it was not. This is because of changes made in gpg-agent.
> I found the workaround is to add the following line to
> dev-support/bin/create-release script right after starting gpg-agent:
> {quote}
> export GPG_AGENT_INFO="~/.gnupg/S.gpg-agent:$(pgrep gpg-agent):1"
> {quote}
> 2.
> {quote}
> gpg: can't connect to `~/.gnupg/S.gpg-agent': invalid value
> {quote}
> I found that this is caused by unmatching gpg-agent and gpg versions
> installed via Docker. I modified dev-support/docker/Dockerfile to install
> gnupg2 instead of gnupg. This made gpg and gpg-agent both 2.1.11 instead of
> one on 2.1.11 the other on 1.14. And this solved the above problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
