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 2023/09/17 08:10:00 UTC

[jira] [Created] (AVRO-3858) [Build] Add some config to ./build.sh sign

Ryan Skraba created AVRO-3858:
---------------------------------

             Summary: [Build] Add some config to ./build.sh sign 
                 Key: AVRO-3858
                 URL: https://issues.apache.org/jira/browse/AVRO-3858
             Project: Apache Avro
          Issue Type: Bug
          Components: build
            Reporter: Ryan Skraba
             Fix For: 1.12.0


When signing artifacts for a release in docker, the user will see:

{code}
+ set +x
Enter password: gpg: using "MY_DEFAULT_KEY" as default secret key for signing
gpg: signing failed: No pinentry
gpg: signing failed: No pinentry
{code}

1) This might be because it wants to pop up a query for the user's key password?  In any case, we give the password on the command line, a pop-up isn't necessary.

2) MY_DEFAULT_KEY isn't the key that I use to sign apache releases (which is very temporarily only mounted during release signing).

We should be able to configure the script with --local-user and --pinentry-mode for signing releases.





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