On 28/01/15 00:35, Junio C Hamano wrote:
A release candidate Git v2.3.0-rc2 is now available for testing
at the usual places.
All signed commit tests fail on RHEL4 which is a regression from 2.2.2.
From t4202.42:
++ git tag -s -m signed_tag_msg signed_tag
gpg: key CDDE430D: secret key without public key - skipped
gpg: skipped `C O Mitter <commit...@example.com>': secret key not available
gpg: signing failed: secret key not available
error: gpg failed to sign the data
error: unable to sign the tag
error: last command exited with $?=128
There are indeed no public keys available after commit 1e3eef which
seems to be contrary to the commit log:
----
Instead import public and secret keys for one key pair from a text
file that holds ASCII-armored export of them.
----
I extracted the pubkeys as ascii armored text from the old binary
keyrings and added them to the new keyring.gpg and then the tests pass.
This is apparently only a problem for older gnupg versions (RHEL4 has
gnupg 1.2.6) since it did not fail on RHEL5 (gnupg 1.4.5).
-tgc
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
