[yocto] Need comments or plan on User- group guidelines which is making us away from commercial products

2023-10-31 Thread Ravi Kumar
Hi team , Most of the IOT lines have been deployed on Yocto now the new trend/requirement is security . On yocto we see that we moved away making every one as root and every resource on the device tree accessible . Where it creates new challenges of creating isolation of services and

[yocto] Running podman from recipe

2023-10-31 Thread Rudolf J Streif
I am trying to run podman to pull images from a registry and repackage them using YP Kirkstone. My build host is Fedora 38 and podman is version 4.7.0 podman is running newuidmap (I wouldn't understand why it does so when doing just a 'pull' but that seems to be the case). newuidmap is

[yocto] [auh][PATCH 6/6] weeklyjob.sh: Add options to handle upgrading meta-oe

2023-10-31 Thread Yoann Congal
For example: ./weeklyjob.sh --layer-dir ../meta-openembedded/ --layer-names "meta-oe" Signed-off-by: Yoann Congal --- weeklyjob.sh | 59 +++- 1 file changed, 58 insertions(+), 1 deletion(-) diff --git a/weeklyjob.sh b/weeklyjob.sh index

[yocto] [auh][PATCH 5/6] upgrade-helper.py: Add layer command line option

2023-10-31 Thread Yoann Congal
From: David Pierret - Layer options can be defined as command line arguments - multiple layers can be defined in a single command each layer is analyzed 1 by 1 to check if upgrades are available. Signed-off-by: David Pierret Reviewed-by: Yoann Congal --- upgrade-helper.py | 68

[yocto] [auh][PATCH 4/6] upgrade-helper.py: Fix indentation

2023-10-31 Thread Yoann Congal
Signed-off-by: Yoann Congal --- upgrade-helper.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/upgrade-helper.py b/upgrade-helper.py index bc485b8..4933a4a 100755 --- a/upgrade-helper.py +++ b/upgrade-helper.py @@ -677,7 +677,7 @@ class UniverseUpdater(Updater):

[yocto] [auh][PATCH 3/6] upgrade-helper.py: extract the inner function of get_packages_to_upgrade

2023-10-31 Thread Yoann Congal
This is to prepare for the futur loop on layers. Signed-off-by: Yoann Congal --- upgrade-helper.py | 23 --- 1 file changed, 16 insertions(+), 7 deletions(-) diff --git a/upgrade-helper.py b/upgrade-helper.py index 2538d61..bc485b8 100755 --- a/upgrade-helper.py +++

[yocto] [auh][PATCH 2/6] upgrade-helper.py: refactor _get_packages_to_upgrade to return a dict

2023-10-31 Thread Yoann Congal
Signed-off-by: Yoann Congal --- upgrade-helper.py | 32 1 file changed, 24 insertions(+), 8 deletions(-) diff --git a/upgrade-helper.py b/upgrade-helper.py index 57bf59a..2538d61 100755 --- a/upgrade-helper.py +++ b/upgrade-helper.py @@ -440,15 +440,23 @@ class

[yocto] [auh][PATCH 1/6] upgrade-helper.py: simplify a condition

2023-10-31 Thread Yoann Congal
Both branches contained the same code Signed-off-by: Yoann Congal --- upgrade-helper.py | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/upgrade-helper.py b/upgrade-helper.py index 1176a73..57bf59a 100755 --- a/upgrade-helper.py +++ b/upgrade-helper.py @@ -674,9 +674,7 @@

[yocto] [auh][PATCH 0/6] Extend AUH to meta-openembedded

2023-10-31 Thread Yoann Congal
v2->v3: * Split single patch in a series. Previous version was: [auh][PATCH v2] upgrade-helper.py: Add layer command line option * Removed short options * Refactor code before main patch "upgrade-helper.py: Add layer command line option" * Folded weeklyjob-oe into weeklyjob David Pierret

[yocto] Query on uboot env in binary format

2023-10-31 Thread SIMON BABY
Hello, Can I know if I can generate uboot.env in binary format ( uboot-env.bin) using yocto build ? Regards Simon -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61537): https://lists.yoctoproject.org/g/yocto/message/61537 Mute This Topic:

Re: [linux-yocto] [yocto-kernel-cache][PATCH] security.cfg: restore strict-only /dev/mem access

2023-10-31 Thread Bruce Ashfield
This looks fine to me. Which kernel versions were you seeing / testing this change on ? Bruce In message: [linux-yocto] [yocto-kernel-cache][PATCH] security.cfg: restore strict-only /dev/mem access on 27/10/2023 C. Andy Martin wrote: > CONFIG_DEVMEM was mistakenly not enabled, which defeats >

Re: [linux-yocto] Trial merge of v5.15.137 v6.1.60 for linux-yocto

2023-10-31 Thread Bruce Ashfield
Thanks Kevin, I've done the merges as well, and didn't see any major issues. Bruce In message: Trial merge of v5.15.137 v6.1.60 for linux-yocto on 26/10/2023 Kevin Hao wrote: > Hi Bruce, > > This is a trial merge of the stable kernel v5.15.137 v6.1.60 for the > following branches in the

Re: [v2][linux-yocto][v6.1/standard/nxp-sdk-6.1/nxp-soc & v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH] media: amphion: Move the blocking check_is_responsed() out of wait event loop

2023-10-31 Thread Bruce Ashfield
v2 is merged. Bruce In message: [v2][linux-yocto][v6.1/standard/nxp-sdk-6.1/nxp-soc & v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH] media: amphion: Move the blocking check_is_responsed() out of wait event loop on 31/10/2023 Xiaolei Wang wrote: > The blocking ops can't be used as a

Re: [yocto] [PATCH yocto-autobuilder-helper 2/2] config.json: add meta-oe to the metrics target

2023-10-31 Thread Yoann Congal
Le 31/10/2023 à 15:49, Ross Burton a écrit : > From: Ross Burton > > This writes the metrics to a new yocto-metrics-meta-oe repository, and > write the results to patchmetrics-meta-oe. > > There's a great/ugly (delete to taste) hack to hide CVEs from oe-core, > so this only lists issues in

Re: [yocto] [PATCH yocto-autobuilder-helper 1/2] Rewrite metrics-gathering scripts

2023-10-31 Thread Yoann Congal
Le 31/10/2023 à 15:49, Ross Burton a écrit : > From: Ross Burton > > Rewrite the scripts that gather the metrics to be more generic. > > Extract the metrics repository cloning out so that we don't have to > repeatedly clone it. > > Make the scripts parse their arguments using getopt and be

Re: [yocto] [PATCH yocto-autobuilder-helper 1/2] Rewrite metrics-gathering scripts

2023-10-31 Thread Ross Burton
Props to Yoann Congal for an early version of this work, review, and fixes. Ross > On 31 Oct 2023, at 14:49, Ross Burton via lists.yoctoproject.org > wrote: > > From: Ross Burton > > Rewrite the scripts that gather the metrics to be more generic. > > Extract the metrics repository cloning

[yocto] [PATCH yocto-autobuilder-helper 2/2] config.json: add meta-oe to the metrics target

2023-10-31 Thread Ross Burton
From: Ross Burton This writes the metrics to a new yocto-metrics-meta-oe repository, and write the results to patchmetrics-meta-oe. There's a great/ugly (delete to taste) hack to hide CVEs from oe-core, so this only lists issues in meta-oe. Signed-off-by: Ross Burton --- config.json | 29

[yocto] [PATCH yocto-autobuilder-helper 1/2] Rewrite metrics-gathering scripts

2023-10-31 Thread Ross Burton
From: Ross Burton Rewrite the scripts that gather the metrics to be more generic. Extract the metrics repository cloning out so that we don't have to repeatedly clone it. Make the scripts parse their arguments using getopt and be more specific about what they're passed. In particular, this

Re: [yocto] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

2023-10-31 Thread Alexander Kanavin
On Tue, 31 Oct 2023 at 13:28, Richard Purdie wrote: > > Then we can pull all of it together into 'devtool esdk ' > > command (or similar), which would enter the esdk environment directly > > via: > > - running 'bitbake meta-ide-support' > > - running the above mentioned bitbake local.conf task

Re: [yocto] Yocto Project Status 31 October 2023 (WW44)

2023-10-31 Thread Neal Caidin
Yes! You are correct Michael. This is that strange in-between week. Next week it goes back to 17:00 CET. Good catch! -- Neal *Neal Caidin* Program Manager The Linux Foundation Durham, NC, U.S.A. - Eastern time zone +1 (919) 238-9104 (w/h) +1 (919) 949-1861 (m) ncai...@linuxfoundation.org On

Re: [yocto] Yocto Project Status 31 October 2023 (WW44)

2023-10-31 Thread Michael Opdenacker via lists.yoctoproject.org
Greetings, On 31.10.23 at 13:29, Neal Caidin wrote: Current Dev Position: YP 4.3 M4 (Feature Freeze) Next Deadline: 2nd October 2023 YP 4.3 M4 build date Next Team Meetings: * Bug Triage meeting Thursday November 2, 7:30 am PDT

[yocto] [meta-rockchip][PATCH v2 1/1] rock-pi-s: add

2023-10-31 Thread Trevor Woerner
ROCK Pi S is a Rockchip RK3308 based SBC from Radxa. It contains a 64-bit quad core processor, USB, ethernet, wireless connectivity, and voice detection engine in 1.7-inches square. The ROCK Pi S comes in two RAM sizes 256MB or 512MB DDR3, and uses an sdmmc card for OS and storage. Optionally,

[yocto] [meta-rockchip][PATCH v2 0/1] rock-pi-s: add

2023-10-31 Thread Trevor Woerner
Add a new MACHINE: rock-pi-s changes since v1: - while the actual patch to add the rock-pi-s was not merged, all of the cleanup patches that were submitted in advance of the "add" patch (and were part of the original series) were applied, therefore those patches are dropped from this

[yocto] Yocto Project Status 31 October 2023 (WW44)

2023-10-31 Thread Neal Caidin
Current Dev Position: YP 4.3 M4 (Feature Freeze) Next Deadline: 2nd October 2023 YP 4.3 M4 build date Next Team Meetings: - Bug Triage meeting Thursday November 2, 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) - Weekly Project Engineering Sync

Re: [yocto] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

2023-10-31 Thread Richard Purdie
On Tue, 2023-10-31 at 13:08 +0100, Alexander Kanavin wrote: > On Mon, 30 Oct 2023 at 16:02, Alexander Kanavin via > lists.openembedded.org > wrote: > > So here's what could be done: > > > > - esdk tools become symlinks in poky/scripts/esdk-tools/. esdk > > environment script puts that in PATH,

Re: [yocto] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

2023-10-31 Thread Alexander Kanavin
On Mon, 30 Oct 2023 at 16:02, Alexander Kanavin via lists.openembedded.org wrote: > So here's what could be done: > > - esdk tools become symlinks in poky/scripts/esdk-tools/. esdk > environment script puts that in PATH, rather than some custom > esdk-specific location (the code to generate that