git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tacitus Aedifex <aedifex@sdf.org>
To: git@vger.kernel.org
Subject: Re: Fixing constant preference prompts during tests
Date: Wed, 26 Sep 2018 21:37:03 +0000	[thread overview]
Message-ID: <20180926213703.GA22278@SDF.ORG> (raw)
In-Reply-To: <xmqqh8icmb8l.fsf@gitster-ct.c.googlers.com>

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 same symptom later when whatever thing
>you are using as a minority right now becomes more prevalent.

Indeed I am. I use Qubes OS with a split GPG setup. I have a virtual machine 
dedicated to handling my crypto keys and I use the qubes GPG wrapper to 
interact with the signing VM through the Xen hypervisor. I think the only thing 
that needs to change is that the tests respect gpg.program setting in 
.gitconfig. Signing and verifying commits and tags works perfectly but the 
tests don't allow me to override which program is used.

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. I have gpg installed on my client VM so in theory it should work. I 
can't tell exctly where the prompt is coming from.

//tæ

  reply	other threads:[~2018-09-26 21:37 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 [this message]
2018-09-26 21:48     ` Junio C Hamano
2018-09-27  0:42       ` Tacitus Aedifex
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180926213703.GA22278@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.
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 NNTP newsgroup(s).