On Thu, Sep 27, 2018 at 12:42:48AM +, Tacitus Aedifex wrote:
> On Wed, Sep 26, 2018 at 02:48:49PM -0700, Junio C Hamano wrote:
> > We do not want your choice of gpg.program or what kind of
> > trust you have personally recorded in your ~/.gnupg/ affect how gpg
> > invoked inside our tests work.
On Wed, Sep 26, 2018 at 02:48:49PM -0700, Junio C Hamano wrote:
We do not want your choice of gpg.program or what kind of
trust you have personally recorded in your ~/.gnupg/ affect how gpg
invoked inside our tests work.
This makes sense to me now. I get what you are saying. The gpg binary inst
Tacitus Aedifex writes:
> It may be a little more complicated than this because looking at the
> tests it seems like they set up their own dummy user with dummy keys
> and use gpg directly.
Yes, that is """the test framework (t/test-lib.sh, t/lib-gpg.sh,
etc.) tries to run our tests in a stable
On Wed, Sep 26, 2018 at 10:15:06AM -0700, Junio C Hamano wrote:
Nobody raised this so far as far as I recall; thanks for the first
one to do so, as it is a sign that you are doing something unusual
(e.g. have newer or different version of GPG than most other people)
and others will hit by the sam
Tacitus Aedifex writes:
> I keep getting prompted for my algorithm preferences while running all
> of the git test suite:
>
> Set preference list to:
> Cipher: AES256, AES192, AES, 3DES
> Digest: SHA512, SHA384, SHA256, SHA224, SHA1
> Compression: Uncompressed
> Features: MDC, Key
I keep getting prompted for my algorithm preferences while running all of the
git test suite:
Set preference list to:
Cipher: AES256, AES192, AES, 3DES
Digest: SHA512, SHA384, SHA256, SHA224, SHA1
Compression: Uncompressed
Features: MDC, Keyserver no-modify
What is the best way
6 matches
Mail list logo
