From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Luca Bocassi <luca.boccassi@gmail.com>,
openembedded-core@lists.openembedded.org
Cc: raj.khem@gmail.com
Subject: Re: [OE-core] [PATCH] systemd: add usrmerge to REQUIRED_DISTRO_FEATURES
Date: Sat, 05 Aug 2023 14:09:22 +0100 [thread overview]
Message-ID: <2bdc76ae7b92c7fb000e1684d0b49a38f408e2ca.camel@linuxfoundation.org> (raw)
In-Reply-To: <20230805110643.2708376-1-luca.boccassi@gmail.com>
On Sat, 2023-08-05 at 12:06 +0100, Luca Bocassi wrote:
> From: Luca Boccassi <luca.boccassi@microsoft.com>
>
> Support for unmerged-usr is deprecated upstream, taints the system and
> has been removed for v255 (next release).
> Enforce building merged-usr images when using systemd. This allows one
> release cycle where it can be tested for any remaining issue, and can
> still be overridden, before it stops working completely.
>
> Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
> ---
> Time to resurrect this. Support for unmerged-usr has been removed and
> will no longer be available starting with v255. Better to get started
> now with the enforcement, so that things can be worked out while it is
> still possible to override it.
>
> meta/recipes-core/systemd/systemd-compat-units.bb | 2 +-
> meta/recipes-core/systemd/systemd-serialgetty.bb | 2 +-
> meta/recipes-core/systemd/systemd.inc | 5 +++++
> meta/recipes-core/systemd/systemd_254.bb | 2 +-
> 4 files changed, 8 insertions(+), 3 deletions(-)
Thanks for sending the patch. I did put this in for testing and because
it makes usrmerge required for the systemd-boot recipe, even sysvinit
based images fail builds with errors like:
https://autobuilder.yoctoproject.org/typhoon/#/builders/37/builds/7580/steps/12/logs/stdio
Is usrmerge needed to systemd-boot as well?
Cheers,
Richard
next prev parent reply other threads:[~2023-08-05 13:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 11:06 [PATCH] systemd: add usrmerge to REQUIRED_DISTRO_FEATURES luca.boccassi
2023-08-05 12:57 ` [OE-core] " Otavio Salvador
2023-08-05 13:09 ` Richard Purdie [this message]
2023-08-05 21:36 ` Luca Boccassi
2023-08-05 21:35 ` [PATCH v2] " luca.boccassi
2023-08-10 11:50 ` [OE-core] " Alexandre Belloni
2023-08-10 12:13 ` Ross Burton
2023-08-10 12:54 ` Richard Purdie
2023-08-11 12:24 ` Richard Purdie
2023-08-11 12:56 ` Luca Boccassi
-- strict thread matches above, loose matches on Subject: below --
2022-07-11 20:29 [PATCH] " luca.boccassi
2022-07-11 22:06 ` [OE-core] " Richard Purdie
2022-07-12 17:16 ` Luca Boccassi
2022-07-12 21:55 ` Richard Purdie
2022-07-12 23:30 ` Luca Boccassi
2022-07-13 13:19 ` Richard Purdie
2022-07-13 15:52 ` Luca Boccassi
2022-07-13 17:00 ` Alexander Kanavin
2022-10-19 18:10 ` Luca Boccassi
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=2bdc76ae7b92c7fb000e1684d0b49a38f408e2ca.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=luca.boccassi@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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