From: Tacitus Aedifex <aedifex@sdf.org>
To: git@vger.kernel.org
Subject: Re: Fixing constant preference prompts during tests
Date: Thu, 27 Sep 2018 00:42:48 +0000 [thread overview]
Message-ID: <20180927004248.GA4550@SDF.ORG> (raw)
In-Reply-To: <xmqqa7o4j5fi.fsf@gitster-ct.c.googlers.com>
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 installed
on my system is fairly new:
gpg --version
gpg (GnuPG) 2.2.8
libgcrypt 1.8.3
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Home: /home/user/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed
I'm not sure if that has anything to do with it. I'm going to have to
investigate further to figure out what is being executed and with what
parameters that leads to the prerefences prompt. While working with GPG on
another project I noticed that GPG doesn't like to work with keyrings other
than the default ones. I tried a bunch of different combinations of
--no-default-keyrings, --homedir, --default-key, etc to try to get GPG to never
touch ~/.gnupg and I couldn't figure it out. It would always re-create ~/.gnupg
and default keyrings and even read gpg.conf when explicitly told not to. I
suspect that is what is going on here.
//tæ
next prev parent reply other threads:[~2018-09-27 0:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 16:26 Fixing constant preference prompts during tests Tacitus Aedifex
2018-09-26 17:15 ` Junio C Hamano
2018-09-26 21:37 ` Tacitus Aedifex
2018-09-26 21:48 ` Junio C Hamano
2018-09-27 0:42 ` Tacitus Aedifex [this message]
2018-09-27 23:12 ` brian m. carlson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180927004248.GA4550@SDF.ORG \
--to=aedifex@sdf.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).