diff options
| author |  Todd Zullinger <tmz@pobox.com> | 2022-03-04 11:25:19 +0100 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2022-03-04 11:36:42 -0800 |
| commit | b0b70d54c4a17476f04ce17255c6558425c11367 (patch) | |
| tree | 1857b55b2196a2d401ad320caa25ea7145e5acf5 /config.mak.dev | |
| parent | t/lib-gpg: reload gpg components after updating trustlist (diff) | |
| download | tgif-b0b70d54c4a17476f04ce17255c6558425c11367.tar.xz | |
t/lib-gpg: kill all gpg components, not just gpg-agent
The gpg-agent is one of several processes that newer releases of GnuPG
start automatically. Issue a kill to each of them to ensure they do not
affect separate tests. (Yes, the separate GNUPGHOME should do that
already. If we find that is case, we could drop the --kill entirely.)
In terms of compatibility, the 'all' keyword was added to the --kill &
--reload options in GnuPG 2.1.18. Debian and RHEL are often used as
indicators of how a change might affect older systems we often try to
support.
- Debian Strech (old old stable), which has limited security support
until June 2022, has GnuPG 2.1.18 (or 2.2.x in backports).
- CentOS/RHEL 7, which is supported until June 2024, has GnuPG
2.0.22, which lacks the --kill option, so the change won't have
any impact.
Signed-off-by: Todd Zullinger <tmz@pobox.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'config.mak.dev')
0 files changed, 0 insertions, 0 deletions