All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <richard.purdie@linuxfoundation.org>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] systemd: Stop supporting sysvinit compatibility
Date: Sun, 15 Feb 2026 17:32:01 +0100	[thread overview]
Message-ID: <DGFOGZFG9RCO.2210182JJUNRG@bootlin.com> (raw)
In-Reply-To: <20260213175618.1801591-1-richard.purdie@linuxfoundation.org>

On Fri Feb 13, 2026 at 6:56 PM CET, Richard Purdie via lists.openembedded.org wrote:
> Systemd has worked with sysvinit compatibility but upstream plans to remove
> this and hence we will no longer be able to support it. We need to remove this
> before the LTS since the support will certainly not be there for the lifetime
> of the LTS.
>
> This patch disables that usage mode and removes some of the compatibility logic.
> There is more that can be removed, this is meant just to signal to people it is
> no longer supported and start that process. Further cleanup can be made over time
> in later commits.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---

Hi Richard,

I suspect we also want to remove the "Systemd with sysvinit compat" and
"Sysvinit with systemd" steps from qa-extras2:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/26/builds/3165
https://git.yoctoproject.org/yocto-autobuilder-helper/tree/config.json#n1562

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-02-15 16:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-13 17:56 [PATCH] systemd: Stop supporting sysvinit compatibility Richard Purdie
2026-02-15 16:32 ` Mathieu Dubois-Briand [this message]
2026-02-15 17:03   ` [OE-core] " Richard Purdie
2026-02-16  6:51     ` Mathieu Dubois-Briand
2026-02-16  7:42       ` Vyacheslav Yurkov
2026-02-16  8:45         ` Richard Purdie

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=DGFOGZFG9RCO.2210182JJUNRG@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.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 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.