public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: "Su, Bao Cheng (RC-CN DF FA R&D)" <baocheng.su@siemens.com>
Subject: Re: [PATCH] optee-client: Add missing runtime dependency
Date: Fri, 14 Jul 2023 17:17:52 +0200	[thread overview]
Message-ID: <53499b0f-b6f2-2d9c-78d5-90cac99eccd4@siemens.com> (raw)
In-Reply-To: <a7ce9c5d-fd4b-9ffe-1758-37cffb6ae99c@siemens.com>

On 13.07.23 07:32, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> The alternative service file uses pgrep and pkill.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> I wasn't able to test yet if this fixes all the issues seen with this 
> service, so this may still be incomplete.
> 
>  meta/recipes-bsp/optee-client/files/debian/control.tmpl | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/recipes-bsp/optee-client/files/debian/control.tmpl b/meta/recipes-bsp/optee-client/files/debian/control.tmpl
> index de780b73..23e1367a 100644
> --- a/meta/recipes-bsp/optee-client/files/debian/control.tmpl
> +++ b/meta/recipes-bsp/optee-client/files/debian/control.tmpl
> @@ -12,6 +12,7 @@ Section: libdevel
>  Architecture: ${DISTRO_ARCH}
>  Multi-Arch: same
>  Depends: libteec1 (= ${binary:Version}),
> +         procps,
>           ${misc:Depends}
>  Description: normal world user space client APIs for OP-TEE (development)
>   OP-TEE is a Trusted Execution Environment (TEE) designed as companion to a

Strike that, wrong line blindly patches. And there are move issues.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux


      reply	other threads:[~2023-07-14 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13  5:32 Jan Kiszka
2023-07-14 15:17 ` Jan Kiszka [this message]

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=53499b0f-b6f2-2d9c-78d5-90cac99eccd4@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=baocheng.su@siemens.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