[yocto] QA notification for completed autobuilder build (yocto-4.0.14.rc1)
A build flagged for QA (yocto-4.0.14.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-4.0.14.rc1 Build URL: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6132 Build hash information: bitbake: 6c1ffa9091d0c53a100e8c8c15122d28642034bd meta-agl: 09890bc1ce3d1836f0e35fbae7713f54d70a72ae meta-arm: b187fb9232ca0a6b5f8f90b4715958546fc41d73 meta-aws: 408f9331156ec101014cf065314d3b90e79e6814 meta-gplv2: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a meta-intel: 3f0115e9e59f94af54b74838f4f9ea7584ae meta-mingw: f6b38ce3c90e1600d41c2ebb41e152936a0357d7 meta-openembedded: 79a6f60dabad9e5b0e041efa91379447ef030482 meta-virtualization: 2d8b3cba8ff27c9ec2187a52b6a551fe1dcfaa07 oecore: 0eb8e67aa6833df0cde29833568a70e65c21d7e5 poky: d8d6d921fad14b82167d9f031d4fca06b5e01883 This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.pur...@linuxfoundation.org -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61609): https://lists.yoctoproject.org/g/yocto/message/61609 Mute This Topic: https://lists.yoctoproject.org/mt/102379529/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: Private: Re: [yocto] [nanbield] meta-intel-fpga layer support
Yes sorry, new here as new with yocto,
Actually I discovered yocto through guides along with intel fpga-soc boards.
These guides specify briefly how to use bitbake to build our system file based
on poky, and add existing recipes/layers.
All what I did is the following :
- I want recipe "django" which depends on layers "openembedded-core",
"meta-python", "meta-oe".
- I git clone in my folder the "meta-openembedded" repo that contains
"meta-python" and "meta-oe". I don't clone "openembedded-core" since it is
already included (partially) in "poky" from what I understood.
- I add django to my local.conf : CORE_IMAGE_EXTRA_INSTALL += " django "
- I add layers to my bblayers.conf : BBLAYERS += "
${TOPDIR}/../meta-openembedded/meta-python "
: BBLAYERS += " ${TOPDIR}/../meta-openembedded/meta-oe "
- and I build the systemfile with bitbake "core-image-full-cmdline" for
instance (it can either be core-image-minimal, I guess this doesn't affect
behavior on adding packages)
I didn't modify anything else beside adding these lines in my .conf files,
since guide I was following didn't mention something else necessary. Did I miss
a step for adding modules of a recipe ? I thought they were all included by
default.
I might mention but I suppose it doesn't affect something, I changed ' MACHINE
= "arria10" ' in local.conf which is my fpga-soc device.
Thanks again,
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61608): https://lists.yoctoproject.org/g/yocto/message/61608
Mute This Topic: https://lists.yoctoproject.org/mt/102373306/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: Private: Re: [yocto] [nanbield] meta-intel-fpga layer support
Please don’t mail directly, keep discussion on the list. > On 3 Nov 2023, at 18:56, roman.le...@univ-pau.fr wrote: > > Thank you for your answer, you are right venv is part of python3, I tried > venv in many ways but my system doesn't recognizes it : > > $:~# python3 -m venv env > /usr/bin/python3: No module named venv.__main__; 'venv' is a package and > cannot be directly executed > $:~# python3 venv env > /usr/bin/python3: can't find '__main__' module in '/home/root/venv' > > I tried with python and python 3.10 aswell , same answer. > > Actually I tried any other module (such as numbers, pickle, audio, > sqlite3,...) and it will give the same error, it seems I don't have any > module that can be found, I'm only able to launch python3 shell. Might this > be related to wrong environment variable ? Most modules can’t be executed directly, but venv should be able to. This is likely a missing dependency in the packaging. Can you confirm that you’ve installed python3-modules into your image to bring in _all_ of the standard library? Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61607): https://lists.yoctoproject.org/g/yocto/message/61607 Mute This Topic: https://lists.yoctoproject.org/mt/102373306/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Package dependencies not generated?
On 03.11.23 at 19:07, Michael Opdenacker via lists.yoctoproject.org wrote:
Hi Khem,
Thank you for helping!
On 03.11.23 at 18:36, Khem Raj wrote:
On Thu, Nov 2, 2023 at 11:16 AM Michael Opdenacker via
lists.yoctoproject.org
wrote:
Greetings,
I compiled rsyslog from meta-oe:
bitbake rsyslog
I set up a binary feed ("bitbake package-index") and a webserver to
serve it, and when I try to install the rsyslog package, I get:
$ opkg install rsyslog
I see you ran bitbake package-index so thats good. maybe you did but
let me ask did you run opkg update before doing opkg install ?
Yes, I did. And anyway I checked in tmp/deploy/ipk that no ipk package
for libestr got generated.
Weird.
I took another example, this time "opus-tools" from from meta-multimedia:
$ bitbake opus-tools
$ bitbake package-index
And on the target:
root@qemux86-64:~# opkg update
Downloading http://10.0.2.2:8000/all/Packages.gz.
Updated source 'uri-all-0'.
Downloading http://10.0.2.2:8000/core2-64/Packages.gz.
Updated source 'uri-core2-64-0'.
Downloading http://10.0.2.2:8000/qemux86_64/Packages.gz.
Updated source 'uri-qemux86_64-0'.
root@qemux86-64:~# opkg install opus-tools
* Solver encountered 1 problem(s):
* Problem 1/1:
* - conflicting requests
* - nothing provides libopus0 >= 1.4 needed by
opus-tools-0.2-r0.core2-64
*
* Solution 1:
* - do not ask to install a package providing opus-tools
So, that's the exact same issue. I am missing a bitbake target or
variable for building the packages for dependencies as well?
I also ran "bitbake world" on OE-core, and got no problem to install a
package and its dependencies got pulled automatically too. It seems the
issue happens when I build a package alone.
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61606): https://lists.yoctoproject.org/g/yocto/message/61606
Mute This Topic: https://lists.yoctoproject.org/mt/102348862/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Package dependencies not generated?
Hi Khem,
Thank you for helping!
On 03.11.23 at 18:36, Khem Raj wrote:
On Thu, Nov 2, 2023 at 11:16 AM Michael Opdenacker via
lists.yoctoproject.org
wrote:
Greetings,
I compiled rsyslog from meta-oe:
bitbake rsyslog
I set up a binary feed ("bitbake package-index") and a webserver to
serve it, and when I try to install the rsyslog package, I get:
$ opkg install rsyslog
I see you ran bitbake package-index so thats good. maybe you did but
let me ask did you run opkg update before doing opkg install ?
Yes, I did. And anyway I checked in tmp/deploy/ipk that no ipk package
for libestr got generated.
Weird.
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61605): https://lists.yoctoproject.org/g/yocto/message/61605
Mute This Topic: https://lists.yoctoproject.org/mt/102348862/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Package dependencies not generated?
On Thu, Nov 2, 2023 at 11:16 AM Michael Opdenacker via
lists.yoctoproject.org
wrote:
>
> Greetings,
>
> I compiled rsyslog from meta-oe:
> bitbake rsyslog
>
> I set up a binary feed ("bitbake package-index") and a webserver to
> serve it, and when I try to install the rsyslog package, I get:
> $ opkg install rsyslog
I see you ran bitbake package-index so thats good. maybe you did but
let me ask did you run opkg update before doing opkg install ?
> * Solver encountered 1 problem(s):
> * Problem 1/1:
> * - conflicting requests
> * - nothing provides libestr0 >= 0.1.11 needed by
> rsyslog-8.2306.0-r0.core2-64
>
> Indeed, no "*libestr*" package(s) got generated. Why not?
>
> I checked RDEPENDS:rsyslog and it contains "logrotate" for which a
> package was indeed generated. I thought that shared libraries
> dependencies were automatically detected and added to runtime
> dependencies. That's confirmed by
> https://docs.yoctoproject.org/dev/overview-manual/concepts.html#automatically-added-runtime-dependencies
> . Why didn't it happen?
>
> I checked that libestr got compiled (it's part of the DEPENDS for
> rsyslog), but I can't find any package for it, even in the working area.
>
> It sounds like a very basic misconception between my keyboard and my
> chair. What did I get wrong?
>
> Thanks in advance for your insights.
>
> Cheers
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61604): https://lists.yoctoproject.org/g/yocto/message/61604
Mute This Topic: https://lists.yoctoproject.org/mt/102348862/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [nanbield] meta-intel-fpga layer support
On 3 Nov 2023, at 15:01, roman.leduc via lists.yoctoproject.org wrote: > In order to work with django I need also virtualenv library. Use venv instead, this is part of python3 itself. Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61603): https://lists.yoctoproject.org/g/yocto/message/61603 Mute This Topic: https://lists.yoctoproject.org/mt/102365661/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Package dependencies not generated?
Hi Jose,
Thanks for your help!
On 03.11.23 at 16:42, Jose Quaresma wrote:
Maybe because rsyslog uses dlopen to load the libestr at runtime,
if this is the case the recipe should explicitly add a runtime dependency
for them.
+RDEPENDS:${PN} += "logrotate libestr"
I'm just thinking out loud and I have no idea if this is the case.
Jose
I don't think that's the case, because "libestr0" is one of the
dependencies of the "rsyslog" package. So, it was automatically
detected, but no package for generated for it. That's what I don't
understand.
Thanks again
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61602): https://lists.yoctoproject.org/g/yocto/message/61602
Mute This Topic: https://lists.yoctoproject.org/mt/102348862/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Package dependencies not generated?
Michael Opdenacker via lists.yoctoproject.org escreveu no dia sexta, 3/11/2023 à(s)
15:05:
> Greetings,
>
> On 02.11.23 at 19:16, Michael Opdenacker wrote:
> > Greetings,
> >
> > I compiled rsyslog from meta-oe:
> > bitbake rsyslog
> >
> > I set up a binary feed ("bitbake package-index") and a webserver to
> > serve it, and when I try to install the rsyslog package, I get:
> > $ opkg install rsyslog
> > * Solver encountered 1 problem(s):
> > * Problem 1/1:
> > * - conflicting requests
> > * - nothing provides libestr0 >= 0.1.11 needed by
> > rsyslog-8.2306.0-r0.core2-64
> >
> > Indeed, no "*libestr*" package(s) got generated. Why not?
> >
> > I checked RDEPENDS:rsyslog and it contains "logrotate" for which a
> > package was indeed generated. I thought that shared libraries
> > dependencies were automatically detected and added to runtime
> > dependencies. That's confirmed by
> >
> https://docs.yoctoproject.org/dev/overview-manual/concepts.html#automatically-added-runtime-dependencies
> > . Why didn't it happen?
> >
> > I checked that libestr got compiled (it's part of the DEPENDS for
> > rsyslog), but I can't find any package for it, even in the working area.
> >
> > It sounds like a very basic misconception between my keyboard and my
> > chair. What did I get wrong?
> >
> > Thanks in advance for your insights.
>
> A simpler way to ask this...
>
> When I build rsyslogd ("bitbake rsyslog"), an ipk package is built for
> this software, but not for its shared library dependencies, for example
> for libestr.
> How to explain this?
>
Maybe because rsyslog uses dlopen to load the libestr at runtime,
if this is the case the recipe should explicitly add a runtime dependency
for them.
+RDEPENDS:${PN} += "logrotate libestr"
I'm just thinking out loud and I have no idea if this is the case.
Jose
> Thanks in advance
> Cheers
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>
>
>
>
--
Best regards,
José Quaresma
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61601): https://lists.yoctoproject.org/g/yocto/message/61601
Mute This Topic: https://lists.yoctoproject.org/mt/102348862/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-rockchip][PATCH] rkbin:rk3308: pre-cleanup
Since 2 recipes can provide the same rk3308-specific blobs, switching
between them can potentially cause: "... is trying to install files into a
shared area when those files already exist" errors. Perform a pre-cleanup
in both recipes so they don't step on each others' toes.
Signed-off-by: Trevor Woerner
---
recipes-bsp/rkbin/rk3308-rkbin_git.bb | 5 +
recipes-bsp/rkbin/rockchip-rkbin_git.bb | 5 +
2 files changed, 10 insertions(+)
diff --git a/recipes-bsp/rkbin/rk3308-rkbin_git.bb
b/recipes-bsp/rkbin/rk3308-rkbin_git.bb
index c6b05b242738..65ee136eff7c 100644
--- a/recipes-bsp/rkbin/rk3308-rkbin_git.bb
+++ b/recipes-bsp/rkbin/rk3308-rkbin_git.bb
@@ -26,6 +26,11 @@ PACKAGES = "${PN}"
ALLOW_EMPTY:${PN} = "1"
do_deploy:rk3308() {
+ # cleanup first
+ rm -f ${DEPLOY_DIR_IMAGE}/bl31-rk3308.elf
+ rm -f ${DEPLOY_DIR_IMAGE}/tee-rk3308.bin
+ rm -f ${DEPLOY_DIR_IMAGE}/ddr-rk3308.bin
+
# Prebuilt TF-A
install -m 644 ${S}/bin/rk33/rk3308_bl31_v*.elf
${DEPLOYDIR}/bl31-rk3308.elf
# Prebuilt OPTEE-OS
diff --git a/recipes-bsp/rkbin/rockchip-rkbin_git.bb
b/recipes-bsp/rkbin/rockchip-rkbin_git.bb
index f1609c7a4957..3f842d669c76 100644
--- a/recipes-bsp/rkbin/rockchip-rkbin_git.bb
+++ b/recipes-bsp/rkbin/rockchip-rkbin_git.bb
@@ -27,6 +27,11 @@ PACKAGES = "${PN}"
ALLOW_EMPTY:${PN} = "1"
do_deploy:rk3308() {
+ # cleanup first
+ rm -f ${DEPLOY_DIR_IMAGE}/bl31-rk3308.elf
+ rm -f ${DEPLOY_DIR_IMAGE}/tee-rk3308.bin
+ rm -f ${DEPLOY_DIR_IMAGE}/ddr-rk3308.bin
+
# Prebuilt TF-A
install -m 644 ${S}/bin/rk33/rk3308_bl31_v*.elf
${DEPLOYDIR}/bl31-rk3308.elf
# Prebuilt OPTEE-OS
--
2.41.0.327.gaa9166bcc0ba
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61600): https://lists.yoctoproject.org/g/yocto/message/61600
Mute This Topic: https://lists.yoctoproject.org/mt/102366120/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Package dependencies not generated?
Greetings,
On 02.11.23 at 19:16, Michael Opdenacker wrote:
Greetings,
I compiled rsyslog from meta-oe:
bitbake rsyslog
I set up a binary feed ("bitbake package-index") and a webserver to
serve it, and when I try to install the rsyslog package, I get:
$ opkg install rsyslog
* Solver encountered 1 problem(s):
* Problem 1/1:
* - conflicting requests
* - nothing provides libestr0 >= 0.1.11 needed by
rsyslog-8.2306.0-r0.core2-64
Indeed, no "*libestr*" package(s) got generated. Why not?
I checked RDEPENDS:rsyslog and it contains "logrotate" for which a
package was indeed generated. I thought that shared libraries
dependencies were automatically detected and added to runtime
dependencies. That's confirmed by
https://docs.yoctoproject.org/dev/overview-manual/concepts.html#automatically-added-runtime-dependencies
. Why didn't it happen?
I checked that libestr got compiled (it's part of the DEPENDS for
rsyslog), but I can't find any package for it, even in the working area.
It sounds like a very basic misconception between my keyboard and my
chair. What did I get wrong?
Thanks in advance for your insights.
A simpler way to ask this...
When I build rsyslogd ("bitbake rsyslog"), an ipk package is built for
this software, but not for its shared library dependencies, for example
for libestr.
How to explain this?
Thanks in advance
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61599): https://lists.yoctoproject.org/g/yocto/message/61599
Mute This Topic: https://lists.yoctoproject.org/mt/102348862/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [nanbield] meta-intel-fpga layer support
Hello dear community, I was trying to use django recipe with core-image-minimal system file (poky langdale release) because it supports meta-intel-fpga layer. In order to work with django I need also virtualenv library. The only virtualenv available on langdale release is virtualenv v1.11.4 ( https://layers.openembedded.org/layerindex/recipe/341147/ ) and unfortunately, it seems not compatible with python3 from the same langdale release which is python3 v3.10.6 ( https://layers.openembedded.org/layerindex/recipe/325778/ ) ! I say this is not compatible, because when I run "virtualenv env" in prompt it outputs me the following : > > > > New python executable in env/bin/python3 > > > > Not overwriting existing python script env/bin/python (you must use > env/bin/python3) > > > > Traceback (most recent call last): > > > > File "/usr/bin/virtualenv", line 8, in > > > > sys.exit(main()) > > > > File "/usr/lib/python3.10/site-packages/virtualenv.py", line 815, in main > > > > create_environment(home_dir, > > > > File "/usr/lib/python3.10/site-packages/virtualenv.py", line 982, in > create_environment > > > > py_executable = os.path.abspath(install_python( > > > > File "/usr/lib/python3.10/site-packages/virtualenv.py", line 1459, in > install_python > > > > fix_local_scheme(home_dir, symlink) > > > > File "/usr/lib/python3.10/site-packages/virtualenv.py", line 1530, in > fix_local_scheme > > > > if sysconfig._get_default_scheme() == 'posix_local': > > > > AttributeError: module 'sysconfig' has no attribute '_get_default_scheme'. > Did you mean: 'get_default_scheme'? > > Especially the last line "...module 'sysconfig' has no attribute '_get_default_scheme'..." >From this post on stack overflow ( >https://stackoverflow.com/questions/71522731/unable-to-activate-virtual-environment-in-python > ) , it seems that virtualenv version is too old and must be upgraded. I know that pip recipe can be added, but not sure if poky is made to run "pip install --upgrade virtualenv" ? Should I try this ? Also the easiest solution would be to use poky nanbield release, because it provides newest virtualenv v.20.24.5 ( https://layers.openembedded.org/layerindex/recipe/352609/ ). But unfortunately I didn't find "meta-intel-fpga" layer support on this release ? What do you think I should do in order to be able to run virtualenv ? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61598): https://lists.yoctoproject.org/g/yocto/message/61598 Mute This Topic: https://lists.yoctoproject.org/mt/102365661/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder-helper] [PATCH] [dunfell] config.json/scripts: Update to handle CVE checks for meta-oe
Backport the recent CVE script changes from the master branch and add in
cvelayer.bbclass
as a way to exclude specific paths from the CVE check. Master can use the layer
overrides
to do this but these are not present on kirkstone.
Signed-off-by: Richard Purdie
---
config.json | 33 --
scripts/cve-generate-chartdata| 65 ++
scripts/cve-report.py | 30 +
scripts/cvecheck/cvelayer.bbclass | 9 +++
scripts/run-cvecheck | 106 ++
5 files changed, 212 insertions(+), 31 deletions(-)
create mode 100755 scripts/cve-generate-chartdata
create mode 100755 scripts/cve-report.py
create mode 100644 scripts/cvecheck/cvelayer.bbclass
diff --git a/config.json b/config.json
index c5d478d..3520e9a 100644
--- a/config.json
+++ b/config.json
@@ -835,7 +835,7 @@
}
},
"metrics" : {
-"NEEDREPOS" : ["poky"],
+"NEEDREPOS" : ["poky", "meta-openembedded"],
"extravars" : [
"INHERIT += 'cve-check'",
"BB_DISKMON_DIRS = ''",
@@ -845,12 +845,35 @@
"BB_SERVER_TIMEOUT = '0'"
],
"step1" : {
-"shortname" : "Generating patch metrics",
-"EXTRACMDS" :
["../../yocto-autobuilder-helper/scripts/run-patchmetrics ../ ../meta/
${HELPERRESULTSDIR}/../../patchmetrics . ${HELPERBRANCHNAME}"]
+"shortname" : "Fetching metrics repositories",
+"EXTRAPLAINCMDS" : [
+"git clone ssh://g...@push.yoctoproject.org/yocto-metrics
&& git clone ssh://g...@push.yoctoproject.org/yocto-metrics-meta-oe",
+"install -D ${SCRIPTSDIR}/cvecheck/cvelayer.bbclass
./build/classes/cvelayer.bbclass"
+]
},
"step2" : {
-"shortname" : "Running CVE checks",
-"EXTRACMDS" :
["../../yocto-autobuilder-helper/scripts/run-cvecheck ../ ../meta/
${HELPERRESULTSDIR}/../../patchmetrics . ${HELPERBRANCHNAME}"]
+"shortname" : "CVE checks for meta",
+"EXTRACMDS" : ["${SCRIPTSDIR}/run-cvecheck --metrics
../yocto-metrics --branch ${HELPERBRANCHNAME} --results
${HELPERRESULTSDIR}/../../patchmetrics --push"]
+},
+"step3" : {
+"shortname" : "CVE checks for meta-oe",
+"ADDLAYER" : [
+"${BUILDDIR}/../meta-openembedded/meta-oe",
+"${BUILDDIR}/../meta-openembedded/meta-python",
+"${BUILDDIR}/../meta-openembedded/meta-perl",
+"${BUILDDIR}/../meta-openembedded/meta-networking",
+"${BUILDDIR}/../meta-openembedded/meta-multimedia",
+"${BUILDDIR}/../meta-openembedded/meta-gnome",
+"${BUILDDIR}/../meta-openembedded/meta-xfce",
+"${BUILDDIR}/../meta-openembedded/meta-filesystems",
+"${BUILDDIR}/../meta-openembedded/meta-initramfs",
+"${BUILDDIR}/../meta-openembedded/meta-webserver"
+],
+"extravars" : [
+"INHERIT += 'cvelayer'",
+"SKIP_PATHS += '${TOPDIR}/../meta'"
+],
+"EXTRACMDS" : ["${SCRIPTSDIR}/run-cvecheck --metrics
../yocto-metrics-meta-oe --branch ${HELPERBRANCHNAME} --results
${HELPERRESULTSDIR}/../../patchmetrics-meta-oe --push"]
}
},
"meta-mingw" : {
diff --git a/scripts/cve-generate-chartdata b/scripts/cve-generate-chartdata
new file mode 100755
index 000..dbbbe82
--- /dev/null
+++ b/scripts/cve-generate-chartdata
@@ -0,0 +1,65 @@
+#!/usr/bin/env python3
+import json, os.path, collections
+import sys
+import argparse
+import subprocess
+import tempfile
+from datetime import datetime, date, timedelta
+
+args = argparse.ArgumentParser(description="Generate CVE count data files")
+args.add_argument("-j", "--json", help="JSON data file to use")
+args.add_argument("-r", "--resultsdir", help="results directory to parse")
+args = args.parse_args()
+
+try:
+with open(args.json) as f:
+counts = json.load(f)
+except FileNotFoundError:
+# if the file does not exist, start with an empty database.
+counts = {}
+
+lastyear = {}
+
+#
+# Write CVE counts by day
+#
+def round_to_day(val):
+return int((datetime.fromtimestamp(int(val)).date() - date(1970, 1,
1)).total_seconds())
+
+a_year_ago = (datetime.now() - timedelta(days=365) - datetime(1970, 1,
1)).total_seconds()
+
+for branch in os.listdir(args.resultsdir):
+branchdir = os.path.join(args.resultsdir, branch)
+for f in os.listdir(branchdir):
+ts = f.split(".")[0]
+rounded_ts = str(round_to_day(ts))
+if rounded_ts not in counts:
+counts[rounded_ts] = {}
+if branch not in counts[rounded_ts]:
+cvereport =
[yocto] [yocto-autobuilder-helper] [PATCH] [kirkstone] config.json/scripts: Update to handle CVE checks for meta-oe
Backport the recent CVE script changes from the master branch and add in
cvelayer.bbclass
as a way to exclude specific paths from the CVE check. Master can use the layer
overrides
to do this but these are not present on kirkstone.
Signed-off-by: Richard Purdie
---
config.json | 33 --
scripts/cve-generate-chartdata| 65 ++
scripts/cve-report.py | 30 +
scripts/cvecheck/cvelayer.bbclass | 9 +++
scripts/run-cvecheck | 106 ++
5 files changed, 212 insertions(+), 31 deletions(-)
create mode 100755 scripts/cve-generate-chartdata
create mode 100755 scripts/cve-report.py
create mode 100644 scripts/cvecheck/cvelayer.bbclass
diff --git a/config.json b/config.json
index 86ba2f4..7828462 100644
--- a/config.json
+++ b/config.json
@@ -910,7 +910,7 @@
}
},
"metrics" : {
-"NEEDREPOS" : ["poky"],
+"NEEDREPOS" : ["poky", "meta-openembedded"],
"extravars" : [
"INHERIT += 'cve-check'",
"BB_DISKMON_DIRS = ''",
@@ -920,12 +920,35 @@
"BB_SERVER_TIMEOUT = '0'"
],
"step1" : {
-"shortname" : "Generating patch metrics",
-"EXTRACMDS" :
["../../yocto-autobuilder-helper/scripts/run-patchmetrics ../ ../meta/
${HELPERRESULTSDIR}/../../patchmetrics . ${HELPERBRANCHNAME}"]
+"shortname" : "Fetching metrics repositories",
+"EXTRAPLAINCMDS" : [
+"git clone ssh://g...@push.yoctoproject.org/yocto-metrics
&& git clone ssh://g...@push.yoctoproject.org/yocto-metrics-meta-oe",
+"install -D ${SCRIPTSDIR}/cvecheck/cvelayer.bbclass
./build/classes/cvelayer.bbclass"
+]
},
"step2" : {
-"shortname" : "Running CVE checks",
-"EXTRACMDS" :
["../../yocto-autobuilder-helper/scripts/run-cvecheck ../ ../meta/
${HELPERRESULTSDIR}/../../patchmetrics . ${HELPERBRANCHNAME}"]
+"shortname" : "CVE checks for meta",
+"EXTRACMDS" : ["${SCRIPTSDIR}/run-cvecheck --metrics
../yocto-metrics --branch ${HELPERBRANCHNAME} --results
${HELPERRESULTSDIR}/../../patchmetrics --push"]
+},
+"step3" : {
+"shortname" : "CVE checks for meta-oe",
+"ADDLAYER" : [
+"${BUILDDIR}/../meta-openembedded/meta-oe",
+"${BUILDDIR}/../meta-openembedded/meta-python",
+"${BUILDDIR}/../meta-openembedded/meta-perl",
+"${BUILDDIR}/../meta-openembedded/meta-networking",
+"${BUILDDIR}/../meta-openembedded/meta-multimedia",
+"${BUILDDIR}/../meta-openembedded/meta-gnome",
+"${BUILDDIR}/../meta-openembedded/meta-xfce",
+"${BUILDDIR}/../meta-openembedded/meta-filesystems",
+"${BUILDDIR}/../meta-openembedded/meta-initramfs",
+"${BUILDDIR}/../meta-openembedded/meta-webserver"
+],
+"extravars" : [
+"INHERIT += 'cvelayer'",
+"SKIP_PATHS += '${TOPDIR}/../meta'"
+],
+"EXTRACMDS" : ["${SCRIPTSDIR}/run-cvecheck --metrics
../yocto-metrics-meta-oe --branch ${HELPERBRANCHNAME} --results
${HELPERRESULTSDIR}/../../patchmetrics-meta-oe --push"]
}
},
"meta-mingw" : {
diff --git a/scripts/cve-generate-chartdata b/scripts/cve-generate-chartdata
new file mode 100755
index 000..dbbbe82
--- /dev/null
+++ b/scripts/cve-generate-chartdata
@@ -0,0 +1,65 @@
+#!/usr/bin/env python3
+import json, os.path, collections
+import sys
+import argparse
+import subprocess
+import tempfile
+from datetime import datetime, date, timedelta
+
+args = argparse.ArgumentParser(description="Generate CVE count data files")
+args.add_argument("-j", "--json", help="JSON data file to use")
+args.add_argument("-r", "--resultsdir", help="results directory to parse")
+args = args.parse_args()
+
+try:
+with open(args.json) as f:
+counts = json.load(f)
+except FileNotFoundError:
+# if the file does not exist, start with an empty database.
+counts = {}
+
+lastyear = {}
+
+#
+# Write CVE counts by day
+#
+def round_to_day(val):
+return int((datetime.fromtimestamp(int(val)).date() - date(1970, 1,
1)).total_seconds())
+
+a_year_ago = (datetime.now() - timedelta(days=365) - datetime(1970, 1,
1)).total_seconds()
+
+for branch in os.listdir(args.resultsdir):
+branchdir = os.path.join(args.resultsdir, branch)
+for f in os.listdir(branchdir):
+ts = f.split(".")[0]
+rounded_ts = str(round_to_day(ts))
+if rounded_ts not in counts:
+counts[rounded_ts] = {}
+if branch not in counts[rounded_ts]:
+cvereport =
[yocto] [PATCH yocto-autobuilder-helper] scripts: pull before updating metrics
From: Ross Burton Do another git-pull in the metrics repository before updating the metrics, in case other metrics jobs running in parallel have updated the repositories since they were cloned. There will always be possibility of racing metrics jobs, but this should reduce the chance of it happening. An alternative would be to commit and then rebase before pushing, but I fear that a git-merge could produce invalid JSON and we'd have to manually fix up the repository. In my opinion, a wasted metrics run is preferable to potentially corrupted repositories. Signed-off-by: Ross Burton --- scripts/run-cvecheck | 6 ++ scripts/run-patchmetrics | 6 ++ 2 files changed, 12 insertions(+) diff --git a/scripts/run-cvecheck b/scripts/run-cvecheck index 711bec2..e0d52df 100755 --- a/scripts/run-cvecheck +++ b/scripts/run-cvecheck @@ -71,6 +71,12 @@ if [ ! -d $RESULTSDIR ]; then mkdir $RESULTSDIR fi +# Do another pull to make sure we're as up to date as possible. This is +# preferable to committing and rebasing before pushing as it would be better to +# waste some time repeating work than commit potentially corrupted files from a +# git merge gone wrong. +git -C $METRICSDIR pull + cd .. set +u . oe-init-build-env build diff --git a/scripts/run-patchmetrics b/scripts/run-patchmetrics index a75cf52..a3f6d8f 100755 --- a/scripts/run-patchmetrics +++ b/scripts/run-patchmetrics @@ -87,6 +87,12 @@ if [ "$BRANCH" != "master" ]; then exit 0 fi +# Do another pull to make sure we're as up to date as possible. This is +# preferable to committing and rebasing before pushing as it would be better to +# waste some time repeating work than commit potentially corrupted files from a +# git merge gone wrong. +git -C $METRICSDIR pull + # # Patch Metrics # -- 2.34.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61595): https://lists.yoctoproject.org/g/yocto/message/61595 Mute This Topic: https://lists.yoctoproject.org/mt/102362849/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [meta-parsec][master,nanbield][PATCH] Update parsec recipes
merged.
thanks
On 10/30/23 8:26 AM, Gowtham Suresh Kumar wrote:
Parsec-service and parsec-tool recipes have been updated to use
1.3.0 and 0.7.0 versions respectively.
Signed-off-by: Gowtham Suresh Kumar
---
.../parsec-service/parsec-service-crates.inc | 736 +-
...rvice_1.2.0.bb => parsec-service_1.3.0.bb} | 2 +-
.../parsec-tool/parsec-tool-crates.inc| 544 ++---
...sec-tool_0.6.0.bb => parsec-tool_0.7.0.bb} | 2 +-
4 files changed, 659 insertions(+), 625 deletions(-)
rename meta-parsec/recipes-parsec/parsec-service/{parsec-service_1.2.0.bb =>
parsec-service_1.3.0.bb} (97%)
rename meta-parsec/recipes-parsec/parsec-tool/{parsec-tool_0.6.0.bb =>
parsec-tool_0.7.0.bb} (88%)
diff --git
a/meta-parsec/recipes-parsec/parsec-service/parsec-service-crates.inc
b/meta-parsec/recipes-parsec/parsec-service/parsec-service-crates.inc
index 604e1ea..bf2c7d4 100644
--- a/meta-parsec/recipes-parsec/parsec-service/parsec-service-crates.inc
+++ b/meta-parsec/recipes-parsec/parsec-service/parsec-service-crates.inc
@@ -2,459 +2,473 @@
# from Cargo.lock
SRC_URI += " \
-crate://crates.io/ahash/0.7.6;name=ahash-0.7.6 \
-crate://crates.io/aho-corasick/0.7.20;name=aho-corasick-0.7.20 \
-crate://crates.io/ansi_term/0.12.1;name=ansi_term-0.12.1 \
-crate://crates.io/anyhow/1.0.69;name=anyhow-1.0.69 \
-crate://crates.io/asn1-rs/0.3.1;name=asn1-rs-0.3.1 \
-crate://crates.io/asn1-rs-derive/0.1.0;name=asn1-rs-derive-0.1.0 \
-crate://crates.io/asn1-rs-impl/0.1.0;name=asn1-rs-impl-0.1.0 \
-crate://crates.io/atty/0.2.14;name=atty-0.2.14 \
-crate://crates.io/autocfg/1.1.0;name=autocfg-1.1.0 \
-crate://crates.io/base64/0.13.1;name=base64-0.13.1 \
-crate://crates.io/bincode/1.3.3;name=bincode-1.3.3 \
-crate://crates.io/bindgen/0.57.0;name=bindgen-0.57.0 \
-crate://crates.io/bindgen/0.63.0;name=bindgen-0.63.0 \
-crate://crates.io/bitfield/0.13.2;name=bitfield-0.13.2 \
-crate://crates.io/bitflags/1.3.2;name=bitflags-1.3.2 \
-crate://crates.io/bumpalo/3.12.0;name=bumpalo-3.12.0 \
-crate://crates.io/bytes/1.4.0;name=bytes-1.4.0 \
-crate://crates.io/cc/1.0.79;name=cc-1.0.79 \
-crate://crates.io/cexpr/0.4.0;name=cexpr-0.4.0 \
-crate://crates.io/cexpr/0.6.0;name=cexpr-0.6.0 \
-crate://crates.io/cfg-if/1.0.0;name=cfg-if-1.0.0 \
-crate://crates.io/clang-sys/1.6.0;name=clang-sys-1.6.0 \
-crate://crates.io/clap/2.34.0;name=clap-2.34.0 \
-crate://crates.io/cmake/0.1.45;name=cmake-0.1.45 \
-crate://crates.io/const-oid/0.7.1;name=const-oid-0.7.1 \
-crate://crates.io/cryptoauthlib-sys/0.2.2;name=cryptoauthlib-sys-0.2.2 \
-crate://crates.io/cryptoki/0.3.1;name=cryptoki-0.3.1 \
-crate://crates.io/cryptoki-sys/0.1.5;name=cryptoki-sys-0.1.5 \
-crate://crates.io/data-encoding/2.3.3;name=data-encoding-2.3.3 \
-crate://crates.io/der/0.5.1;name=der-0.5.1 \
-crate://crates.io/der-parser/7.0.0;name=der-parser-7.0.0 \
-crate://crates.io/derivative/2.2.0;name=derivative-2.2.0 \
-crate://crates.io/displaydoc/0.2.3;name=displaydoc-0.2.3 \
-crate://crates.io/either/1.8.1;name=either-1.8.1 \
-crate://crates.io/enumflags2/0.7.5;name=enumflags2-0.7.5 \
-crate://crates.io/enumflags2_derive/0.7.4;name=enumflags2_derive-0.7.4 \
-crate://crates.io/env_logger/0.8.4;name=env_logger-0.8.4 \
-crate://crates.io/errno/0.2.8;name=errno-0.2.8 \
-crate://crates.io/errno-dragonfly/0.1.2;name=errno-dragonfly-0.1.2 \
-crate://crates.io/fallible-iterator/0.2.0;name=fallible-iterator-0.2.0 \
-
crate://crates.io/fallible-streaming-iterator/0.1.9;name=fallible-streaming-iterator-0.1.9
\
-crate://crates.io/fastrand/1.9.0;name=fastrand-1.9.0 \
-crate://crates.io/fixedbitset/0.2.0;name=fixedbitset-0.2.0 \
-crate://crates.io/form_urlencoded/1.1.0;name=form_urlencoded-1.1.0 \
-crate://crates.io/futures/0.3.27;name=futures-0.3.27 \
-crate://crates.io/futures-channel/0.3.27;name=futures-channel-0.3.27 \
-crate://crates.io/futures-core/0.3.27;name=futures-core-0.3.27 \
-crate://crates.io/futures-executor/0.3.27;name=futures-executor-0.3.27 \
-crate://crates.io/futures-io/0.3.27;name=futures-io-0.3.27 \
-crate://crates.io/futures-macro/0.3.27;name=futures-macro-0.3.27 \
-crate://crates.io/futures-sink/0.3.27;name=futures-sink-0.3.27 \
-crate://crates.io/futures-task/0.3.27;name=futures-task-0.3.27 \
-crate://crates.io/futures-util/0.3.27;name=futures-util-0.3.27 \
-crate://crates.io/generic-array/0.14.6;name=generic-array-0.14.6 \
-crate://crates.io/getrandom/0.2.8;name=getrandom-0.2.8 \
-crate://crates.io/glob/0.3.1;name=glob-0.3.1 \
-crate://crates.io/grpcio/0.9.1;name=grpcio-0.9.1 \
-crate://crates.io/grpcio-sys/0.9.1+1.38.0;name=grpcio-sys-0.9.1+1.38.0 \
-crate://crates.io/hashbrown/0.12.3;name=hashbrown-0.12.3 \
-crate://crates.io/hashlink/0.8.1;name=hashlink-0.8.1 \
-
[yocto] [yocto-autobuilder-helper] [PATCH] config.json: Fix upgrade helper conf path
Signed-off-by: Richard Purdie
---
config.json | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/config.json b/config.json
index 7505e59..ee13bcf 100644
--- a/config.json
+++ b/config.json
@@ -1467,7 +1467,7 @@
"git config user.email a...@yoctoproject.org",
"git config user.name 'Auto Upgrade Helper'",
"git switch -C tmp-auh-upgrades HEAD",
-"install -D ${SCRIPTSDIR}/auh-config/upgrade-helper.conf
./upgrade-helper/upgrade-helper.conf"
+"install -D ${SCRIPTSDIR}/auh-config/upgrade-helper.conf
./build/upgrade-helper/upgrade-helper.conf"
]
},
"step2" : {
@@ -1504,7 +1504,7 @@
"git -C ./meta-openembedded config user.email
a...@yoctoproject.org",
"git -C ./meta-openembedded config user.name 'Auto Upgrade
Helper'",
"git -C ./meta-openembedded switch -C tmp-auh-upgrades
HEAD",
-"install -D
${SCRIPTSDIR}/auh-config/upgrade-helper-meta-oe.conf
./upgrade-helper/upgrade-helper.conf"
+"install -D
${SCRIPTSDIR}/auh-config/upgrade-helper-meta-oe.conf
./build/upgrade-helper/upgrade-helper.conf"
]
},
"step2": {
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61593): https://lists.yoctoproject.org/g/yocto/message/61593
Mute This Topic: https://lists.yoctoproject.org/mt/102361508/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe:
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder-helper] [PATCH] auh-meta-oe: Send to the openembedded-devel mailing list, not core
To do that we need a separate config file.
Signed-off-by: Richard Purdie
---
config.json | 2 +-
.../auh-config/upgrade-helper-meta-oe.conf| 42 +++
2 files changed, 43 insertions(+), 1 deletion(-)
create mode 100644 scripts/auh-config/upgrade-helper-meta-oe.conf
diff --git a/config.json b/config.json
index dd45578..7505e59 100644
--- a/config.json
+++ b/config.json
@@ -1504,7 +1504,7 @@
"git -C ./meta-openembedded config user.email
a...@yoctoproject.org",
"git -C ./meta-openembedded config user.name 'Auto Upgrade
Helper'",
"git -C ./meta-openembedded switch -C tmp-auh-upgrades
HEAD",
-"install -D ${SCRIPTSDIR}/auh-config/upgrade-helper.conf
./upgrade-helper/upgrade-helper.conf"
+"install -D
${SCRIPTSDIR}/auh-config/upgrade-helper-meta-oe.conf
./upgrade-helper/upgrade-helper.conf"
]
},
"step2": {
diff --git a/scripts/auh-config/upgrade-helper-meta-oe.conf
b/scripts/auh-config/upgrade-helper-meta-oe.conf
new file mode 100644
index 000..14c6957
--- /dev/null
+++ b/scripts/auh-config/upgrade-helper-meta-oe.conf
@@ -0,0 +1,42 @@
+[maintainer_override]
+# mails for recipe upgrades will go to john.doe instead of jane.doe, etc
+#ross.bur...@intel.com=anibal.li...@linux.intel.com
+
+[settings]
+# recipes in blacklist will be skipped
+blacklist=linux-libc-headers linux-yocto alsa-utils-scripts
build-appliance-image
+
+#maintainers_whitelist=anibal.li...@linux.intel.com
+
+# SMTP server
+smtp=localhost:25
+
+# from whom should the mails arrive
+from=a...@yoctoproject.org
+
+# who should get the status mail with statistics, at the end
+status_recipients=openembedded-de...@lists.openembedded.org
+
+# who should be CCd with upgrade emails
+cc_recipients=openembedded-de...@lists.openembedded.org
+
+# clean sstate directory before upgrading
+#clean_sstate=yes
+
+# clean tmp directory before upgrading
+#clean_tmp=yes
+
+# machines to test build with
+#machines=qemux86 qemux86-64 qemuarm qemumips qemuppc
+#machines=qemux86
+
+buildhistory=yes
+
+#testimage=yes
+#testimage_name=core-image-minimal
+
+#workdir=/home/auh/work/
+publish_work_url=https://autobuilder.yocto.io/pub/auh
+
+commit_revert_policy=all
+
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61592): https://lists.yoctoproject.org/g/yocto/message/61592
Mute This Topic: https://lists.yoctoproject.org/mt/102361360/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe:
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder-helper] [PATCH] config.json: Add auto-upgrade-helper repo definition
Signed-off-by: Richard Purdie
---
config.json | 6 ++
1 file changed, 6 insertions(+)
diff --git a/config.json b/config.json
index 1b3c2b0..b2d6fb8 100644
--- a/config.json
+++ b/config.json
@@ -1631,6 +1631,12 @@
"branch" : "master",
"revision" : "HEAD",
"no-layer-add" : true
+},
+"auto-upgrade-helper" : {
+"url" : "git://git.yoctoproject.org/auto-upgrade-helper",
+"branch" : "master",
+"revision" : "HEAD",
+"no-layer-add" : true
}
},
"buildtools" : {
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61591): https://lists.yoctoproject.org/g/yocto/message/61591
Mute This Topic: https://lists.yoctoproject.org/mt/102361268/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe:
https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [yocto-autobuilder-helper][PATCH v4 1/2] config.json: Move AUH from custom scripts to config.json
On Fri, 2023-11-03 at 10:44 +0100, Alexander Kanavin wrote: > On Fri, 3 Nov 2023 at 10:37, Alexander Kanavin via > lists.yoctoproject.org > wrote: > > > > Ka-boom: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/130/builds/59 > > " > ERROR: Command . ./oe-init-build-env; bitbake-layers add-layer > /home/pokybuild/yocto-worker/auh/build/auto-upgrade-helper failed with > exit code 1, see errors above. (1699003823.8) > " > > I'm not exactly sure, but I think this should be addressed by adding > an entry in config.json with "no-layer-add" : true (there are examples > there). My changes have a piece at the end of config.json which adds the repo and fix that issue. I'll separate out that change and add it that way. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61590): https://lists.yoctoproject.org/g/yocto/message/61590 Mute This Topic: https://lists.yoctoproject.org/mt/102344544/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/leave/6691583/21656/737036229/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [yocto-autobuilder-helper][PATCH v4 1/2] config.json: Move AUH from custom scripts to config.json
On Fri, 3 Nov 2023 at 10:37, Alexander Kanavin via lists.yoctoproject.org wrote: > > Ka-boom: > https://autobuilder.yoctoproject.org/typhoon/#/builders/130/builds/59 " ERROR: Command . ./oe-init-build-env; bitbake-layers add-layer /home/pokybuild/yocto-worker/auh/build/auto-upgrade-helper failed with exit code 1, see errors above. (1699003823.8) " I'm not exactly sure, but I think this should be addressed by adding an entry in config.json with "no-layer-add" : true (there are examples there). Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61589): https://lists.yoctoproject.org/g/yocto/message/61589 Mute This Topic: https://lists.yoctoproject.org/mt/102344544/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [yocto-autobuilder-helper][PATCH v4 1/2] config.json: Move AUH from custom scripts to config.json
Ka-boom:
https://autobuilder.yoctoproject.org/typhoon/#/builders/130/builds/59
Alex
On Thu, 2 Nov 2023 at 16:21, Yoann Congal wrote:
>
> setup-auh and run-auh were doing what the AB config.json does:
> * creating repo checkouts: Now use NEEDREPOS
> * configuring bitbake env: Now use extravars
>
> This refactoring is needed to prepare adding AUH meta-oe support.
>
> Signed-off-by: Yoann Congal
> ---
> config.json | 26 ++---
> scripts/auh-config/local.conf.append | 5
> scripts/run-auh | 34
> scripts/setup-auh| 29
> 4 files changed, 23 insertions(+), 71 deletions(-)
> delete mode 100644 scripts/auh-config/local.conf.append
> delete mode 100755 scripts/run-auh
> delete mode 100755 scripts/setup-auh
>
> diff --git a/config.json b/config.json
> index 1b3c2b0..2e33c73 100644
> --- a/config.json
> +++ b/config.json
> @@ -1454,9 +1454,29 @@
> "TEMPLATE" : "buildperf"
> },
> "auh" : {
> -"EXTRAPLAINCMDS" : [
> -"${SCRIPTSDIR}/setup-auh ${HELPERBUILDDIR};
> ${SCRIPTSDIR}/run-auh ${HELPERBUILDDIR} ${WEBPUBLISH_DIR}/pub/auh/"
> -]
> +"NEEDREPOS" : ["poky", "auto-upgrade-helper"],
> +"extravars" :[
> +"INHERIT += 'buildhistory'",
> +"LICENSE_FLAGS_ACCEPTED = 'commercial'",
> +"DISTRO_FEATURES:append:libc-glibc = ' systemd usrmerge'",
> +"DISTRO_FEATURES:append = ' pam'"
> +],
> +"step1" : {
> +"shortname" : "setup AUH",
> +"EXTRAPLAINCMDS" : [
> +"git config user.email a...@yoctoproject.org",
> +"git config user.name 'Auto Upgrade Helper'",
> +"git switch -C tmp-auh-upgrades HEAD",
> +"install -D ${SCRIPTSDIR}/auh-config/upgrade-helper.conf
> ./upgrade-helper/upgrade-helper.conf"
> +]
> +},
> +"step2" : {
> +"shortname" : "run AUH",
> +"EXTRACMDS" : [
> +"../auto-upgrade-helper/upgrade-helper.py -e all",
> +"cp -rf ./upgrade-helper/* ${WEBPUBLISH_DIR}/pub/auh/"
> +]
> +}
> },
> "yocto-mirror" : {
> "MACHINE" : "qemux86-64",
> diff --git a/scripts/auh-config/local.conf.append
> b/scripts/auh-config/local.conf.append
> deleted file mode 100644
> index ee7ee2d..000
> --- a/scripts/auh-config/local.conf.append
> +++ /dev/null
> @@ -1,5 +0,0 @@
> -
> -INHERIT += "buildhistory"
> -LICENSE_FLAGS_ACCEPTED = "commercial"
> -DISTRO_FEATURES:append:libc-glibc = ' systemd usrmerge'
> -DISTRO_FEATURES:append = ' pam'
> diff --git a/scripts/run-auh b/scripts/run-auh
> deleted file mode 100755
> index 0419dd1..000
> --- a/scripts/run-auh
> +++ /dev/null
> @@ -1,34 +0,0 @@
> -#!/bin/bash
> -#
> -# SPDX-License-Identifier: GPL-2.0-only
> -#
> -# Run Auto Upgrade Helper in a directory set up by setup_auh.
> -#
> -# Called with $1 - the directory where the setup was created
> -
> -if [ -z $1 ]; then
> - echo "Use: $0 auh_setup_dir [publish_dir]"
> - exit 1
> -fi
> -
> -full_dir=$(readlink -e $1)
> -
> -auh_dir=$full_dir/auto-upgrade-helper
> -poky_dir=$full_dir/poky
> -build_dir=$full_dir/build
> -sstate_dir=$full_dir/build/sstate-cache
> -
> -pushd $poky_dir
> -
> -# Base the upgrades on poky master
> -git fetch origin
> -git checkout -B tmp-auh-upgrades origin/master
> -
> -source $poky_dir/oe-init-build-env $build_dir
> -$auh_dir/upgrade-helper.py -e all
> -
> -if [ -n $2 ]; then
> - cp -rf $build_dir/upgrade-helper/* $2
> -fi
> -
> -popd
> diff --git a/scripts/setup-auh b/scripts/setup-auh
> deleted file mode 100755
> index d6b83fe..000
> --- a/scripts/setup-auh
> +++ /dev/null
> @@ -1,29 +0,0 @@
> -#!/bin/bash
> -#
> -# SPDX-License-Identifier: GPL-2.0-only
> -#
> -# Initialize Auto Upgrade Helper in a directory.
> -#
> -# Called with $1 - the directory to place the setup
> -CONFIG_DIR=`dirname $0`/auh-config
> -
> -if [ -z $1 ]; then
> - echo "Use: $0 target_dir"
> - exit 1
> -fi
> -
> -mkdir -p $1
> -pushd $1
> -
> -git clone git://git.yoctoproject.org/poky
> -pushd poky
> -git config user.email a...@yoctoproject.org
> -git config user.name "Auto Upgrade Helper"
> -popd
> -git clone git://git.yoctoproject.org/auto-upgrade-helper
> -source poky/oe-init-build-env build
> -mkdir -p upgrade-helper
> -popd
> -
> -cp $CONFIG_DIR/upgrade-helper.conf $1/build/upgrade-helper
> -cat $CONFIG_DIR/local.conf.append >> $1/build/conf/local.conf
> --
> 2.30.2
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61588): https://lists.yoctoproject.org/g/yocto/message/61588
Mute This Topic: https://lists.yoctoproject.org/mt/102344544/21656
Group Owner:
[linux-yocto] Trial merge of v6.1.61 for linux-yocto
Hi Bruce, This is a trial merge of the stable kernel v6.1.61 for the following branches in the linux-yocto. 84d68d8dc1d6 v6.1/standard/sdkv5.10/axxia defd1068ac96 v6.1/standard/preempt-rt/sdkv5.10/axxia 96c8d58c9a96 v6.1/standard/base 9e276c93d51b v6.1/standard/preempt-rt/base a2ac97adabd3 v6.1/standard/ti-sdk-6.1/ti-j7xxx 4ba815fdb536 v6.1/standard/preempt-rt/ti-sdk-6.1/ti-j7xxx fb9b1f7fa976 v6.1/standard/nxp-sdk-6.1/nxp-soc 18a5fee6b7a1 v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc 893a38faf249 v6.1/standard/cn-sdkv5.15/octeon db08d90c1b35 v6.1/standard/preempt-rt/cn-sdkv5.15/octeon 655c9551d324 v6.1/standard/bcm-2xxx-rpi 6fc57af6c818 v6.1/standard/preempt-rt/bcm-2xxx-rpi a5bfbfab3ce8 v6.1/standard/nxp-sdk-5.15/nxp-s32g 0d8d5d5c2331 v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g 729ee2f9e4a8 v6.1/standard/intel-sdk-6.1/intel-socfpga cec2271a1389 v6.1/standard/preempt-rt/intel-sdk-6.1/intel-socfpga 495e3d17c1e1 v6.1/standard/x86 a1b9425c1bc8 v6.1/standard/preempt-rt/x86 6972f955575e v6.1/standard/sdkv6.1/xlnx-soc 79d17b9dffd7 v6.1/standard/preempt-rt/sdkv6.1/xlnx-soc This is a pretty normal stable release without any merge conflict or build errors. All the branches have passed my build test. I have pushed all these branches to: https://github.com/haokexin/linux You can use this as a reference for the linux-yocto stable kernel bump. Thanks, Kevin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13266): https://lists.yoctoproject.org/g/linux-yocto/message/13266 Mute This Topic: https://lists.yoctoproject.org/mt/102360599/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] serial: fsl_linflexuart: Fix Woverflow warning on conversion
From: Kevin Hao
A Woverflow warning was introduced by SDK commit e11fb4e609ab ("linflex:
Correctly clear UARTSR in interrupt mode").
drivers/tty/serial/fsl_linflexuart.c: In function ‘linflex_rxint’:
drivers/tty/serial/fsl_linflexuart.c:629:24: warning: conversion from ‘long
unsigned int’ to ‘u32’ {aka ‘unsigned int’} changes value from
‘18446744073709551613’ to ‘4294967293’ [-Woverflow]
629 | writel(~LINFLEXD_UARTSR_DTFTFF, sport->membase +
UARTSR)
Fix it by force casting to u32.
Signed-off-by: Kevin Hao
---
Hi Bruce,
Could you help me merge this into the following two branches?
v6.1/standard/nxp-sdk-5.15/nxp-s32g
v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g
drivers/tty/serial/fsl_linflexuart.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/fsl_linflexuart.c
b/drivers/tty/serial/fsl_linflexuart.c
index eb868ead47e6..45c965cb2412 100644
--- a/drivers/tty/serial/fsl_linflexuart.c
+++ b/drivers/tty/serial/fsl_linflexuart.c
@@ -626,7 +626,7 @@ static irqreturn_t linflex_rxint(int irq, void *dev_id)
break;
rx = readb(sport->membase + BDRM);
- writel(~LINFLEXD_UARTSR_DTFTFF, sport->membase + UARTSR);
+ writel(~(u32)LINFLEXD_UARTSR_DTFTFF, sport->membase + UARTSR);
flg = TTY_NORMAL;
sport->icount.rx++;
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13265):
https://lists.yoctoproject.org/g/linux-yocto/message/13265
Mute This Topic: https://lists.yoctoproject.org/mt/102360590/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [PATCH] nxp-s32g: update to compatile with SDK BSP38
This patch updates v6.1 kernel cache for nxp-s32g to compatible with SDK BSP38, and the related configs refers to both LTS22 and SDK BSP38. Moreover, the CONFIG_NVMEM_SCMI is added to support SCMI protocol/transport style, but now the ATF transport side is not ready, and it will cause the following panic when STR: Unable to handle kernel paging request at virtual address ffe8 Mem abort info: ESR = 0x9605 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x05: level 1 translation fault Data abort info: ISV = 0, ISS = 0x0005 CM = 0, WnR = 0 swapper pgtable: 4k pages, 39-bit VAs, pgdp=8b83e000 [ffe8] pgd=, p4d=, pud= Internal error: Oops: 9605 [#1] PREEMPT SMP Modules linked in: 8021q llce_can llce_mailbox pfeng(O) llce_core sch_fq_codel openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 CPU: 1 PID: 961 Comm: rtcwake Tainted: G O 5.15.129-yocto-standard #1 Hardware name: NXP S32G274A-RDB2 (DT) pstate: 0005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : scmi_dev_suspend+0xc/0x40 lr : __device_suspend+0x2bc/0x444 sp : ffc00d13ba90 x29: ffc00d13ba90 x28: ffc008ad78c4 x27: ff880ba2a260 x26: 0002 x25: ffc009d4619c x24: ffc008d5b6e0 x23: ff880ba28930 x22: x21: 0002 x20: ffc00b299d60 x19: ff880ba28810 x18: x17: 203a7367616c6620 x16: 7265766972642064 x15: ffc00aa968c2 x14: x13: 30203a7367616c66 x12: 2072657669726420 x11: 00f2 x10: ffc009d46d78 x9 : ffc008ad773c x8 : f287 x7 : ffc009d9ed78 x6 : 0001 x5 : ff880ba28810 x4 : 0001 x3 : ffc009769008 x2 : x1 : 0002 x0 : ff880ba28810 Call trace: scmi_dev_suspend+0xc/0x40 dpm_suspend+0x184/0x26c dpm_suspend_start+0x84/0xa0 suspend_devices_and_enter+0x148/0x20c enter_state+0x148/0x1dc pm_suspend+0x60/0xf0 state_store+0x94/0x120 kobj_attr_store+0x18/0x30 sysfs_kf_write+0x54/0x80 kernfs_fop_write_iter+0x128/0x1c0 new_sync_write+0xf0/0x18c vfs_write+0x1c4/0x220 ksys_write+0x70/0x100 __arm64_sys_write+0x24/0x30 invoke_syscall+0x5c/0x130 el0_svc_common.constprop.0+0x68/0x124 do_el0_svc+0x4c/0xb0 el0_svc+0x54/0x110 el0t_64_sync_handler+0xa4/0x130 el0t_64_sync+0x1a0/0x1a4 Code: d503201f aa1e03e9 d503201f f9403402 (f85e8042) ---[ end trace b5605e874e1249c4 ]--- Kernel panic - not syncing: Oops: Fatal exception SMP: stopping secondary CPUs Kernel Offset: disabled CPU features: 0x9,2001,2842 Memory Limit: none ---[ end Kernel panic - not syncing: Oops: Fatal exception ]--- So disable this config by default to fix the above issues, and it will be enabled when related codes all ready. Signed-off-by: Zhantao Tang --- bsp/nxp-s32g/nxp-s32g.cfg | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/bsp/nxp-s32g/nxp-s32g.cfg b/bsp/nxp-s32g/nxp-s32g.cfg index 1b8eae74..df6458b8 100644 --- a/bsp/nxp-s32g/nxp-s32g.cfg +++ b/bsp/nxp-s32g/nxp-s32g.cfg @@ -19,7 +19,10 @@ CONFIG_SOC_S32CC=y CONFIG_SCHED_MC=y CONFIG_ARM_SMMU=y +CONFIG_NXP_GLOBAL_TIME_STM=y + CONFIG_PINCTRL_S32CC=y +CONFIG_PINCTRL_SCMI=y CONFIG_CPU_IDLE=y CONFIG_ARM_PSCI_CPUIDLE=y @@ -52,6 +55,7 @@ CONFIG_NET_DSA_TAG_SJA1105=y CONFIG_NXP_TJA11XX_PHY=y CONFIG_NET_DSA_SJA1105=y CONFIG_NET_DSA_SJA1105_PTP=y +CONFIG_BRIDGE_VLAN_FILTERING=y #Serial CONFIG_SERIAL_AMBA_PL011=y @@ -65,6 +69,8 @@ CONFIG_SPI_FSL_DSPI=y CONFIG_SPI_SPIDEV=y CONFIG_GPIO_CDEV=y CONFIG_GPIO_S32CC=y +CONFIG_GPIO_SCMI=y +CONFIG_SENSORS_INA2XX=y #PCIE CONFIG_PCI=y @@ -119,7 +125,7 @@ CONFIG_INPUT_UINPUT=y # Thermal CONFIG_THERMAL=y -CONFIG_S32CC_THERMAL=y +CONFIG_QORIQ_THERMAL=y # ADC CONFIG_IIO=y @@ -156,6 +162,8 @@ CONFIG_S32CC_WDT=y CONFIG_BLK_DEV_NVME=y CONFIG_NVME_TARGET=y CONFIG_NVMEM_S32CC_SIUL2=y +CONFIG_NVMEM_S32CC_OCOTP=y +# CONFIG_NVMEM_SCMI is not set #LLCE CONFIG_CAN_LLCE=y -- 2.25.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13264): https://lists.yoctoproject.org/g/linux-yocto/message/13264 Mute This Topic: https://lists.yoctoproject.org/mt/102359525/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [yocto-kernel-cache kernel v6.1]: nxp-s32g: update to compatile with SDK BSP38
Hi Bruce, There is a patch to update v6.1 kernel cache for nxp-s32g bsp, would you please help to merge the following patch into yocto-6.1 branch? Thanks, Zhantao -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13263): https://lists.yoctoproject.org/g/linux-yocto/message/13263 Mute This Topic: https://lists.yoctoproject.org/mt/102359524/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
