All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kristian Klausen <kristian@klausen.dk>
To: Armin Kuster <akuster808@gmail.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] [meta-security][PATCH 2/2] swtpm: fix build issues of missing expect
Date: Wed, 29 Sep 2021 08:44:43 +0200	[thread overview]
Message-ID: <YVQLW66LKT7DXF1Z@bob> (raw)
In-Reply-To: <20210928233909.3574965-2-akuster808@gmail.com>

Den Tue, Sep 28, 2021 at 16:39:09 -0700 skrev Armin Kuster:
> Signed-off-by: Armin Kuster <akuster808@gmail.com>
> ---
>  meta-tpm/recipes-tpm/swtpm/swtpm_0.6.1.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta-tpm/recipes-tpm/swtpm/swtpm_0.6.1.bb b/meta-tpm/recipes-tpm/swtpm/swtpm_0.6.1.bb
> index 807c02b..d602ee0 100644
> --- a/meta-tpm/recipes-tpm/swtpm/swtpm_0.6.1.bb
> +++ b/meta-tpm/recipes-tpm/swtpm/swtpm_0.6.1.bb
> @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=fe8092c832b71ef20dfe4c6d3decb3a8"
>  SECTION = "apps"
>  
>  # coreutils-native and net-tools-native are reportedly only required for the tests
> -DEPENDS = "libtasn1 coreutils-native expect socat glib-2.0 net-tools-native libtpm json-glib"
> +DEPENDS = "libtasn1 coreutils-native expect socat glib-2.0 net-tools-native libtpm json-glib expect expect-native"

expect is there twice now (+ native). Would expect-native be enough or 
do we also need expect?

>  
>  SRCREV = "98187d24fe14851653a7c46eb16e9c5f0b9beaa1"
>  SRC_URI = "git://github.com/stefanberger/swtpm.git;branch=stable-0.6 \
> @@ -28,7 +28,7 @@ PACKAGECONFIG[openssl] = "--with-openssl, --without-openssl, openssl"
>  # expect, bash, tpm2-pkcs11-tools (tpm2_ptool), tpmtool and certtool is
>  # used by swtpm-create-tpmca (the last two is provided by gnutls)
>  # gnutls is required by: swtpm-create-tpmca, swtpm-localca and swtpm_cert
> -PACKAGECONFIG[gnutls] = "--with-gnutls, --without-gnutls, gnutls, gnutls, expect bash tpm2-pkcs11-tools"
> +PACKAGECONFIG[gnutls] = "--with-gnutls, --without-gnutls, gnutls, gnutls, bash tpm2-pkcs11-tools"

expect is needed as a runtime dependency for swtpm-create-tpmca, but I 
added it as a recommended dependency as I don't think all people are 
interesting in swtpm-create-tpmca working out-of-the-box.
expect should still be here, no?

>  PACKAGECONFIG[selinux] = "--with-selinux, --without-selinux, libselinux"
>  PACKAGECONFIG[cuse] = "--with-cuse, --without-cuse, fuse"
>  PACKAGECONFIG[seccomp] = "--with-seccomp, --without-seccomp, libseccomp"
> -- 
> 2.25.1
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#54899): https://lists.yoctoproject.org/g/yocto/message/54899
> Mute This Topic: https://lists.yoctoproject.org/mt/85937662/6376886
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [kristian@klausen.dk]
> -=-=-=-=-=-=-=-=-=-=-=-
> 



  reply	other threads:[~2021-09-29  6:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 23:39 [meta-security][PATCH 1/2] swtpm: update to 0.6.1 Armin Kuster
2021-09-28 23:39 ` [meta-security][PATCH 2/2] swtpm: fix build issues of missing expect Armin Kuster
2021-09-29  6:44   ` Kristian Klausen [this message]
2021-09-30 13:55     ` [yocto] " akuster808

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=YVQLW66LKT7DXF1Z@bob \
    --to=kristian@klausen.dk \
    --cc=akuster808@gmail.com \
    --cc=yocto@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.