|
Enhancements/Bugs closed WW33!
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Current high bug count owners for Yocto Project 4.1
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Yocto Project Newcomer & Unassigned Bugs - Help Needed
Stephen Jolley
All,
The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project. If anyone can help, please take ownership of the bug and send patches! If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.
Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 417 unassigned or newcomer bugs.
We're hoping people may be able to spare some time now and again to help out with these. Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system. There are also roughly four different "priority" classes right now, “4.1”, “4.2”, "4.99" and "Future", the more pressing/urgent issues being in "4.1" and then “4.2”.
Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account). The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[PATCH yocto-autobuilder-helper 1/2] config.json: enable CPU and IO pressure regulation
Aryaman Gupta <aryaman.gupta@...>
Prevent severe system overload by setting the pressure limits for CPU
and IO at 10000. Signed-off-by: Aryaman Gupta <aryaman.gupta@...> Signed-off-by: Randy Macleod <Randy.Macleod@...> --- config.json | 2 ++ 1 file changed, 2 insertions(+) diff --git a/config.json b/config.json index 5f37e77..1173797 100644 --- a/config.json +++ b/config.json @@ -46,6 +46,8 @@ "BB_GENERATE_MIRROR_TARBALLS = '1'", "BB_NUMBER_THREADS = '16'", "PARALLEL_MAKE = '-j 16 -l 52'", + "BB_PRESSURE_MAX_CPU = '10000'", + "BB_PRESSURE_MAX_IO = '10000'", "XZ_MEMLIMIT = '5%'", "XZ_THREADS = '8'", "ZSTD_THREADS = '8'", -- 2.35.3
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[PATCH yocto-autobuilder-helper 2/2] scripts/archive_buildstats.py: archive buildstats to tar.zst
Aryaman Gupta <aryaman.gupta@...>
Archive the buildstats of every failed build and 1% of random builds. Convert
the time-stamped buildstats directory to a compressed tarball using the hostname as a prefix (to the file name only) so that one can identify the source machine. Move these tarballs to the directory: testresults/<build_name>/buildstats/ The archiving is performed during the "collect results" step. Signed-off-by: Aryaman Gupta <aryaman.gupta@...> Signed-off-by: Randy MacLeod <Randy.MacLeod@...> --- scripts/archive_buildstats.py | 37 +++++++++++++++++++++++++++++++++++ scripts/run-config | 1 + 2 files changed, 38 insertions(+) create mode 100755 scripts/archive_buildstats.py diff --git a/scripts/archive_buildstats.py b/scripts/archive_buildstats.py new file mode 100755 index 0000000..de866e5 --- /dev/null +++ b/scripts/archive_buildstats.py @@ -0,0 +1,37 @@ +#!/usr/bin/env python3 +# +# SPDX-License-Identifier: GPL-2.0-only +# +import glob, os, random, subprocess, socket, sys + +def usage(): + print("Usage: " + sys.argv[0] + " <src> <dest> <target>") + +def main(): + if len(sys.argv) != 4: + usage() + sys.exit() + + builddir = sys.argv[1] + dest = sys.argv[2] + target = sys.argv[3] + dest_bsdir = os.path.join(dest, target, "buildstats") + subprocess.run(["mkdir", "-p", dest_bsdir]) + + build_bsdir = os.path.join(builddir, "tmp/buildstats") + hostname = socket.gethostname() + os.chdir(build_bsdir) + fail_path = os.path.join(dest, target, "intermittent_failure_host_data") + fail_output = glob.glob(fail_path + '/*top_summary.txt') + + #archive the buildstats of failures and 1% of random builds + if fail_output or random.randint(1,100)%100 == 0: + for timestamp in os.listdir(build_bsdir): + if hostname: + output = hostname + "-" + timestamp + ".tar.zst" + else: + output = "nohostname-"+ timestamp + ".tar.zst" + subprocess.check_call("tar -I zstd -cf "+output+" "+timestamp+"/*", shell=True) + subprocess.run(["mv", output, dest_bsdir]) + +main() \ No newline at end of file diff --git a/scripts/run-config b/scripts/run-config index 838847a..953977e 100755 --- a/scripts/run-config +++ b/scripts/run-config @@ -334,6 +334,7 @@ elif args.phase == "finish" and args.stepname == "collect-results": hp.printheader("Running results collection") runcmd([scriptsdir + "/collect-results", args.builddir, args.results_dir, args.target]) runcmd([scriptsdir + "/summarize_top_output.py", args.results_dir, args.target]) + runcmd([scriptsdir + "/archive_buildstats.py", args.builddir, args.results_dir, args.target]) sys.exit(0) if jcfg: -- 2.35.3
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
no framebuffer graphics when fbcon cursor is disabled
#framebuffer
#yocto
#honister
douglas.cooper1@...
Hello,
Im using the 5.10.100 kernel from the meta-intel layer and have an image that runs most of the df_* demos as well as cinematicexperience Qt5 example without any interference from the console output. I have an application that writes directly to the framebuffer device but gets smothered by text from the console. When I try to unbind the fbcon or disable the cursor I am also prevented from graphics being displayed. If for example i run `cat /dev/urandom > /dev/fb0` i get noise as expected with a small blinking cursor from the terminal, but if i disable the cursor that command does nothing. Any thoughts on how i can display framebuffer graphics without console interference would be much appreciated, -Doug
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[meta-security][PATCH] cyptmount: Fix mount.h conflicts seen with glibc 2.36+
Signed-off-by: Armin Kuster <akuster808@...>
--- .../cryptmount/cryptmount_5.3.3.bb | 4 +++- .../cryptmount/files/remove_linux_fs.patch | 19 +++++++++++++++++++ 2 files changed, 22 insertions(+), 1 deletion(-) create mode 100644 recipes-security/cryptmount/files/remove_linux_fs.patch diff --git a/recipes-security/cryptmount/cryptmount_5.3.3.bb b/recipes-security/cryptmount/cryptmount_5.3.3.bb index 6e653c8..fb522cb 100644 --- a/recipes-security/cryptmount/cryptmount_5.3.3.bb +++ b/recipes-security/cryptmount/cryptmount_5.3.3.bb @@ -3,7 +3,9 @@ HOMEPAGE = "http://cryptmount.sourceforge.net/" LIC_FILES_CHKSUM = "file://README;beginline=3;endline=4;md5=673a990de93a2c5531a0f13f1c40725a" LICENSE = "GPL-2.0-only" -SRC_URI = "https://sourceforge.net/projects/cryptmount/files/${BPN}/${BPN}-5.3/${BPN}-${PV}.tar.gz" +SRC_URI = "https://sourceforge.net/projects/cryptmount/files/${BPN}/${BPN}-5.3/${BPN}-${PV}.tar.gz \ + file://remove_linux_fs.patch \ + " SRC_URI[sha256sum] = "682953ff5ba497d48d6b13e22ca726c98659abd781bb8596bb299640dd255d9b" diff --git a/recipes-security/cryptmount/files/remove_linux_fs.patch b/recipes-security/cryptmount/files/remove_linux_fs.patch new file mode 100644 index 0000000..304b853 --- /dev/null +++ b/recipes-security/cryptmount/files/remove_linux_fs.patch @@ -0,0 +1,19 @@ +# From glibc 2.36, <linux/mount.h> (included from <linux/fs.h>) and +# <sys/mount.h> (included from glibc) are no longer compatible: +# https://sourceware.org/glibc/wiki/Release/2.36#Usage_of_.3Clinux.2Fmount.h.3E_and_.3Csys.2Fmount.h.3E + +Upstream-Status: Pending +Signed-off-by: Armin Kuster <akuster808@...> + +Index: cryptmount-5.3.3/cryptmount.c +=================================================================== +--- cryptmount-5.3.3.orig/cryptmount.c ++++ cryptmount-5.3.3/cryptmount.c +@@ -41,7 +41,6 @@ + #ifdef HAVE_SYSLOG + # include <syslog.h> + #endif +-#include <linux/fs.h> /* Beware ordering conflict with sys/mount.h */ + + + #include "armour.h" -- 2.25.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: do_install & RDEPENDS
Alexander Kanavin
It's hard to say what happens if we can't see your recipes. Can you
toggle quoted messageShow quoted text
publish them? Alex
On Mon, 15 Aug 2022 at 00:54, Gian Lorenzo Meocci <glmeocci@...> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: question about PREFERRED_RPROVIDER
John Wang
I did as Richard suggested, It worked as expected now
feature-public.bb or feature-private.bb: SRC_URI = "git://public or git://private" PROVIDES += "virtual/feature" RPROVIDES:${PN} += " \ virtual-feature \ " machine.conf: PREFERRED_PROVIDER_virtual/feature = "feature-public" Khem Raj <raj.khem@...> 于2022年8月13日周六 22:11写道： No, and I will avoid to use AUTOREV, thank you I checked the yocto-manual, and saw If you use a virtual/\* item with PREFERRED_PROVIDER, then any recipe that PROVIDES that item but is not selected (defined) by PREFERRED_PROVIDER is prevented from building, which is usually desirable since this mechanism is designed to select between mutually exclusive alternative providers[1]. Do you mean if I use AUTOREV, bitbake sill tries to fetch ? And, I am confused about the "PREFERRED_RPROVIDER" , I saw someone use this variable[2], but I cannot find any thing about it In the manual [3] [1] https://docs.yoctoproject.org/ref-manual/variables.html#term-PREFERRED_PROVIDER [2] https://github.com/search?q=PREFERRED_RPROVIDER_virtual&type=code [3] https://docs.yoctoproject.org/genindex.html#P
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
do_install & RDEPENDS
glmeocci@...
Inside the do_install I copy some files but it seems that bitbake set those files in the RDEPENS. In the log during the do_root_fs I see: Requires(post): ... mylib.so After that the commands fail with the error message: Problem: conflicting requests - nothing provides mylib.so needed by mypackage-0.10.14r0.core2_64 Is there a way to disable this behaviour?
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: A bitbake error caused by "Variable BB_ENV_EXTRAWHITE"
#bitbake
Alexander Kanavin
Then you need to check the output of 'env'
a) when you start the shell b) when you use oe-init-build-env and figure out how the incorrect variable gets into the environment. Are you using oe-init-build-env from an old yocto? Alex On Sat, 13 Aug 2022 at 15:02, Kaiwan N Billimoria <kaiwan.billimoria@...> wrote: Hello,you probably need to exit the shell and then restart it and
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: question about PREFERRED_RPROVIDER
fetcher will try to get versions of recipes during parse phase and if
toggle quoted messageShow quoted text
your recipes are using AUTOREV they will try to poke at git server for latest commit SHA are you using AUTOREV by chance ?
On Sat, Aug 13, 2022 at 2:57 AM John Wang <wangzq.jn@...> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[meta-security][PATCH] suricata: fix compile issue
make[2]: *** No rule to make target '../rust/target/arm-poky-linux-gnueabi/release/libsuricata.a', needed by 'suricata'
Signed-off-by: Armin Kuster <akuster808@...> --- recipes-ids/suricata/suricata_6.0.6.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/recipes-ids/suricata/suricata_6.0.6.bb b/recipes-ids/suricata/suricata_6.0.6.bb index 35054ef..efa4bdd 100644 --- a/recipes-ids/suricata/suricata_6.0.6.bb +++ b/recipes-ids/suricata/suricata_6.0.6.bb @@ -145,6 +145,8 @@ export logdir = "${localstatedir}/log" CACHED_CONFIGUREVARS = "ac_cv_func_malloc_0_nonnull=yes ac_cv_func_realloc_0_nonnull=yes" do_configure:prepend () { + # use host for RUST_SURICATA_LIB_XC_DIR + sed -i -e 's:host_alias:host:' ${S}/configure.ac oe_runconf } -- 2.25.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: question about PREFERRED_RPROVIDER
Richard Purdie
On Sat, 2022-08-13 at 17:57 +0800, John Wang wrote:
Hi,"virtual" entries only work in PROVIDES and PREFERRED_PROVIDER, not in the runtime version of the variable. Cheers, Richard
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
question about PREFERRED_RPROVIDER
John Wang
Hi,
There is a package with two versions, private and public. But when I use the PREFERRED_RPROVIDER to select the public version, bitbake still tries fetch the private one, and then bitabke terminates because do_fetch fails (no permission) What I expect is that when I select the public repository version, it should not fetch the private repository, am I right? Or, should I not use the PREFERRED_RPROVIDER to select a public/private repo ? Could someone guide me :) feature-public.bb ``` SRC_URI = "git://public" RPROVIDES:${PN} += " \ virtual-feature \ " ``` feature-private.bb ``` SRC_URI= "git://private" RPROVIDES:${PN} += " \ virtual-feature \ " ``` machine.conf ``` PREFERRED_RPROVIDER_virtual-feature = "feature-public" ```
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: A bitbake error caused by "Variable BB_ENV_EXTRAWHITE"
#bitbake
Alexander Kanavin
Hello,
toggle quoted messageShow quoted text
you probably need to exit the shell and then restart it and re-initialize your environment (with oe-init-build-env), as it contains the obsolete variable. Alex
On Sat, 13 Aug 2022 at 05:13, <lucky33newman@...> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
A bitbake error caused by "Variable BB_ENV_EXTRAWHITE"
#bitbake
Yan Xinkuan
Hellow everyone, this is Yan. I am new to Yocto Project, still, I am learning.
There is a question, when I bitbaked my image I found this ERROR: yanxk@yanxk-Ubuntu:~/Yocto/poky/build$ bitbake core-image-sato
ERROR: Variable BB_ENV_EXTRAWHITE has been renamed to BB_ENV_PASSTHROUGH_ADDITIONS
ERROR: Variable BB_ENV_EXTRAWHITE from the shell environment has been renamed to BB_ENV_PASSTHROUGH_ADDITIONS
ERROR: Exiting to allow enviroment variables to be corrected
How can I do a quick fix, and why is it working wrong? By the way, I check the link https://git.openembedded.org/bitbake/commit/?id=87104b6a167188921da157c7dba45938849fb22a , which most likely the main cause. Waiting for a help.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: [meta-security][PATCH] samhain-standalone: fix buildpaths issue
merged
toggle quoted messageShow quoted text
On 8/11/22 02:40, Yu, Mingli wrote:
From: Mingli Yu <mingli.yu@...>
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: [meta-security][PATCH V2] meta-security: Add recipe for Glome
merged
toggle quoted messageShow quoted text
On 8/8/22 11:40, John Broadbent via lists.yoctoproject.org wrote:
From: John Edward Broadbent <jebr@...>
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: [meta-cgl][PATCH] resource-agents: Bug fix.
Merged.
toggle quoted messageShow quoted text
On 8/7/2022 7:22 PM, leimaohui wrote:
Fix error as the fowllowing:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|