|
Look at the default value of the RPM macro named "__gpg_sign_cmd" in /usr/lib/rpm/macros, or with rpm --eval: |
The feature was added in commit: rpm-software-management/rpm@932f14f
In all modern systems with rpm >= 4.14.0-rc1, you should be able to rely on _gpg_sign_cmd_extra_args as upstream feature.
If your __gpg_sign_cmd is defined as:
#==============================================================================
# ---- GPG/PGP/PGP5 signature macros.
# Macro(s) to hold the arguments passed to GPG/PGP for package
# signing and verification.
#
%__gpg_sign_cmd %{__gpg} \
gpg --no-verbose --no-armor \
%{?_gpg_digest_algo:--digest-algo %{_gpg_digest_algo}} \
--no-secmem-warning \
%{?_gpg_sign_cmd_extra_args:%{_gpg_sign_cmd_extra_args}} \
-u "%{_gpg_name}" -sbo %{__signature_filename} %{__plaintext_filename}
Then _gpg_sign_cmd_extra_args is exactly the feature you need. You can do this just by adding this to .rpmmacros:
%_gpg_sign_cmd_extra_args --pinentry-mode loopback
And now you can be sure you are not going to break __gpg_sign_cmd in the future.
rpmsign-plugin/src/main/resources/jenkins/plugins/rpmsign/RpmSignPlugin/help-passphrase.html
Line 19 in 44c6d44
The feature was added in commit: rpm-software-management/rpm@932f14f
In all modern systems with rpm >= 4.14.0-rc1, you should be able to rely on
_gpg_sign_cmd_extra_argsas upstream feature.If your
__gpg_sign_cmdis defined as:Then
_gpg_sign_cmd_extra_argsis exactly the feature you need. You can do this just by adding this to .rpmmacros:And now you can be sure you are not going to break
__gpg_sign_cmdin the future.