On Sun, Nov 13, 2022 at 3:00 AM Simon Josefsson via Gnulib discussion
list wrote:
> Hi. I had a background job doing 'make check' in a project that
> triggered a GnuPG private key operation PIN prompt... this was
> surprising to me, and the attached fix should avoid that happening. If
> my PIN h
On 2022-11-11 00:40, Ondrej Valousek wrote:
I think I have complete picture now. I also think that eventually I can
eventually fix gnulib (hopefully the gnulib folks stay supportive) as there are
already some pieces of code for AIX that I could possibly reuse.
Thanks for taking this on.
What
Karl, I see that I messed up in June, and committed a make-stds.texi
change to a vendor branch in Savannah's CVS repository for gnustandards,
as opposed to doing it in the main branch. (My knowledge of CVS is no
longer what it was, and I wish Savannah would switch to Git, but I
digress...). Thi
On 2022-11-13 02:59, Simon Josefsson via Gnulib discussion list wrote:
I think this behaviour
should generally be considered a bug.
Yes. Tests shouldn't do that sort of thing, and we have to be cognizant
of the privacy implications of code run by developers (as well as all
the other implicati
Hi. I had a background job doing 'make check' in a project that
triggered a GnuPG private key operation PIN prompt... this was
surprising to me, and the attached fix should avoid that happening. If
my PIN had been cached, this would have signed a commit behind my back
(although this would have be
