QA notification for completed autobuilder build (yocto-3.1.14.rc1)
Richard Purdie
A build flagged for QA (yocto-3.1.14.rc1) was completed on the autobuilder and
is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.1.14.rc1 Build hash information: bitbake: be6ecc160ac4a8d9715257b9b955363cecc081ea meta-agl: 7a644d636237459c54128a71d083cb6f9e1b8e60 meta-arm: ce535dfb96de4d2529f091d7d85a7172c626001c meta-aws: 9979cfa676105cb68cfadfdaeabf044d7c919319 meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac meta-intel: 87984115eb6ed1a4c17204629dcb100f6b76fe82 meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7 meta-openembedded: ab9fca485e13f6f2f9761e1d2810f87c2e4f060a oecore: f3be01483b01c88f8c4ba24ca73ccf1bcc33665c poky: bba323389749ec3e306509f8fb12649f031be152 This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.purdie@... |
|
Re: How to prevent auto start of matchbox-terminal at boot?
Dave Beal
Thanks, Alex! That was it. The script that started the matchbox-terminal is /usr/bin/mini-x-session. I just edited this file and commented out the terminal line and another line that was setting my display to an incorrect resolution.
|
|
Where setup KCONF_AUDIT_LEVEL value
Mauro Ziliani
Hi all.
The KCONF_AUDIT_LEVEL variable must be setup in a .conf file or I can change it in a recipe? I try to understand why my file defconfig is not used my kernel configurator MZ |
|
Re: boot script for barebox in build/deploy/images/$IMAGE_NAME/ directory
Gary Huband
In Zeus I have a recipe that installs the file (a u-boot boot.scr for me):
install -m 0644 boot.scr ${DEPLOYDIR}
Make sure the recipe is included in your image. Then in my machine conf:
IMAGE_BOOT_FILES = "zImage oftree imx7d-phyboard-zeta-004.dtb imx7d-phyboard-zeta-004-m4.dtb boot.scr"
Gary
From: yocto@... <yocto@...> on behalf of Ivan Riabtsov via lists.yoctoproject.org <ivriabtsov=gmail.com@...>
Sent: Saturday, January 29, 2022 10:47 PM To: Yocto-mailing-list <yocto@...> Subject: [yocto] boot script for barebox in build/deploy/images/$IMAGE_NAME/ directory Hello everyone, I need to put the boot.sh file in the
build/deploy/images/$IMAGE_NAME/ directory during the build, how can I do this using the yocto build system?
Gary Huband
Sr. Software and Systems Engineer
Office: 434.284.8071 x720 Direct: 434.260.4995 Gary@...
: : : : : : : : : : : : : : : : : : : : : : : : : : :
![]() This email and any files transmitted with it are confidential and proprietary and intended solely for the use of the individual or entity to whom they are addressed.
Any dissemination, distribution or copying of this communication is strictly prohibited without our prior permission. If you received this in error, please contact the sender and delete the material from any computer.
|
|
Re: Fetch private gitlab repo using ssh with Yocto recipe
#bitbake
Sourabh Hegde
Hello @Nicolas @Erik @Khem, |
|
Re: How to prevent auto start of matchbox-terminal at boot?
Alexander Kanavin
The logs reveal that 'packagegroup-core-x11 packagegroup-core-x11-base packagegroup-core-x11-xserver' are all installed. x11-base pulls in recipes-graphics/mini-x-session/mini-x-session_0.1.bb which starts a minimal session with a terminal. You should either drop x11-base, or tweak mini-x-session script to do what you want. Alex On Mon, 31 Jan 2022 at 01:22, Dave Beal via lists.yoctoproject.org <dbeal=cardinalpeak.com@...> wrote: Thanks, Alex. The log file is attached. |
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.5_M2.rc6)
Teoh, Jay Shen
Hi all,
toggle quoted message
Show quoted text
This is the full report for yocto-3.5_M2.rc6: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high milestone defects. new issue found Bug 14708 - [3.5 M2] Failed to boot up on NFS with systemd ======= Bugs ======== https://bugzilla.yoctoproject.org/show_bug.cgi?id=14708 Thanks, Jay -----Original Message----- |
|
Re: How to prevent auto start of matchbox-terminal at boot?
Dave Beal
Thanks, Alex. The log file is attached.
By the way, I'd be happy with a solution that involves changing a file on the target system after the Yocto build is complete. The fix doesn't need to be in the Yocto build. = Dave
|
|
Re: How to prevent auto start of matchbox-terminal at boot?
Alexander Kanavin
Please share the log.do_rootfs for your image, otherwise it's difficult to say why the terminal ends up being there and gets autostarted. Alex On Sun, 30 Jan 2022 at 22:01, Dave Beal via lists.yoctoproject.org <dbeal=cardinalpeak.com@...> wrote:
|
|
How to prevent auto start of matchbox-terminal at boot?
Dave Beal
Hello Yocto Community - I am using Yocto to build a core-image-minimal image for Intel hardware. When the system boots, it automatically starts a matchbox-terminal as root. This is a huge security hole for this embedded system product, because anyone who plugs in a keyboard and monitor has access to this terminal. I've spent about two days trying to figure out how to start X without this terminal appearing. I assume there's a config file somewhere indicating that this terminal should start automatically, but I haven't been able to find it. Any suggestions? Thanks! = Dave Beal Cardinal Peak, LLC Colorado, USA |
|
[meta-security][PATCH] lkrg-module: update to 0.9.2
see https://github.com/lkrg-org/lkrg
Support new stable and mainline kernels 5.14 to at least 5.16-rc* Support new longterm kernels 5.4.118+, 4.19.191+, 4.14.233+ update SRC_URI as location changed. refresh patch. Signed-off-by: Armin Kuster <akuster808@...> --- recipes-kernel/lkrg/files/makefile_cleanup.patch | 8 ++++---- .../lkrg/{lkrg-module_0.9.1.bb => lkrg-module_0.9.2.bb} | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) rename recipes-kernel/lkrg/{lkrg-module_0.9.1.bb => lkrg-module_0.9.2.bb} (84%) diff --git a/recipes-kernel/lkrg/files/makefile_cleanup.patch b/recipes-kernel/lkrg/files/makefile_cleanup.patch index 106dc3f..a4db2d9 100644 --- a/recipes-kernel/lkrg/files/makefile_cleanup.patch +++ b/recipes-kernel/lkrg/files/makefile_cleanup.patch @@ -4,10 +4,10 @@ This needs more work. Its my starting point. Signed-off-by: Armin Kuster <akuster808@...> -Index: lkrg-0.9.0/Makefile +Index: lkrg-0.9.2/Makefile =================================================================== ---- lkrg-0.9.0.orig/Makefile -+++ lkrg-0.9.0/Makefile +--- lkrg-0.9.2.orig/Makefile ++++ lkrg-0.9.2/Makefile @@ -4,28 +4,10 @@ # Author: # - Adam 'pi3' Zabrocki (http://pi3.com.pl) @@ -39,7 +39,7 @@ Index: lkrg-0.9.0/Makefile src/modules/hashing/p_lkrg_fast_hash.o \ src/modules/comm_channel/p_comm_channel.o \ src/modules/integrity_timer/p_integrity_timer.o \ -@@ -91,23 +73,14 @@ $(TARGET)-objs += src/modules/ksyms/p_re +@@ -92,23 +74,14 @@ $(TARGET)-objs += src/modules/ksyms/p_re src/p_lkrg_main.o diff --git a/recipes-kernel/lkrg/lkrg-module_0.9.1.bb b/recipes-kernel/lkrg/lkrg-module_0.9.2.bb similarity index 84% rename from recipes-kernel/lkrg/lkrg-module_0.9.1.bb rename to recipes-kernel/lkrg/lkrg-module_0.9.2.bb index 782c6e3..e055fbe 100644 --- a/recipes-kernel/lkrg/lkrg-module_0.9.1.bb +++ b/recipes-kernel/lkrg/lkrg-module_0.9.2.bb @@ -9,10 +9,10 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=5105ead24b08a32954f34cbaa7112432" DEPENDS = "virtual/kernel elfutils" -SRC_URI = "https://www.openwall.com/lkrg/lkrg-${PV}.tar.gz \ +SRC_URI = "https://download.openwall.net/pub/projects/lkrg/lkrg-${PV}.tar.gz \ file://makefile_cleanup.patch " -SRC_URI[sha256sum] = "cabbee1addbf3ae23a584203831e4bd1b730d22bfd1b3e44883214f220b3babd" +SRC_URI[sha256sum] = "c2b501c47089cce3ec3114cef6520b73aa3a098836183186b9bb5e097c99ac27" S = "${WORKDIR}/lkrg-${PV}" -- 2.25.1 |
|
boot script for barebox in build/deploy/images/$IMAGE_NAME/ directory
Ivan Riabtsov <ivriabtsov@...>
Hello everyone, I need to put the boot.sh file in the
build/deploy/images/$IMAGE_NAME/ directory during the build, how can I do this using the yocto build system? |
|
[meta-security][PATCH 2/2] tpm2-pkcs11_1.7.0: Drop dstat from DPENDS
dstat was removed from meta-oe.
Signed-off-by: Armin Kuster <akuster808@...> --- meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_1.7.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_1.7.0.bb b/meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_1.7.0.bb index 3a0917a..d70dbfa 100644 --- a/meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_1.7.0.bb +++ b/meta-tpm/recipes-tpm2/tpm2-pkcs11/tpm2-pkcs11_1.7.0.bb @@ -4,7 +4,7 @@ SECTION = "security/tpm" LICENSE = "BSD-2-Clause" LIC_FILES_CHKSUM = "file://LICENSE;md5=0fc19f620a102768d6dbd1e7166e78ab" -DEPENDS = "autoconf-archive pkgconfig dstat sqlite3 openssl libtss2-dev tpm2-tools libyaml p11-kit python3-setuptools-native" +DEPENDS = "autoconf-archive pkgconfig sqlite3 openssl libtss2-dev tpm2-tools libyaml p11-kit python3-setuptools-native" SRC_URI = "git://github.com/tpm2-software/tpm2-pkcs11.git;branch=master;protocol=https \ file://bootstrap_fixup.patch \ -- 2.25.1 |
|
[meta-security][PATCH 1/2] packagegroup-security-tpm2.bb: remove dynamic pkgs
fixes:
packagegroup-security-tpm2-1.0-r0 do_package_write_rpm: An allarch packagegroup shouldn't depend on packages which are dynamically renamed (libtss2-tcti-device to libtss2-tcti-device0) Signed-off-by: Armin Kuster <akuster808@...> --- .../recipes-core/packagegroup/packagegroup-security-tpm2.bb | 3 --- 1 file changed, 3 deletions(-) diff --git a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb index b8324e5..fb36fab 100644 --- a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb +++ b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb @@ -13,9 +13,6 @@ RDEPENDS:packagegroup-security-tpm2 = " \ trousers \ tpm2-tss \ libtss2 \ - libtss2-mu \ - libtss2-tcti-device \ - libtss2-tcti-mssim \ tpm2-abrmd \ tpm2-pkcs11 \ " -- 2.25.1 |
|
Re: Python3 app install best practice
Mauro Ziliani
Hi list.
toggle quoted message
Show quoted text
I solved my problem working with distutils parameteres inside myapp.bb recipe Mauro On 26/01/22 18:30, Mauro Ziliani via lists.yoctoproject.org wrote:
Hi all |
|
Re: [oe] Inclusive Language Proposal for YP/OE
Peter Kjellerstedt
toggle quoted message
Show quoted text
-----Original Message-----[cut] For license handling, we’d use the opportunity to clean up theI am not so sure about this name. Not only is it extremely long, but at least I would like to revise the entire system of how licenses are handled. The major reason for this is that our legal department requires us to have a list of allowed licenses rather than a list of disallowed licenses. Thus we have a COMPATIBLE_LICENSES variable. We then set INCOMPATIBLE_LICENSE to AVAILABLE_LICENSES - COMPATIBLE_LICENSES. However, after the introduction of all official SPDX licenses into OE-Core a while ago this became problematic as the current implementation will go through all licenses specified in INCOMPATIBLE_LICENSE many, many times during recipe parsing, which caused the time to parse all recipes to increase three times for us. Thus I would like to implement proper support for COMPATIBLE_LICENSES in addition to the INCOMPATIABLE_LICENSE variable to allow choosing the option that suits the situation best. However, in either case there would still need to be a way to specify exceptions to the incompatible licenses, which is why I would prefer that the name is not locked to the INCOMPATIBLE_LICENSE variable. Here are a couple of alternatives: * LICENSE_EXCEPTIONS * ALLOWED_RECIPES * LICENSE_ALLOWED_RECIPES It is also that the WHITELIST variables have two use cases today, one is to allow a _recipe_ to be built and the other is to allow a _package_ to be added to an image even if it has an incompatible license. The first use case can just as easily be achieved by setting INCOMPATIBLE_LICENSE:pn-foo = "" for a recipe foo that shall be allowed to be built even if it has an incompatible license. With this in mind, maybe the variable should actually be an image variable and specify a list of allowed packages instead, e.g., IMAGE_ALLOWED_PACKAGES. Whether the variable with a list of allowed recipes is then still needed or if it is enough to manipulate INCOMPATIBLE_LICENSE as per above can be discussed. //Peter |
|
Re: libquadmath
On 2022-01-04 10:00, staticd wrote:
One final update for anyone who might run into this problem.Hi, If you can come up with a reasonably simple reproducer and it fails on a supported branch: https://wiki.yoctoproject.org/wiki/Releases then we'd appreciate if if you could report the bug in the YP Bugzilla: https://wiki.yoctoproject.org/wiki/Bugzilla_Configuration_and_Bug_Tracking Don't worry too much about getting every field right if you aren't familiar with the overall project. There's no guarantee that we'll get someone to work on it but at least it's tracked and we might get to it at some point. ../Randy On Mon, Jan 3, 2022 at 4:55 PM staticd <staticd@... <mailto:staticd@...>> wrote: -- # Randy MacLeod # Wind River Linux |
|
Re: Preferred provide base-utils issue
Paul van Berlo <pvanberlo@...>
Hi, Adding that line results in an error: ERROR: Nothing RPROVIDES 'syslog' (but /yocto/poky-dunfell/meta/recipes-core/packagegroups/packagegroup-core-boot.bb, /yocto/poky-dunfell/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb, /yocto/poky-dunfell/meta/recipes-core/initrdscripts/initramfs-module-install-efi_1.0.bb RDEPENDS on or otherwise requires it) The kernel panic ends with "not syncing: Attempted to kill init! exitcode=0x00000100". This is using the genericx86-64 machine. Regards, Paul van Berlo On Fri, 28 Jan 2022 at 18:43 Randy MacLeod <randy.macleod@...> wrote: On 2022-01-26 11:17, Paul van Berlo wrote: |
|
Re: Preferred provide base-utils issue
On 2022-01-26 11:17, Paul van Berlo wrote:
Hello,Hi Paul, Try adding: VIRTUAL-RUNTIME_base-utils-syslog = "syslog" as shown on: https://git.yoctoproject.org/poky/tree/meta-poky/conf/local.conf.sample.extended#n371 I would expect that since you have systemd, you'd have the systemd journal as well so you wouldn't need syslog but it would be good to do a sanity check. If that doesn't help, show us what the kernel panic is saying. Is this with a custom BSP and if so can you reproduce with qemux86-64? Try the same things using poky on the master branch if you can. ../Randy -- # Randy MacLeod # Wind River Linux |
|
Re: Fetch private gitlab repo using ssh with Yocto recipe
#bitbake
On Fri, Jan 28, 2022 at 2:27 AM VIVAVIS AG <embedded@...> wrote:
yeah something like that works, we use it for yoe which always uses container to build see https://github.com/YoeDistro/yoe-distro/blob/master/envsetup.sh#L528-L541 Regards, |
|