From: Jan Kiszka <jan.kiszka@siemens.com>
To: Amy_Fong@mentor.com, isar-users@googlegroups.com
Subject: Re: [PATCH] gnupg fails on nonexistent /dev/tty
Date: Mon, 26 Nov 2018 16:26:18 +0100 [thread overview]
Message-ID: <dd732f86-2ea4-acca-8930-6b8a952fd391@siemens.com> (raw)
In-Reply-To: <20181126151812.25677-1-Amy_Fong@mentor.com>
On 26.11.18 16:18, Amy_Fong@mentor.com wrote:
> From: Amy Fong <Amy_Fong@mentor.com>
>
> Add --no-tty option to gnupg for noninteractive usage.
>
Thanks!
Could you add the information where you have seen it and where not? IIRC, it was
some version difference in the gpg package that triggered it.
> Signed-off-by: Amy Fong <Amy_Fong@mentor.com>
> ---
> meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> index e735726..e89b7c1 100644
> --- a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> +++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> @@ -150,7 +150,7 @@ do_generate_keyring() {
> if [ -n "${@d.getVar("APTKEYFILES", True) or ""}" ]; then
> for keyfile in ${@d.getVar("APTKEYFILES", True)}; do
> gpg --no-default-keyring --keyring "${APTKEYRING}" \
> - --homedir "${DL_DIR}" --import "$keyfile"
> + --no-tty --homedir "${DL_DIR}" --import "$keyfile"
> done
> fi
> }
>
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-11-26 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 15:18 Amy_Fong
2018-11-26 15:26 ` Jan Kiszka [this message]
2018-11-27 1:16 ` Amy Fong
2018-11-29 12:14 ` Maxim Yu. Osipov
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=dd732f86-2ea4-acca-8930-6b8a952fd391@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Amy_Fong@mentor.com \
--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