Date   

USB Installer for initial deployment

Matthias Schoepfer
 

Hi there,

I am looking for some kind of package or software, that creates an (USB thumb drive) installer for initial installation and deployment of a yocto image. So you can flash the image onto an USB thumb drive and boot from it (arch is x86-64 so this should be easy), and after asking if that is really what you want, will erase the local storage and partition the drive (root A/B, data, swap) and copies over the image from the yocto build. I know that there is some thing into this direction in the meta-intel layer, but that is not quite well documented nor do I think it will suit our needs (regarding partitioning for example).

So, before I write terrible bash scripts into an initramfs init (because this is my best idea so far), if someone could give me a hint were to look would be great.

Thanks and regards,

    Matthias


Re: [PATCH yocto-autobuilder-helper] scripts/archive_buildstats.py: copy all buildstats

Richard Purdie
 

On Wed, 2022-06-22 at 17:12 -0400, Randy MacLeod wrote:
As a first pass, collect all the tmp/buildstats logs
using 'cp -a', to enable review and graphing of all builds.
The goal is to understand the trends in the /proc/pressure/{cpu|io}
data that is now gathered as part of the buildstats system.

Signed-off-by: Aryaman Gupta <Aryaman.Gupta@...>
Signed-off-by: Randy MacLeod <Randy.MacLeod@...>
---
scripts/archive_buildstats.py | 27 +++++++++++++++++++++++++++
scripts/run-config | 1 +
2 files changed, 28 insertions(+)
create mode 100755 scripts/archive_buildstats.py
The NAS couldn't cope with the number of small files these data trees
contained leading to timeouts. If you want to do something like this
you'll probably have to create tarball archives of the results.

Cheers,

Richard


[meta-security][PATCH] lkrg: update to 0.9.3

Armin Kuster
 

refresh patch

Signed-off-by: Armin Kuster <akuster808@...>
---
.../lkrg/files/makefile_cleanup.patch | 72 +++++++------------
...g-module_0.9.2.bb => lkrg-module_0.9.3.bb} | 7 +-
2 files changed, 30 insertions(+), 49 deletions(-)
rename recipes-kernel/lkrg/{lkrg-module_0.9.2.bb => lkrg-module_0.9.3.bb} (90%)

diff --git a/recipes-kernel/lkrg/files/makefile_cleanup.patch b/recipes-kernel/lkrg/files/makefile_cleanup.patch
index 799b1a6..f29afbe 100644
--- a/recipes-kernel/lkrg/files/makefile_cleanup.patch
+++ b/recipes-kernel/lkrg/files/makefile_cleanup.patch
@@ -1,73 +1,53 @@
-Upstream-Status: Pending
-
-This needs more work. Its my starting point.
-
+Upstream-Status: Inappropriate [embedded specific]
+
Signed-off-by: Armin Kuster <akuster808@...>

+
Index: git/Makefile
===================================================================
--- git.orig/Makefile
+++ git/Makefile
-@@ -4,28 +4,10 @@
- # Author:
- # - Adam 'pi3' Zabrocki (http://pi3.com.pl)
- ##
--
--P_OUTPUT = output
+@@ -7,15 +7,8 @@
+
+ P_OUTPUT = output
P_PWD ?= $(shell pwd)
-P_KVER ?= $(shell uname -r)
--P_BOOTUP_SCRIPT ?= scripts/bootup/lkrg-bootup.sh
--TARGET := p_lkrg
+ P_BOOTUP_SCRIPT ?= scripts/bootup/lkrg-bootup.sh
+ TARGET := p_lkrg
-ifneq ($(KERNELRELEASE),)
- KERNEL := /lib/modules/$(KERNELRELEASE)/build
-else
- ## KERNELRELEASE not set.
- KERNEL := /lib/modules/$(P_KVER)/build
-endif
--
--#
--# Uncomment for debug compilation
--#
--# ccflags-m := -ggdb -DP_LKRG_DEBUG_BUILD -finstrument-functions
--# ccflags-y := ${ccflags-m}
--# p_lkrg-objs += src/modules/print_log/p_lkrg_debug_log.o

--obj-m += $(TARGET).o
--$(TARGET)-objs += src/modules/ksyms/p_resolve_ksym.o \
-+obj-m := p_lkrg.o
-+p_lkrg-y := src/modules/ksyms/p_resolve_ksym.o \
- src/modules/hashing/p_lkrg_fast_hash.o \
- src/modules/comm_channel/p_comm_channel.o \
- src/modules/integrity_timer/p_integrity_timer.o \
-@@ -92,23 +74,14 @@ $(TARGET)-objs += src/modules/ksyms/p_re
+ #
+ # Use DEBUG=on for debug build.
+@@ -94,14 +87,13 @@ $(TARGET)-objs += src/modules/ksyms/p_re
src/p_lkrg_main.o


-all:
-# $(MAKE) -C $(KERNEL) M=$(P_PWD) modules CONFIG_DEBUG_SECTION_MISMATCH=y
- $(MAKE) -C $(KERNEL) M=$(P_PWD) modules
-- mkdir -p $(P_OUTPUT)
-- cp $(P_PWD)/$(TARGET).ko $(P_OUTPUT)
--
--install:
-- $(MAKE) -C $(KERNEL) M=$(P_PWD) modules_install
-- depmod -a
-- $(P_PWD)/$(P_BOOTUP_SCRIPT) install
-
--uninstall:
-- $(P_PWD)/$(P_BOOTUP_SCRIPT) uninstall
+modules:
+ $(MAKE) -C $(KERNEL_SRC) M=$(P_PWD) modules
-+
-+modules_install:
+ mkdir -p $(P_OUTPUT)
+ cp $(P_PWD)/$(TARGET).ko $(P_OUTPUT)
+
+-install:
+- $(MAKE) -C $(KERNEL) M=$(P_PWD) modules_install
++moduled_install:
+ $(MAKE) -C $(KERNEL_SRC) M=$(P_PWD) modules_install
+ depmod -a
+ $(P_PWD)/$(P_BOOTUP_SCRIPT) install
+
+@@ -109,7 +101,7 @@ uninstall:
+ $(P_PWD)/$(P_BOOTUP_SCRIPT) uninstall

clean:
- $(MAKE) -C $(KERNEL) M=$(P_PWD) clean
-- $(RM) Module.markers modules.order
-- $(RM) $(P_PWD)/src/modules/kmod/client/kmod/Module.markers
-- $(RM) $(P_PWD)/src/modules/kmod/client/kmod/modules.order
-- $(RM) -rf $(P_OUTPUT)
-+ rm -f *.o *~ core .depend .*.cmd *.ko *.mod.c
-+ rm -f Module.markers Module.symvers modules.order
-+ rm -rf .tmp_versions Modules.symvers
++ $(MAKE) -C $(KERNEL_SRC) M=$(P_PWD) clean
+ $(RM) Module.markers modules.order
+ $(RM) $(P_PWD)/src/modules/kmod/client/kmod/Module.markers
+ $(RM) $(P_PWD)/src/modules/kmod/client/kmod/modules.order
diff --git a/recipes-kernel/lkrg/lkrg-module_0.9.2.bb b/recipes-kernel/lkrg/lkrg-module_0.9.3.bb
similarity index 90%
rename from recipes-kernel/lkrg/lkrg-module_0.9.2.bb
rename to recipes-kernel/lkrg/lkrg-module_0.9.3.bb
index 85f7d44..2553974 100644
--- a/recipes-kernel/lkrg/lkrg-module_0.9.2.bb
+++ b/recipes-kernel/lkrg/lkrg-module_0.9.3.bb
@@ -9,10 +9,11 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=5105ead24b08a32954f34cbaa7112432"

DEPENDS = "virtual/kernel elfutils"

-SRCREV = "43db5f19fca259feb1962f6db33382348cbc8320"
-
SRC_URI = "git://github.com/lkrg-org/lkrg.git;protocol=https;branch=main \
- file://makefile_cleanup.patch "
+ file://makefile_cleanup.patch \
+"
+
+SRCREV = "c578e9f786299b67ffd62057b4534b0bf4fb7ece"

S = "${WORKDIR}/git"

--
2.25.1


Re: LInker Errors: Cannot find crti.o/crtbeginS.o. No such file or directory. #honister #make #yocto

Khem Raj
 



On Thu, Jun 23, 2022 at 1:36 AM <douglas.cooper1@...> wrote:

Hello. Im trying to write a recipe for an autoconf based project. Ive managed to resolve most of the include and linker issues with the exception of the subject error. The files in question exist at <sysroot>/usr/lib64 and <sysroot>/usr/lib64/${TARGET_SYS}/10.3.1 and those paths appear to be on the file search path with sysroot set as expected. Any help would be appreciated.


It’s linker cmdline which is interesting here please post it and that will help to see further 





[PATCH yocto-autobuilder-helper] scripts/archive_buildstats.py: copy all buildstats

Randy MacLeod
 

As a first pass, collect all the tmp/buildstats logs
using 'cp -a', to enable review and graphing of all builds.
The goal is to understand the trends in the /proc/pressure/{cpu|io}
data that is now gathered as part of the buildstats system.

Signed-off-by: Aryaman Gupta <Aryaman.Gupta@...>
Signed-off-by: Randy MacLeod <Randy.MacLeod@...>
---
scripts/archive_buildstats.py | 27 +++++++++++++++++++++++++++
scripts/run-config | 1 +
2 files changed, 28 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..bdbe9f4
--- /dev/null
+++ b/scripts/archive_buildstats.py
@@ -0,0 +1,27 @@
+#!/usr/bin/env python3
+#
+# SPDX-License-Identifier: GPL-2.0-only
+#
+
+import os, 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]
+
+ bsdir = os.path.join(builddir, "tmp/buildstats")
+ directory = os.path.join(dest, target)
+
+ os.system('mkdir -p ' + directory)
+ # cp -a <path-to-worker-buildstats> <directory>
+ os.system('cp -a ' + builddir + ' ' + directory)
+
+main()
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.32.0


LInker Errors: Cannot find crti.o/crtbeginS.o. No such file or directory. #honister #make #yocto

douglas.cooper1@...
 

Hello. Im trying to write a recipe for an autoconf based project. Ive managed to resolve most of the include and linker issues with the exception of the subject error. The files in question exist at <sysroot>/usr/lib64 and <sysroot>/usr/lib64/${TARGET_SYS}/10.3.1 and those paths appear to be on the file search path with sysroot set as expected. Any help would be appreciated.


Packages have unmet dependencies #hardknott #bitbake #kernelmodule

fabatera
 

Hi all,

I'm trying to debug this issue for quite a while but couldn't get any helpful indication on how to solve it.
(In case it matters, the build runs on a docker container with shared volumes for SSTATE and Downloads. )

The issue: First image build works ok. But "bitbake -c clean packagegroup-modules-test" and rebuild generates the error message below.
- my_dev package is inside packagegroup-modules-test.

ERROR: core-image-test-1.0-r0 do_rootfs: Unable to install packages. Command '/long_path/core-image-test/1.0-r0/recipe-sysroot-native/usr/bin/apt-get  install --allow-downgrades --allow-remove-essential --allow-change-held-packages --allow-unauthenticated --no-remove __many_packages_here__ packagegroup-modules-test' returned 100:
 Reading package lists...
 Building dependency tree...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:
 
 The following packages have unmet dependencies:
  kernel-module-hci-uart-my_dev-sdiouart-5.10.52-lts-5.10.y+g0e9bc956f2ca : Depends: kernel-5.10.52-lts-5.10.y+g0e9bc956f2ca but it is not installable
  kernel-module-mlan-my_dev-sdiouart-5.10.52-lts-5.10.y+g0e9bc956f2ca : Depends: kernel-5.10.52-lts-5.10.y+g0e9bc956f2ca but it is not installable
  kernel-module-sdw61x-my_dev-sdiouart-5.10.52-lts-5.10.y+g0e9bc956f2ca : Depends: kernel-5.10.52-lts-5.10.y+g0e9bc956f2ca but it is not installable
                                                                           Depends: kernel-module-cfg80211-5.10.52-lts-5.10.y+g0e9bc956f2ca but it is not installable
 E: Unable to correct problems, you have held broken packages.

Thanks for any help!


Re: [PATCH yocto-autobuilder-helper 4/4] Revert "scripts: run-docs-build: do not turn sphinx warnings into errors"

Michael Opdenacker
 

Hello Quentin,

On 6/22/22 15:02, Richard Purdie wrote:
On Wed, 2022-06-22 at 14:50 +0200, Michael Opdenacker wrote:
Hi Quentin

On 3/15/22 17:31, Quentin Schulz wrote:
From: Quentin Schulz <quentin.schulz@...>

The patch was meant as a quick temporary work-around to have the docs
built and published.

Now that releases where -W flag is set (turning warnings into errors)
are appropriately patched to make those warnings disappear (on Sphinx
v3.2.1 which is the one used on the builder), this patch can be reverted
so that next time a warning appears the doc building will fail but will
not destroy the doc website (because of commit
6a4e6ef18d1415c719be51c773d7c57cae5549cf "scripts: run-docs-build: make
the script fail hard ASAP when there's an error", since rsync will not
be run if any error happens before).

This reverts commit 931d409b255a85f2217ca093d8391a678ce00ddb.

Cc: Quentin Schulz <foss+yocto@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>
---
scripts/run-docs-build | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index 73cba3f..b9b331b 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -33,14 +33,14 @@ cd $bbdocs
echo Building bitbake master branch
git checkout master
make clean
-SPHINXOPTS="-j auto" make publish
+make publish
mkdir $outputdir/bitbake
cp -r ./_build/final/* $outputdir/bitbake
We're trying to build the docs with Sphinx 5.0.0 on a special branch,
and we're getting warnings causing the builds to fail:
https://autobuilder.yoctoproject.org/typhoon/#/builders/114/builds/487/steps/5/logs/stdio

If this patch hadn't been reverted, we would probably be fine.

What should we do now? Patch docs for all past Sphinx based releases? If
we tolerated warnings, we would have to do this less often when we want
to upgrade Sphinx.

In my opinion, another more trouble-free solution would be not to
regenerate docs for past releases, but instead only for the latest
commits in the branches we currently support.

What do you think?
We use the ability to regenerate previous releases to update the
switcher lists and potentially other style related changes in future
which keeps the docs looking consistent. We may have to disable the
errors on warnings :(

Richard and I eventually did that: disabling the errors on warnings, so that we can make progress on the Sphinx updates and the generation of epub and pdf formats.

This won´t prevent us from discussing this further at the right time.

Cheers
Michael.

--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


[PATCH yocto-autobuilder-helper] run-docs-build: allow build warnings again

Michael Opdenacker
 

From: Michael Opdenacker <michael.opdenacker@...>

This allows to switch to a more recent of Sphinx
which will generate warnings with old versions of docs.

This way, it's not immediately necessary to patch
all such versions.

This commit reverts
https://git.yoctoproject.org/yocto-autobuilder-helper/commit/?id=8273124feb9da2ffe93fcee7c4529d5597e1684a
which originally reverted
https://git.yoctoproject.org/yocto-autobuilder-helper/commit/?id=931d409b255a85f2217ca093d8391a678ce00ddb

Signed-off-by: Michael Opdenacker <michael.opdenacker@...>
---
scripts/run-docs-build | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index 648a29d..0f74520 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -63,7 +63,7 @@ for branch in 1.46 $(git branch --remote --contains "$first_sphinx_commit" --for
git checkout $branch
git checkout master releases.rst
make clean
- make publish
+ SPHINXOPTS="-j auto" make publish

if [ "$branch" = "master-next" ]; then
branch="next"
@@ -136,7 +136,7 @@ for branch in dunfell $(git branch --remote --contains "$first_sphinx_commit" --
fi

make clean
- make publish
+ SPHINXOPTS="-j auto" make publish

# Strip yocto- from tag names
branch=$(echo "$branch" | sed 's/yocto-//')
--
2.34.1


[meta-security][PATCH 2/2] security-build-image: add lkrg-module to build image

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-core/images/security-build-image.bb | 1 +
1 file changed, 1 insertion(+)

diff --git a/recipes-core/images/security-build-image.bb b/recipes-core/images/security-build-image.bb
index a8757f9..411cd20 100644
--- a/recipes-core/images/security-build-image.bb
+++ b/recipes-core/images/security-build-image.bb
@@ -3,6 +3,7 @@ DESCRIPTION = "A small image for building meta-security packages"
IMAGE_FEATURES += "ssh-server-openssh"

IMAGE_INSTALL = "\
+ ${@bb.utils.contains("DISTRO_FEATURES", "lkrg", "lkrg-module", "",d)} \
packagegroup-base \
packagegroup-core-boot \
packagegroup-core-security \
--
2.25.1


[meta-security][PATCH 1/2] chipsec: update to 1.8.5

Armin Kuster
 

minor recipe cleanup

Signed-off-by: Armin Kuster <akuster808@...>
---
.../{chipsec_git.bb => chipsec_1.8.5.bb} | 21 +++++++++----------
1 file changed, 10 insertions(+), 11 deletions(-)
rename recipes-security/chipsec/{chipsec_git.bb => chipsec_1.8.5.bb} (71%)

diff --git a/recipes-security/chipsec/chipsec_git.bb b/recipes-security/chipsec/chipsec_1.8.5.bb
similarity index 71%
rename from recipes-security/chipsec/chipsec_git.bb
rename to recipes-security/chipsec/chipsec_1.8.5.bb
index d6c3ff2..48dfe45 100644
--- a/recipes-security/chipsec/chipsec_git.bb
+++ b/recipes-security/chipsec/chipsec_1.8.5.bb
@@ -7,21 +7,17 @@ DESCRIPTION = "CHIPSEC is a framework for analyzing the security \
LICENSE = "GPL-2.0-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=bc2d1f9b427be5fb63f6af9da56f7c5d"

-SRC_URI = "git://github.com/chipsec/chipsec.git;branch=master;protocol=https \
- "
+DEPENDS = "virtual/kernel nasm-native"

-SRCREV = "b2a61684826dc8b9f622a844a40efea579cd7e7d"
-
-COMPATIBLE_HOST = "(i.86|x86_64).*-linux"
+SRC_URI = "git://github.com/chipsec/chipsec.git;branch=main;protocol=https"
+SRCREV = "07a532aac9f6c3d94b8895cf89336b6a2e60c0d9"

S = "${WORKDIR}/git"
-EXTRA_OEMAKE = "CC='${CC}' LDFLAGS='${LDFLAGS}' CFLAGS='${CFLAGS}'"
-
-DEPENDS = "virtual/kernel nasm-native python3-setuptools-native"
-RDEPENDS:${PN} += "python3 python3-modules"

inherit module setuptools3

+EXTRA_OEMAKE = "CC='${CC}' LDFLAGS='${LDFLAGS}' CFLAGS='${CFLAGS}'"
+
do_compile:append() {
cd ${S}/drivers/linux
oe_runmake KSRC=${STAGING_KERNEL_BUILDDIR}
@@ -31,5 +27,8 @@ do_install:append() {
install -m 0644 ${S}/drivers/linux/chipsec.ko ${D}${PYTHON_SITEPACKAGES_DIR}/chipsec/helper/linux
}

-FILES:${PN} += "${exec_prefix} \
-"
+COMPATIBLE_HOST = "(i.86|x86_64).*-linux"
+
+FILES:${PN} += "${exec_prefix}"
+
+RDEPENDS:${PN} = "python3 python3-modules"
--
2.25.1


Re: [PATCH yocto-autobuilder-helper 4/4] Revert "scripts: run-docs-build: do not turn sphinx warnings into errors"

Richard Purdie
 

On Wed, 2022-06-22 at 14:50 +0200, Michael Opdenacker wrote:
Hi Quentin

On 3/15/22 17:31, Quentin Schulz wrote:
From: Quentin Schulz <quentin.schulz@...>

The patch was meant as a quick temporary work-around to have the docs
built and published.

Now that releases where -W flag is set (turning warnings into errors)
are appropriately patched to make those warnings disappear (on Sphinx
v3.2.1 which is the one used on the builder), this patch can be reverted
so that next time a warning appears the doc building will fail but will
not destroy the doc website (because of commit
6a4e6ef18d1415c719be51c773d7c57cae5549cf "scripts: run-docs-build: make
the script fail hard ASAP when there's an error", since rsync will not
be run if any error happens before).

This reverts commit 931d409b255a85f2217ca093d8391a678ce00ddb.

Cc: Quentin Schulz <foss+yocto@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>
---
scripts/run-docs-build | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index 73cba3f..b9b331b 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -33,14 +33,14 @@ cd $bbdocs
echo Building bitbake master branch
git checkout master
make clean
-SPHINXOPTS="-j auto" make publish
+make publish
mkdir $outputdir/bitbake
cp -r ./_build/final/* $outputdir/bitbake
We're trying to build the docs with Sphinx 5.0.0 on a special branch,
and we're getting warnings causing the builds to fail:
https://autobuilder.yoctoproject.org/typhoon/#/builders/114/builds/487/steps/5/logs/stdio

If this patch hadn't been reverted, we would probably be fine.

What should we do now? Patch docs for all past Sphinx based releases? If
we tolerated warnings, we would have to do this less often when we want
to upgrade Sphinx.

In my opinion, another more trouble-free solution would be not to
regenerate docs for past releases, but instead only for the latest
commits in the branches we currently support.

What do you think?
We use the ability to regenerate previous releases to update the
switcher lists and potentially other style related changes in future
which keeps the docs looking consistent. We may have to disable the
errors on warnings :(

Cheers,

Richard


Re: [PATCH yocto-autobuilder-helper 4/4] Revert "scripts: run-docs-build: do not turn sphinx warnings into errors"

Michael Opdenacker
 

Hi Quentin

On 3/15/22 17:31, Quentin Schulz wrote:
From: Quentin Schulz <quentin.schulz@...>

The patch was meant as a quick temporary work-around to have the docs
built and published.

Now that releases where -W flag is set (turning warnings into errors)
are appropriately patched to make those warnings disappear (on Sphinx
v3.2.1 which is the one used on the builder), this patch can be reverted
so that next time a warning appears the doc building will fail but will
not destroy the doc website (because of commit
6a4e6ef18d1415c719be51c773d7c57cae5549cf "scripts: run-docs-build: make
the script fail hard ASAP when there's an error", since rsync will not
be run if any error happens before).

This reverts commit 931d409b255a85f2217ca093d8391a678ce00ddb.

Cc: Quentin Schulz <foss+yocto@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>
---
scripts/run-docs-build | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index 73cba3f..b9b331b 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -33,14 +33,14 @@ cd $bbdocs
echo Building bitbake master branch
git checkout master
make clean
-SPHINXOPTS="-j auto" make publish
+make publish
mkdir $outputdir/bitbake
cp -r ./_build/final/* $outputdir/bitbake
We're trying to build the docs with Sphinx 5.0.0 on a special branch, and we're getting warnings causing the builds to fail: https://autobuilder.yoctoproject.org/typhoon/#/builders/114/builds/487/steps/5/logs/stdio

If this patch hadn't been reverted, we would probably be fine.

What should we do now? Patch docs for all past Sphinx based releases? If we tolerated warnings, we would have to do this less often when we want to upgrade Sphinx.

In my opinion, another more trouble-free solution would be not to regenerate docs for past releases, but instead only for the latest commits in the branches we currently support.

What do you think?
Cheers
Michael.

--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


Yocto Project Status 21 June 2022 (WW25)

Neal Caidin
 

Current Dev Position: YP 4.1 M2

Next Deadline: 11th July 2022 YP 4.1 M2 Build


Next Team Meetings:


Key Status/Updates:

  • YP 3.1.17 was released

  • We’ve taken a decision to remove the versions from the sstate feeds so one sstate url now applies for all project active releases. This simplifies the user interface to that data and also makes it easier to mirror too.

  • Older data on the sstate mirror will age out over time if that data isn’t used on the autobuilder. This should mean the most active/useful data is shared.

  • It was generally a quiet week otherwise with various recipe upgrades.

  • Help is very much welcome in trying to resolve our autobuilder intermittent issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT


Ways to contribute:


YP 4.1 Milestone Dates:

  • YP 4.1 M2 build date 2022/07/11

  • YP 4.1 M2 Release date 2022/07/22

  • YP 4.1 M3 build date 2022/08/22

  • YP 4.1 M3 Release date 2022/09/02

  • YP 4.1 M4 build date 2022/10/03

  • YP 4.1 M4 Release date 2022/10/28


Upcoming dot releases:

  • YP 3.1.17 was released

  • YP 4.0.2 build date 2022/06/27

  • YP 4.0.2 Release date 2022/07/08

  • YP 3.1.18 build date 2022/07/18

  • YP 3.1.18 Release date 2022/07/29

  • YP 4.0.3 build date 2022/08/08

  • YP 4.0.3 Release date 2022/08/19

  • YP 3.1.19 build date 2022/08/29

  • YP 3.1.19 Release date 2022/09/09

  • YP 4.0.4 build date 2022/09/19

  • YP 4.0.4 Release date 2022/09/30

  • YP 3.1.20 build date 2022/10/10

  • YP 3.1.20 Release date 2022/10/21

  • YP 4.0.5 build date 2022/10/31

  • YP 4.0.5 Release date 2022/11/11


Tracking Metrics:


The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC


The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status


[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]



Neal Caidin
Program Manager, Program Management & Operations
The Linux Foundation
+1 (919) 238-9104 (w/h)
+1 (919) 949-1861 (m)




[meta-security][PATCH] packagegroup-core-security: skip mips firejail

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-core/packagegroup/packagegroup-core-security.bb | 2 ++
recipes-security/Firejail/firejail_0.9.70.bb | 2 ++
2 files changed, 4 insertions(+)

diff --git a/recipes-core/packagegroup/packagegroup-core-security.bb b/recipes-core/packagegroup/packagegroup-core-security.bb
index ef65428..05951da 100644
--- a/recipes-core/packagegroup/packagegroup-core-security.bb
+++ b/recipes-core/packagegroup/packagegroup-core-security.bb
@@ -41,6 +41,8 @@ RDEPENDS:packagegroup-security-utils = "\
${@bb.utils.contains("DISTRO_FEATURES", "pax", "pax-utils packctl", "",d)} \
"

+RDEPENDS:packagegroup-security-utils:remove:mipsarch = "firejail"
+
SUMMARY:packagegroup-security-scanners = "Security scanners"
RDEPENDS:packagegroup-security-scanners = "\
${@bb.utils.contains_any("TUNE_FEATURES", "riscv32 riscv64", "", " arpwatch",d)} \
diff --git a/recipes-security/Firejail/firejail_0.9.70.bb b/recipes-security/Firejail/firejail_0.9.70.bb
index fc9066b..35f7b07 100644
--- a/recipes-security/Firejail/firejail_0.9.70.bb
+++ b/recipes-security/Firejail/firejail_0.9.70.bb
@@ -58,4 +58,6 @@ pkg_postinst_ontarget:${PN} () {
${libdir}/${BPN}/fseccomp memory-deny-write-execute ${libdir}/${BPN}/seccomp.mdwx
}

+COMPATIBLE_MACHINE:mips64 = "(!.*mips64).*"
+
RDEPENDS:${PN} = "bash"
--
2.25.1


M+ & H bugs with Milestone Movements WW25

Stephen Jolley
 

All,

YP M+ or high bugs which moved to a new milestone in WW25 are listed below:

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

5322

Global DNS fallback mechanism not present in poky distro

randy.macleod@...

unassigned@...

4.1 M1

4.1 M3

 

7600

syslinux: port extX support patches to syslinux community

randy.macleod@...

sakib.sajal@...

4.1 M1

4.1 M3

 

10693

Add a testcase for multilib eSDK on the autobuilder

randy.macleod@...

Qi.Chen@...

4.1 M1

4.1 M2

 

12060

It is possible to specify a PACKAGE and a PKG_ rename that conflict

randy.macleod@...

unassigned@...

4.1 M1

4.1 M3

 

12279

enhance manifest not found warning

randy.macleod@...

Aryaman.Gupta@...

4.1 M1

4.1 M2

 

12917

Warnings from nightly-multilib builds (build-deps)

randy.macleod@...

unassigned@...

4.1 M1

4.1 M3

 

12937

Consistent naming scheme for deployed artifacts

richard.purdie@...

Martin.Jansa@...

4.1 M1

4.1 M3

 

13025

WIC image install support

kexin.hao@...

kexin.hao@...

4.1 M1

Future

 

13226

Support out of tree modules for alternate kernels

randy.macleod@...

bruce.ashfield@...

4.1 M1

4.1 M3

 

13251

Symlinks overridden when building multitple kernels

randy.macleod@...

bruce.ashfield@...

4.1 M1

4.1 M3

 

13288

pseudo should not follow symlinks in /proc

randy.macleod@...

sakib.sajal@...

4.1 M1

4.1 M2

 

14007

When qemu hangs, try to create a snapshot or core file.

randy.macleod@...

saul.wold@...

4.1 M1

4.1 M2

 

14553

insane.bbclass: host-user-contaminated QA doesn't skip the home directory

randy.macleod@...

unassigned@...

4.1 M1

4.1 M3

 

14691

Bitbake does not check for all required perl modules to build oe-core

randy.macleod@...

sakib.sajal@...

4.1 M1

4.1 M3

 

14745

cve-checker update to support NVD json 5.0 format

richard.purdie@...

akuster808@...

4.1 M1

4.1 M3

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Enhancements/Bugs closed WW25!

Stephen Jolley
 

All,

The below were the owners of enhancements or bugs closed during the last week!

Who

Count

michael.opdenacker@...

2

ross.burton@...

1

pavel@...

1

richard.purdie@...

1

randy.macleod@...

1

akuster808@...

1

Grand Total

7

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,

Below is the list as of top 39 bug owners as of the end of WW25 of who have open medium or higher bugs and enhancements against YP 4.1.   There are 91 possible work days left until the final release candidates for YP 4.1 needs to be released.

Who

Count

michael.opdenacker@...

37

ross.burton@...

26

david.reyna@...

23

bruce.ashfield@...

20

randy.macleod@...

15

richard.purdie@...

11

sakib.sajal@...

10

saul.wold@...

9

JPEWhacker@...

9

tim.orling@...

8

Aryaman.Gupta@...

5

jon.mason@...

4

mhalstead@...

4

akuster808@...

3

pgowda.cve@...

2

raj.khem@...

2

hongxu.jia@...

2

Qi.Chen@...

2

tvgamblin@...

2

jay.shen.teoh@...

1

martin.beeger@...

1

piotr.lobacz@...

1

nicolas.dechesne@...

1

thomas.perrot@...

1

ola.x.nilsson@...

1

behanw@...

1

sundeep.kokkonda@...

1

pavel@...

1

abongwabonalais@...

1

Martin.Jansa@...

1

liezhi.yang@...

1

shachar@...

1

mostthingsweb@...

1

alexandre.belloni@...

1

throos@...

1

alejandro@...

1

qorin.qorinna@...

1

open.source@...

1

aehs29@...

1

Grand Total

214

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 418 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@...

 


verification requested but nobody cares : bzImage while booting in secureboot mode #dunfell #yocto

Pavan <yc.pavan92@...>
 

Hi ,
I have been trying to enable Secureboot to my board having Intel-x86 architecture  and I am following the steps given in this link https://github.com/jiazhang0/meta-secure-core for Yocto Dunfell branch.

Problem: In non Secureboot mode Yocto Boots normally and everything works fine but when Secureboot is enabled till grub it boots and loads grub-menu then after
If I press boot option it will simply throw this error 
verification requested but nobody cares: bzImage
and stucks there.

I am not getting why this error is coming and what fixes to be made.

BTW grub version is grub-efi-2.04.

Below are the local.conf settings for Secureboot.

UEFI_SB = "1"
BUNDLE = "1"
GRUB_SIGN_VERIFY='0'
GRUB_SIGN_VERIFY_STRICT='0'
DEBUG_FLAGS_forcevariable = ""
IMAGE_INSTALL += "kernel-image-bzimage"
USER_CLASSES_remove = "image-prelink"
MASTER_KEYS_DIR = "/home/yocto/poky/meta-secure-core/meta-signing-key/scripts/user-keys"
 
IMA_KEYS_DIR = "${MASTER_KEYS_DIR}/ima_keys"
IMA_EVM_KEY_DIR = "${MASTER_KEYS_DIR}/ima_keys"
RPM_KEYS_DIR = "${MASTER_KEYS_DIR}/rpm_keys"
BOOT_KEYS_DIR = "${MASTER_KEYS_DIR}/boot_keys"
MOK_SB_KEYS_DIR = "${MASTER_KEYS_DIR}/mok_sb_keys"
SYSTEM_TRUSTED_KEYS_DIR = "${MASTER_KEYS_DIR}/system_trusted_keys"
SECONDARY_TRUSTED_KEYS_DIR = "${MASTER_KEYS_DIR}/secondary_trusted_keys"
MODSIGN_KEYS_DIR = "${MASTER_KEYS_DIR}/modsign_keys"
UEFI_SB_KEYS_DIR = "${MASTER_KEYS_DIR}/uefi_sb_keys"
GRUB_PUB_KEY = "${MASTER_KEYS_DIR}/boot_keys/boot_pub_key"
GRUB_PW_FILE = "${MASTER_KEYS_DIR}/boot_keys/boot_cfg_pw"
OSTREE_GPGDIR = "${MASTER_KEYS_DIR}/rpm_keys"
 
RPM_GPG_NAME = "PKG-SecureCore"
RPM_GPG_PASSPHRASE = "root"
RPM_FSK_PASSWORD = "root"
BOOT_GPG_NAME = "BOOT-SecureCore"
BOOT_GPG_PASSPHRASE = "root"
OSTREE_GPGID = "PKG-SecureCore"
OSTREE_GPG_PASSPHRASE = "root"
OSTREE_GRUB_PW_FILE = "${GRUB_PW_FILE}"
I am stuck with this issue from last 5 days ,please help me to solve this issue.

Thanks and Regards
Pavan







1261 - 1280 of 58593