Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Mikko Rapeli <mikko.rapeli@linaro.org>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v5 1/2] systemd: Build the systemctl executable
Date: Wed, 19 Feb 2025 11:14:34 +0100	[thread overview]
Message-ID: <1fb8f845-7562-4a1a-a624-847e6b9386d5@gmail.com> (raw)
In-Reply-To: <Z7WsNsR9-8lbzxjr@nuoska>

On 19.02.2025 11:02, Mikko Rapeli wrote:
> Hi,
>
> On Wed, Feb 19, 2025 at 09:44:09AM +0000, Richard Purdie wrote:
>> On Tue, 2025-02-18 at 12:56 +0100, Vyacheslav Yurkov via
>> lists.openembedded.org wrote:
>>> From: Vyacheslav Yurkov <uvv.mail@gmail.com>
>>>
>>> Instead of the python re-implementation build the actual systemctl
>>> from
>>> the systemd source tree. The python script was used when systemd
>>> didn't
>>> provide an option to build individual executables. It is possible in
>>> the
>>> meantime, so instead of always adapting the script when there's a new
>>> functionality, we simply use upstream implementation.
>>>
>>> License-Update: Base recipe is used
>>>
>>> Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com>
>>> ---
>>>   .../systemd/systemd-systemctl-native.bb       |  26 +-
>>>   ...-meson-add-install-tag-for-systemctl.patch |  25 ++
>>>   ...2-meson-Bypass-certain-config-checks.patch |  64 +++
>>>   .../systemd/systemd-systemctl/systemctl       | 376 ----------------
>>> --
>>>   
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/9/builds/1022
>>
>> and many similar failures unfortunately. Did we get out of sync with
>> systemd versions?
> I think a rebase is needed since point release update from 257.1 to 257.3.
> Should be trivial. The patch file can be dropped since 257.3 already
> has it. Thanks for upstreaming it!
>
> Cheers,
>
> -Mikko

Oops, I did check that it was still applicable before sending v5. But 
yeah, v6 should be even simpler. will send rebased version soon.

Slava


      reply	other threads:[~2025-02-19 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 11:56 [PATCH v5 1/2] systemd: Build the systemctl executable uvv.mail
2025-02-18 11:56 ` [PATCH v5 2/2] oeqa/selftest: Drop dependency on systemd-native uvv.mail
2025-02-18 12:09   ` Mikko Rapeli
2025-02-19  9:44 ` [OE-core] [PATCH v5 1/2] systemd: Build the systemctl executable Richard Purdie
2025-02-19 10:02   ` Mikko Rapeli
2025-02-19 10:14     ` Vyacheslav Yurkov [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=1fb8f845-7562-4a1a-a624-847e6b9386d5@gmail.com \
    --to=uvv.mail@gmail.com \
    --cc=Openembedded-core@lists.openembedded.org \
    --cc=mikko.rapeli@linaro.org \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox