"Tom G. Christensen" writes:
> On 29/01/15 16:43, Jeff King wrote:
>
>> Another option is to just declare that version old and broken, and skip
>> the tests (either by checking its version, or just checking after we
>> import the keys that we can actually _use_ them).
>>
> That would seem a bit h
On 29/01/15 16:43, Jeff King wrote:
Weird. The pubkeys are there in keyring.gpg; I wonder why the older
version of gpg has trouble extracting them (and how one was _supposed_
to export secret keys at that time).
Importing the unmodified keyring.gpg with 1.2.6 yields this:
$ gpg --homedir "$GNU
On Thu, Jan 29, 2015 at 10:43:20AM -0500, Jeff King wrote:
> It feels a bit hacky, and I wish I knew more about why the current file
> doesn't work (i.e., if we did "gpg --export-secret-keys" with v1.2.6,
> would it produce different output that can be read by both versions?).
> Another option is
On Thu, Jan 29, 2015 at 02:11:05PM +0100, Tom G. Christensen wrote:
> 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
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 withou
5 matches
Mail list logo
