Its needed for ensuring the systemd distro feature
Signed-off-by: Khem Raj
---
meta-oe/recipes-extended/etcd/etcd_3.5.7.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-oe/recipes-extended/etcd/etcd_3.5.7.bb
b/meta-oe/recipes-extended/etcd/etcd_3.5.7.bb
index 3e7bb0f6
Hi Adrian,
Thanks for your quick reply.
I was looking at the packages-split folders the other day and yes it is
packaged there.
Thanks for pointing out rm_sysvinit_initddir. I debugged this a bit, and it
turns out that "sysvinit" is actually still in DISTRO_FEATURES along with
"systemd." In L
Hi Ken
We are using NetworkManager with systemd without facing this issue. If
the problematic init script ends up on the target device I would expect
that it is also installed in the packages-split folder. But I cannot
see that for the builds which I have available. (The path is something
like bui
Hello,
I believe I have found a bug in meta-networking: networkmanager in Langdale
when upgrading from Kirkstone. It appears that this recent change:
https://git.openembedded.org/meta-openembedded/commit/?id=009bc195629ac4e885d7ae5148a175c8c8147e8f
restructured the recipe and packages for netwo
Hi Armin,
On 11/05/2023 18:36, Armin Kuster wrote:
>
>
> On 5/10/23 5:06 AM, Jack Mitchell wrote:
>> Upstream-Status: Backport
>> Link:
>> https://github.com/nss-dev/nss/commit/cbf5a2bce75ca2c2fd3e247796b9892f5298584e
>>
>> Signed-off-by: Jack Mitchell
>
> What is the difference between the pa