Hi RP,

This is just configuration change which defines the absolute path for the command to silence the warning when systemd-analyze verify the unit files and the command may be installed in different place between OE and non-OE, so it should be OE specific, will resend v2 to mark it is configuration specific.

Thanks,
From: Richard Purdie <richard.purdie@linuxfoundation.org>
Sent: Thursday, January 7, 2021 19:29
To: Yu, Mingli <Mingli.Yu@windriver.com>; openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] systemd: use the absolute path in service file
 
On Thu, 2021-01-07 at 17:56 +0800, Yu, Mingli wrote:
> From: Mingli Yu <mingli.yu@windriver.com>
>
> Fixes:
>  # systemd-analyze --man=false verify /lib/systemd/system/systemd-kexec.service
>  systemd-kexec.service: Command systemctl is not executable: No such file or directory
>
> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
> ---
>  .../0001-service-use-the-abosolute-path.patch | 253 ++++++++++++++++++
>  meta/recipes-core/systemd/systemd_247.2.bb    |   5 +
>  2 files changed, 258 insertions(+)
>  create mode 100644 meta/recipes-core/systemd/systemd/0001-service-use-the-abosolute-path.patch
>
> diff --git a/meta/recipes-core/systemd/systemd/0001-service-use-the-abosolute-path.patch b/meta/recipes-core/systemd/systemd/0001-service-use-the-abosolute-path.patch
> new file mode 100644
> index 0000000000..dc8e8b3052
> --- /dev/null
> +++ b/meta/recipes-core/systemd/systemd/0001-service-use-the-abosolute-path.patch
> @@ -0,0 +1,253 @@
> +From 98a60faaca7f1a6b753f73556705cc68aa19e383 Mon Sep 17 00:00:00 2001
> +From: Mingli Yu <mingli.yu@windriver.com>
> +Date: Thu, 7 Jan 2021 06:40:29 +0000
> +Subject: [PATCH] service: use the abosolute path
> +
> +Fixes:
> + # systemd-analyze --man=false verify /lib/systemd/system/systemd-kexec.service
> + systemd-kexec.service: Command systemctl is not executable: No such file or directory
> +
> +Upstream-Status: Inappropriate [OE specific]

At the very least you need to explain why this is OE specific and
doesn't affect upstream. I strongly suspect there is a different issue
at work here and it should be fixed differently.

Cheers,

Richard