From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v2 0/2] Fix gpg-agent management
Date: Mon, 13 Sep 2021 17:31:05 +0300 [thread overview]
Message-ID: <20210913143107.181118-1-amikan@ilbers.de> (raw)
Management logic of starting and stopping gpg-agent in isar-bootstrap
was still not working properly. Starting of gpg-agent happened for every
bitbake run, and stopping did not happen at all. This is not a big issue
when building Isar inside kas, but should be fixed for chroot
environment.
---
Changes since v1:
- Simplify conditions.
Anton Mikanovich (2):
isar-bootstrap: Fix GPG need check function
isar-bootstrap: Do not let gpg-agent to stay running
.../isar-bootstrap/isar-bootstrap.inc | 20 +++++++++----------
1 file changed, 9 insertions(+), 11 deletions(-)
--
2.25.1
next reply other threads:[~2021-09-13 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 14:31 Anton Mikanovich [this message]
2021-09-13 14:31 ` [PATCH v2 1/2] isar-bootstrap: Fix GPG need check function Anton Mikanovich
2021-09-13 14:31 ` [PATCH v2 2/2] isar-bootstrap: Do not let gpg-agent to stay running Anton Mikanovich
2021-09-29 14:22 ` [PATCH v2 0/2] Fix gpg-agent management Anton Mikanovich
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=20210913143107.181118-1-amikan@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
/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