Re: [yocto] EXTRA_USERS_PARAMS doesn't work to generate password for root and add new users
On Wed, Aug 23, 2023 at 10:11 PM Jeffrey Simons wrote: > > On Wed, Aug 23, 2023 at 03:50 PM, Crane wrote: > > > > > On Wed, Aug 23, 2023 at 03:45 AM, Mauro wrote: > > > > > > > > You can put the encrypted password (the result of the "openssl passwd -6 > > > root" command) directly in the variable, taking care to put a "\" before > > > the three "$" contained in the string. Something like this: > > > > > > EXTRA_USERS_PARAMS=" usermod -p > > > > > '\$6\$CEM0hANiVS9VXN8N\$Q9XK1KTpq2faq2fNbSRLNeeA4mmQsl8g1Gwl3QnTPlRPb5ljCAa./bbhffcthXxUen4jSFL6HKGQPlHZNQkfA/' > > > root; useradd -p > > > > > '\$6\$5wVybJkbuowR0iMi\$tnEJEEbXbcRfksKRSt7rjlY1hRERrjqFOlCaa0s1ivISxAHT7MFdcnZvVbRHgkqRSYzA1oLUxtR0LuvDTMPR5/' > > > crane; " > > > > Tried as well. And a \ is added automatically in front of $, so no need to > > add > > it. But still not working. > > There must be something else missing. Anyway to debug in this case? > > > > From testing I have observed that the extrausers does not work from a recipe, > while useradd works correctly from a recipe. > The extrausers should work as expected from within the distribution > description, so you might want to try that. > > For debugging you could print the bitbake variables to screen (-e) and grep > on the EXTRA_USERS_PARAMS. > See this https://github.com/YoeDistro/yoe-distro/blob/master/conf/projects/rpi4-64/config.conf#L57-L66 you might try something like that in config metadata e.g. local.conf > Hope this is will help you solving the issue. > > -- > With kind regards, > > Jeffrey Simons > > Software Engineer > Royal Boon Edam International B.V. > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60871): https://lists.yoctoproject.org/g/yocto/message/60871 Mute This Topic: https://lists.yoctoproject.org/mt/100887124/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] EXTRA_USERS_PARAMS doesn't work to generate password for root and add new users
On Wed, Aug 23, 2023 at 03:50 PM, Crane wrote: > > On Wed, Aug 23, 2023 at 03:45 AM, Mauro wrote: > > > > > You can put the encrypted password (the result of the "openssl passwd -6 > > root" command) directly in the variable, taking care to put a "\" before > > the three "$" contained in the string. Something like this: > > > > EXTRA_USERS_PARAMS=" usermod -p > > > '\$6\$CEM0hANiVS9VXN8N\$Q9XK1KTpq2faq2fNbSRLNeeA4mmQsl8g1Gwl3QnTPlRPb5ljCAa./bbhffcthXxUen4jSFL6HKGQPlHZNQkfA/' > > root; useradd -p > > > '\$6\$5wVybJkbuowR0iMi\$tnEJEEbXbcRfksKRSt7rjlY1hRERrjqFOlCaa0s1ivISxAHT7MFdcnZvVbRHgkqRSYzA1oLUxtR0LuvDTMPR5/' > > crane; " > > Tried as well. And a \ is added automatically in front of $, so no need to add > it. But still not working. > There must be something else missing. Anyway to debug in this case? > >From testing I have observed that the extrausers does not work from a recipe, >while useradd works correctly from a recipe. The extrausers should work as expected from within the distribution description, so you might want to try that. For debugging you could print the bitbake variables to screen (-e) and grep on the EXTRA_USERS_PARAMS. Hope this is will help you solving the issue. -- With kind regards, Jeffrey Simons Software Engineer Royal Boon Edam International B.V. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60870): https://lists.yoctoproject.org/g/yocto/message/60870 Mute This Topic: https://lists.yoctoproject.org/mt/100887124/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [meta-virtualization] nerdctl broken in kirkstone
which task is failing ?
On Wed, Aug 23, 2023 at 2:31 PM Marek Belisko wrote:
>
> Hi,
>
> I'm trying to add nerdctl to an image using kirkstone release for
> meta-virtualization.
> I've added bbappend with following fix:
>
> SRC_URI =
> "git://github.com/containerd/nerdctl.git;name=nerdcli;branch=main;protocol=https"
>
> (branch name in original recipe is master but main is required)
>
> but then anyways it fails with:
>
> rsync: [sender] change_dir
> "/data/projects/test/build/tmp/work/cortexa53-crypto-poky-linux/nerdctl/v0.18.0-r0/nerdctl-v0.18.0/src/import/vendor.fetch/github.com/Masterminds/semver/v3"
> failed: No such file or directory (2)
> | rsync error: some files/attrs were not transferred (see previous errors)
> (code 23) at main.c(1327) [sender=3.2.5]
>
> And in ${BP} I cannot see any of those vendor stuff which should be present.
> Is there some fix for that already pending or it's known issue?
>
> Thanks and BR,
>
> marek
>
> --
> as simple and primitive as possible
> -
> Marek Belisko - OPEN-NANDRA
> Freelance Developer
>
> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> Tel: +421 915 052 184
> skype: marekwhite
> twitter: #opennandra
> web: http://open-nandra.com
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60869): https://lists.yoctoproject.org/g/yocto/message/60869
Mute This Topic: https://lists.yoctoproject.org/mt/100924569/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-virtualization] nerdctl broken in kirkstone
Hi,
I'm trying to add nerdctl to an image using kirkstone release for
meta-virtualization.
I've added bbappend with following fix:
SRC_URI = "git://
github.com/containerd/nerdctl.git;name=nerdcli;branch=main;protocol=https"
(branch name in original recipe is master but main is required)
but then anyways it fails with:
rsync: [sender] change_dir
"/data/projects/test/build/tmp/work/cortexa53-crypto-poky-linux/nerdctl/v0.18.0-r0/nerdctl-v0.18.0/src/import/vendor.fetch/
github.com/Masterminds/semver/v3" failed: No such file or directory (2)
| rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1327) [sender=3.2.5]
And in ${BP} I cannot see any of those vendor stuff which should be
present. Is there some fix for that already pending or it's known issue?
Thanks and BR,
marek
--
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer
Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60868): https://lists.yoctoproject.org/g/yocto/message/60868
Mute This Topic: https://lists.yoctoproject.org/mt/100924569/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-lts-mixins][PATCH 4/4] Fix RISC-V support
Building Rust projects for RISC-V platforms was failing due to the
layer not including a copy of lib/oe/rust.py to get all the changes
from oe-core commit 1cfb9c8a ("rust-target-config: match riscv target
names with what rust expects"). Reverting the changes from that
commit seems likely to make things less robust, so instead add a
copy of the updated lib/oe/rust.py in lib/mixin and update callers
of arch_to_rust_arch to use it. This is not ideal from an ease
of further maintenance perspective, but seems more inline with the
intent of matching the behavior of the Rust toolchain as it stands
in Mickledore branch.
Signed-off-by: Scott Murray
---
classes/rust-common.bbclass| 4 ++--
classes/rust-target-config.bbclass | 2 +-
conf/layer.conf| 4
lib/mixin/rust.py | 13 +
4 files changed, 20 insertions(+), 3 deletions(-)
create mode 100644 lib/mixin/rust.py
diff --git a/classes/rust-common.bbclass b/classes/rust-common.bbclass
index 8782727..a8971cd 100644
--- a/classes/rust-common.bbclass
+++ b/classes/rust-common.bbclass
@@ -51,7 +51,7 @@ def rust_base_triple(d, thing):
if d.getVar('{}_ARCH'.format(thing)) == d.getVar('TARGET_ARCH') and
target_is_armv7(d):
arch = "armv7"
else:
-arch = oe.rust.arch_to_rust_arch(d.getVar('{}_ARCH'.format(thing)))
+arch = mixin.rust.arch_to_rust_arch(d.getVar('{}_ARCH'.format(thing)))
# Substituting "unknown" when vendor is empty will match rust's standard
# targets when building native recipes (including rust-native itself)
@@ -77,7 +77,7 @@ def rust_base_triple(d, thing):
# In some cases uname and the toolchain differ on their idea of the arch name
-RUST_BUILD_ARCH = "${@oe.rust.arch_to_rust_arch(d.getVar('BUILD_ARCH'))}"
+RUST_BUILD_ARCH = "${@mixin.rust.arch_to_rust_arch(d.getVar('BUILD_ARCH'))}"
# Naming explanation
# Yocto
diff --git a/classes/rust-target-config.bbclass
b/classes/rust-target-config.bbclass
index 21a56ed..663b02c 100644
--- a/classes/rust-target-config.bbclass
+++ b/classes/rust-target-config.bbclass
@@ -343,7 +343,7 @@ def rust_gen_target(d, thing, wd, arch):
if arch == "arm" and target_is_armv7(d):
arch = 'armv7'
-rust_arch = oe.rust.arch_to_rust_arch(arch)
+rust_arch = mixin.rust.arch_to_rust_arch(arch)
if abi:
arch_abi = "{}-{}".format(rust_arch, abi)
diff --git a/conf/layer.conf b/conf/layer.conf
index b057c77..fa0cbd6 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -23,3 +23,7 @@ BBMASK:append = " meta/recipes-devtools/cargo/
meta/recipes-devtools/rust/ meta/
# These are in bitbake.conf in langdale and up, adding them here to make
# using the layer more turn-key seems reasonable.
BB_BASEHASH_IGNORE_VARS:append = " RUST_BUILD_SYS RUST_HOST_SYS
RUST_TARGET_SYS"
+
+# Since we cannot overlay the lib/oe version easily, make sure our backport
+# of rust.py in lib/mixin is picked up.
+OE_EXTRA_IMPORTS:append = " mixin.rust"
diff --git a/lib/mixin/rust.py b/lib/mixin/rust.py
new file mode 100644
index 000..185553e
--- /dev/null
+++ b/lib/mixin/rust.py
@@ -0,0 +1,13 @@
+#
+# Copyright OpenEmbedded Contributors
+#
+# SPDX-License-Identifier: MIT
+#
+
+# Handle mismatches between `uname -m`-style output and Rust's arch names
+def arch_to_rust_arch(arch):
+if arch == "ppc64le":
+return "powerpc64le"
+if arch in ('riscv32', 'riscv64'):
+return arch + 'gc'
+return arch
--
2.41.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60867): https://lists.yoctoproject.org/g/yocto/message/60867
Mute This Topic: https://lists.yoctoproject.org/mt/100921022/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-lts-mixins][PATCH 3/4] librsvg: upgrade to 2.54.6
From: Chee Yang Lee
update include fix for CVE-2023-38633.
Signed-off-by: Chee Yang Lee
Signed-off-by: Steve Sakoman
Signed-off-by: Scott Murray
---
recipes-gnome/librsvg/{librsvg_2.54.5.bb => librsvg_2.54.6.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename recipes-gnome/librsvg/{librsvg_2.54.5.bb => librsvg_2.54.6.bb} (97%)
diff --git a/recipes-gnome/librsvg/librsvg_2.54.5.bb
b/recipes-gnome/librsvg/librsvg_2.54.6.bb
similarity index 97%
rename from recipes-gnome/librsvg/librsvg_2.54.5.bb
rename to recipes-gnome/librsvg/librsvg_2.54.6.bb
index 59278d1..b917b76 100644
--- a/recipes-gnome/librsvg/librsvg_2.54.5.bb
+++ b/recipes-gnome/librsvg/librsvg_2.54.6.bb
@@ -20,7 +20,7 @@ SRC_URI +=
"file://0001-Makefile.am-pass-rust-target-to-cargo-also-when-not-.pat
file://0001-system-deps-src-lib.rs-do-not-probe-into-harcoded-li.patch \
"
-SRC_URI[archive.sha256sum] =
"4f03190f45324d1fa1f52a79dfcded1f64eaf49b3ae2f88eedab0c07617cae6e"
+SRC_URI[archive.sha256sum] =
"0ee6174140b5fc017e19a75c26e8c3324a560bf2c37f7abd3da06bd58542bb03"
# librsvg is still autotools-based, but is calling cargo from its
automake-driven makefiles
# so we cannot use cargo class directly, but still need bits and pieces from
it
--
2.41.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60866): https://lists.yoctoproject.org/g/yocto/message/60866
Mute This Topic: https://lists.yoctoproject.org/mt/100921021/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-lts-mixins][PATCH 2/4] rust-common.bbclass: move musl-specific linking fix from rust-source.inc
From: Alexander Kanavin
This needs to be done for any item that is linked under rustc,
and not just rust itself. Latest python-cryptography exposes the issue.
(From OE-Core rev: 967d847a9815df43d0c92ca61cc544e1fe5dcc03)
Signed-off-by: Alexander Kanavin
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit d3811228747590ea06e8d68be4785d45ec9c478f)
Signed-off-by: Steve Sakoman
Signed-off-by: Scott Murray
---
classes/rust-common.bbclass | 4
recipes-devtools/rust/rust-source.inc | 5 -
2 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/classes/rust-common.bbclass b/classes/rust-common.bbclass
index e0cedd7..8782727 100644
--- a/classes/rust-common.bbclass
+++ b/classes/rust-common.bbclass
@@ -158,6 +158,10 @@ WRAPPER_TARGET_CXX = "${CXX}"
WRAPPER_TARGET_CCLD = "${CCLD}"
WRAPPER_TARGET_LDFLAGS = "${LDFLAGS}"
WRAPPER_TARGET_EXTRALD = ""
+# see
recipes-devtools/gcc/gcc/0018-Add-ssp_nonshared-to-link-commandline-for-musl-targe.patch
+# we need to link with ssp_nonshared on musl to avoid "undefined reference to
`__stack_chk_fail_local'"
+# when building MACHINE=qemux86 for musl
+WRAPPER_TARGET_EXTRALD:libc-musl = "-lssp_nonshared"
WRAPPER_TARGET_AR = "${AR}"
# compiler is used by gcc-rs
diff --git a/recipes-devtools/rust/rust-source.inc
b/recipes-devtools/rust/rust-source.inc
index b25b5c1..0534e59 100644
--- a/recipes-devtools/rust/rust-source.inc
+++ b/recipes-devtools/rust/rust-source.inc
@@ -17,8 +17,3 @@ export TARGET_VENDOR
UPSTREAM_CHECK_URI =
"https://forge.rust-lang.org/infra/other-installation-methods.html;
UPSTREAM_CHECK_REGEX = "rustc-(?P\d+(\.\d+)+)-src"
-
-# see
recipes-devtools/gcc/gcc/0018-Add-ssp_nonshared-to-link-commandline-for-musl-targe.patch
-# we need to link with ssp_nonshared on musl to avoid "undefined reference to
`__stack_chk_fail_local'"
-# when building MACHINE=qemux86 for musl
-WRAPPER_TARGET_EXTRALD:libc-musl = "-lssp_nonshared"
--
2.41.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60865): https://lists.yoctoproject.org/g/yocto/message/60865
Mute This Topic: https://lists.yoctoproject.org/mt/100921019/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-lts-mixins][PATCH 1/4] cargo.bbclass: set up cargo environment in common do_compile
From: Alexander Kanavin
cargo_do_compile runs only if the recipe is built using cargo
as the top level tool. Some recipes hide usage of cargo inside setuptools
(or autoconf) and use do_compile definitions specific to those,
and so the environment isn't properly set up.
This was exposed by latest versions of python3-cryptography.
(From OE-Core rev: a1946efdbec608d47f9e992c1b5cf3c671a204fc)
Signed-off-by: Alexander Kanavin
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 9f4ff643a028d7f5670d80861f2ce19ca2d90faa)
Signed-off-by: Steve Sakoman
Signed-off-by: Scott Murray
---
classes/cargo.bbclass| 1 -
classes/cargo_common.bbclass | 4
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/classes/cargo.bbclass b/classes/cargo.bbclass
index 7a8cc1e..3ef0bbb 100644
--- a/classes/cargo.bbclass
+++ b/classes/cargo.bbclass
@@ -55,7 +55,6 @@ oe_cargo_build () {
do_compile[progress] = "outof:\s+(\d+)/(\d+)"
cargo_do_compile () {
- oe_cargo_fix_env
oe_cargo_build
}
diff --git a/classes/cargo_common.bbclass b/classes/cargo_common.bbclass
index 82ab25b..1ca0be4 100644
--- a/classes/cargo_common.bbclass
+++ b/classes/cargo_common.bbclass
@@ -149,6 +149,10 @@ python cargo_common_do_patch_paths() {
}
do_configure[postfuncs] += "cargo_common_do_patch_paths"
+do_compile:prepend () {
+oe_cargo_fix_env
+}
+
oe_cargo_fix_env () {
export CC="${RUST_TARGET_CC}"
export CXX="${RUST_TARGET_CXX}"
--
2.41.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60864): https://lists.yoctoproject.org/g/yocto/message/60864
Mute This Topic: https://lists.yoctoproject.org/mt/100921018/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-lts-mixins][PATCH 0/4] kirkstone/rust-1.68 branch updates
Pull in a couple of recent fixes that were backported to Mickledore, a
librsvg update that Steve has queued in mickledore-nut, and a fix for
building for RISC-V platforms.
Alexander Kanavin (2):
cargo.bbclass: set up cargo environment in common do_compile
rust-common.bbclass: move musl-specific linking fix from
rust-source.inc
Chee Yang Lee (1):
librsvg: upgrade to 2.54.6
Scott Murray (1):
Fix RISC-V support
classes/cargo.bbclass | 1 -
classes/cargo_common.bbclass| 4
classes/rust-common.bbclass | 8 ++--
classes/rust-target-config.bbclass | 2 +-
conf/layer.conf | 4
lib/mixin/rust.py | 13 +
recipes-devtools/rust/rust-source.inc | 5 -
.../{librsvg_2.54.5.bb => librsvg_2.54.6.bb}| 2 +-
8 files changed, 29 insertions(+), 10 deletions(-)
create mode 100644 lib/mixin/rust.py
rename recipes-gnome/librsvg/{librsvg_2.54.5.bb => librsvg_2.54.6.bb} (97%)
--
2.41.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60863): https://lists.yoctoproject.org/g/yocto/message/60863
Mute This Topic: https://lists.yoctoproject.org/mt/100921017/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-selinux][PATCH 3/3] linux-yocto: drop CONFIG_SECURITY_SELINUX_DISABLE
CONFIG_SECURITY_SELINUX_DISABLE has been removed since kernel 6.4[1][2]. [1] https://github.com/SELinuxProject/selinux-kernel/wiki/DEPRECATE-runtime-disable [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f22f9aaf6c3d92ebd5ad9e67acc03afebaaeb289 Signed-off-by: Yi Zhao --- recipes-kernel/linux/files/selinux.cfg | 1 - 1 file changed, 1 deletion(-) diff --git a/recipes-kernel/linux/files/selinux.cfg b/recipes-kernel/linux/files/selinux.cfg index a081095..8333a05 100644 --- a/recipes-kernel/linux/files/selinux.cfg +++ b/recipes-kernel/linux/files/selinux.cfg @@ -23,7 +23,6 @@ CONFIG_SECURITYFS=y CONFIG_SECURITY_NETWORK=y CONFIG_SECURITY_SELINUX=y CONFIG_SECURITY_SELINUX_BOOTPARAM=y -CONFIG_SECURITY_SELINUX_DISABLE=y CONFIG_SECURITY_SELINUX_DEVELOP=y CONFIG_SECURITY_SELINUX_AVC_STATS=y CONFIG_AUDIT_GENERIC=y -- 2.25.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60862): https://lists.yoctoproject.org/g/yocto/message/60862 Mute This Topic: https://lists.yoctoproject.org/mt/100916960/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-selinux][PATCH 2/3] libselinux-python: fix build with musl
libselinux-python also requires the patch which provided by [1] to fix
build with musl.
[1]
https://git.yoctoproject.org/meta-selinux/commit/?id=23d8e2d86317170c0a3c155640c71b83329ff726
Signed-off-by: Yi Zhao
---
recipes-security/selinux/libselinux-python_3.5.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/recipes-security/selinux/libselinux-python_3.5.bb
b/recipes-security/selinux/libselinux-python_3.5.bb
index 3555a72..b382be1 100644
--- a/recipes-security/selinux/libselinux-python_3.5.bb
+++ b/recipes-security/selinux/libselinux-python_3.5.bb
@@ -14,6 +14,7 @@ FILESEXTRAPATHS:prepend := "${THISDIR}/libselinux:"
SRC_URI += "\
file://0001-Makefile-fix-python-modules-install-path-for-multili.patch
\
file://0002-Do-not-use-PYCEXT-and-rely-on-the-installed-file-nam.patch
\
+file://0003-libselinux-restore-drop-the-obsolete-LSF-transitiona.patch
\
"
S = "${WORKDIR}/git/libselinux"
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60861): https://lists.yoctoproject.org/g/yocto/message/60861
Mute This Topic: https://lists.yoctoproject.org/mt/100916957/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-selinux][PATCH 1/3] selinux-python: add python3-distro and binutils to RDEPENDS
Add python3-distro and binutils to RDEPENDS for sepolicy to fix runtime
error:
$ sepolicy -h
Traceback (most recent call last):
File "/usr/bin/sepolicy", line 690, in
gen_manpage_args(subparsers)
File "/usr/bin/sepolicy", line 375, in gen_manpage_args
man.add_argument("-o", "--os", dest="os", default=get_os_version(),
File "/usr/lib/python3.11/site-packages/sepolicy/__init__.py", line 1245, in
get_os_version
import distro
ModuleNotFoundError: No module named 'distro'
$ sepolicy generate --init /usr/sbin/sshd
/bin/sh: line 1: nm: command not found
Signed-off-by: Yi Zhao
---
recipes-security/selinux/selinux-python_3.5.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/recipes-security/selinux/selinux-python_3.5.bb
b/recipes-security/selinux/selinux-python_3.5.bb
index 9ff63db..79125d0 100644
--- a/recipes-security/selinux/selinux-python_3.5.bb
+++ b/recipes-security/selinux/selinux-python_3.5.bb
@@ -54,8 +54,10 @@ RDEPENDS:${PN}-semanage = "\
${PN} \
"
RDEPENDS:${PN}-sepolicy = "\
+binutils \
python3-core \
python3-codecs \
+python3-distro \
python3-syslog \
python3-multiprocessing \
${PN} \
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60860): https://lists.yoctoproject.org/g/yocto/message/60860
Mute This Topic: https://lists.yoctoproject.org/mt/100916956/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] SDK build generally broken?
Thanks a lot for your answers and your time! It turned out that the
only problem was the following:
TOOLCHAIN_HOST_TASK += "nativesdk-cmake"
When I remove this, I still get the CMake Toolchain file but the error
is gone.
I must have missed something, it seems this is done by default. At
least here adding this task breaks the SDK and it is not needed at all.
So I am happily building again.
Best Regards
David
Am Dienstag, dem 22.08.2023 um 09:36 +0100 schrieb Richard Purdie:
> On Tue, 2023-08-22 at 06:58 +, David Daniel wrote:
> > Thanks for your reply! I cannot think of how I could mix the two
> > but I
> > checked out 4.2.2, added my machine, sourced oe-init-build-env and
> > started the build. So the bitbake I use comes from the poky
> > repository
> > and the checkout I use.
> >
> > Is there a good guideline what a machine must define and do in
> > order to
> > be fully compliant and compatible? I have gone through the BSP
> > Developer Guide and provided all listed necessary items. Still it
> > seems
> > that I am missing something or that I am doing wrong. Since I can
> > successfully build the image though, even when I include my own
> > distro
> > layer and use it all that SDK build problems seem awkward to me.
> >
> > Or is there any particular thing an SDK build needs from a BSP
> > layer
> > that is not listed explicitely in the BSP Developer Guide?
> >
> > Thanks for any help!
> > Greets
> >
> > Am Montag, dem 21.08.2023 um 23:53 +0100 schrieb Richard Purdie:
> > > On Mon, 2023-08-21 at 12:49 +, David Daniel wrote:
> > > > Hello everybody
> > > >
> > > > Has anyone successfully built an SDK lately? I cannot build any
> > > > SDK,
> > > > neither for my image nor for core-image-minimal.
> > > >
> > > > If I define my own image I get the error (I already wrote -
> > > > nobody
> > > > any
> > > > idea?) that the dummy-sdk package is to be built for a
> > > > different
> > > > architecture:
> > > >
> > > >
> > > > x86_64_nativesdk 3.1.2-r0 oe-repo 330 k
> > > > nativesdk-openssl-conf
> > > > x86_64_nativesdk
> > > > 3.1.2-r0 oe-repo 12 k
> > > > target-sdk-provides-dummy
> > > > sdk_provides_dummy_target
> > > > 1.0-r0 oe-repo 9.0 k
> > > >
> > > > THIS ERROR ONLY APPEARS IF I DEFINE MY OWN IMAGE (though the
> > > > image
> > > > can be built and works).
> > > >
> > > > I guess this is due to the following code in the sdk-dummy
> > > > recipe:
> > > >
> > > > python() {
> > > > # Put the package somewhere separate to ensure it's never
> > > > used
> > > > except
> > > > # when we want it
> > > > # (note that we have to do this in anonymous python here to
> > > > avoid
> > > > # allarch.bbclass disabling itself)
> > > > d.setVar('PACKAGE_ARCH', '${DUMMYARCH}')
> > > > }
> > > >
> > > > But furthermore, I am completely unable to build the SDK with
> > > > my
> > > > machine - I took the machine from the working image sources I
> > > > am
> > > > working with and took a plain master poky checkout (bleeding
> > > > master).
> > > > When I want to build the SDK for the core-image-minimal I get
> > > > the
> > > > following error:
> > > >
> > > > ERROR: m4-native-1.4.19-r0 do_collect_spdx_deps: Error
> > > > executing a
> > > > python function in exec_func_python() autogenerated:
> > > >
> > > > The stack trace of python calls that resulted in this
> > > > exception/failure was:
> > > > File: 'exec_func_python() autogenerated', lineno: 2, function:
> > > >
> > > > 0001:
> > > > *** 0002:do_collect_spdx_deps(d)
> > > > 0003:
> > > > File: '/home/david/yocto/bf133/poky/meta/classes/create-spdx-
> > > > 2.2.bbclass', lineno: 494, function: do_collect_spdx_deps
> > > > 0490: from pathlib import Path
> > > > 0491:
> > > > 0492: spdx_deps_file = Path(d.getVar("SPDXDEPS"))
> > > > 0493:
> > > > *** 0494: deps = collect_direct_deps(d, "do_create_spdx")
> > > > 0495:
> > > > 0496: with spdx_deps_file.open("w") as f:
> > > > 0497: json.dump(deps, f)
> > > > 0498:}
> > > > File: '/home/david/yocto/bf133/poky/meta/classes/create-spdx-
> > > > 2.2.bbclass', lineno: 475, function: collect_direct_deps
> > > > 0471: deps = set()
> > > > 0472: for dep_name in this_dep[3]:
> > > > 0473: dep_data = taskdepdata[dep_name]
> > > > 0474: if dep_data[1] == dep_task and dep_data[0] !=
> > > > pn:
> > > > *** 0475: deps.add((dep_data[0], dep_data[7]))
> > > > 0476:
> > > > 0477: return sorted(deps)
> > > > 0478:
> > > > 0479:collect_direct_deps[vardepsexclude] +=
> > > > "BB_TASKDEPDATA"
> > > > Exception: IndexError: list index out of range
> > > >
> > > > ERROR: Logfile of failure stored in:
> > > > /mnt/data/yocto/bf133/sdk/build/tmp/work/x86_64-linux/m4-
> > > > native/1.4.19/temp/log.do_collect_spdx_deps.731506
> > > > ERROR: Task
Re: [yocto] EXTRA_USERS_PARAMS doesn't work to generate password for root and add new users
On Wed, Aug 23, 2023 at 03:45 AM, Mauro wrote: > > You can put the encrypted password (the result of the "openssl passwd -6 > root" command) directly in the variable, taking care to put a "\" before > the three "$" contained in the string. Something like this: > > EXTRA_USERS_PARAMS=" usermod -p > '\$6\$CEM0hANiVS9VXN8N\$Q9XK1KTpq2faq2fNbSRLNeeA4mmQsl8g1Gwl3QnTPlRPb5ljCAa./bbhffcthXxUen4jSFL6HKGQPlHZNQkfA/' > root; useradd -p > '\$6\$5wVybJkbuowR0iMi\$tnEJEEbXbcRfksKRSt7rjlY1hRERrjqFOlCaa0s1ivISxAHT7MFdcnZvVbRHgkqRSYzA1oLUxtR0LuvDTMPR5/' > crane; " Tried as well. And a \ is added automatically in front of $, so no need to add it. But still not working. There must be something else missing. Anyway to debug in this case? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60858): https://lists.yoctoproject.org/g/yocto/message/60858 Mute This Topic: https://lists.yoctoproject.org/mt/100887124/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx8: Enable PHY_FSL_IMX8Q_PCIE for imx8qm pci
nxp-imx8 has been updated to version 6.1.22, PHY_FSL_IMX8Q_PCIE is necessary for imx8qm, so enable it. Signed-off-by: Xiaolei Wang --- bsp/nxp-imx8/nxp-imx8.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/bsp/nxp-imx8/nxp-imx8.cfg b/bsp/nxp-imx8/nxp-imx8.cfg index 9ba3ee88..918df233 100644 --- a/bsp/nxp-imx8/nxp-imx8.cfg +++ b/bsp/nxp-imx8/nxp-imx8.cfg @@ -45,6 +45,7 @@ CONFIG_PCI=y CONFIG_PCI_MSI=y CONFIG_PCI_IMX6=y CONFIG_PCI_IMX6_HOST=y +CONFIG_PHY_FSL_IMX8Q_PCIE=y CONFIG_IMX_DSP=y CONFIG_IMX_SCU=y -- 2.25.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13011): https://lists.yoctoproject.org/g/linux-yocto/message/13011 Mute This Topic: https://lists.yoctoproject.org/mt/100914005/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] CFP for YPS 2023.11 now open!
Its sunny, it is summer, you're just back from vacation? Nothing better to get into the flow again than writing a proposal for the 2023.11 edition of the Yocto Project Summit! We love to hear about all your Yocto things. What you made, what you broke, what you learned, what you created. The CFP is open now at https://pretalx.com/yocto-project-summit-2023-11/cfp Josef on behalf of the YPS organization team -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60857): https://lists.yoctoproject.org/g/yocto/message/60857 Mute This Topic: https://lists.yoctoproject.org/mt/100913070/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Pick up ${PV} dynamically from environment or file or filename
On Sat, Aug 19, 2023 at 12:07:08PM +0200, Alexander Kanavin wrote: > I think the easiest would be to run a shell script prior to starting > bitbake, which would check what jar needs to be used, and write the > SRC_URI with the name and the checksum into a .inc file in the > meta-layer. Then there's a static .bb file that would include the > .inc, and do the installation/packaging. Changes to .inc would then be > under version control and thus reproducible. Thanks for this extermely helpful advice I did not think of. I made a shell script, inspecting the jar files and extracting the version with a regexp from the filename. This is injected as PV into a inc file the latter bb recipe require. This way the inc contains only PV, the bb recipe is fix. The shell script is invoked from the outer build brocess between maven and bitbake. Many thanks! Kind Regards Konstantin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60856): https://lists.yoctoproject.org/g/yocto/message/60856 Mute This Topic: https://lists.yoctoproject.org/mt/100819403/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Pick up ${PV} dynamically from environment or file or filename
On Fri, Aug 18, 2023 at 08:48:46PM +, Darcy Watkins wrote: > Then make use of the GIT AUTOREV facility to fetch from that GIT repo. Interesting idea which I will track in the future, thank you very much! Regards Konstantin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60855): https://lists.yoctoproject.org/g/yocto/message/60855 Mute This Topic: https://lists.yoctoproject.org/mt/100819403/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] EXTRA_USERS_PARAMS doesn't work to generate password for root and add new users
On 22/08/23 18:00, Crane wrote: On Tue, Aug 22, 2023 at 11:36 AM, Mauro wrote: Try with this: EXTRA_USERS_PARAMS=" usermod -p '$(openssl passwd -6 root)' root; useradd -p '$(openssl passwd -6 2023)' crane; " Uh, I'm using this one successfully, on a Yocto Warrior. Not working. Here is the value of the variable becoming: EXTRA_USERS_PARAMS=" usermod -p '\$(openssl passwd -6 root)' root; useradd -p '\$(openssl passwd -6 2023)' crane; " One \ is added before $ symbol. Then the \ is added automatically by Yocto? Maybe something has changed in variables parsing...or could be a bug? Don't know, help needed from the experts! You can put the encrypted password (the result of the "openssl passwd -6 root" command) directly in the variable, taking care to put a "\" before the three "$" contained in the string. Something like this: EXTRA_USERS_PARAMS=" usermod -p '\$6\$CEM0hANiVS9VXN8N\$Q9XK1KTpq2faq2fNbSRLNeeA4mmQsl8g1Gwl3QnTPlRPb5ljCAa./bbhffcthXxUen4jSFL6HKGQPlHZNQkfA/' root; useradd -p '\$6\$5wVybJkbuowR0iMi\$tnEJEEbXbcRfksKRSt7rjlY1hRERrjqFOlCaa0s1ivISxAHT7MFdcnZvVbRHgkqRSYzA1oLUxtR0LuvDTMPR5/' crane; " By the way, this approach has the advantage to mask the password. -- Mauro Salvini | KOAN sas | Bergamo - Italia embedded software engineering http://KoanSoftware.com -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60854): https://lists.yoctoproject.org/g/yocto/message/60854 Mute This Topic: https://lists.yoctoproject.org/mt/100887124/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] nxp-lx2xxx: add Inphi IN112525 Retimer and Lynx 28G PHYs support
Enable these two configs to add support for Inphi IN112525 S03 Retimer PHY and the Lynx SerDes 28G PHY as found on NXP's Layerscape platforms such as LX2160A. Signed-off-by: Xulin Sun --- bsp/nxp-lx2xxx/nxp-lx2xxx.cfg | 2 ++ 1 file changed, 2 insertions(+) diff --git a/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg b/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg index 85e6871d..1b55967f 100644 --- a/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg +++ b/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg @@ -125,6 +125,8 @@ CONFIG_CORTINA_PHY=y CONFIG_INPHI_PHY=y CONFIG_REGULATOR=y CONFIG_AT803X_PHY=y +CONFIG_PHY_INPHI_IN112525_RETIMER=y +CONFIG_PHY_FSL_LYNX_28G=y # # I2C support -- 2.35.5 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13010): https://lists.yoctoproject.org/g/linux-yocto/message/13010 Mute This Topic: https://lists.yoctoproject.org/mt/100910596/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
