Re: [yocto] Out-of-tree Kernel Modules
Le mer. 30 oct. 2024 à 20:01, Yishai Jaffe via lists.yoctoproject.org a écrit : > Hi Quentin, > > On Wed, Oct 30, 2024 at 5:01 PM Quentin Schulz > wrote: > >> Hi Yishai, >> >> On 10/30/24 3:54 PM, Yishai Jaffe via Lists.Yoctoproject.Org wrote: >> > You don't often get email from yishai1999= >> gmail@lists.yoctoproject.org. Learn why this is important< >> https://aka.ms/LearnAboutSenderIdentification> >> > Thanks Quentin, >> > Changing the include to uapi/linux/sched/types.h solved the issue. >> > But just so I'm clear on this - Can you explain when I should use uapi >> headers vs when to use the regular linux/xxx headers? >> > >> >> You should include the header where the structure is defined. >> >> The "issue" in Yocto is that the headers aren't coming from your kernel >> sources but from a generic linux kernel header recipe, and this is made >> on purpose. The generic linux kernel header recipe is at 6.6 in >> Scarthgap. Styhead has 6.10. The structure is defined in a different >> header in 6.6 and in 6.7+ (including 6.10), so your out-of-tree module >> needs the path from 6.6 in order to compile in Scarthgap, but will need >> another path from 6.7+ in order to compile in Styhead. >> >> > I think my question wasn't clear enough. > I meant to ask about the general usage of uapi header files. > When are definitions put in the uapi headers and when are they in the > regular linux headers? > The best explanation I could find when I hit this issue a few weeks ago is a stack overflow answer: https://stackoverflow.com/a/18858544 (+links inside) Does that help? > >> You can handle that via #if in your code, if you need the exact same >> source code to build on different Yocto/kernel versions. That is the >> cross to bear when one develops out of tree kernel modules sadly. >> >> Cheers, >> Quentin >> > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#64191): https://lists.yoctoproject.org/g/yocto/message/64191 Mute This Topic: https://lists.yoctoproject.org/mt/109295266/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Multi-layer GitLab CI/CD (multi-project pipelines and merge request CI)
ded/kas-cherry-es.yml > """ > --- > header: >version: 14 >includes: > - repo: meta-cherry-es >file: meta-bsp/kas-cherry-es.yml > target: >- cherry-es-extended-image > repos: >meta-cherry-es: > layers: >meta-extended: >meta-openembedded: > layers: >meta-oe: >meta-networking: > """ > > The important parts in .gitlab-ci.yml in meta-theobroma-systems-demo: > > """ > --- > workflow: >rules: > # Allow multi-project pipeline trigger, c.f. > # > > https://docs.gitlab.com/ee/ci/pipelines/downstream_pipelines.html#multi-project-pipelines > # so that a merge request in meta-cherry-es can trigger a pipeline > # in meta-theobroma-systems-demo > - if: $CI_PIPELINE_SOURCE == "pipeline" > > [snip] > > .build: >tags: > - docker >image: ghcr.io/siemens/kas/kas:4.3.2 >stage: build >script: > - | >if [ "$CI_PIPELINE_SOURCE" = "pipeline" ]; then > # FIXME: not generic (though not an issue for us :) ) > ADD_KAS_FILE="kas-mr-meta-cherry-es.yml" > parent_dir=$(basename "$PARENT_CI_PROJECT_PATH") > mkdir -p "$parent_dir" > cd "$parent_dir" > git init . > # Horrendous multi-line commands to make yamllint happy with > 80-character-long lines > repository="$(echo "$PARENT_CI_SERVER_URL" | \ >sed "s^\(http.*://\)\(.*\)^\1gitlab-ci-token:$CI_JOB_TOKEN@ > \2^")" > repository="$repository/$PARENT_CI_PROJECT_PATH" > ref="$PARENT_CI_MERGE_REQUEST_REF_PATH" > # FIXME: Note: only "required" because our internal gitlab > server is using a self-signed certificate > git -c http.sslVerify=false fetch "$repository" "$ref" || exit 1 > # Make sure we're testing what we're supposed to test > test "$PARENT_CI_COMMIT_SHA" = "$(git rev-parse FETCH_HEAD)" || > exit 1 > git checkout FETCH_HEAD || exit 1 > cd .. >else > # FIXME: not generic (though not an issue for us :) ) > ADD_KAS_FILE="kas-commit-meta-cherry-es.yml" >fi >export ADD_KAS_FILE > - KAS_MACHINE="$CI_JOB_NAME" kas build > "kas-cherry-es.yml:$ADD_KAS_FILE" > >artifacts: > paths: >- build/tmp/deploy/images/$CI_JOB_NAME/*.rootfs-*.wic >- build/tmp/deploy/images/$CI_JOB_NAME/*.rootfs-*.wic.bmap >- build/tmp/deploy/images/$CI_JOB_NAME/fitImage*$CI_JOB_NAME-*.bin >- build/tmp/deploy/images/$CI_JOB_NAME/idbloader.img-$CI_JOB_NAME-* >- build/tmp/deploy/images/$CI_JOB_NAME/u-boot-$CI_JOB_NAME-*.itb > exclude: >- build/tmp/deploy/images/$CI_JOB_NAME/fitImage*linux*.bin >timeout: 10h > > tiger-haikou: >extends: .build > """ > > My kas-*.yml files which will be used by the kas build command: > > kas-cherry-es.yml > """ > --- > header: >version: 14 >includes: > - repo: meta-cherry-es >file: meta-extended/kas-cherry-es.yml > target: >- cherry-es-demo-image > repos: >meta-openembedded: > layers: >meta-oe: >meta-networking: >meta-theobroma-systems-demo: > """ > > kas-commit-meta-cherry-es.yml > """ > --- > header: >version: 14 > repos: >meta-cherry-es: > url: https://git.embedded.cherry.de/yocto-layers/meta-cherry-es.git > commit: 71a6eee9c4cfe1a3c922b9a3c36acc6e0766a5d8 > branch: scarthgap > """ > > kas-mr-meta-cherry-es.yml > """ > --- > header: >version: 14 > repos: >meta-cherry-es: > path: meta-cherry-es > """ > > Things could be easier if kas allowed refs/merge-requests/X/head as > branch and using environment variables, in which case I could manage > with only one kas configuration file and avoid this horrendous series of > commands to manually fetch the source code. Maybe I missed something here? > > This also is not really capable of handling more than one git repo you > depend one. Say you have a layerF which layerC depends on, this wouldn't > be able to know which changes to test, layerF or layerA, but there's > probably some smart way to handle that in a generic way. I had this > issue in the past because i used to have three git repo
Re: [yocto] How I can update the Yocto SDK incrementally/partially?
Le mar. 8 oct. 2024 à 11:27, salahaldeen.alt...@yahoo.com via lists.yoctoproject.org a écrit : > Hi All, > > I have the need to update the yocto SDK incrementally without the need to > rebuild it every time from scratch. > I have the package management ipk enabled in my configuration. > > can I use opkg install after sourcing the SDK script? which requirement I > need to get it running? > updating the rootfs on the target is working fine, but updating the SDK is > not working > That sounds like the eSDK : https://docs.yoctoproject.org/sdk-manual/extensible.html#applying-updates-to-an-installed-extensible-sdk Have you tried it? Regards, > Salahaldeen > > > > -- Yoann Congal Smile ECS - Tech expert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63965): https://lists.yoctoproject.org/g/yocto/message/63965 Mute This Topic: https://lists.yoctoproject.org/mt/108885909/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Does yocto recipe support fetching from SRC_URC as ipk pakage?
Le mar. 8 oct. 2024 à 11:27, salahaldeen.alt...@yahoo.com via
lists.yoctoproject.org
a écrit :
> Hi All,
>
> I have one request from one custom to fetch the recipe from ipk package,
> is this recommended?
> Does any one tested fetching from ipk?
>
> the recipe looks like this
>
> SRC_URI = "http://your-server-url/path/to/package.ipk";
> # Fetches the IPK and unpacks it
> do_unpack[depends] += "opkg-native:do_populate_sysroot"
> S = "${WORKDIR}"
>
> # Install the package using opkg
> do_install() {
> opkg-cl -o ${D} install ${WORKDIR}/package.ipk
> }
>
This looks like the bin_package class:
https://git.yoctoproject.org/poky/plain/meta/classes-recipe/bin_package.bbclass
https://docs.yoctoproject.org/ref-manual/classes.html#bin-package
Have you found/looked into it?
>
> Regards,
> Salahaldeen
>
>
>
>
--
Yoann Congal
Smile ECS - Tech expert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63964): https://lists.yoctoproject.org/g/yocto/message/63964
Mute This Topic: https://lists.yoctoproject.org/mt/108885904/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [yocto-autobuilder2][PATCH] schedulers: metrics: Start again with master for the daily full download
(Replying to myself to keep conclusion of an IRC discussion)
Le sam. 16 mars 2024 à 00:29, Yoann Congal a écrit :
> Change the order of metrics branches:
> * First, master at 5am which may do the full CVE download (might take
> 1 hour to finish).
> * Then, the other branches starting at 6am to allow them to use the
> fresh download.
> * And, finally, generate global charts data from individual branch
> metrics (at 8am)
>
That would not work since the master metrics can go well above 1h (e.g.
https://autobuilder.yoctoproject.org/typhoon/#/builders/138/builds/1343)
What we want is:
* A triggering builder (see
https://docs.buildbot.net/3.8.0/manual/configuration/steps/trigger.html)
that
* for each branch,
* trigger a builder that do the run-cvecheck (starting with master for
the NVD database download)
* Finish with the chart generation (run-cvechart)
That way, we will have proper ordering/dependencies between metrics
computing and chart generation.
NB: Trying to order builders on the AB based on estimated build duration
does not work because workers are quite loaded and the pressure regulation
can extend the build time quite a bit.
> Compared with commit 839c3cedbf6f ("schedulers: metrics: Start with master
> for the daily full download"),
> the last part is new.
>
> Signed-off-by: Yoann Congal
> ---
>
> schedulers.py | 9 +++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/schedulers.py b/schedulers.py
> index a30383f..67cc739 100644
> --- a/schedulers.py
> +++ b/schedulers.py
> @@ -497,12 +497,17 @@
> schedulers.append(sched.Nightly(name='nightly-meta-oe-mirror',
> branch='master',
> schedulers.append(sched.Nightly(name='nightly-reproducible-meta-oe',
> branch='master', properties=parent_default_props('reproducible-meta-oe'),
>builderNames=['reproducible-meta-oe'], hour=2,
> minute=0, dayOfWeek=5))
>
> -# Run metrics at 3-7am each day
> +# Run metrics at 5-8am each day
> +# Starts with master which may do a full CVE database download and start
> other
> +# branches 1 hour later to allow them to re-use the fresh download.
> +schedulers.append(sched.Nightly(name='nightly-metrics', branch='master',
> properties=parent_default_props('metrics'), builderNames=['metrics'],
> hour=5, minute=0))
> schedulers.append(sched.Nightly(name='nightly-metrics-dunfell',
> branch='dunfell', properties=parent_default_props('metrics', 'dunfell'),
> builderNames=['metrics'], hour=6, minute=0, codebases = {'' : {'branch' :
> 'dunfell'}}))
> schedulers.append(sched.Nightly(name='nightly-metrics-kirkstone',
> branch='kirkstone', properties=parent_default_props('metrics',
> 'kirkstone'), builderNames=['metrics'], hour=6, minute=15, codebases = {''
> : {'branch' : 'kirkstone'}}))
> schedulers.append(sched.Nightly(name='nightly-metrics-mickledore',
> branch='mickledore', properties=parent_default_props('metrics',
> 'mickledore'), builderNames=['metrics'], hour=6, minute=30, codebases = {''
> : {'branch' : 'mickledore'}}))
> schedulers.append(sched.Nightly(name='nightly-metrics-nanbield',
> branch='nanbield', properties=parent_default_props('metrics', 'nanbield'),
> builderNames=['metrics'], hour=6, minute=45, codebases = {'' : {'branch' :
> 'nanbield'}}))
> -schedulers.append(sched.Nightly(name='nightly-metrics', branch='master',
> properties=parent_default_props('metrics'), builderNames=['metrics'],
> hour=7, minute=0))
> +# Generate charts after every branch had its metrics computed
> +schedulers.append(sched.Nightly(name='nightly-metrics-charts',
> branch='master', properties=parent_default_props('metrics'),
> builderNames=['metrics-charts'], hour=8, minute=0))
> +
>
> # Run check-layer-nightly twice a week for nanbield
> schedulers.append(sched.Nightly(name='nightly-check-layer-nanbield',
> properties=parent_default_props('check-layer-nightly', 'nanbield'),
> --
> 2.39.2
>
>
--
Yoann Congal
Smile ECS - Tech expert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62772): https://lists.yoctoproject.org/g/yocto/message/62772
Mute This Topic: https://lists.yoctoproject.org/mt/104959134/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder2][PATCH] schedulers: metrics: Start again with master for the daily full download
Change the order of metrics branches:
* First, master at 5am which may do the full CVE download (might take
1 hour to finish).
* Then, the other branches starting at 6am to allow them to use the
fresh download.
* And, finally, generate global charts data from individual branch
metrics (at 8am)
Compared with commit 839c3cedbf6f ("schedulers: metrics: Start with master for
the daily full download"),
the last part is new.
Signed-off-by: Yoann Congal
---
schedulers.py | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/schedulers.py b/schedulers.py
index a30383f..67cc739 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -497,12 +497,17 @@
schedulers.append(sched.Nightly(name='nightly-meta-oe-mirror', branch='master',
schedulers.append(sched.Nightly(name='nightly-reproducible-meta-oe',
branch='master', properties=parent_default_props('reproducible-meta-oe'),
builderNames=['reproducible-meta-oe'], hour=2, minute=0,
dayOfWeek=5))
-# Run metrics at 3-7am each day
+# Run metrics at 5-8am each day
+# Starts with master which may do a full CVE database download and start other
+# branches 1 hour later to allow them to re-use the fresh download.
+schedulers.append(sched.Nightly(name='nightly-metrics', branch='master',
properties=parent_default_props('metrics'), builderNames=['metrics'], hour=5,
minute=0))
schedulers.append(sched.Nightly(name='nightly-metrics-dunfell',
branch='dunfell', properties=parent_default_props('metrics', 'dunfell'),
builderNames=['metrics'], hour=6, minute=0, codebases = {'' : {'branch' :
'dunfell'}}))
schedulers.append(sched.Nightly(name='nightly-metrics-kirkstone',
branch='kirkstone', properties=parent_default_props('metrics', 'kirkstone'),
builderNames=['metrics'], hour=6, minute=15, codebases = {'' : {'branch' :
'kirkstone'}}))
schedulers.append(sched.Nightly(name='nightly-metrics-mickledore',
branch='mickledore', properties=parent_default_props('metrics', 'mickledore'),
builderNames=['metrics'], hour=6, minute=30, codebases = {'' : {'branch' :
'mickledore'}}))
schedulers.append(sched.Nightly(name='nightly-metrics-nanbield',
branch='nanbield', properties=parent_default_props('metrics', 'nanbield'),
builderNames=['metrics'], hour=6, minute=45, codebases = {'' : {'branch' :
'nanbield'}}))
-schedulers.append(sched.Nightly(name='nightly-metrics', branch='master',
properties=parent_default_props('metrics'), builderNames=['metrics'], hour=7,
minute=0))
+# Generate charts after every branch had its metrics computed
+schedulers.append(sched.Nightly(name='nightly-metrics-charts',
branch='master', properties=parent_default_props('metrics'),
builderNames=['metrics-charts'], hour=8, minute=0))
+
# Run check-layer-nightly twice a week for nanbield
schedulers.append(sched.Nightly(name='nightly-check-layer-nanbield',
properties=parent_default_props('check-layer-nightly', 'nanbield'),
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62771): https://lists.yoctoproject.org/g/yocto/message/62771
Mute This Topic: https://lists.yoctoproject.org/mt/104959134/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 1/2] run-cvecheck: Split out the chart generation code
run-cvecheck had a special case for master were it would generate chart data after computing CVE metrics. This had to happen last in the list branches calling run-cvecheck. By spliting run-cvecheck into 2: * run-cvecheck (only does the cve-check), * run-cvecharts (only does the chart generation), ... we can run-cvecheck on master first while keeping run-cvecharts last. Signed-off-by: Yoann Congal --- scripts/run-cvecharts | 79 +++ scripts/run-cvecheck | 13 --- 2 files changed, 79 insertions(+), 13 deletions(-) create mode 100755 scripts/run-cvecharts diff --git a/scripts/run-cvecharts b/scripts/run-cvecharts new file mode 100755 index 000..d55 --- /dev/null +++ b/scripts/run-cvecharts @@ -0,0 +1,79 @@ +#!/bin/bash +# +# SPDX-License-Identifier: GPL-2.0-only +# + +set -eu + +ARGS=$(getopt -o '' --long 'metrics:,results:,push' -n 'run-cvecharts' -- "$@") +if [ $? -ne 0 ]; then +echo 'Cannot parse arguments...' >&2 +exit 1 +fi +eval set -- "$ARGS" +unset ARGS + +# Location of the yocto-autobuilder-helper scripts +OURDIR=$(dirname $0) +# The metrics repository to use +METRICSDIR="" +# Where to copy results to +RESULTSDIR="" +# Whether to push the metrics +PUSH=0 + +while true; do +case "$1" in +'--metrics') +METRICSDIR=$(realpath $2) +shift 2 +continue +;; +'--results') +RESULTSDIR=$(realpath -m $2) +shift 2 +continue +;; +'--push') +PUSH=1 +shift +continue +;; +'--') +shift +break +;; +*) +echo "Unexpected value $1" >&2 +exit 1 +;; +esac +done + +if ! test "$METRICSDIR" -a "$RESULTSDIR"; then +echo "Not all required options specified" +exit 1 +fi + +# +# CVE Chart data generation +# +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 + +$OURDIR/cve-generate-chartdata --json $METRICSDIR/cve-count-byday.json --resultsdir $METRICSDIR/cve-check/ +git -C $METRICSDIR add cve-count-byday.json +git -C $METRICSDIR commit -asm "Autobuilder updating CVE counts" || true +if [ "$PUSH" = "1" ]; then + git -C $METRICSDIR push +fi + +cp $METRICSDIR/cve-count-byday.json $RESULTSDIR +cp $METRICSDIR/cve-count-byday-lastyear.json $RESULTSDIR diff --git a/scripts/run-cvecheck b/scripts/run-cvecheck index 373f57c..13ba6e3 100755 --- a/scripts/run-cvecheck +++ b/scripts/run-cvecheck @@ -94,16 +94,3 @@ if [ -e tmp/log/cve/cve-summary.json ]; then fi $OURDIR/cve-report.py tmp/log/cve/cve-summary.json > $RESULTSDIR/cve-status-$BRANCH.txt fi - -if [ "$BRANCH" = "master" ]; then -mkdir -p $METRICSDIR/cve-check/$BRANCH/ -$OURDIR/cve-generate-chartdata --json $METRICSDIR/cve-count-byday.json --resultsdir $METRICSDIR/cve-check/ -git -C $METRICSDIR add cve-count-byday.json -git -C $METRICSDIR commit -asm "Autobuilder updating CVE counts" || true -if [ "$PUSH" = "1" ]; then -git -C $METRICSDIR push -fi - -cp $METRICSDIR/cve-count-byday.json $RESULTSDIR -cp $METRICSDIR/cve-count-byday-lastyear.json $RESULTSDIR -fi -- 2.39.2 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62769): https://lists.yoctoproject.org/g/yocto/message/62769 Mute This Topic: https://lists.yoctoproject.org/mt/104959075/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 2/2] config.json: metrics: Add new metrics-charts builder
This builder generates global chart data from individual branch metrics.
By splitting it out of metrics we can simplify metrics and schedule it
more freely.
This builder should be scheduled after metrics has been run for every
branch.
Signed-off-by: Yoann Congal
---
config.json | 17 +
1 file changed, 17 insertions(+)
diff --git a/config.json b/config.json
index 763121a..5b63313 100644
--- a/config.json
+++ b/config.json
@@ -1332,6 +1332,23 @@
"EXTRACMDS": [ "${SCRIPTSDIR}/run-abint
${HELPERRESULTSDIR}/../../abint/"]
}
},
+"metrics-charts" : {
+"NEEDREPOS" : ["poky", "meta-openembedded"],
+"step1" : {
+"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"
+]
+},
+"step2" : {
+"shortname" : "CVE charts for meta",
+"EXTRACMDS" : ["${SCRIPTSDIR}/run-cvecharts --metrics
../yocto-metrics --results ${HELPERRESULTSDIR}/../../patchmetrics --push"]
+},
+"step3" : {
+"shortname" : "CVE charts for meta-oe",
+"EXTRACMDS" : ["${SCRIPTSDIR}/run-cvecharts --metrics
../yocto-metrics-meta-oe --results
${HELPERRESULTSDIR}/../../patchmetrics-meta-oe --push"]
+}
+},
"meta-mingw" : {
"NEEDREPOS" : ["poky", "meta-mingw"],
"MACHINE" : "qemux86-64",
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62770): https://lists.yoctoproject.org/g/yocto/message/62770
Mute This Topic: https://lists.yoctoproject.org/mt/104959076/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder2][PATCH] schedulers: metrics: Start with master for the daily full download
Change the order of metrics branches:
* First, master at 5am which may do the full CVE download (might take
1 hour to finish).
* Then, the other branches starting at 6am to allow them to use the
fresh download.
Signed-off-by: Yoann Congal
---
schedulers.py | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/schedulers.py b/schedulers.py
index a30383f..34e2b70 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -497,12 +497,14 @@
schedulers.append(sched.Nightly(name='nightly-meta-oe-mirror', branch='master',
schedulers.append(sched.Nightly(name='nightly-reproducible-meta-oe',
branch='master', properties=parent_default_props('reproducible-meta-oe'),
builderNames=['reproducible-meta-oe'], hour=2, minute=0,
dayOfWeek=5))
-# Run metrics at 3-7am each day
+# Run metrics at 5-7am each day
+# Starts with master which may do a full CVE database download and start other
+# branches 1 hour later to allow them to re-use the fresh download.
+schedulers.append(sched.Nightly(name='nightly-metrics', branch='master',
properties=parent_default_props('metrics'), builderNames=['metrics'], hour=5,
minute=0))
schedulers.append(sched.Nightly(name='nightly-metrics-dunfell',
branch='dunfell', properties=parent_default_props('metrics', 'dunfell'),
builderNames=['metrics'], hour=6, minute=0, codebases = {'' : {'branch' :
'dunfell'}}))
schedulers.append(sched.Nightly(name='nightly-metrics-kirkstone',
branch='kirkstone', properties=parent_default_props('metrics', 'kirkstone'),
builderNames=['metrics'], hour=6, minute=15, codebases = {'' : {'branch' :
'kirkstone'}}))
schedulers.append(sched.Nightly(name='nightly-metrics-mickledore',
branch='mickledore', properties=parent_default_props('metrics', 'mickledore'),
builderNames=['metrics'], hour=6, minute=30, codebases = {'' : {'branch' :
'mickledore'}}))
schedulers.append(sched.Nightly(name='nightly-metrics-nanbield',
branch='nanbield', properties=parent_default_props('metrics', 'nanbield'),
builderNames=['metrics'], hour=6, minute=45, codebases = {'' : {'branch' :
'nanbield'}}))
-schedulers.append(sched.Nightly(name='nightly-metrics', branch='master',
properties=parent_default_props('metrics'), builderNames=['metrics'], hour=7,
minute=0))
# Run check-layer-nightly twice a week for nanbield
schedulers.append(sched.Nightly(name='nightly-check-layer-nanbield',
properties=parent_default_props('check-layer-nightly', 'nanbield'),
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62754): https://lists.yoctoproject.org/g/yocto/message/62754
Mute This Topic: https://lists.yoctoproject.org/mt/104913450/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] config.json: metrics: Switch to daily CVE DB full-download
By using CVE_DB_INCR_UPDATE_AGE_THRES = CVE_DB_INCR_UPDATE_AGE_THRES = 6h,
cve-check will do a NVD database full download if the database is older
than 6h or reuse it un-updated if its younger than 6h. Since the metrics
builder is scheduled every day, that will result in a daily
full-download.
That will workaround NVD API limitations were some updates may be missed
and the incrementaly updated database is not equivalent to a freshly
downloaded database.
Signed-off-by: Yoann Congal
---
This patch depends on [PATCH 2/2] cve-update-nvd2-native: Add an age threshold
for incremental update
https://lists.openembedded.org/g/openembedded-core/message/197046
---
config.json | 1 +
1 file changed, 1 insertion(+)
diff --git a/config.json b/config.json
index fdf4052..763121a 100644
--- a/config.json
+++ b/config.json
@@ -1290,6 +1290,7 @@
"CVE_CHECK_FORMAT_JSON = '1'",
"CVE_CHECK_SHOW_WARNINGS = '0'",
"CVE_DB_UPDATE_INTERVAL = '21600'",
+"CVE_DB_INCR_UPDATE_AGE_THRES = '21600'",
"BB_SERVER_TIMEOUT = '0'"
],
"step1" : {
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62753): https://lists.yoctoproject.org/g/yocto/message/62753
Mute This Topic: https://lists.yoctoproject.org/mt/104913380/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 v2 2/2] config.json: meta-oe-repro: fix meta-networking -> meta-python dependency
Since [0], meta-networking depends on meta-python. So, add meta-python
layer wherever meta-networking is used.
[0]:
https://git.openembedded.org/meta-openembedded/commit/?id=ab7c469bfeb7aba97402d8eab03d9bb18725c6af
Signed-off-by: Yoann Congal
---
config.json | 2 ++
1 file changed, 2 insertions(+)
diff --git a/config.json b/config.json
index ece5422..0c34161 100644
--- a/config.json
+++ b/config.json
@@ -385,10 +385,12 @@
"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-networking/
DISPLAY=:1 BB_LOGCONFIG=$(readlink -f $BB_LOGCONFIG) oe-selftest --newbuilddir
$BUILDDIR/build-st-meta-networking -r reproducible"],
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-oe",
+"${BUILDDIR}/../meta-openembedded/meta-python",
"${BUILDDIR}/../meta-openembedded/meta-networking"
],
"extravars" : [
"EXCLUDE_FROM_WORLD:layer-openembedded-layer = '1'",
+"EXCLUDE_FROM_WORLD:layer-meta-python = '1'",
"USERADD_GID_TABLES:append = '
files/static-group-meta-networking'",
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-networking'",
"USERADD_GID_TABLES:append = '
files/static-group-meta-oe'",
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62654): https://lists.yoctoproject.org/g/yocto/message/62654
Mute This Topic: https://lists.yoctoproject.org/mt/104712573/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 v2 1/2] config.json: meta-oe-repro: exclude packages that failed previously
Those are the non-reproducible packages from:
https://autobuilder.yoctoproject.org/typhoon/#/builders/155/builds/13
https://autobuilder.yoctoproject.org/typhoon/#/builders/155/builds/14
Only somewhat innocuous non-repro are added to
OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES (compile date in package, TMPDIR
path, ...).
Actual non-repros were not excluded :
* drbd-utils: a udev rule is either enabled or disabled
* apache2: a index.html is present or not in the package
* toybox-inittab: a getty is started or not on serial ports
Signed-off-by: Yoann Congal
---
v1->v2:
* Added non-reproducible packages from
https://autobuilder.yoctoproject.org/typhoon/#/builders/155/builds/14
---
config.json | 33 -
1 file changed, 28 insertions(+), 5 deletions(-)
diff --git a/config.json b/config.json
index 0ef4d54..ece5422 100644
--- a/config.json
+++ b/config.json
@@ -324,7 +324,7 @@
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-networking'",
"USERADD_GID_TABLES:append = '
files/static-group-meta-oe'",
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'",
-"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES = 'xfsprogs-doc zfs
zfs-dbg zfs-dev'"
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES = 'e2tools-ptest
xfsprogs-doc zfs zfs-dbg zfs-dev'"
]
},
"step2" : {
@@ -345,7 +345,7 @@
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-networking'",
"USERADD_GID_TABLES:append = '
files/static-group-meta-oe'",
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'",
-"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES = 'geary geary-dbg
gegl-dev gimp gimp-dbg gnome-terminal-src grilo-src gtk-vnc-src'"
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES = 'geary geary-dbg
gegl-dev gimp gimp-dbg gnome-terminal-src grilo-src gtk-vnc-src ibus'"
]
},
"step3" : {
@@ -392,7 +392,15 @@
"USERADD_GID_TABLES:append = '
files/static-group-meta-networking'",
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-networking'",
"USERADD_GID_TABLES:append = '
files/static-group-meta-oe'",
-"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'"
+"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES = 'blueman
blueman-dbg blueman-src civetweb-dev dhcp-relay-staticdev ettercap-src
fetchmail fetchmail-dbg'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'freediameter
freediameter-src freeradius htpdate-doc keepalived keepalived-dbg'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES +=
'kernel-module-mdio-netlink-6.6.17-yocto-standard libbearssl-staticdev libfko3
libfko-client libfko-daemon'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'libfko-dbg
libmosquitto1 libowfat-staticdev libruli-staticdev libsamba-util0
mdio-netlink-dbg mosquitto'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'mosquitto-dbg
ncftp ncftp-dbg ncftp-src ndisc6-dbg ndisc6-misc ndisc6-ndisc6 ndisc6-rdisc6
ndisc6-rdnssd'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES +=
'ndisc6-rltraceroute6 netsniff-ng-doc ntpsec-src openl2tp openl2tp-dbg
ot-br-posix ot-br-posix-dbg'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'postfix-cfg
proftpd proftpd-dbg proftpd-dev rdist rdist-dbg samba-dbg tayga tayga-dbg
wolfssl wolfssl-dbg'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'znc znc-doc'"
]
},
"step6" : {
@@ -403,7 +411,21 @@
],
"extravars" : [
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'",
-"USERADD_GID_TABLES:append = ' files/static-group-meta-oe'"
+"USERADD_GID_TABLES:append = '
files/static-group-meta-oe'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES = 'boinc-client-dev
cjson-ptest cpuid-doc crash crash-dbg crash-src dhrystone dhrystone-dbg
dhrystone-dev'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'dhrys
[yocto] [yocto-autobuilder-helper][PATCH] config.json: meta-oe-repro: exclude packages that failed previously
Those are the non-reproducible packages from:
https://autobuilder.yoctoproject.org/typhoon/#/builders/155/builds/13
Only somewhat innocuous non-repro are added to
OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES (compile date in package, TMPDIR
path, ...).
Actual non-repros were not excluded :
* drbd-utils: a udev rule is either enabled or disabled
* apache2: a index.html is present or not in the package
* toybox-inittab: a getty is started or not on serial ports
Signed-off-by: Yoann Congal
---
config.json | 29 ++---
1 file changed, 26 insertions(+), 3 deletions(-)
diff --git a/config.json b/config.json
index f9c67cb..01f82fc 100644
--- a/config.json
+++ b/config.json
@@ -392,7 +392,15 @@
"USERADD_GID_TABLES:append = '
files/static-group-meta-networking'",
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-networking'",
"USERADD_GID_TABLES:append = '
files/static-group-meta-oe'",
-"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'"
+"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES = 'blueman
blueman-dbg blueman-src civetweb-dev dhcp-relay-staticdev ettercap-src
fetchmail fetchmail-dbg'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'freediameter
freediameter-src freeradius htpdate-doc keepalived keepalived-dbg'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES +=
'kernel-module-mdio-netlink-6.6.17-yocto-standard libbearssl-staticdev libfko3
libfko-client libfko-daemon'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'libfko-dbg
libmosquitto1 libowfat-staticdev libruli-staticdev libsamba-util0
mdio-netlink-dbg mosquitto'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'mosquitto-dbg
ncftp ncftp-dbg ncftp-src ndisc6-dbg ndisc6-misc ndisc6-ndisc6 ndisc6-rdisc6
ndisc6-rdnssd'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES +=
'ndisc6-rltraceroute6 netsniff-ng-doc ntpsec-src openl2tp openl2tp-dbg
ot-br-posix ot-br-posix-dbg'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'postfix-cfg
proftpd proftpd-dbg proftpd-dev rdist rdist-dbg samba-dbg tayga tayga-dbg
wolfssl wolfssl-dbg'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'znc znc-doc'"
]
},
"step6" : {
@@ -403,7 +411,21 @@
],
"extravars" : [
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'",
-"USERADD_GID_TABLES:append = ' files/static-group-meta-oe'"
+"USERADD_GID_TABLES:append = '
files/static-group-meta-oe'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES = 'boinc-client-dev
cjson-ptest cpuid-doc crash crash-dbg crash-src dhrystone dhrystone-dbg
dhrystone-dev'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'dhrystone-src
directfb directfb-dbg doxygen-src editorconfig-core-c-dev etcd-cpp-apiv3-dev
fbgrab-doc'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'fluentbit-src
fvwm-dbg fvwm-doc fvwm-extra gcab-src gosu gosu-dbg gosu-dev gosu-staticdev
gphoto2'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'gphoto2-dbg
hddtemp-locale-de hdf5 hdf5-dbg hdf5-src hdf5-staticdev hplip hplip-dbg
jpnevulator-doc'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'jsonrpc-dev
kpatch-build kpatch-doc ldns libbotan-3-bin libbotan-3-dbg libbotan-3-dev
libck-doc'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'libdbus-cxx-dev
libforms libiio-src libjcat-dbg libjcat-ptest libthrift-c-glib-zlib-src
libvncserver-dev'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES +=
'libwebsockets-testapps libwmf libyui-ncurses-dbg libyui-ncurses-dev
lmbench-staticdev log4cpp lprng'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'lprng-dbg lshw
lshw-locale-fr mariadb-dbg mariadb-server mariadb-src mce-test mime-support-doc
minifi-cpp'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'minifi-cpp-dbg
minifi-cpp-src mozjs-115-src mpv mpv-dbg nana nbench-byte nbench-byte-dbg
nbench-byte-src'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'nspr-staticdev
openocd openocd-dbg pcp pcp-dev pcp-doc pcp-src perfetto perf
[yocto] [yocto-autobuilder-helper][PATCH] config.json: meta-oe-repro: exclude python3-pandas* from repro test
Exclude python3-pandas{,-src,-dbg} from reproducible tests as these look
non-reproducile for now[0][1].
[0]:
https://autobuilder.yoctoproject.org/typhoon/#/builders/155/builds/12/steps/40/logs/stdio
[1]:
https://autobuilder.yocto.io/pub/repro-fail-openembedded/meta-python/oe-reproducible-20240217-j7swf3az/packages/diff-html/
Signed-off-by: Yoann Congal
---
config.json | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/config.json b/config.json
index 3032fd7..1596d1e 100644
--- a/config.json
+++ b/config.json
@@ -429,7 +429,8 @@
"USERADD_GID_TABLES:append = '
files/static-group-meta-oe'",
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'",
"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES = 'python3-frozenlist
python3-frozenlist-dbg python3-kivy-src python3-pycocotools-src
python3-pydantic-core'",
-"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'python3-pyproj
python3-pyproj-dbg python3-pyproj-src python3-pyzmq python3-yarl
python3-yarl-dbg'"
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'python3-pyproj
python3-pyproj-dbg python3-pyproj-src python3-pyzmq python3-yarl
python3-yarl-dbg'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES +=
'python3-pandas-dbg python3-pandas-src python3-pandas'"
]
},
"step9" : {
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62529): https://lists.yoctoproject.org/g/yocto/message/62529
Mute This Topic: https://lists.yoctoproject.org/mt/104418637/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder2][PATCH] schedulers: decrease frequency of meta-oe-mirror on stable branches
Since the stable meta-oe branches tend to be updated once a month. Run
meta-oe-mirror twice a month to be sure to catch every update.
Signed-off-by: Yoann Congal
---
schedulers.py | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/schedulers.py b/schedulers.py
index 5ddcc7a..b9f3a09 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -489,23 +489,26 @@
schedulers.append(sched.Nightly(name='nightly-metrics-mickledore', branch='mickl
schedulers.append(sched.Nightly(name='nightly-metrics-nanbield',
branch='nanbield', properties=parent_default_props('metrics', 'nanbield'),
builderNames=['metrics'], hour=6, minute=45, codebases = {'' : {'branch' :
'nanbield'}}))
schedulers.append(sched.Nightly(name='nightly-metrics', branch='master',
properties=parent_default_props('metrics'), builderNames=['metrics'], hour=7,
minute=0))
-# Run check-layer-nightly amd meta-oe-mirror twice a week for nanbield
+# Run check-layer-nightly twice a week for nanbield
schedulers.append(sched.Nightly(name='nightly-check-layer-nanbield',
properties=parent_default_props('check-layer-nightly', 'nanbield'),
builderNames=['check-layer-nightly'], dayOfWeek=[3, 7],
hour=2, minute=0, codebases = {'' : {'branch' : 'nanbield'}}))
+# Run meta-oe-mirror twice a month for nanbield
schedulers.append(sched.Nightly(name='nightly-meta-oe-mirror-nanbield',
properties=parent_default_props('meta-oe-mirror', 'nanbield'),
- builderNames=['meta-oe-mirror'], dayOfWeek=[3, 7], hour=2,
minute=0, codebases = {'' : {'branch' : 'nanbield'}}))
+ builderNames=['meta-oe-mirror'], dayOfMonth=[1, 15], hour=2,
minute=0, codebases = {'' : {'branch' : 'nanbield'}}))
-# Run check-layer-nightly and meta-oe-mirror twice a week for kirkstone
+# Run check-layer-nightly twice a week for kirkstone
schedulers.append(sched.Nightly(name='nightly-check-layer-kirkstone',
properties=parent_default_props('check-layer-nightly', 'kirkstone'),
builderNames=['check-layer-nightly'], dayOfWeek=[0, 3],
hour=2, minute=0, codebases = {'' : {'branch' : 'kirkstone'}}))
+# Run meta-oe-mirror twice a month for kirkstone
schedulers.append(sched.Nightly(name='nightly-meta-oe-mirror-kirkstone',
properties=parent_default_props('meta-oe-mirror', 'kirkstone'),
- builderNames=['meta-oe-mirror'], dayOfWeek=[0, 3], hour=2,
minute=0, codebases = {'' : {'branch' : 'kirkstone'}}))
+ builderNames=['meta-oe-mirror'], dayOfMonth=[2, 16], hour=2,
minute=0, codebases = {'' : {'branch' : 'kirkstone'}}))
-# Run check-layer-nightly and meta-oe-mirror twice a week for dunfell
+# Run check-layer-nightly twice a week for dunfell
schedulers.append(sched.Nightly(name='nightly-check-layer-dunfell',
properties=parent_default_props('check-layer-nightly', 'dunfell'),
builderNames=['check-layer-nightly'], dayOfWeek=[1, 4],
hour=2, minute=0, codebases = {'' : {'branch' : 'dunfell'}}))
+# Run meta-oe-mirror twice a month for dunfell
schedulers.append(sched.Nightly(name='nightly-meta-oe-mirror-dunfell',
properties=parent_default_props('meta-oe-mirror', 'dunfell'),
- builderNames=['meta-oe-mirror'], dayOfWeek=[1, 4], hour=2,
minute=0, codebases = {'' : {'branch' : 'dunfell'}}))
+ builderNames=['meta-oe-mirror'], dayOfMonth=[3, 17], hour=2,
minute=0, codebases = {'' : {'branch' : 'dunfell'}}))
# Run the build performance tests at 3am, 9am, 3pm and 9pm
schedulers.append(sched.Nightly(name='nightly-buildperf', branch='master',
properties=parent_default_props('buildperf-debian11'),
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62303): https://lists.yoctoproject.org/g/yocto/message/62303
Mute This Topic: https://lists.yoctoproject.org/mt/103979258/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder2][PATCH] schedulers: Run reproducible-meta-oe for master once a week on weekends
Signed-off-by: Yoann Congal
---
schedulers.py | 4
1 file changed, 4 insertions(+)
diff --git a/schedulers.py b/schedulers.py
index 561f2b4..edd77b5 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -476,6 +476,10 @@
schedulers.append(sched.Nightly(name='nightly-check-layer', branch='master', pro
schedulers.append(sched.Nightly(name='nightly-meta-oe-mirror',
branch='master', properties=parent_default_props('meta-oe-mirror'),
builderNames=['meta-oe-mirror'], hour=0, minute=0))
+# Run reproducible-meta-oe for master once a week on weekends (2am on Saturday)
+schedulers.append(sched.Nightly(name='nightly-reproducible-meta-oe',
branch='master', properties=parent_default_props('reproducible-meta-oe'),
+ builderNames=['reproducible-meta-oe'], hour=2, minute=0,
dayOfWeek=5))
+
# Run metrics at 3-7am each day
schedulers.append(sched.Nightly(name='nightly-metrics-dunfell',
branch='dunfell', properties=parent_default_props('metrics', 'dunfell'),
builderNames=['metrics'], hour=6, minute=0, codebases = {'' : {'branch' :
'dunfell'}}))
schedulers.append(sched.Nightly(name='nightly-metrics-kirkstone',
branch='kirkstone', properties=parent_default_props('metrics', 'kirkstone'),
builderNames=['metrics'], hour=6, minute=15, codebases = {'' : {'branch' :
'kirkstone'}}))
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62246): https://lists.yoctoproject.org/g/yocto/message/62246
Mute This Topic: https://lists.yoctoproject.org/mt/103914016/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [yocto-autobuilder2] [PATCH] schedulers: Drop mickledore for meta-oe/layer-checks
Hi,
Le lun. 8 janv. 2024 à 14:34, Richard Purdie <
richard.pur...@linuxfoundation.org> a écrit :
> Signed-off-by: Richard Purdie
> ---
> schedulers.py | 6 --
> 1 file changed, 6 deletions(-)
>
This patch has been merged but not applied to the scheduler config maybe ?
meta-oe-mirror still run on Mickledore 12 days after this patch :
https://autobuilder.yoctoproject.org/typhoon/#/builders/156/builds/215
> diff --git a/schedulers.py b/schedulers.py
> index 4d7522a9..b8ff44b5 100644
> --- a/schedulers.py
> +++ b/schedulers.py
> @@ -487,12 +487,6 @@
> schedulers.append(sched.Nightly(name='nightly-check-layer-nanbield',
> properties=
> schedulers.append(sched.Nightly(name='nightly-meta-oe-mirror-nanbield',
> properties=parent_default_props('meta-oe-mirror', 'nanbield'),
>builderNames=['meta-oe-mirror'], dayOfWeek=[3, 7],
> hour=2, minute=0, codebases = {'' : {'branch' : 'nanbield'}}))
>
> -# Run check-layer-nightly amd meta-oe-mirror twice a week for mickledore
> -schedulers.append(sched.Nightly(name='nightly-check-layer-mickledore',
> properties=parent_default_props('check-layer-nightly', 'mickledore'),
> - builderNames=['check-layer-nightly'], dayOfWeek=[2, 5],
> hour=2, minute=0, codebases = {'' : {'branch' : 'mickledore'}}))
> -schedulers.append(sched.Nightly(name='nightly-meta-oe-mirror-mickledore',
> properties=parent_default_props('meta-oe-mirror', 'mickledore'),
> - builderNames=['meta-oe-mirror'], dayOfWeek=[2, 5],
> hour=2, minute=0, codebases = {'' : {'branch' : 'mickledore'}}))
> -
> # Run check-layer-nightly and meta-oe-mirror twice a week for kirkstone
> schedulers.append(sched.Nightly(name='nightly-check-layer-kirkstone',
> properties=parent_default_props('check-layer-nightly', 'kirkstone'),
>builderNames=['check-layer-nightly'], dayOfWeek=[0, 3],
> hour=2, minute=0, codebases = {'' : {'branch' : 'kirkstone'}}))
> --
> 2.39.2
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#62101):
> https://lists.yoctoproject.org/g/yocto/message/62101
> Mute This Topic: https://lists.yoctoproject.org/mt/103596671/4316185
> Group Owner: yocto+ow...@lists.yoctoproject.org
> Unsubscribe:
> https://lists.yoctoproject.org/g/yocto/leave/7785375/4316185/289819188/xyzzy
> [yoann.con...@smile.fr]
> -=-=-=-=-=-=-=-=-=-=-=
--
Yoann Congal
Smile ECS - Tech expert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62205): https://lists.yoctoproject.org/g/yocto/message/62205
Mute This Topic: https://lists.yoctoproject.org/mt/103596671/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder-helper][dunfell][PATCH] config.json: Make meta-oe source mirror config wider coverage (polkit)
Some recipes (gnome-settings-daemon, accountsservice) depend on polkit DISTRO_FEATURES. Set this up so that we get wider source mirror coverage and fewer warnings. Signed-off-by: Yoann Congal --- config.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.json b/config.json index 1a92c80..74c261b 100644 --- a/config.json +++ b/config.json @@ -1102,7 +1102,7 @@ "PNBLACKLIST[dvb-apps] = '1'", "PNBLACKLIST[tvheadend] = '1'", "LICENSE_FLAGS_ACCEPTED = 'commercial'", -"DISTRO_FEATURES_append = ' pam systemd usrmerge'", +"DISTRO_FEATURES_append = ' pam systemd usrmerge polkit'", "FORTRAN_forcevariable = ',fortran'", "RUNTIMETARGET_append_pn-gcc-runtime = ' libquadmath'" ], -- 2.39.2 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62169): https://lists.yoctoproject.org/g/yocto/message/62169 Mute This Topic: https://lists.yoctoproject.org/mt/103764636/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Menuconfig saving erased after bitbake clean
Le 09/01/2024 à 13:03, MOHAMMED HASSAN a écrit : > Hi guys, Hi, > I open menuconfig and add/remove some features, save and exit. > If I build using "bitbake linux-meson" the built image has all the features. > However If I use "bitbake linux-meson -c clean && bitbake linux-meson" , then > all the menuconfig modifications are erased and the default configuration is > built. > What to do. That's normal behavior. The output of menuconfig is saved as in the temporary directory (build/tmp/...) which is removed during the clean task. Information on how to keep the defconfig can be found here : https://docs.yoctoproject.org/dev/kernel-dev/common.html#using-menuconfig (You may want to use the documentation of your specific branch) Regards, > > > Thanks > Hassan > > > > -- Yoann Congal Smile ECS - Tech Expert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62118): https://lists.yoctoproject.org/g/yocto/message/62118 Mute This Topic: https://lists.yoctoproject.org/mt/103618090/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][dunfell][PATCH] config.json: Make meta-oe source mirror config wider coverage
Le 02/01/2024 à 19:10, Martin Jansa a écrit :
>> Backport: new->old override syntax
>
> FWIW: dunfell is forward compatible with new syntax, so this shouldn't be
> needed (other than the consistency with other metadata).
I did not know that. Thanks!
Either way, I would use the old syntax in this case to match what is documented
in local.conf template, recipe comments, etc. But it is nice to know :)
> On Tue, Jan 2, 2024 at 7:07 PM Yoann Congal <mailto:yoann.con...@smile.fr>> wrote:
>
> Some recipes depend on DISTRO_FEATURES, commercial licensing or compiler
> config like fortran. Set these things so that we get wider soruce mirror
> coverage and fewer warnings.
>
> 'commercial' license usage is ok here since we're not building and then
> shipping any binaries or using it, only mirroring the source code.
>
> Signed-off-by: Richard Purdie <mailto:richard.pur...@linuxfoundation.org>>
> (cherry picked from commit 93d47af8abbc6558f9a098a0c7fa6c0e901424a9)
> Signed-off-by: Yoann Congal <mailto:yoann.con...@smile.fr>>
> Backport: new->old override syntax
> ---
> This should fix the warnings of the AB meta-oe-mirror/dunfell builds
> ---
> config.json | 6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/config.json b/config.json
> index 3520e9a..1a92c80 100644
> --- a/config.json
> +++ b/config.json
> @@ -1100,7 +1100,11 @@
> ],
> "extravars" : [
> "PNBLACKLIST[dvb-apps] = '1'",
> - "PNBLACKLIST[tvheadend] = '1'"
> + "PNBLACKLIST[tvheadend] = '1'",
> + "LICENSE_FLAGS_ACCEPTED = 'commercial'",
> + "DISTRO_FEATURES_append = ' pam systemd usrmerge'",
> + "FORTRAN_forcevariable = ',fortran'",
> + "RUNTIMETARGET_append_pn-gcc-runtime = ' libquadmath'"
> ],
> "step1" : {
> "shortname" : "Sources pre-fetching",
> --
> 2.39.2
>
>
>
>
--
Yoann Congal
Smile ECS - Tech Expert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62068): https://lists.yoctoproject.org/g/yocto/message/62068
Mute This Topic: https://lists.yoctoproject.org/mt/103486578/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder-helper][dunfell][PATCH] config.json: Make meta-oe source mirror config wider coverage
Some recipes depend on DISTRO_FEATURES, commercial licensing or compiler
config like fortran. Set these things so that we get wider soruce mirror
coverage and fewer warnings.
'commercial' license usage is ok here since we're not building and then
shipping any binaries or using it, only mirroring the source code.
Signed-off-by: Richard Purdie
(cherry picked from commit 93d47af8abbc6558f9a098a0c7fa6c0e901424a9)
Signed-off-by: Yoann Congal
Backport: new->old override syntax
---
This should fix the warnings of the AB meta-oe-mirror/dunfell builds
---
config.json | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/config.json b/config.json
index 3520e9a..1a92c80 100644
--- a/config.json
+++ b/config.json
@@ -1100,7 +1100,11 @@
],
"extravars" : [
"PNBLACKLIST[dvb-apps] = '1'",
-"PNBLACKLIST[tvheadend] = '1'"
+"PNBLACKLIST[tvheadend] = '1'",
+"LICENSE_FLAGS_ACCEPTED = 'commercial'",
+"DISTRO_FEATURES_append = ' pam systemd usrmerge'",
+"FORTRAN_forcevariable = ',fortran'",
+"RUNTIMETARGET_append_pn-gcc-runtime = ' libquadmath'"
],
"step1" : {
"shortname" : "Sources pre-fetching",
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62066): https://lists.yoctoproject.org/g/yocto/message/62066
Mute This Topic: https://lists.yoctoproject.org/mt/103486578/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder-helper][kirkstone][PATCH] config.json: Make meta-oe source mirror config wider coverage
From: Richard Purdie
Some recipes depend on DISTRO_FEATURES, commercial licensing or compiler
config like fortran. Set these things so that we get wider soruce mirror
coverage and fewer warnings.
'commercial' license usage is ok here since we're not building and then
shipping any binaries or using it, only mirroring the source code.
Signed-off-by: Richard Purdie
(cherry picked from commit 93d47af8abbc6558f9a098a0c7fa6c0e901424a9)
Signed-off-by: Yoann Congal
---
This will fix many AB warnings for meta-oe-mirror/kirkstone
configuration
---
config.json | 6 ++
1 file changed, 6 insertions(+)
diff --git a/config.json b/config.json
index 7828462..7c53c46 100644
--- a/config.json
+++ b/config.json
@@ -1180,6 +1180,12 @@
"${BUILDDIR}/../meta-openembedded/meta-initramfs",
"${BUILDDIR}/../meta-openembedded/meta-webserver"
],
+"extravars" : [
+"LICENSE_FLAGS_ACCEPTED = 'commercial'",
+"DISTRO_FEATURES:append = ' pam systemd usrmerge'",
+"FORTRAN:forcevariable = ',fortran'",
+"RUNTIMETARGET:append:pn-gcc-runtime = ' libquadmath'"
+],
"step1" : {
"shortname" : "Sources pre-fetching",
"BBTARGETS" : "universe -c fetch -k",
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62065): https://lists.yoctoproject.org/g/yocto/message/62065
Mute This Topic: https://lists.yoctoproject.org/mt/103485053/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] config.json: reproducible-meta-oe: Add missing USERADD_UID/GID_TABLES
Some USERADD_UID/GID_TABLES were missing for lower layers which caused
some recipes to be not buildable because of skipped recipes (e.g. xfmpc,
python3-ldap)
Signed-off-by: Yoann Congal
---
config.json | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/config.json b/config.json
index b8d1f31..f52034d 100644
--- a/config.json
+++ b/config.json
@@ -423,7 +423,9 @@
"${BUILDDIR}/../meta-openembedded/meta-python"
],
"extravars" : [
-"EXCLUDE_FROM_WORLD:layer-openembedded-layer = '1'"
+"EXCLUDE_FROM_WORLD:layer-openembedded-layer = '1'",
+"USERADD_GID_TABLES:append = '
files/static-group-meta-oe'",
+"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'"
]
},
"step9" : {
@@ -457,7 +459,14 @@
"EXCLUDE_FROM_WORLD:layer-gnome-layer = '1'",
"EXCLUDE_FROM_WORLD:layer-multimedia-layer = '1'",
"EXCLUDE_FROM_WORLD:layer-meta-python = '1'",
-"EXCLUDE_FROM_WORLD:layer-networking-layer = '1'"
+"EXCLUDE_FROM_WORLD:layer-networking-layer = '1'",
+"USERADD_GID_TABLES:append = '
files/static-group-meta-oe'",
+"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'",
+"USERADD_GID_TABLES:append = '
files/static-group-meta-networking'",
+"USERADD_UID_TABLES:append = '
files/static-passwd-meta-networking'",
+"USERADD_GID_TABLES:append = '
files/static-group-meta-multimedia'",
+"USERADD_UID_TABLES:append = '
files/static-passwd-meta-multimedia'",
+"USERADD_UID_TABLES:append = '
files/static-passwd-meta-gnome'"
]
}
},
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61705): https://lists.yoctoproject.org/g/yocto/message/61705
Mute This Topic: https://lists.yoctoproject.org/mt/102616502/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] config.json: reproducible-meta-oe: add meta-webserver static GIDs
This is needed to fix a reproducibility error in netdata. Signed-off-by: Yoann Congal --- This depends on a patch in meta-oe/meta-webserver: [meta-webserver][PATCH] static-id: add missing netdata group https://lists.openembedded.org/g/openembedded-devel/message/106765 --- config.json | 1 + 1 file changed, 1 insertion(+) diff --git a/config.json b/config.json index 819fc7c..b8d1f31 100644 --- a/config.json +++ b/config.json @@ -435,6 +435,7 @@ ], "extravars" : [ "EXCLUDE_FROM_WORLD:layer-openembedded-layer = '1'", +"USERADD_GID_TABLES:append = ' files/static-group-meta-webserver'", "USERADD_UID_TABLES:append = ' files/static-passwd-meta-webserver'", "USERADD_GID_TABLES:append = ' files/static-group-meta-oe'", "USERADD_UID_TABLES:append = ' files/static-passwd-meta-oe'" -- 2.30.2 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61704): https://lists.yoctoproject.org/g/yocto/message/61704 Mute This Topic: https://lists.yoctoproject.org/mt/102609262/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] config.json: reproducible-meta-oe: exclude known repro fails
Use the new OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES to not trigger a test
failure on the known not-reproducible packages from meta-openembedded.
Signed-off-by: Yoann Congal
---
config.json | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/config.json b/config.json
index d10a3a8..819fc7c 100644
--- a/config.json
+++ b/config.json
@@ -318,7 +318,8 @@
"USERADD_GID_TABLES:append = '
files/static-group-meta-networking'",
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-networking'",
"USERADD_GID_TABLES:append = '
files/static-group-meta-oe'",
-"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'"
+"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES = 'xfsprogs-doc zfs
zfs-dbg zfs-dev'"
]
},
"step2" : {
@@ -338,7 +339,8 @@
"USERADD_GID_TABLES:append = '
files/static-group-meta-networking'",
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-networking'",
"USERADD_GID_TABLES:append = '
files/static-group-meta-oe'",
-"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'"
+"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES = 'geary geary-dbg
gegl-dev gimp gimp-dbg gnome-terminal-src grilo-src gtk-vnc-src ibus-doc'"
]
},
"step3" : {
@@ -346,6 +348,12 @@
"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-initramfs/
DISPLAY=:1 BB_LOGCONFIG=$(readlink -f $BB_LOGCONFIG) oe-selftest --newbuilddir
$BUILDDIR/build-st-meta-initramfs -r reproducible"],
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-initramfs"
+],
+"extravars" : [
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES = 'kexec-klibc
kexec-tools-klibc-dbg'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'mtdinfo-klibc
ubiattach-klibc ubiblock-klibc ubicrc32-klibc ubidetach-klibc ubiformat-klibc
ubimkvol-klibc'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES += 'ubinfo-klibc
ubinize-klibc ubirename-klibc ubirmvol-klibc ubirsvol-klibc ubiupdatevol-klibc
ubi-utils-klibc-dbg'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES +=
'vmcore-dmesg-klibc kexecboot-klibc kexecboot-klibc-dbg'"
]
},
"step4" : {
@@ -403,7 +411,8 @@
"USERADD_GID_TABLES:append = '
files/static-group-meta-perl'",
"USERADD_UID_TABLES:append = '
files/static-passwd-meta-perl'",
"USERADD_GID_TABLES:append = '
files/static-group-meta-oe'",
-"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'"
+"USERADD_UID_TABLES:append = '
files/static-passwd-meta-oe'",
+"OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES = 'libencode-perl-src
libhtml-tree-perl libhtml-tree-perl-doc libmodule-build-tiny-perl po4a
po4a-doc'"
]
},
"step8" : {
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61703): https://lists.yoctoproject.org/g/yocto/message/61703
Mute This Topic: https://lists.yoctoproject.org/mt/102605968/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Devtool fails if SRCREV is set to ${AUTOREV} #kirkstone #devtool #yocto
Le 08/11/2023 à 17:28, Chris Wyse a écrit :
> I ran into this problem as well. It doesn't seem like SRCPV is being set
> properly before use in the externalsrc.bbclass. I added the following line
> before bpn = d.getVar('BPN'), and now it works fine. Unfortunately, I needed
> to create another layer that overrides the poky classes to include it in my
> build. Here's the added line:
>
> srcpv = d.getVar('SRCPV')
>
> And here's a bit of context:
>
> python () {
> externalsrc = d.getVar('EXTERNALSRC')
> externalsrcbuild = d.getVar('EXTERNALSRC_BUILD')
>
> if externalsrc and not externalsrc.startswith("/"):
> bb.error("EXTERNALSRC must be an absolute path")
> if externalsrcbuild and not externalsrcbuild.startswith("/"):
> bb.error("EXTERNALSRC_BUILD must be an absolute path")
>
> srcpv = d.getVar('SRCPV')
>
> # If this is the base recipe and EXTERNALSRC is set for it or any of its
> # derivatives, then enable BB_DONT_CACHE to force the recipe to always be
> # re-parsed so that the file-checksums function for do_compile is run
> every
> # time.
> bpn = d.getVar('BPN')
> classextend = (d.getVar('BBCLASSEXTEND') or '').split()
> if bpn == d.getVar('PN') or not classextend:
> if (externalsrc or
> ('native' in classextend and
> d.getVar('EXTERNALSRC:pn-%s-native' % bpn)) or
> ('nativesdk' in classextend and
> d.getVar('EXTERNALSRC:pn-nativesdk-%s' % bpn)) or
> ('cross' in classextend and
> d.getVar('EXTERNALSRC:pn-%s-cross' % bpn))):
> d.setVar('BB_DONT_CACHE', '1')
>
> if externalsrc:
> import oe.recipeutils
> import oe.path
>
> d.setVar('S', externalsrc)
> if externalsrcbuild:
> d.setVar('B', externalsrcbuild)
> else:
> d.setVar('B', '${WORKDIR}/${BPN}-${PV}')
>
>
>
Hi Chris,
Thanks! This looks really interesting.
I've added your proposed fix to
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14918#c3 (the matching bug
that does happen to be assigned to me)
I'll try to look at what you sent in the next few days but in the meantime, if
you can/want you can always send this patch to the mailing list :)
Regards,
--
Yoann Congal
Smile ECS - Tech Expert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61641): https://lists.yoctoproject.org/g/yocto/message/61641
Mute This Topic: https://lists.yoctoproject.org/mt/93100438/21656
Mute #kirkstone:https://lists.yoctoproject.org/g/yocto/mutehashtag/kirkstone
Mute #devtool:https://lists.yoctoproject.org/g/yocto/mutehashtag/devtool
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
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 v3] AUH: Add Openembedded auto-update-helper with list of layer to test
Hello,
Le 28/10/2023 à 10:27, Richard Purdie a écrit :
> Hi David,
>
> On Thu, 2023-10-26 at 15:03 +0200, David Pierret wrote:
>> - Modify the setup-auh to use repositories cloned by the auto-builder.
>> Manage the case where meta-openembedded is not used.
>>
>> - Modify the run-auh to manage the optional additional layer.
>> Only 1 layer can be provided.
>>
>> - Add auh-meta-openembedded job with 1 step per layer.
>>
>> Signed-off-by: David Pierret
>> ---
>> config.json | 102 --
>> scripts/run-auh | 39 --
>> scripts/setup-auh | 34 ++--
>> 3 files changed, 146 insertions(+), 29 deletions(-)
>
> This took a while to review. Firstly, this really should be written as
> a set of commits with incremental changes.
>
> For example, changing the script to use poky from the autobuilder
> checkout instead of the local clone is one logical change. We could
> take and review/merge that independently of the other changes.
>
> Another logical independent change is using auto-upgrade-helper from
> the checkout of the autobuilder. That did highlight an issue that the
> autobuilder does not provide a checkout of that repository.>
> With that and this work in mind I added auh-meta-oe here:
>
> https://git.yoctoproject.org/yocto-autobuilder2/commit/?id=47c0119b6e87f920566d2176793ef8d982cf31e2
>
> and then added the auto-upgrade-helper repo here:
>
> https://git.yoctoproject.org/yocto-autobuilder2/commit/?id=854a60ce8bf8ce0feec370bc6782cc12aa1e29a5
>
> which then means this patch is closer to working.
>
> I had to make some tweaks on top of the patch to make it work:
>
> https://git.yoctoproject.org/yocto-autobuilder-helper/commit/?h=master-next&id=673745f473024020ed9efece26462e8c884dc819
>
> where I found that:
>
> * poky in the AB context is $1/.. since it is the top level
> container of the layers
> * meta-openembedded is located at ${HELPERBUILDDIR}/../meta-openembedded
> * we still need to source the build env script. The AB could be
> configured to do that for us but currently isn't.
> * we need to trim the machine_list down as mentioned
> * the naming we're using is auh-meta-oe, not auh-meta-openembedded
> * I've temporarily configured to use the test-list so we don't
> send lots of mail to all users
> * layer dependencies were missing in ADDLAYER. I hate having to do
> that but it is is what it is right now
I've just sent a reworked version of this patch :
https://lists.yoctoproject.org/g/yocto/message/61579
[yocto-autobuilder-helper][PATCH v4 0/2] Extend auto-upgrade helper to
meta-openembedded
https://lists.yoctoproject.org/g/yocto/message/61580
[yocto-autobuilder-helper][PATCH v4 1/2] config.json: Move AUH from custom
scripts to config.json
https://lists.yoctoproject.org/g/yocto/message/61581
[yocto-autobuilder-helper][PATCH v4 2/2] config.json: Extend AUH to
meta-openembedded layers
While moving stuff from the scripts to config.json, I found the scripts to be
mostly redundant and choose to remove them.
I've took most of RP's tweaks but not the test-list change.
I hope this one will be easier to review.
> With that, we get this "successful" build:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/159/builds/5
>
> which shows the exit code handling isn't great but probably deliberate
> to avoid autobuilder errors.
>
> This gets us to the point where the code in the upgrade helper itself
> needs the layer support changing.
>
> Since I've now had to look into that code, it seems the layer options
> are entirely missing from the commandline options parser. I'd strongly
> suggest dropping layer_machines variable and just use the machines
> value in all cases.
>
> "layer-mode" seems pointless as you can determine if we're in "layer
> mode" if a layer is specified on the commandline (which needs adding).
>
> I'm hoping you could use the layer overrides to be able to identify
> which recipes to upgrade.
I did not find how to use layer overrides here...
Maybe once AUH is more integrated into oe-core as RP suggested on IRC?
Regards,
--
Yoann Congal
Smile ECS - Tech Expert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61582): https://lists.yoctoproject.org/g/yocto/message/61582
Mute This Topic: https://lists.yoctoproject.org/mt/102199062/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 v4 2/2] config.json: Extend AUH to meta-openembedded layers
Add each a new builder "auh-meta-oe" and one step by meta-openembedded
layers.
Co-authored-by: David Pierret
Signed-off-by: Yoann Congal
---
config.json | 126
1 file changed, 126 insertions(+)
diff --git a/config.json b/config.json
index 2e33c73..0caf6e6 100644
--- a/config.json
+++ b/config.json
@@ -1478,6 +1478,132 @@
]
}
},
+"auh-meta-oe": {
+"NEEDREPOS": ["poky", "auto-upgrade-helper", "meta-openembedded"],
+"extravars": [
+"INHERIT += 'buildhistory'",
+"LICENSE_FLAGS_ACCEPTED = 'commercial'",
+"DISTRO_FEATURES:append:libc-glibc = ' systemd usrmerge'",
+"DISTRO_FEATURES:append = ' pam'"
+],
+"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"
+],
+"step1": {
+"shortname": "setup AUH for meta-oe layers",
+"EXTRAPLAINCMDS": [
+"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"
+]
+},
+"step2": {
+"shortname": "run AUH for layer meta-oe",
+"extravars": [
+"RECIPE_MAINTAINER:layer-openembedded-layer = 'Forced
maintainer for AUH'"
+],
+"EXTRACMDS": [
+"../auto-upgrade-helper/upgrade-helper.py -e all
--layer-dir ${BUILDDIR}/../meta-openembedded/ --layer-names meta-oe"
+]
+},
+"step3": {
+"shortname": "run AUH for layer meta-python",
+"extravars": [
+"RECIPE_MAINTAINER:layer-meta-python = 'Forced maintainer
for AUH'"
+],
+"EXTRACMDS": [
+"../auto-upgrade-helper/upgrade-helper.py -e all
--layer-dir ${BUILDDIR}/../meta-openembedded/ --layer-names meta-python"
+]
+},
+"step4": {
+"shortname": "run AUH for layer meta-perl",
+"extravars": [
+"RECIPE_MAINTAINER:layer-perl-layer = 'Forced maintainer
for AUH'"
+],
+"EXTRACMDS": [
+"../auto-upgrade-helper/upgrade-helper.py -e all
--layer-dir ${BUILDDIR}/../meta-openembedded/ --layer-names meta-perl"
+]
+},
+"step5": {
+"shortname": "run AUH for layer meta-networking",
+"extravars": [
+"RECIPE_MAINTAINER:layer-networking-layer = 'Forced
maintainer for AUH'"
+],
+"EXTRACMDS": [
+"../auto-upgrade-helper/upgrade-helper.py -e all
--layer-dir ${BUILDDIR}/../meta-openembedded/ --layer-names meta-networking"
+]
+},
+"step6": {
+"shortname": "run AUH for layer meta-multimedia",
+"extravars": [
+"RECIPE_MAINTAINER:layer-multimedia-layer = 'Forced
maintainer for AUH'"
+],
+"EXTRACMDS": [
+"../auto-upgrade-helper/upgrade-helper.py -e all
--layer-dir ${BUILDDIR}/../meta-openembedded/ --layer-names meta-multimedia"
+
[yocto] [yocto-autobuilder-helper][PATCH v4 0/2] Extend auto-upgrade helper to meta-openembedded
In order to extend AUH runs to meta-oe layers, we first need to refactor AUH runs on oe-core a bit. Then create a new builder dedicated to AUH runs on meta-oe layers. v3->v4: * Split patch between poky AUH refactoring and AUH extension to meta-oe * Refactor/simplify AUH a bit more (helper script setup/run-auh inlined) Yoann Congal (2): config.json: Move AUH from custom scripts to config.json config.json: Extend AUH to meta-openembedded layers config.json | 152 ++- scripts/auh-config/local.conf.append | 5 - scripts/run-auh | 34 -- scripts/setup-auh| 29 - 4 files changed, 149 insertions(+), 71 deletions(-) delete mode 100644 scripts/auh-config/local.conf.append delete mode 100755 scripts/run-auh delete mode 100755 scripts/setup-auh -- 2.30.2 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61579): https://lists.yoctoproject.org/g/yocto/message/61579 Mute This Topic: https://lists.yoctoproject.org/mt/102344543/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 v4 1/2] config.json: Move AUH from custom scripts to config.json
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 (#61580): https://lists.yoctoproject.org/g/yocto/message/61580
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]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [master-next][yocto-autobuilder-helper][PATCH] config.json: force RECIPE_MAINTAINER for meta-oe layers
Without it, auto-upgrade-helper skip most of the recipes because they do
not have a specific maintainer.
Signed-off-by: Yoann Congal
---
config.json | 30 ++
1 file changed, 30 insertions(+)
diff --git a/config.json b/config.json
index 6143969..ddf015f 100644
--- a/config.json
+++ b/config.json
@@ -1480,6 +1480,9 @@
"shortname" : "run AUH for layer meta-oe",
"ADDLAYER" : ["${BUILDDIR}/../meta-openembedded/meta-oe"],
+"extravars" : [
+"RECIPE_MAINTAINER:layer-openembedded-layer = 'Forced
maintainer for AUH'"
+],
"EXTRAPLAINCMDS" : [
"${SCRIPTSDIR}/run-auh ${HELPERBUILDDIR}
${WEBPUBLISH_DIR}/pub/auh/ ${HELPERBUILDDIR}/../meta-openembedded meta-oe"
]
@@ -1490,6 +1493,9 @@
"${BUILDDIR}/../meta-openembedded/meta-oe",
"${BUILDDIR}/../meta-openembedded/meta-python"
],
+"extravars" : [
+"RECIPE_MAINTAINER:layer-meta-python = 'Forced maintainer
for AUH'"
+],
"EXTRAPLAINCMDS" : [
"${SCRIPTSDIR}/run-auh ${HELPERBUILDDIR}
${WEBPUBLISH_DIR}/pub/auh/ ${HELPERBUILDDIR}/../meta-openembedded meta-python"
]
@@ -1500,6 +1506,9 @@
"${BUILDDIR}/../meta-openembedded/meta-oe",
"${BUILDDIR}/../meta-openembedded/meta-perl"
],
+"extravars" : [
+"RECIPE_MAINTAINER:layer-perl-layer = 'Forced maintainer
for AUH'"
+],
"EXTRAPLAINCMDS" : [
"${SCRIPTSDIR}/run-auh ${HELPERBUILDDIR}
${WEBPUBLISH_DIR}/pub/auh/ ${HELPERBUILDDIR}/../meta-openembedded meta-perl"
]
@@ -1510,6 +1519,9 @@
"${BUILDDIR}/../meta-openembedded/meta-oe",
"${BUILDDIR}/../meta-openembedded/meta-networking"
],
+"extravars" : [
+"RECIPE_MAINTAINER:layer-networking-layer = 'Forced
maintainer for AUH'"
+],
"EXTRAPLAINCMDS" : [
"${SCRIPTSDIR}/run-auh ${HELPERBUILDDIR}
${WEBPUBLISH_DIR}/pub/auh/ ${HELPERBUILDDIR}/../meta-openembedded
meta-networking"
]
@@ -1521,6 +1533,9 @@
"${BUILDDIR}/../meta-openembedded/meta-python",
"${BUILDDIR}/../meta-openembedded/meta-multimedia"
],
+"extravars" : [
+"RECIPE_MAINTAINER:layer-multimedia-layer = 'Forced
maintainer for AUH'"
+],
"EXTRAPLAINCMDS" : [
"${SCRIPTSDIR}/run-auh ${HELPERBUILDDIR}
${WEBPUBLISH_DIR}/pub/auh/ ${HELPERBUILDDIR}/../meta-openembedded
meta-multimedia"
]
@@ -1533,6 +1548,9 @@
"${BUILDDIR}/../meta-openembedded/meta-networking",
"${BUILDDIR}/../meta-openembedded/meta-gnome"
],
+"extravars" : [
+"RECIPE_MAINTAINER:layer-gnome-layer = 'Forced maintainer
for AUH'"
+],
"EXTRAPLAINCMDS" : [
"${SCRIPTSDIR}/run-auh ${HELPERBUILDDIR}
${WEBPUBLISH_DIR}/pub/auh/ ${HELPERBUILDDIR}/../meta-openembedded meta-gnome"
]
@@ -1547,6 +1565,9 @@
"${BUILDDIR}/../meta-openembedded/meta-gnome",
"${BUILDDIR}/../meta-openembedded/meta-xfce"
],
+"extravars" : [
+"RECIPE_MAINTAINER:layer-xfce-layer = 'Forced maintainer
for AUH'"
+],
"EXTRAPLAINCMDS" : [
"${SCRIPTSDIR}/run-auh ${HELPERBUILDDIR}
${WEBPUBLISH_DIR}/pub/auh/ ${HELPERBUILDDIR}/../meta-openembedded meta-xfce"
]
@@ -1559,6 +1580,9 @@
"${BUILDDIR}/../meta-openembedded/meta-networking",
"${BUILDDIR}/../meta-openembedded/meta-filesystems"
],
+"extravars" : [
+"RECIPE_MAINTAINER:layer-filesystems-layer = 'Forced
maintainer for AUH'"
+],
"EXTRAPLAINCMDS" : [
"${SCRIPTSDIR}/run-auh ${HELPERBUILDDIR}
${WEBPUBLISH_DIR}/
Re: [yocto] [auh][PATCH 0/6] Extend AUH to meta-openembedded
Le 01/11/2023 à 01:05, Yoann Congal a écrit : > v2->v3: > * Split single patch in a series. Previous version was: > [auh][PATCH v2] upgrade-helper.py: Add layer command line option I've just noticed that the "v3" tag is missing from the mail subject. Sorry about that :( > * Removed short options > * Refactor code before main patch "upgrade-helper.py: Add layer command line > option" > * Folded weeklyjob-oe into weeklyjob > > David Pierret (1): > upgrade-helper.py: Add layer command line option > > Yoann Congal (5): > upgrade-helper.py: simplify a condition > upgrade-helper.py: refactor _get_packages_to_upgrade to return a dict > upgrade-helper.py: extract the inner function of > get_packages_to_upgrade > upgrade-helper.py: Fix indentation > weeklyjob.sh: Add options to handle upgrading meta-oe > > upgrade-helper.py | 109 -- > weeklyjob.sh | 59 ++++++++- > 2 files changed, 134 insertions(+), 34 deletions(-) > -- Yoann Congal Smile ECS - Tech Expert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61548): https://lists.yoctoproject.org/g/yocto/message/61548 Mute This Topic: https://lists.yoctoproject.org/mt/102309890/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [auh][PATCH 6/6] weeklyjob.sh: Add options to handle upgrading meta-oe
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 94598a2..00f3575 100755 --- a/weeklyjob.sh +++ b/weeklyjob.sh @@ -13,6 +13,59 @@ poky_dir=~/poky build_dir=~/build-tmp-auh-upgrades sstate_dir=~/sstate-cache +ARGS=$(getopt -o '' --long 'layer-dir:,layer-names:,layer-machines:' -n 'weeklyjob.sh' -- "$@") +if [ $? -ne 0 ]; then +echo 'Cannot parse arguments...' >&2 +exit 1 +fi +eval set -- "$ARGS" +unset ARGS + +LAYERDIR="." +LAYERNAMES="" +LAYERMACHINES="" +DEFAULT=1 + +while true; do +case "$1" in +'--layer-dir') +LAYERDIR=$(realpath $2) + DEFAULT=0 +shift 2 +continue +;; +'--layer-names') +LAYERNAMES+=" $2" + DEFAULT=0 +shift 2 +continue +;; +'--layer-machines') +LAYERMACHINES+=" $2" + DEFAULT=0 +shift 2 +continue +;; +'--') +shift +break +;; +*) +echo "Unexpected value $1" >&2 +exit 1 +;; +esac +done + +# Default to poky/meta +if [ "$LAYERNAMES" == "" ]; then +LAYERNAMES="meta" +fi +# Default to qemux86-64 +if [ "$LAYERMACHINES" == "" ]; then +LAYERMACHINES="qemux86-64" +fi + pushd $poky_dir # Base the upgrades on poky master @@ -20,7 +73,11 @@ 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 [ "$DEFAULT" -ne 0 ]; then + $auh_dir/upgrade-helper.py -e all +else + $auh_dir/upgrade-helper.py -e all --layer-dir $LAYERDIR --layer-names "$LAYERNAMES" --layer-machines "$LAYERMACHINES" +fi # clean up to avoid the disk filling up rm -rf $build_dir/tmp/ -- 2.30.2 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61544): https://lists.yoctoproject.org/g/yocto/message/61544 Mute This Topic: https://lists.yoctoproject.org/mt/102309898/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [auh][PATCH 5/6] upgrade-helper.py: Add layer command line option
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 ++-
1 file changed, 44 insertions(+), 24 deletions(-)
diff --git a/upgrade-helper.py b/upgrade-helper.py
index 4933a4a..3be6d68 100755
--- a/upgrade-helper.py
+++ b/upgrade-helper.py
@@ -105,6 +105,12 @@ def parse_cmdline():
help="do not compile, just change the checksums,
remove PR, and commit")
parser.add_argument("-c", "--config-file", default=None,
help="Path to the configuration file. Default is
$BUILDDIR/upgrade-helper/upgrade-helper.conf")
+parser.add_argument("--layer-names", nargs='*', action="store", default='',
+help="layers to include in the upgrade research")
+parser.add_argument("--layer-dir", action="store", default='',
+help="the layers root directory")
+parser.add_argument("--layer-machines", nargs='*', action="store",
default='',
+help="machine to build for the layers")
return parser.parse_args()
def parse_config_file(config_file):
@@ -441,7 +447,8 @@ class Updater(object):
I(" ### The list of recipes to be upgraded #")
for pkg_to_upgrade in pkgs_to_upgrade:
-I(" %s, %s, %s, %s, %s" % (
+I(" %s, %s, %s, %s, %s, %s" % (
+pkg_to_upgrade["layer_name"],
pkg_to_upgrade["pn"],
pkg_to_upgrade["cur_ver"],
pkg_to_upgrade["next_ver"],
@@ -583,24 +590,26 @@ class UniverseUpdater(Updater):
def __init__(self, args):
Updater.__init__(self, args)
-if len(args.recipe) == 1 and args.recipe[0] == "all":
-self.recipes = []
-else:
-self.recipes = args.recipe
-
-# to filter recipes in upgrade
-if not self.recipes and self.opts['layer_mode'] == 'yes':
+if len(args.recipe) == 1 and args.recipe[0] == "all" and
self.opts['layer_mode'] != 'yes':
+self.recipes = [('', [])]
+elif self.opts['layer_mode'] == 'yes':
# when layer mode is enabled and no recipes are specified
# we need to figure out what recipes are provided by the
# layer to try upgrade
-self.recipes = self._get_recipes_by_layer()
-
+self.recipes = []
+for layer in self.opts['layer_name'].split(' '):
+recipes_for_layer = self._get_recipes_by_layer(layer)
+I("layer %s => Recipes %s", layer, recipes_for_layer)
+self.recipes.append((layer, recipes_for_layer))
+else:
+self.recipes = [('', args.recipe)]
+
if args.to_version:
if len(self.recipes) != 1:
E(" -t is only supported when upgrade one recipe\n")
exit(1)
-def _get_recipes_by_layer(self):
+def _get_recipes_by_layer(self, layer=''):
recipes = []
recipe_regex = re.compile('^(?P.*):$')
@@ -620,7 +629,7 @@ class UniverseUpdater(Updater):
if not 'skipped' in line:
s = layer_regex.search(line)
if s:
-if s.group('name').strip() == self.opts['layer_name']:
+if s.group('name').strip() == layer:
recipes.append(name)
return recipes
@@ -673,7 +682,7 @@ class UniverseUpdater(Updater):
def _get_packages_to_upgrade(self, packages=None):
# Prepare a single pkg dict data (or None is not upgradable) from
recipeutils.get_recipe_upgrade_status data.
-def _get_pkg_to_upgrade(self, pn, status, cur_ver, next_ver,
maintainer, revision, no_upgrade_reason):
+def _get_pkg_to_upgrade(self, layer_name, pn, status, cur_ver,
next_ver, maintainer, revision, no_upgrade_reason):
pkg_to_upgrade = None
if self.args.to_version:
@@ -683,6 +692,7 @@ class UniverseUpdater(Updater):
# Always do the upgrade if recipes are specified
if self.recipes and pn in self.recipes or
self._pkg_upgradable(pn, next_ver, maintainer):
pkg_to_upgrade = {
+"layer_name": layer_name,
[yocto] [auh][PATCH 4/6] upgrade-helper.py: Fix indentation
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): pkg_to_upgrade = None if self.args.to_version: - next_ver = self.args.to_version +next_ver = self.args.to_version if status == 'UPDATE' and not no_upgrade_reason: # Always do the upgrade if recipes are specified -- 2.30.2 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61542): https://lists.yoctoproject.org/g/yocto/message/61542 Mute This Topic: https://lists.yoctoproject.org/mt/102309896/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [auh][PATCH 3/6] upgrade-helper.py: extract the inner function of get_packages_to_upgrade
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
+++ b/upgrade-helper.py
@@ -671,12 +671,10 @@ class UniverseUpdater(Updater):
return True
def _get_packages_to_upgrade(self, packages=None):
-
-pkgs = oe.recipeutils.get_recipe_upgrade_status(self.recipes)
-
-pkgs_list = []
-for pkg in pkgs:
-pn, status, cur_ver, next_ver, maintainer, revision,
no_upgrade_reason = pkg
+
+# Prepare a single pkg dict data (or None is not upgradable) from
recipeutils.get_recipe_upgrade_status data.
+def _get_pkg_to_upgrade(self, pn, status, cur_ver, next_ver,
maintainer, revision, no_upgrade_reason):
+pkg_to_upgrade = None
if self.args.to_version:
next_ver = self.args.to_version
@@ -691,7 +689,6 @@ class UniverseUpdater(Updater):
"maintainer": maintainer,
"revision": revision
}
-pkgs_list.append(pkg_to_upgrade)
else:
if no_upgrade_reason:
I(" Skip package %s (status = %s, current version = %s," \
@@ -702,6 +699,18 @@ class UniverseUpdater(Updater):
" next version = %s)" %
(pn, status, cur_ver, next_ver))
+return pkg_to_upgrade
+
+pkgs = oe.recipeutils.get_recipe_upgrade_status(self.recipes)
+
+pkgs_list = []
+for pkg in pkgs:
+pn, status, cur_ver, next_ver, maintainer, revision,
no_upgrade_reason = pkg
+
+pkg_to_upgrade = _get_pkg_to_upgrade(self, pn, status, cur_ver,
next_ver, maintainer, revision, no_upgrade_reason)
+if pkg_to_upgrade:
+pkgs_list.append(pkg_to_upgrade)
+
return pkgs_list
def pkg_upgrade_handler(self, pkg_ctx):
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61541): https://lists.yoctoproject.org/g/yocto/message/61541
Mute This Topic: https://lists.yoctoproject.org/mt/102309893/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [auh][PATCH 2/6] upgrade-helper.py: refactor _get_packages_to_upgrade to return a dict
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 Updater(object):
pkgs_ctx = {}
I(" ### The list of recipes to be upgraded #")
-for p, ov, nv, m, r in pkgs_to_upgrade:
-I(" %s, %s, %s, %s, %s" % (p, ov, nv, m, r))
+for pkg_to_upgrade in pkgs_to_upgrade:
+I(" %s, %s, %s, %s, %s" % (
+pkg_to_upgrade["pn"],
+pkg_to_upgrade["cur_ver"],
+pkg_to_upgrade["next_ver"],
+pkg_to_upgrade["maintainer"],
+pkg_to_upgrade["revision"],
+))
+
+p = pkg_to_upgrade["pn"]
pkgs_ctx[p] = {}
pkgs_ctx[p]['PN'] = p
-pkgs_ctx[p]['PV'] = ov
-pkgs_ctx[p]['NPV'] = nv
-pkgs_ctx[p]['MAINTAINER'] = m
-pkgs_ctx[p]['NSRCREV'] = r
+pkgs_ctx[p]['PV'] = pkg_to_upgrade["cur_ver"]
+pkgs_ctx[p]['NPV'] = pkg_to_upgrade["next_ver"]
+pkgs_ctx[p]['MAINTAINER'] = pkg_to_upgrade["maintainer"]
+pkgs_ctx[p]['NSRCREV'] = pkg_to_upgrade["revision"]
pkgs_ctx[p]['base_dir'] = self.uh_recipes_all_dir
I(" ")
@@ -471,7 +479,8 @@ class Updater(object):
succeeded_pkgs_ctx = []
failed_pkgs_ctx = []
attempted_pkgs = 0
-for pn, _, _, _, _ in pkgs_to_upgrade:
+for pkg_to_upgrade in pkgs_to_upgrade:
+pn = pkg_to_upgrade["pn"]
pkg_ctx = pkgs_ctx[pn]
pkg_ctx['error'] = None
@@ -675,7 +684,14 @@ class UniverseUpdater(Updater):
if status == 'UPDATE' and not no_upgrade_reason:
# Always do the upgrade if recipes are specified
if self.recipes and pn in self.recipes or
self._pkg_upgradable(pn, next_ver, maintainer):
-pkgs_list.append((pn, cur_ver, next_ver, maintainer,
revision))
+pkg_to_upgrade = {
+"pn": pn,
+"cur_ver": cur_ver,
+"next_ver": next_ver,
+"maintainer": maintainer,
+"revision": revision
+}
+pkgs_list.append(pkg_to_upgrade)
else:
if no_upgrade_reason:
I(" Skip package %s (status = %s, current version = %s," \
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61540): https://lists.yoctoproject.org/g/yocto/message/61540
Mute This Topic: https://lists.yoctoproject.org/mt/102309892/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [auh][PATCH 1/6] upgrade-helper.py: simplify a condition
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 @@ class UniverseUpdater(Updater): if status == 'UPDATE' and not no_upgrade_reason: # Always do the upgrade if recipes are specified -if self.recipes and pn in self.recipes: -pkgs_list.append((pn, cur_ver, next_ver, maintainer, revision)) -elif self._pkg_upgradable(pn, next_ver, maintainer): +if self.recipes and pn in self.recipes or self._pkg_upgradable(pn, next_ver, maintainer): pkgs_list.append((pn, cur_ver, next_ver, maintainer, revision)) else: if no_upgrade_reason: -- 2.30.2 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61539): https://lists.yoctoproject.org/g/yocto/message/61539 Mute This Topic: https://lists.yoctoproject.org/mt/102309891/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [auh][PATCH 0/6] Extend AUH to meta-openembedded
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 (1): upgrade-helper.py: Add layer command line option Yoann Congal (5): upgrade-helper.py: simplify a condition upgrade-helper.py: refactor _get_packages_to_upgrade to return a dict upgrade-helper.py: extract the inner function of get_packages_to_upgrade upgrade-helper.py: Fix indentation weeklyjob.sh: Add options to handle upgrading meta-oe upgrade-helper.py | 109 -- weeklyjob.sh | 59 - 2 files changed, 134 insertions(+), 34 deletions(-) -- 2.30.2 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61538): https://lists.yoctoproject.org/g/yocto/message/61538 Mute This Topic: https://lists.yoctoproject.org/mt/102309890/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [PATCH yocto-autobuilder-helper 2/2] config.json: add meta-oe to the metrics target
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 meta-oe.
>
> Signed-off-by: Ross Burton
Thanks Ross!
Reviewed-by: Yoann Congal
> ---
> config.json | 29 -
> 1 file changed, 24 insertions(+), 5 deletions(-)
>
> diff --git a/config.json b/config.json
> index f3a4ee7..1b3c2b0 100644
> --- a/config.json
> +++ b/config.json
> @@ -1198,7 +1198,7 @@
> }
> },
> "metrics" : {
> -"NEEDREPOS" : ["poky"],
> +"NEEDREPOS" : ["poky", "meta-openembedded"],
> "extravars" : [
> "INHERIT += 'cve-check'",
> "BB_DISKMON_DIRS = ''",
> @@ -1210,18 +1210,37 @@
> "step1" : {
> "shortname" : "Fetching metrics repositories",
> "EXTRAPLAINCMDS" : [
> -"git clone
> ssh://g...@push.yoctoproject.org/yocto-metrics"
> +"git clone
> ssh://g...@push.yoctoproject.org/yocto-metrics && git clone
> ssh://g...@push.yoctoproject.org/yocto-metrics-meta-oe"
> ]
> },
> "step2" : {
> -"shortname" : "Generating patch metrics for Poky",
> +"shortname" : "Patch metrics for meta",
> "EXTRACMDS" : ["${SCRIPTSDIR}/run-patchmetrics --poky ../
> --metrics ../yocto-metrics --repo ../ --layer ../meta --branch
> ${HELPERBRANCHNAME} --results ${HELPERRESULTSDIR}/../../patchmetrics --push"]
> },
> "step3" : {
> -"shortname" : "Running CVE checks for Poky",
> +"shortname" : "CVE checks for meta",
> "EXTRACMDS" : ["${SCRIPTSDIR}/run-cvecheck --metrics
> ../yocto-metrics --branch ${HELPERBRANCHNAME} --results
> ${HELPERRESULTSDIR}/../../patchmetrics --push"]
> +},
> +"step4" : {
> +"shortname" : "Patch metrics for meta-oe",
> +"EXTRACMDS" : ["${SCRIPTSDIR}/run-patchmetrics --poky ../
> --metrics ../yocto-metrics-meta-oe --repo ../meta-openembedded --layer
> ../meta-openembedded --branch ${HELPERBRANCHNAME} --results
> ${HELPERRESULTSDIR}/../../patchmetrics-meta-oe --push"]
> +},
> +"step5" : {
> +"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"
> +],
> +"EXTRACMDS" : ["echo 'do_cve_check:layer-core = \"\"' >>
> conf/auto.conf ; ${SCRIPTSDIR}/run-cvecheck --metrics
> ../yocto-metrics-meta-oe --branch ${HELPERBRANCHNAME} --results
> ${HELPERRESULTSDIR}/../../patchmetrics-meta-oe --push"]
> }
> -
> },
> "meta-mingw" : {
> "NEEDREPOS" : ["poky", "meta-mingw"],
>
>
>
>
>
--
Yoann Congal
Smile ECS - Tech Expert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61536): https://lists.yoctoproject.org/g/yocto/message/61536
Mute This Topic: https://lists.yoctoproject.org/mt/102298519/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [PATCH yocto-autobuilder-helper 1/2] Rewrite metrics-gathering scripts
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 more specific
> about what they're passed. In particular, this means that for the patch
> review run we pass the _repository_ that we're scanning so we can do git
> operations on it, and the base of the _layers_ (either a layer, or a
> directory containing layers) so we know what to scan.
>
> Be more clever when identifying what commits we need to analyse for
> patch review: instead of iterating through a set randomly, we can keep
> the revision list sorted and the checkout operations are a lot faster.
>
> Remove the commit/file count metric addition as patchreview itself does
> that now.
>
> Add an explicit --push option so it's easy to test the scripts in
> isolation without pushing.
>
> Signed-off-by: Ross Burton
Thanks Ross!
Reviewed-by: Yoann Congal
> ---
> config.json| 14 +++--
> scripts/cve-generate-chartdata | 8 ++-
> scripts/patchmetrics-update| 109 +---
> scripts/run-cvecheck | 106 +++
> scripts/run-patchmetrics | 110 -
> 5 files changed, 251 insertions(+), 96 deletions(-)
>
> diff --git a/config.json b/config.json
> index 918cf08..f3a4ee7 100644
> --- a/config.json
> +++ b/config.json
> @@ -1208,12 +1208,18 @@
> "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"
> +]
> },
> "step2" : {
> -"shortname" : "Running CVE checks",
> -"EXTRACMDS" :
> ["../../yocto-autobuilder-helper/scripts/run-cvecheck ../ ../meta/
> ${HELPERRESULTSDIR}/../../patchmetrics . ${HELPERBRANCHNAME}"]
> +"shortname" : "Generating patch metrics for Poky",
> +"EXTRACMDS" : ["${SCRIPTSDIR}/run-patchmetrics --poky ../
> --metrics ../yocto-metrics --repo ../ --layer ../meta --branch
> ${HELPERBRANCHNAME} --results ${HELPERRESULTSDIR}/../../patchmetrics --push"]
> +},
> +"step3" : {
> +"shortname" : "Running CVE checks for Poky",
> +"EXTRACMDS" : ["${SCRIPTSDIR}/run-cvecheck --metrics
> ../yocto-metrics --branch ${HELPERBRANCHNAME} --results
> ${HELPERRESULTSDIR}/../../patchmetrics --push"]
> }
>
> },
> diff --git a/scripts/cve-generate-chartdata b/scripts/cve-generate-chartdata
> index 95d12ff..dbbbe82 100755
> --- a/scripts/cve-generate-chartdata
> +++ b/scripts/cve-generate-chartdata
> @@ -11,8 +11,12 @@ 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()
>
> -with open(args.json) as f:
> -counts = json.load(f)
> +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 = {}
>
> diff --git a/scripts/patchmetrics-update b/scripts/patchmetrics-update
> index 65d351e..2fa7e4a 100755
> --- a/scripts/patchmetrics-update
> +++ b/scripts/patchmetrics-update
> @@ -1,65 +1,76 @@
> #!/usr/bin/env python3
> -import json, os.path, collections
> -import sys
> +
> +import json
> +import pathlib
> import argparse
> import subprocess
> import tempfile
> +import sys
> +
> +# Given a git repository and a base to search for layers (either a layer
> +# directly, or a directory containing layers), run the patchscript and update
> +# the specified JSON file.
>
> args = argparse.ArgumentParser(description="Update Patch Metrics")
> -args.ad
Re: [yocto] Http access token fetching with gitsm fetcher
Hi,
Le ven. 20 oct. 2023 à 15:32, Adrian Freihofer
a écrit :
> Did you already consider to write the credentials in a .netrc file?
>
> Regards
> Adrian
>
> schrieb am Fr., 20. Okt. 2023, 13:55:
>>
>> Greetings!
>> I try to use gitsm fetcher to fetch bitbucket repository with read-only
>> https access token. SRC_URI looks like this
>>
>> SRC_URI =
>> "gitsm://**.git;protocol=https;branch=${BRANCH};user=azoykin:${TOKEN}"
>>
>> This recipe fetches parent repository, but is unable to fetch submodule,
>> writing fatal: could not read Username for 'https://tps-git.topcon.com': No
>> such device or address in log.do_fetch
>> It happens because url is passed to fetcher function already with user
>> string. I suggest a patch to fix this issue
I'm sorry but this is a known WONTFIX bug :
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13550
See : https://git.openembedded.org/bitbake/tree/lib/bb/fetch2/gitsm.py#n127
The only supported way to do this (that I know of) is to use .netrc as
Adrian suggested.
Regards,
--
Yoann Congal
Smile ECS - Tech expert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61434): https://lists.yoctoproject.org/g/yocto/message/61434
Mute This Topic: https://lists.yoctoproject.org/mt/102079282/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] config.json: add a workaround for the "autobuilderlog.json" error
Le jeu. 19 oct. 2023 à 01:22, Jose Quaresma a écrit :
> Hi Yoann,
Hi!
> I have found the same for BBLAYERS that was fixed [1] expanding any relative
> path that could exist.
> Maybe it would be better to also expand BB_LOGCONFIG when the newbuilddir
> argument is present.
>
> [1]
> https://git.yoctoproject.org/poky/commit/id=f5f465ff5777eb99941db3dda84e65d4699d97f7
OOOooohh That is interesting, Thanks!
For reference, I've had to fix the URL:
https://git.yoctoproject.org/poky/commit/?id=f5f465ff5777eb99941db3dda84e65d4699d97f7
And thank you for updating the bug :)
> Jose
>
> Yoann Congal escreveu no dia quarta, 18/10/2023 à(s)
> 23:28:
>>
>> For the reproducible-meta-oe builder, workaround the bug #15241 [1], by
>> passing BB_LOGCONFIG through "readlink -f" to avoid relative reference
>> to the main build dir.
>>
>> Also, switch from BBPATH to BUILDDIR to reference the main build dir.
>>
>> [1]: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15241
>>
>> Signed-off-by: Yoann Congal
>> ---
>> config.json | 20 ++--
>> 1 file changed, 10 insertions(+), 10 deletions(-)
>>
>> diff --git a/config.json b/config.json
>> index c01a453..84da67b 100644
>> --- a/config.json
>> +++ b/config.json
>> @@ -303,7 +303,7 @@
>> ],
>> "step1" : {
>> "shortname" : "Repro meta-oe/meta-filesystems",
>> -"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
>> OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-filesystems/
>> DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-filesystems -r
>> reproducible"],
>> +"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
>> OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-filesystems/
>> DISPLAY=:1 BB_LOGCONFIG=$(readlink -f $BB_LOGCONFIG) oe-selftest
>> --newbuilddir $BUILDDIR/build-st-meta-filesystems -r reproducible"],
>> "ADDLAYER" : [
>> "${BUILDDIR}/../meta-openembedded/meta-oe",
>> "${BUILDDIR}/../meta-openembedded/meta-python",
>> @@ -323,7 +323,7 @@
>> },
>> "step2" : {
>> "shortname" : "Repro meta-oe/meta-gnome",
>> -"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
>> OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-gnome/
>> DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-gnome -r
>> reproducible"],
>> +"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
>> OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-gnome/
>> DISPLAY=:1 BB_LOGCONFIG=$(readlink -f $BB_LOGCONFIG) oe-selftest
>> --newbuilddir $BUILDDIR/build-st-meta-gnome -r reproducible"],
>> "ADDLAYER" : [
>> "${BUILDDIR}/../meta-openembedded/meta-oe",
>> "${BUILDDIR}/../meta-openembedded/meta-python",
>> @@ -343,14 +343,14 @@
>> },
>> "step3" : {
>> "shortname" : "Repro meta-oe/meta-initramfs",
>> -"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
>> OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-initramfs/
>> DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-initramfs -r
>> reproducible"],
>> +"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
>> OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-initramfs/
>> DISPLAY=:1 BB_LOGCONFIG=$(readlink -f $BB_LOGCONFIG) oe-selftest
>> --newbuilddir $BUILDDIR/build-st-meta-initramfs -r reproducible"],
>> "ADDLAYER" : [
>> "${BUILDDIR}/../meta-openembedded/meta-initramfs"
>> ]
>> },
>> "step4" : {
>> "shortname" : "Repro meta-oe/meta-multimedia",
>> -"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
>> OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-multimedia/
>> DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-multimedia -r
>> reproducible"],
>> +"EXTRACMDS&quo
[yocto] [yocto-autobuilder-helper][PATCH] config.json: add a workaround for the "autobuilderlog.json" error
For the reproducible-meta-oe builder, workaround the bug #15241 [1], by
passing BB_LOGCONFIG through "readlink -f" to avoid relative reference
to the main build dir.
Also, switch from BBPATH to BUILDDIR to reference the main build dir.
[1]: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15241
Signed-off-by: Yoann Congal
---
config.json | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/config.json b/config.json
index c01a453..84da67b 100644
--- a/config.json
+++ b/config.json
@@ -303,7 +303,7 @@
],
"step1" : {
"shortname" : "Repro meta-oe/meta-filesystems",
-"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-filesystems/
DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-filesystems -r
reproducible"],
+"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-filesystems/
DISPLAY=:1 BB_LOGCONFIG=$(readlink -f $BB_LOGCONFIG) oe-selftest --newbuilddir
$BUILDDIR/build-st-meta-filesystems -r reproducible"],
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-oe",
"${BUILDDIR}/../meta-openembedded/meta-python",
@@ -323,7 +323,7 @@
},
"step2" : {
"shortname" : "Repro meta-oe/meta-gnome",
-"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-gnome/
DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-gnome -r
reproducible"],
+"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-gnome/
DISPLAY=:1 BB_LOGCONFIG=$(readlink -f $BB_LOGCONFIG) oe-selftest --newbuilddir
$BUILDDIR/build-st-meta-gnome -r reproducible"],
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-oe",
"${BUILDDIR}/../meta-openembedded/meta-python",
@@ -343,14 +343,14 @@
},
"step3" : {
"shortname" : "Repro meta-oe/meta-initramfs",
-"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-initramfs/
DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-initramfs -r
reproducible"],
+"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-initramfs/
DISPLAY=:1 BB_LOGCONFIG=$(readlink -f $BB_LOGCONFIG) oe-selftest --newbuilddir
$BUILDDIR/build-st-meta-initramfs -r reproducible"],
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-initramfs"
]
},
"step4" : {
"shortname" : "Repro meta-oe/meta-multimedia",
-"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-multimedia/
DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-multimedia -r
reproducible"],
+"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-multimedia/
DISPLAY=:1 BB_LOGCONFIG=$(readlink -f $BB_LOGCONFIG) oe-selftest --newbuilddir
$BUILDDIR/build-st-meta-multimedia -r reproducible"],
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-oe",
"${BUILDDIR}/../meta-openembedded/meta-python",
@@ -367,7 +367,7 @@
},
"step5" : {
"shortname" : "Repro meta-oe/meta-networking",
-"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-networking/
DISPLAY=:1 oe-selftest --newbuilddir $BBPATH/build-st-meta-networking -r
reproducible"],
+"EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc;
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail-openembedded/meta-networking/
DISPLAY=:1 BB_LOGCONFIG=$(readlink -f $BB_LOGCONFIG) oe-selftest --newbuilddir
$BUILDDIR/build-st-meta-networking -r reproducible"],
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-oe",
"${BUILDDIR}/../meta-openembedded
Re: [yocto] [yocto-autobuilder-helper][PATCH] config.json : reproducible-meta-oe build fixes
Le mar. 10 oct. 2023 à 15:14, Richard Purdie a écrit : > That isn't actually valid json but I fixed it and will schedule a test > build. Huh, sorry about that :( > I also tweaked the shortnames to make it clear it is meta-OE as > "OE" isn't very specific. Thanks! -- Yoann Congal Smile ECS - Tech expert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61303): https://lists.yoctoproject.org/g/yocto/message/61303 Mute This Topic: https://lists.yoctoproject.org/mt/101871837/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] devtool build error
Le mer. 4 oct. 2023 à 16:17, SIMON BABY a écrit :
> Thanks Yoann .
> Do we have any workaround ?
>
> Is there any other way to change the kernel source other than devtool?
>
I would either :
1) Spend the time to fix the bug
2) Do what I did in the good-ol' days before I used devtool :
* patch in tmp/work-shared/kernel-source directory (path approximated from
memory)
* convince bitbake to build without cleaning your patch (something with
"bitbake -C compile ..." maybe?)
* once tested, git format-patch to extract patches that can be used in
your recipe
It's hard to tell for sure which one will be shorter for you.
1) is definitely better for the community so I encourage you to try it ;)
Regards,
> Regards
> Simon
>
> Sent from my iPhone
>
> On Oct 3, 2023, at 11:27 PM, Yoann CONGAL wrote:
>
>
> Hello,
>
> Le mer. 4 oct. 2023 à 00:31, SIMON BABY a écrit :
>
>> Hello Team,
>>
>>
>> Can someone help to fix the error I see when using devtool build or
>> devtool update-recipe.
>>
>>
>> *Exception: bb.fetch2.FetchError: Fetcher failure: Recipe uses a floating
>> tag/branch '5.15/linux' for repo 'github.com/intel/linux-intel-lts.git
>> <http://github.com/intel/linux-intel-lts.git>' without a fixed SRCREV yet
>> doesn't call bb.fetch2.get_srcrev() (use SRCPV in PV for OE).*
>>
> This looks like a recently opened bug (and a thread) :
> Bug 14918 - Devtool fails if SRCREV is set to ${AUTOREV}
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14918
>
> Thread :
> https://lists.openembedded.org/g/bitbake-devel/message/13976?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Arecentpostdate%2Fsticky%2C%2CAUTOREV%2C20%2C2%2C0%2C93674384
>
> Sorry, there is no fix yet but maybe you can contribute
> information/context for the bug?
>
> Regards,
>
> --
> Yoann Congal
> Smile ECS
>
>>
--
Yoann Congal
Smile ECS - Tech expert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61239): https://lists.yoctoproject.org/g/yocto/message/61239
Mute This Topic: https://lists.yoctoproject.org/mt/101744963/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] devtool build error
Hello,
Le mer. 4 oct. 2023 à 00:31, SIMON BABY a écrit :
> Hello Team,
>
>
> Can someone help to fix the error I see when using devtool build or
> devtool update-recipe.
>
>
> *Exception: bb.fetch2.FetchError: Fetcher failure: Recipe uses a floating
> tag/branch '5.15/linux' for repo 'github.com/intel/linux-intel-lts.git
> <http://github.com/intel/linux-intel-lts.git>' without a fixed SRCREV yet
> doesn't call bb.fetch2.get_srcrev() (use SRCPV in PV for OE).*
>
This looks like a recently opened bug (and a thread) :
Bug 14918 - Devtool fails if SRCREV is set to ${AUTOREV}
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14918
Thread :
https://lists.openembedded.org/g/bitbake-devel/message/13976?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Arecentpostdate%2Fsticky%2C%2CAUTOREV%2C20%2C2%2C0%2C93674384
Sorry, there is no fix yet but maybe you can contribute information/context
for the bug?
Regards,
--
Yoann Congal
Smile ECS
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61227): https://lists.yoctoproject.org/g/yocto/message/61227
Mute This Topic: https://lists.yoctoproject.org/mt/101744963/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Poky/Mickledore bitbake menuconfig does not work
Le mer. 20 sept. 2023 à 19:59, Yoann CONGAL a
écrit :
> Le mar. 19 sept. 2023 à 18:57, Sebert, Holger.ext <
> holger.sebert@karlstorz.com> a écrit :
>
>> Hi Yoann, hi Zoran,
>>
>
> Hi,
>
>
>> The bug is not present on the Poky master branch.
>>
>> Until the project is rebased onto the next release, I will simply disable
>> CCache whenever I need to do a kernel menuconfig.
>>
>
> You peaked my curiosity and I've tracked down the fix on master : Your
> problem is fixed by
>
> https://git.yoctoproject.org/poky/commit/?id=d4664d2b7974354e73d891762ebb2c8a12d62438
>
> I've requested a backport on mickledore :
> https://lists.openembedded.org/g/openembedded-core/message/187934
>
Fix has now been merged in mickledore :
https://git.yoctoproject.org/poky/commit/?h=mickledore&id=cd0c6173a375e5c7b617985ca2efcf167c92c827
You would just have to update your poky mickledore branch to fix your
problem :)
Enjoy!
Regards,
>
>
>> Thanks!
>>
>> -Holger
>>
>>
>> Von: Yoann CONGAL
>> Gesendet: Donnerstag, 14. September 2023 23:52
>> An: Sebert, Holger.ext
>> Cc: Zoran Stojsavljevic; Yocto-mailing-list
>> Betreff: [Ext] Re: [yocto] Poky/Mickledore bitbake menuconfig does not
>> work
>>
>> Hi,
>>
>> Le jeu. 14 sept. 2023 à 14:10, Sebert, Holger.ext <
>> holger.sebert@karlstorz.com<mailto:holger.sebert@karlstorz.com>>
>> a écrit :
>> Hi Zoran,
>>
>> I was able to reproduce the behavior described in my original post by
>> enabling CCache. Here are the precise steps to reproduce:
>>
>> 1. Checkout Poky/Mickledore
>> 2. Add the following to `build/conf/local.conf`:
>> INHERIT += "ccache"
>> 3. Run `bitbake -c menuconfig virtual/kernel`
>>
>> The reason for the failure is that due to CCache the compiler is no
>> longer `gcc` but `ccache gcc`, i.e. we have the following variables in the
>> environment:
>>
>> CC="ccache x86_64-poky-linux-gcc"
>> HOSTCC="ccache gcc"
>> ...
>> etc.
>>
>> This is when the wrong quoting in the invocation of `menuconfig` leads to
>> errors.
>>
>> Could you please verify/check?
>>
>>
>> I have reproduced this. It really looks like a bug!
>>
>> [...]
>> On Mon, Aug 21, 2023 at 3:48 PM Sebert, Holger.ext
>> mailto:holger.sebert@karlstorz.com>>
>> wrote:
>> >
>> > Hi,
>> >
>> > I am using a Yocto-Poky-Mickledore (version 4.2.1) based system.
>> >
>> > For configuring the kernel, I would like to use the command
>> >
>> > bitbake -c menuconfig virtual/kernel
>> >
>> > If I do that, Bitbake opens an xterm window and runs the build steps
>> > for Kconfig. However, after the compiler has finised, the xterm window
>> > immediately closes and Bitbake exists as if nothing happened, i.e. it
>> > does not show any error message or similar.
>> >
>> > I investigated the problem and found out that, internally, Bitbake
>> > calls the following command for starting Kconfig:
>> >
>> > make menuconfig CC="ccache x86_64-system-linux-gcc ..." \
>> > CFLAGS="..." HOSTCC="ccache gcc" HOSTCCFLAGS="..."
>> >
>> > The quotes, however, seem to get lost when starting the actual command
>> > in the terminal. This leads to a command line like follows:
>> >
>> > make menuconfig CC=ccache x86_64-system-linux-gcc ... \
>> > CFLAGS=... HOSTCC="ccache gcc" HOSTCCFLAGS="...
>> >
>> > which is clearly wrong.
>> >
>> > The following patch fixes the problem in
>> meta/classes-recipe/cml1.bbclass:
>> >
>> > diff --git a/meta/classes-recipe/cml1.bbclass
>> b/meta/classes-recipe/cml1.bbclass
>> > index a09a042c3f..d6001d6fd0 100644
>> > --- a/meta/classes-recipe/cml1.bbclass
>> > +++ b/meta/classes-recipe/cml1.bbclass
>> > @@ -53,7 +53,8 @@ python do_menuconfig() {
>> > # ensure that environment variables are overwritten with this
>> tasks 'd' values
>> > d.appendVar("OE_TERMINAL_EXPORTS", " PKG_CONFIG_DIR
>> PKG_CONFIG_PATH PKG_CONFIG_LIBDIR PKG_CONFIG_SYSROOT_DIR")
>> >
>> > -oe_terminal("sh -c \"make %s; if [ \\$? -ne 0 ]; then echo
>> 'Command failed.'; printf 'Press any key to continue... &
Re: [yocto] bbappend not working for recipe with git in name
Hello, Le lun. 25 sept. 2023 à 06:55, John Klug a écrit : > bitbake-layers show-appends reports: > > Summary: There were 3 WARNING messages. > === Matched appended recipes === > kernel-module-nxp89xx_git.bb: > > > /home/jklug/mlinux-kirk2/layers/meta-multitech-nxp/recipes-kernel/kernel-module-nxp89xx/kernel-module-nxp89xx_%.bbappend > WARNING: kernel-module-nxp89xx.bb: missing append for preferred version > I may be wrong but it looks like you have 2 kernel-module-nxp89xx recipes : * one called kernel-module-nxp89xx_git.bb which is bbappended in you layer * another one called kernel-module-nxp89xx.bb (no PV in filename), which is preferred over the _git one. I guess you an either : * Use kernel-module-nxp89xx.bb : rename your bbappend to kernel-module-nxp89xx.bbappend * keep kernel-module-nxp89xx_git.bb : remove or inhibit kernel-module-nxp89xx.bb I have tried _git instead of _%. > > I have also tried 1.0, since bitbake -e reports: > > PV="1.0" > > What should I be doing? Nothing in the bbappend does anything, unless I > make it invalid, then I get an error. > > SRCREV is set in this recipe as a hash. > > > John Klug > > > Regards, -- Yoann Congal Smile ECS - Tech expert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61104): https://lists.yoctoproject.org/g/yocto/message/61104 Mute This Topic: https://lists.yoctoproject.org/mt/101569034/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Poky/Mickledore bitbake menuconfig does not work
Le mar. 19 sept. 2023 à 18:57, Sebert, Holger.ext <
holger.sebert@karlstorz.com> a écrit :
> Hi Yoann, hi Zoran,
>
Hi,
> The bug is not present on the Poky master branch.
>
> Until the project is rebased onto the next release, I will simply disable
> CCache whenever I need to do a kernel menuconfig.
>
You peaked my curiosity and I've tracked down the fix on master : Your
problem is fixed by
https://git.yoctoproject.org/poky/commit/?id=d4664d2b7974354e73d891762ebb2c8a12d62438
I've requested a backport on mickledore :
https://lists.openembedded.org/g/openembedded-core/message/187934
Regards,
> Thanks!
>
> -Holger
>
> ____
> Von: Yoann CONGAL
> Gesendet: Donnerstag, 14. September 2023 23:52
> An: Sebert, Holger.ext
> Cc: Zoran Stojsavljevic; Yocto-mailing-list
> Betreff: [Ext] Re: [yocto] Poky/Mickledore bitbake menuconfig does not work
>
> Hi,
>
> Le jeu. 14 sept. 2023 à 14:10, Sebert, Holger.ext <
> holger.sebert@karlstorz.com<mailto:holger.sebert@karlstorz.com>>
> a écrit :
> Hi Zoran,
>
> I was able to reproduce the behavior described in my original post by
> enabling CCache. Here are the precise steps to reproduce:
>
> 1. Checkout Poky/Mickledore
> 2. Add the following to `build/conf/local.conf`:
> INHERIT += "ccache"
> 3. Run `bitbake -c menuconfig virtual/kernel`
>
> The reason for the failure is that due to CCache the compiler is no longer
> `gcc` but `ccache gcc`, i.e. we have the following variables in the
> environment:
>
> CC="ccache x86_64-poky-linux-gcc"
> HOSTCC="ccache gcc"
> ...
> etc.
>
> This is when the wrong quoting in the invocation of `menuconfig` leads to
> errors.
>
> Could you please verify/check?
>
>
> I have reproduced this. It really looks like a bug!
>
> [...]
> On Mon, Aug 21, 2023 at 3:48 PM Sebert, Holger.ext
> mailto:holger.sebert@karlstorz.com>>
> wrote:
> >
> > Hi,
> >
> > I am using a Yocto-Poky-Mickledore (version 4.2.1) based system.
> >
> > For configuring the kernel, I would like to use the command
> >
> > bitbake -c menuconfig virtual/kernel
> >
> > If I do that, Bitbake opens an xterm window and runs the build steps
> > for Kconfig. However, after the compiler has finised, the xterm window
> > immediately closes and Bitbake exists as if nothing happened, i.e. it
> > does not show any error message or similar.
> >
> > I investigated the problem and found out that, internally, Bitbake
> > calls the following command for starting Kconfig:
> >
> > make menuconfig CC="ccache x86_64-system-linux-gcc ..." \
> > CFLAGS="..." HOSTCC="ccache gcc" HOSTCCFLAGS="..."
> >
> > The quotes, however, seem to get lost when starting the actual command
> > in the terminal. This leads to a command line like follows:
> >
> > make menuconfig CC=ccache x86_64-system-linux-gcc ... \
> > CFLAGS=... HOSTCC="ccache gcc" HOSTCCFLAGS="...
> >
> > which is clearly wrong.
> >
> > The following patch fixes the problem in
> meta/classes-recipe/cml1.bbclass:
> >
> > diff --git a/meta/classes-recipe/cml1.bbclass
> b/meta/classes-recipe/cml1.bbclass
> > index a09a042c3f..d6001d6fd0 100644
> > --- a/meta/classes-recipe/cml1.bbclass
> > +++ b/meta/classes-recipe/cml1.bbclass
> > @@ -53,7 +53,8 @@ python do_menuconfig() {
> > # ensure that environment variables are overwritten with this tasks
> 'd' values
> > d.appendVar("OE_TERMINAL_EXPORTS", " PKG_CONFIG_DIR PKG_CONFIG_PATH
> PKG_CONFIG_LIBDIR PKG_CONFIG_SYSROOT_DIR")
> >
> > -oe_terminal("sh -c \"make %s; if [ \\$? -ne 0 ]; then echo 'Command
> failed.'; printf 'Press any key to continue... '; read r; fi\"" %
> d.getVar('KCONFIG_CONFIG_COMMAND'),
> > +make_cmd = "make %s" %
> d.getVar('KCONFIG_CONFIG_COMMAND').replace('"', '\\"')
> > +oe_terminal("sh -c \"%s; if [ \\$? -ne 0 ]; then echo 'Command
> failed.'; printf 'Press any key to continue... '; read r; fi\"" % make_cmd,
> > d.getVar('PN') + ' Configuration', d)
>
> This patch looks interesting!
> I would use shlex.join() to safely construct the command :
> https://docs.python.org/3/library/shlex.html#shlex.join<
> https://urldefense.com/v3/__https://docs.python.org/3/library/shlex.html*shlex.join__;Iw!
Re: [yocto] Poky/Mickledore bitbake menuconfig does not work
Hi,
Le jeu. 14 sept. 2023 à 14:10, Sebert, Holger.ext <
holger.sebert@karlstorz.com> a écrit :
> Hi Zoran,
>
> I was able to reproduce the behavior described in my original post by
> enabling CCache. Here are the precise steps to reproduce:
>
> 1. Checkout Poky/Mickledore
> 2. Add the following to `build/conf/local.conf`:
> INHERIT += "ccache"
> 3. Run `bitbake -c menuconfig virtual/kernel`
>
> The reason for the failure is that due to CCache the compiler is no longer
> `gcc` but `ccache gcc`, i.e. we have the following variables in the
> environment:
>
> CC="ccache x86_64-poky-linux-gcc"
> HOSTCC="ccache gcc"
> ...
> etc.
>
> This is when the wrong quoting in the invocation of `menuconfig` leads to
> errors.
>
> Could you please verify/check?
>
I have reproduced this. It really looks like a bug!
> [...]
> On Mon, Aug 21, 2023 at 3:48 PM Sebert, Holger.ext
> wrote:
> >
> > Hi,
> >
> > I am using a Yocto-Poky-Mickledore (version 4.2.1) based system.
> >
> > For configuring the kernel, I would like to use the command
> >
> > bitbake -c menuconfig virtual/kernel
> >
> > If I do that, Bitbake opens an xterm window and runs the build steps
> > for Kconfig. However, after the compiler has finised, the xterm window
> > immediately closes and Bitbake exists as if nothing happened, i.e. it
> > does not show any error message or similar.
> >
> > I investigated the problem and found out that, internally, Bitbake
> > calls the following command for starting Kconfig:
> >
> > make menuconfig CC="ccache x86_64-system-linux-gcc ..." \
> > CFLAGS="..." HOSTCC="ccache gcc" HOSTCCFLAGS="..."
> >
> > The quotes, however, seem to get lost when starting the actual command
> > in the terminal. This leads to a command line like follows:
> >
> > make menuconfig CC=ccache x86_64-system-linux-gcc ... \
> > CFLAGS=... HOSTCC="ccache gcc" HOSTCCFLAGS="...
> >
> > which is clearly wrong.
> >
> > The following patch fixes the problem in
> meta/classes-recipe/cml1.bbclass:
> >
> > diff --git a/meta/classes-recipe/cml1.bbclass
> b/meta/classes-recipe/cml1.bbclass
> > index a09a042c3f..d6001d6fd0 100644
> > --- a/meta/classes-recipe/cml1.bbclass
> > +++ b/meta/classes-recipe/cml1.bbclass
> > @@ -53,7 +53,8 @@ python do_menuconfig() {
> > # ensure that environment variables are overwritten with this tasks
> 'd' values
> > d.appendVar("OE_TERMINAL_EXPORTS", " PKG_CONFIG_DIR PKG_CONFIG_PATH
> PKG_CONFIG_LIBDIR PKG_CONFIG_SYSROOT_DIR")
> >
> > -oe_terminal("sh -c \"make %s; if [ \\$? -ne 0 ]; then echo 'Command
> failed.'; printf 'Press any key to continue... '; read r; fi\"" %
> d.getVar('KCONFIG_CONFIG_COMMAND'),
> > +make_cmd = "make %s" %
> d.getVar('KCONFIG_CONFIG_COMMAND').replace('"', '\\"')
> > +oe_terminal("sh -c \"%s; if [ \\$? -ne 0 ]; then echo 'Command
> failed.'; printf 'Press any key to continue... '; read r; fi\"" % make_cmd,
> > d.getVar('PN') + ' Configuration', d)
>
This patch looks interesting!
I would use shlex.join() to safely construct the command :
https://docs.python.org/3/library/shlex.html#shlex.join
> > What do you think? Is my observed behavior a configuration error of my
> > setup or does the patch above indeed make sense?
>
The patch makes sense to me.
I guess your next steps are :
* If you want to contribute your patch : reproduce the bug and rebase your
patch on master and send it to the mailing list
* Or, create a bug in https://bugzilla.yoctoproject.org/
Best Regards,
--
Yoann Congal
Smile ECS - Tech expert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61012): https://lists.yoctoproject.org/g/yocto/message/61012
Mute This Topic: https://lists.yoctoproject.org/mt/100872991/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Memory requirements for building images with different architectures
Hi! Le ven. 8 sept. 2023 à 08:01, MOHAMMED HASSAN a écrit : > Right, you're not the only one! > See > > https://docs.yoctoproject.org/ref-manual/system-requirements.html#minimum-free-disk-space > and https://docs.yoctoproject.org/dev/dev-manual/disk-space.html > > I can use rm_work and remove all the build related files, however every > subsequent build would take a lot more time to build. I want my builds to > be as fast as possible. Do you have any suggestions to for faster builds > while consuming less memory space. > rm_work does not impact build time. Every important piece of built software is kept in the "sstate cache" and this cache is not removed by rm_work. I usually have rm_work activated globally and reasonable build time : most things are not re-built but taken from the sstate cache. Regards, -- Yoann Congal Smile ECS - Tech expert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60944): https://lists.yoctoproject.org/g/yocto/message/60944 Mute This Topic: https://lists.yoctoproject.org/mt/101231469/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] https://wiki.yoctoproject.org/ certificate expired
Hi, It seems like the https://wiki.yoctoproject.org/ certificate has expired :( "notAfter=Jun 13 03:28:00 2023 GMT" Regards, -- Yoann Congal Smile ECS - Tech expert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60269): https://lists.yoctoproject.org/g/yocto/message/60269 Mute This Topic: https://lists.yoctoproject.org/mt/99500641/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [PATCH yocto-autobuilder-helper] auh: publish output on https://autobuilder.yocto.io/pub/auh/
On 4/28/23 09:01, Alexander Kanavin wrote:
> AUH itself already has an option to include the link into
> its email reports; the option just needs to be enabled.
>
> [YOCTO #15103]
>
> Signed-off-by: Alexander Kanavin
Looks good to me!
Reviewed-by: Yoann Congal
Thanks!
> ---
> config.json| 2 +-
> scripts/auh-config/upgrade-helper.conf | 2 +-
> scripts/run-auh| 6 +-
> 3 files changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/config.json b/config.json
> index 9da4d85..a2ba46e 100644
> --- a/config.json
> +++ b/config.json
> @@ -1186,7 +1186,7 @@
> },
> "auh" : {
> "EXTRAPLAINCMDS" : [
> -"${SCRIPTSDIR}/setup-auh ${HELPERBUILDDIR};
> ${SCRIPTSDIR}/run-auh ${HELPERBUILDDIR}"
> +"${SCRIPTSDIR}/setup-auh ${HELPERBUILDDIR};
> ${SCRIPTSDIR}/run-auh ${HELPERBUILDDIR} ${WEBPUBLISH_DIR}/pub/auh/"
> ]
> },
> "a-quick" : {
> diff --git a/scripts/auh-config/upgrade-helper.conf
> b/scripts/auh-config/upgrade-helper.conf
> index 3a0aa6c..e0fed11 100644
> --- a/scripts/auh-config/upgrade-helper.conf
> +++ b/scripts/auh-config/upgrade-helper.conf
> @@ -29,7 +29,7 @@ buildhistory=yes
> #testimage_name=core-image-minimal
>
> #workdir=/home/auh/work/
> -#publish_work_url=https://logs.yoctoproject.org/auh/
> +publish_work_url=https://autobuilder.yocto.io/pub/auh
>
> commit_revert_policy=all
>
> diff --git a/scripts/run-auh b/scripts/run-auh
> index 527ff96..0419dd1 100755
> --- a/scripts/run-auh
> +++ b/scripts/run-auh
> @@ -7,7 +7,7 @@
> # Called with $1 - the directory where the setup was created
>
> if [ -z $1 ]; then
> - echo "Use: $0 auh_setup_dir"
> + echo "Use: $0 auh_setup_dir [publish_dir]"
>exit 1
> fi
>
> @@ -27,4 +27,8 @@ 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
>
>
>
>
>
--
Yoann Congal
Smile ECS - Tech Expert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59869): https://lists.yoctoproject.org/g/yocto/message/59869
Mute This Topic: https://lists.yoctoproject.org/mt/98553558/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Skipping recipes depending on MACHINE
Hi, Le jeu. 9 mars 2023 à 08:11, Mauro Ziliani a écrit : > Good morning. > > I made a project for IMX6 platform. > > Now I ported it to x86. > > I made a layer for IMX6, but some recipe.bb cannot be compiled fo x86, > or some recipe.bbappend has not a mother, so the bibtake stops. > > I to adapt the layer to x86 architecture I put some BBMASK += "" in my > conf/bblayers.conf for x86 build environment and I excluded every > unneeeded file for x86. > > Can I put the BBMASK in some conf file inside the layer to do the same, > dependig on MACHINE, using OVERRIDE? > > The first idea was put BBMASK in layer.conf, like this > > BBMASK_intel-corei7-64 = " \ > \ > " > > I'd like to became my layer "auto-configurable" about MACHINE value > > > Any idea? > Have you looked into COMPATIBLE_MACHINE? => https://docs.yoctoproject.org/ref-manual/variables.html#term-COMPATIBLE_MACHINE Looks like a perfect match for what you are trying to do! Regards, -- Yoann Congal -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59372): https://lists.yoctoproject.org/g/yocto/message/59372 Mute This Topic: https://lists.yoctoproject.org/mt/97491481/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Importance of ECC RAM on the build computer
Hi! Le ven. 17 févr. 2023 à 06:08, a écrit : > Is there generally suggested advice regarding the importance of ECC on the > build computer? I'm very new to Yocto so I'm not sure if there is a chance > the final build image could experience some corruption due to flipped bits > in RAM or if I'm totally overthinking this. Last time I checked. The ECC vs non-ECC price difference was not worth the time you may spend in case of a RAM bitflip. Here, we put ECC RAM in our build systems and I guess it's quite the industry standard. It is also possible that Yocto does some kind of CRC checking of its own > that makes this a non-issue. Any guidance would be appreciated. Thank you! > Yocto does source integrity checks (the stuff it downloads from the internet) but it can't do much more after that. I've yet to debug a RAM bitflip but I guess it may trigger any kind of weird behavior which may be hard to debug and time consuming. My advice is : keep your time and sanity, use ECC RAM. Regards, -- Yoann Congal Smile ECS - Expert technique -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59237): https://lists.yoctoproject.org/g/yocto/message/59237 Mute This Topic: https://lists.yoctoproject.org/mt/97022997/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Git repo setup for Yocto upstream contribution
On 1/9/23 10:29, Alexander Kanavin wrote:
I've been making patches against an integrated poky checkout for many
years, including bitbake patches. They're usually correctly picked up
and applied; you only need to ensure you route them to correct mailing
lists.
Ok, I'll keep it that way.
Thanks!
Alex
On Sat, 7 Jan 2023 at 14:05, Yoann Congal wrote:
Hi,
Since I plan to work regularly on upstream Yocto and contributing, I
wonder about the best way to best setup my git repos to do that...
I've started with the upstream poky repo but when I make a commit on,
for example, bitbake, my patch applies on a bitbake/some-path file which
does not exist in the bitbake repo (only "some-path" exists in the
bitbake repo).
Is this something I should address ? I found some patches for bitbake in
the mailing list that are for "bitbake/..." paths... So, maybe, basing
my patches on the poky repo is totally OK for now...?
To the Yocto maintainers, how do you manage this (poky repo, combo-layer
and individual bitbake/doc/meta-yocto repo) ?
Note: I have found the "combo-layer splitpatch" tool but it does not
look like a full solution... Maybe I'm missing something?
Thanks!
--
Yoann Congal ("yocton" on IRC)
Smile ECS - Tech Expert
--
Yoann Congal
Smile ECS - Tech Expert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58946): https://lists.yoctoproject.org/g/yocto/message/58946
Mute This Topic: https://lists.yoctoproject.org/mt/96112311/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] Git repo setup for Yocto upstream contribution
Hi,
Since I plan to work regularly on upstream Yocto and contributing, I
wonder about the best way to best setup my git repos to do that...
I've started with the upstream poky repo but when I make a commit on,
for example, bitbake, my patch applies on a bitbake/some-path file which
does not exist in the bitbake repo (only "some-path" exists in the
bitbake repo).
Is this something I should address ? I found some patches for bitbake in
the mailing list that are for "bitbake/..." paths... So, maybe, basing
my patches on the poky repo is totally OK for now...?
To the Yocto maintainers, how do you manage this (poky repo, combo-layer
and individual bitbake/doc/meta-yocto repo) ?
Note: I have found the "combo-layer splitpatch" tool but it does not
look like a full solution... Maybe I'm missing something?
Thanks!
--
Yoann Congal ("yocton" on IRC)
Smile ECS - Tech Expert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58933): https://lists.yoctoproject.org/g/yocto/message/58933
Mute This Topic: https://lists.yoctoproject.org/mt/96112311/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] #bitbake Can't get application sources from private git using SSH keys #bitbake #yocto
Hello, Le jeu. 29 juil. 2021 à 08:22, a écrit : > SRC_URI = "git://g...@.com:xxx/xxx.git" > Could someone please suggest on how to write a recipe to get the > application code from private git hub using SSH keys. > The ':' in SRC_URI is not handled like in the git clone command line. You may need to change it to a '/' SRC_URI = "git://g...@.com/xxx/xxx.git;protocol=ssh;" This is a frequent error (I make it at least once per project) Hope this helps! Regards, -- Yoann Congal Smile ECS - Expert technique -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#54253): https://lists.yoctoproject.org/g/yocto/message/54253 Mute This Topic: https://lists.yoctoproject.org/mt/84523137/21656 Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto Mute #bitbake:https://lists.yoctoproject.org/g/yocto/mutehashtag/bitbake Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] what to include in a "hardware bringup image"?
Hello, It might be a bit heavy but I usually install a text editor and python-periphery (https://github.com/vsergeev/python-periphery) (It did not know c-periphery but this is the same author) Before having full fledged linux drivers, it allows to check devices IDs, make simple requests like get a sensor value or enable a PMIC regulator. I'm interested in the list of packages you'll end up with... Will you share it here ? Regards, -- Yoann Congal Smile ECS - Expert technique -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#53188): https://lists.yoctoproject.org/g/yocto/message/53188 Mute This Topic: https://lists.yoctoproject.org/mt/82112196/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
