[
https://issues.apache.org/jira/browse/MGPG-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16148058#comment-16148058
]
Ulises Cervino Beresi commented on MGPG-59:
-------------------------------------------
This proposed remedy doesn't work for build servers, e.g. jenkins.
A better approach is to use {{--pinentry-mode loopback}} once the keys have
been loaded in the agent.
> GPG Plugin: "gpg: signing failed: Inappropriate ioctl for device"
> -----------------------------------------------------------------
>
> Key: MGPG-59
> URL: https://issues.apache.org/jira/browse/MGPG-59
> Project: Maven GPG Plugin
> Issue Type: Bug
> Affects Versions: 1.6
> Reporter: Paul Hammant
> Attachments: screenshot-1.png
>
>
> Some versions and configurations of GPG want to pop an interactive UI, which
> the maven-gpg-plugin cannot handle. This appears in the log, before Maven
> quits without much advice:
> {{*gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect}}
> {{"gpg: signing failed: Inappropriate ioctl for device"}}
> !screenshot-1.png!
> *The remedy is for the user to do something with gpg on the command line
> before going into mvn-release:prepare*. Something that will allow gpg to
> remember (for a period of time) the passphrase entered in that interactive
> UI, that the maven invocation of gpg can take advantage of afterwards.
> Historically there was a gpg option '--no-use-agent', but not all gpg
> implementations support that today, not will going forwards as it is being
> removed.
> Suggestion: On command error, System.out.println the remedy above, perhaps
> even suggesting the command to run:
> {{gpg --use-agent --armor --detach-sign --output $(mktemp) pom.xml}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
