Date   

Re: [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)

Raj, Khem <khem_raj@...>
 

Is the sato-sdk on qemuppc also intermittent issue 

From: tsc@... <tsc@...> on behalf of Richard Purdie <richard.purdie@...>
Sent: Wednesday, April 20, 2022 12:29:29 AM
To: qa-build-notification@... <qa-build-notification@...>; yocto@... <yocto@...>
Cc: Yocto TSC <tsc@...>; Mittal, Anuj <anuj.mittal@...>
Subject: [EXTERNAL] Re: [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)
 
On Wed, 2022-04-20 at 06:02 +0000, Pokybuild User wrote:
> A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder and is available at:
>
>
>     https://urldefense.com/v3/__https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1__;!!CQl3mcHX2A!XITvSVzpVXHE-hKopFwPzKrqpC-fi6MhLyNlACbodEIHW7S3PBGSenxMWW9GU4pG$
>
>
> Build hash information:
>
> bitbake: d01d8326331cfe59208674cfc53aa26c0028b313
> meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62
> meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20
> meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58
> meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
> meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d
> meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
> meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e
> oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660
> poky: eee9fba7b4d5d7a268a495688039027390894e6d

3.3.6 built but there were two issues. One was a qemu boot test failure for
core-image-sato-sdk on qemuppc-alt. I did have a look for logs but there aren't
any, qemu never seemed to start but nothing to indicate why. Since the other
tests for ppc passed, I think this is one of our general intermittent problems
on ppc and we should ignore it.

The other was some valgrind ptest failures. Those are known intermittent issues
and I believe also not significant from a release perspective.

Cheers,

Richard





SRC_URI from AWS codecommit with user and password #yocto

mail2uvijay@...
 

Hi All,

I have an application writing in Qt/QML for specific embedded target, The repo for this application is maintained in AWS codecommit which has user and password .
How to mentioned in the recipe SRC_URI to fetch from the repo which has user/password. I dont have SSH access for the same.
Let me know if you need more details.
tried this https://www.yoctoproject.org/pipermail/yocto/2014-April/019135.html no luck.

Regards,
Vijay


Re: package and booting an initramfs image

Zoran
 

Please, read carefully thru this yocto @ thread.

https://www.yoctoproject.org/pipermail/yocto/2018-July/041680.html

Zee
_______

On Tue, Apr 19, 2022 at 8:27 PM <toyonembedded@...> wrote:

I have a need to package my kernel, dtb, and rootfs manually and then boot this as an initramfs. I'm not sure which files from the deploy/images directory to use. I see there is an rootfs.cpio.gz file so I'm starting with that. If I unpack that I see the kernel Image and dtb in the /boot folder and what appears to be a filesystem in the rest. If I try to boot this as my kernel in u-boot I get this
Bad Linux ARM64 Image magic!
** No partition table - mmc 2 **
** No partition table - mmc 2 **

Does this cpio.gz file have everything I need? How do I boot with it and enter an initramfs?



IPv6 Autogeneration Not Persisting

Syed, Nabeel <nabsyed@...>
 

I’m trying to auto-generate IPv6 for interfaces on a ZPE Systems device but not able to. It keeps reverting to a value of ‘1’ after a reboot even though the config file clearly has ‘3’. Anyone run into something similar?

 

 

root@device:/home/admin# cat /proc/version

Linux version 5.4.137-yocto-standard (oe-user@oe-host) (gcc version 9.3.0 (GCC)) #1 SMP PREEMPT Sat Jul 31 06:19:39 UTC 2021

 

root@device:/home/admin# sysctl net.ipv6.conf.sfp0.addr_gen_mode

net.ipv6.conf.sfp0.addr_gen_mode = 1

 

root@device:/home/admin# cat /etc/sysctl.conf | grep net.ipv6.conf.sfp0.addr_gen_mode

net.ipv6.conf.sfp0.addr_gen_mode=3

 

 

Nabeel

 


[meta-security][PATCH] Add EROFS support to dm-verity-img class

Joshua Harley
 

Add support for the EROFS image, and it's compressed options, to the
dm-verity-img.bbclass setup, theoretically this is a simple addition to
the list of types however there is a quirk in how Poky handles the
filesystems in poky/meta/classes/image_types.bbclass.

Specifically the 'IMAGE_CMD' and 'IMAGE_FSTYPES' use a hyphen, e.g.
erofs-lz4, however in the image_type bbclass the task for that would be
"do_image_erofs_lz4", replacing the hyphen with an underscore.

As the dm-verity-img.bbclass adds a dependency to the wic image creation
on the do_image_* task then it fails as there is no
"do_image_erofs-lz4", so simply replace the hypen with an underscore.
---
classes/dm-verity-img.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/classes/dm-verity-img.bbclass b/classes/dm-verity-img.bbclass
index 16d395b..cc6a7f5 100644
--- a/classes/dm-verity-img.bbclass
+++ b/classes/dm-verity-img.bbclass
@@ -60,7 +60,7 @@ verity_setup() {
veritysetup --data-block-size=1024 --hash-offset=$SIZE format $OUTPUT $OUTPUT | tail -n +2 | process_verity
}

-VERITY_TYPES = "ext2.verity ext3.verity ext4.verity btrfs.verity"
+VERITY_TYPES = "ext2.verity ext3.verity ext4.verity btrfs.verity erofs.verity erofs-lz4.verity erofs-lz4hc.verity"
IMAGE_TYPES += "${VERITY_TYPES}"
CONVERSIONTYPES += "verity"
CONVERSION_CMD_verity = "verity_setup ${type}"
@@ -87,6 +87,6 @@ python __anonymous() {
# If we're using wic: we'll have to use partition images and not the rootfs
# source plugin so add the appropriate dependency.
if 'wic' in image_fstypes:
- dep = ' %s:do_image_%s' % (pn, verity_type)
+ dep = ' %s:do_image_%s' % (pn, verity_type.replace("-", "_"))
d.appendVarFlag('do_image_wic', 'depends', dep)
}
--
2.26.2


Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)

Richard Purdie
 

On Wed, 2022-04-20 at 06:02 +0000, Pokybuild User wrote:
A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder and is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1


Build hash information:

bitbake: d01d8326331cfe59208674cfc53aa26c0028b313
meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62
meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20
meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58
meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d
meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e
oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660
poky: eee9fba7b4d5d7a268a495688039027390894e6d
3.3.6 built but there were two issues. One was a qemu boot test failure for
core-image-sato-sdk on qemuppc-alt. I did have a look for logs but there aren't
any, qemu never seemed to start but nothing to indicate why. Since the other
tests for ppc passed, I think this is one of our general intermittent problems
on ppc and we should ignore it.

The other was some valgrind ptest failures. Those are known intermittent issues
and I believe also not significant from a release perspective.

Cheers,

Richard


QA notification for completed autobuilder build (yocto-3.3.6.rc1)

Pokybuild User <pokybuild@...>
 

A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder and is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1


Build hash information:

bitbake: d01d8326331cfe59208674cfc53aa26c0028b313
meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62
meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20
meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58
meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d
meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e
oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660
poky: eee9fba7b4d5d7a268a495688039027390894e6d



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@...


[meta-raspberrypi][PATCH] meta-raspberrypi: u-boot: remove the randundant patch

Meng Li
 

This patch had been merged into u-boot upstream. Its commit is
29f7d05a347a("dm: core: Move ofdata_to_platdata() call earlier").
So, remove the randundant patch to avoid building error.

Signed-off-by: Meng Li <Meng.Li@...>
---
...Move-ofdata_to_platdata-call-earlier.patch | 51 -------------------
recipes-bsp/u-boot/u-boot_%.bbappend | 3 --
2 files changed, 54 deletions(-)
delete mode 100644 recipes-bsp/u-boot/files/0001-dm-core-Move-ofdata_to_platdata-call-earlier.patch

diff --git a/recipes-bsp/u-boot/files/0001-dm-core-Move-ofdata_to_platdata-call-earlier.patch b/recipes-bsp/u-boot/files/0001-dm-core-Move-ofdata_to_platdata-call-earlier.patch
deleted file mode 100644
index 996ad10..0000000
--- a/recipes-bsp/u-boot/files/0001-dm-core-Move-ofdata_to_platdata-call-earlier.patch
+++ /dev/null
@@ -1,51 +0,0 @@
-From 336d86ebd146905cf4384912f4f27699b6e37c72 Mon Sep 17 00:00:00 2001
-From: Simon Glass <sjg@...>
-Date: Sun, 29 Dec 2019 21:19:17 -0700
-Subject: [PATCH] dm: core: Move ofdata_to_platdata() call earlier
-
-This method is supposed to extract platform data from the device tree. It
-should be done before the device itself is probed. Move it earlier in the
-device_probe() function.
-
-Upstream-Status: Backport
-
-Signed-off-by: Simon Glass <sjg@...>
----
- drivers/core/device.c | 14 +++++++-------
- 1 file changed, 7 insertions(+), 7 deletions(-)
-
-diff --git a/drivers/core/device.c b/drivers/core/device.c
-index 4e03708..291ff4c 100644
---- a/drivers/core/device.c
-+++ b/drivers/core/device.c
-@@ -375,6 +375,13 @@ int device_probe(struct udevice *dev)
- return 0;
- }
-
-+ if (drv->ofdata_to_platdata &&
-+ (CONFIG_IS_ENABLED(OF_PLATDATA) || dev_has_of_node(dev))) {
-+ ret = drv->ofdata_to_platdata(dev);
-+ if (ret)
-+ goto fail;
-+ }
-+
- seq = uclass_resolve_seq(dev);
- if (seq < 0) {
- ret = seq;
-@@ -411,13 +418,6 @@ int device_probe(struct udevice *dev)
- goto fail;
- }
-
-- if (drv->ofdata_to_platdata &&
-- (CONFIG_IS_ENABLED(OF_PLATDATA) || dev_has_of_node(dev))) {
-- ret = drv->ofdata_to_platdata(dev);
-- if (ret)
-- goto fail;
-- }
--
- /* Only handle devices that have a valid ofnode */
- if (dev_of_valid(dev)) {
- /*
---
-2.7.4
-
diff --git a/recipes-bsp/u-boot/u-boot_%.bbappend b/recipes-bsp/u-boot/u-boot_%.bbappend
index 4587d3d..e50acf5 100644
--- a/recipes-bsp/u-boot/u-boot_%.bbappend
+++ b/recipes-bsp/u-boot/u-boot_%.bbappend
@@ -6,9 +6,6 @@ SRC_URI:append:rpi = " \

SRC_URI:append:rpi = " file://0001-rpi-always-set-fdt_addr-with-firmware-provided-FDT-address.patch"

-# special fix for raspberrypi-cm3
-SRC_URI:append:raspberrypi-cm3 = " file://0001-dm-core-Move-ofdata_to_platdata-call-earlier.patch"
-
DEPENDS:append:rpi = " u-boot-default-script"

do_install:append:rpi () {
--
2.35.1


package and booting an initramfs image

Embedded 1
 

I have a need to package my kernel, dtb, and rootfs manually and then boot this as an initramfs. I'm not sure which files from the deploy/images directory to use. I see there is an rootfs.cpio.gz file so I'm starting with that. If I unpack that I see the kernel Image and dtb in the /boot folder and what appears to be a filesystem in the rest. If I try to boot this as my kernel in u-boot I get this
Bad Linux ARM64 Image magic!
** No partition table - mmc 2 **
** No partition table - mmc 2 **

Does this cpio.gz file have everything I need? How do I boot with it and enter an initramfs?


[RFC PATCH yocto-autobuilder-helper 6/6] scripts: run-docs-build: reuse logic to link to latest tag

Quentin Schulz
 

From: Quentin Schulz <quentin.schulz@...>

Since the latest tag already has a specific handling in the forloop,
let's just move the symlink creation inside the forloop.

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

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index faba0fe..ecc5332 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -142,6 +142,8 @@ for branch in dunfell $(git branch --remote --contains "$first_sphinx_commit" --
branch=""
mkdir $outputdir/$latest_tag
cp -r ./_build/final/* $outputdir/$latest_tag
+ echo Linking to $latest_tag as current
+ ln -s $latest_tag $outputdir/current
elif [ "$branch" = "transition" ]; then
branch=""
else
@@ -153,11 +155,6 @@ for branch in dunfell $(git branch --remote --contains "$first_sphinx_commit" --
git clean -f
done

-# get current release (e.g. most recent tag), and add a 'current' link
-tag=$(git tag --list 'yocto-*' | sort --version-sort | tail -1 | cut -c7-)
-echo Linking to $tag as current
-ln -s $tag $outputdir/current
-
# Update bitbake switchers.js with the copy from master ypdocs
cd $outputdir/bitbake
find . -name switchers.js -exec cp $outputdir/current/_static/switchers.js {} \;
--
2.35.1


[RFC PATCH yocto-autobuilder-helper 5/6] scripts: run-docs-build: make latest documentation tag the default version

Quentin Schulz
 

From: Quentin Schulz <quentin.schulz@...>

Currently, the master branch is the default branch being displayed by
default when reaching the Yocto docs website. When big changes are
implemented for the next release, these are shown immediately to the
user, even though there is currently no release available for those
changes. This is an issue when e.g. behaviors are changed, new features
are added, variables get renamed or some syntaxes change because the
user might try to use things that aren't available to them yet.

I believe more people are using released version of Yocto
Project/Bitbake than people working on latest master. So let's make the
default version of the docs the latest tag (in terms of version number,
not date of tagging) to avoid too much confusion.

The master branch of the docs is now available at /dev subpath.

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

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index 8044b60..faba0fe 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -46,6 +46,9 @@ mkdir $outputdir/bitbake
# We copy the releases.rst file from master so that all versions of the docs
# see the latest releases.
first_sphinx_commit=84ccba0f4aff91528f764523fe1205a354c889ed
+
+latest_branch=$(git branch --remote --contains "$first_sphinx_commit" --format '%(refname:lstrip=3)' --sort='-version:refname' | grep --max-count=1 "[0-9]*\.[0-9]*")
+
for branch in 1.46 $(git branch --remote --contains "$first_sphinx_commit" --format '%(refname:lstrip=3)'); do
if [ "$branch" = "HEAD" ]; then
continue
@@ -61,7 +64,12 @@ for branch in 1.46 $(git branch --remote --contains "$first_sphinx_commit" --for
branch="next"
mkdir $outputdir/bitbake/$branch
elif [ "$branch" = "master" ]; then
+ branch="dev"
+ mkdir $outputdir/bitbake/$branch
+ elif [ "$branch" = "$latest_branch" ]; then
branch=""
+ mkdir $outputdir/bitbake/$latest_branch
+ cp -r ./_build/final/* $outputdir/bitbake/$latest_branch
else
mkdir $outputdir/bitbake/$branch
fi
@@ -83,6 +91,9 @@ cd $ypdocs
# Again, keeping even the no longer supported releases (see above comment)
first_sphinx_commit=01dd5af7954e24552aca022917669b27bb0541ed
first_dunfell_sphinx_commit=c25fe058b88b893b0d146f3ed27320b47cdec236
+
+latest_tag=$(git tag --contains "$first_sphinx_commit" --contains "$first_dunfell_sphinx_commit" --sort="version:refname" 'yocto-*' | tail -1 | sed 's/yocto-//')
+
for branch in dunfell $(git branch --remote --contains "$first_sphinx_commit" --format '%(refname:lstrip=3)') $(git tag --contains "$first_sphinx_commit" --contains "$first_dunfell_sphinx_commit" 'yocto-*') transition; do
if [ "$branch" = "HEAD" ]; then
continue
@@ -124,7 +135,14 @@ for branch in dunfell $(git branch --remote --contains "$first_sphinx_commit" --
if [ "$branch" = "master-next" ]; then
branch="next"
mkdir $outputdir/$branch
- elif [ "$branch" = "master" ] || [ "$branch" = "transition" ]; then
+ elif [ "$branch" = "master" ]; then
+ branch="dev"
+ mkdir $outputdir/$branch
+ elif [ "$branch" = "$latest_tag" ]; then
+ branch=""
+ mkdir $outputdir/$latest_tag
+ cp -r ./_build/final/* $outputdir/$latest_tag
+ elif [ "$branch" = "transition" ]; then
branch=""
else
mkdir $outputdir/$branch
--
2.35.1


[PATCH yocto-autobuilder-helper 4/6] scripts: run-docs-build: use set_versions.py and switchers.js.in from master

Quentin Schulz
 

From: Quentin Schulz <quentin.schulz@...>

set_versions.py and switchers.js.in need to be up-to-date so that a
consistent behavior is kept between different branches and tags of the
documentation.

Right now, kirkstone branch is lagging behind master and therefore does
not have the latest changes from master (e.g. the new obsolete
algorithm, which obviously isn't an issue right now, but will be in two
years). Using master version for those scripts also lightens the
maintenance burden.

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

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index a060a31..8044b60 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -102,11 +102,9 @@ for branch in dunfell $(git branch --remote --contains "$first_sphinx_commit" --
git am "${scriptdir}/docs-build-patches/${branch}/"000*
fi

- git checkout master releases.rst
+ git checkout master releases.rst sphinx-static/switchers.js.in set_versions.py
if [ -e poky.yaml ]; then
- git checkout master sphinx-static/switchers.js.in
cp poky.yaml poky.yaml.in
- git checkout master set_versions.py
case $branch in
yocto-*)
./set_versions.py $(echo "$branch" | sed 's/yocto-//')
--
2.35.1


[PATCH yocto-autobuilder-helper 3/6] scripts: run-docs-build: add option to skip upstream rsync

Quentin Schulz
 

From: Quentin Schulz <quentin.schulz@...>

The rsync only makes sense for the Autobuilder as most people don't have
access to docs@.... Therefore, to allow for easier
contribution to this script, let's allow to skip the rsync so the script
can continue to run.

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

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index 6569928..a060a31 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -8,6 +8,7 @@
# Can be found here: https://autobuilder.yocto.io/pub/buildtools/
# - docbookarchive as the path to old (pre 3.1.5 and Sphinx migration) docs tarball
# Can be found here: https://downloads.yoctoproject.org/mirror/docbook-mirror/docbook-archives-20201105.tar.xz
+# - PUBLISH (0/1) for whether the files should be rsync'ed to docs.yoctoproject.org

set -e
set -u
@@ -20,6 +21,7 @@ bbdocs=$(realpath "$3/doc/")
docs_buildtools=${docs_buildtools:-/srv/autobuilder/autobuilder.yocto.io/pub/buildtools/x86_64-buildtools-docs-nativesdk-standalone-3.2+snapshot-20201105.sh}
outputdir=$builddir/output
scriptdir="$(dirname "$(readlink -f "${BASH_SOURCE[0]}")")"
+PUBLISH=${PUBLISH:-1}


cd $builddir
@@ -68,10 +70,12 @@ for branch in 1.46 $(git branch --remote --contains "$first_sphinx_commit" --for
git reset --hard
done

-# only sync bitbake folder for now. We need bitbake to be published first
-# since the bitbake intersphinx index will be downloaded to build yocto-docs
-cd $outputdir
-rsync -irlp --checksum --ignore-times --delete bitbake docs@...:docs/
+if [ "$PUBLISH" -ne 0 ]; then
+ # only sync bitbake folder for now. We need bitbake to be published first
+ # since the bitbake intersphinx index will be downloaded to build yocto-docs
+ cd $outputdir
+ rsync -irlp --checksum --ignore-times --delete bitbake docs@...:docs/
+fi

cd $ypdocs

@@ -142,5 +146,7 @@ ln -s $tag $outputdir/current
cd $outputdir/bitbake
find . -name switchers.js -exec cp $outputdir/current/_static/switchers.js {} \;

-cd $outputdir
-rsync -irlp --checksum --ignore-times --delete . docs@...:docs/
+if [ "$PUBLISH" -ne 0 ]; then
+ cd $outputdir
+ rsync -irlp --checksum --ignore-times --delete . docs@...:docs/
+fi
--
2.35.1


[PATCH yocto-autobuilder-helper 2/6] scripts: run-docs-build: allow to pass buildtools script and docbook tarball paths

Quentin Schulz
 

From: Quentin Schulz <quentin.schulz@...>

Currently, the path to buildtools script and docbook tarball are
hardcoded to work on Yocto Project Autobuilder. However, this makes it
harder to contribute to this script because it is very unlikely those
paths exist on a developer PC.

Instead, let's allow to override variables by using the environment and
make the current hardcoded values the default ones.

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

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index 6e25549..6569928 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -2,6 +2,12 @@
# Called with $1 as the build directory
# $2 as the path to yocto-docs
# $3 as the path to bitbake
+#
+# Environment variables:
+# - docs_buildtools as the path to buildtools script for the docs.
+# Can be found here: https://autobuilder.yocto.io/pub/buildtools/
+# - docbookarchive as the path to old (pre 3.1.5 and Sphinx migration) docs tarball
+# Can be found here: https://downloads.yoctoproject.org/mirror/docbook-mirror/docbook-archives-20201105.tar.xz

set -e
set -u
@@ -11,7 +17,7 @@ set -x
builddir=$(realpath "$1")
ypdocs=$(realpath "$2/documentation/")
bbdocs=$(realpath "$3/doc/")
-docs_buildtools=/srv/autobuilder/autobuilder.yocto.io/pub/buildtools/x86_64-buildtools-docs-nativesdk-standalone-3.2+snapshot-20201105.sh
+docs_buildtools=${docs_buildtools:-/srv/autobuilder/autobuilder.yocto.io/pub/buildtools/x86_64-buildtools-docs-nativesdk-standalone-3.2+snapshot-20201105.sh}
outputdir=$builddir/output
scriptdir="$(dirname "$(readlink -f "${BASH_SOURCE[0]}")")"

@@ -23,7 +29,7 @@ $docs_buildtools -y -d $builddir/buildtools

# Getting the old docbook built docs from an archive. Not rebuilding them.
#wget https://downloads.yoctoproject.org/mirror/docbook-mirror/docbook-archives-20201105.tar.xz
-docbookarchive=/srv/autobuilder/autobuilder.yocto.io/pub/docbook-mirror/docbook-archives-20201105.tar.xz
+docbookarchive=${docbookarchive:-/srv/autobuilder/autobuilder.yocto.io/pub/docbook-mirror/docbook-archives-20201105.tar.xz}
mkdir $outputdir
cd $outputdir
echo Extracing old content from archive
--
2.35.1


[PATCH yocto-autobuilder-helper 1/6] scripts: run-docs-build: transform argument paths into absolute paths

Quentin Schulz
 

From: Quentin Schulz <quentin.schulz@...>

The script is written in such a way that absolute paths are expected.
Instead of failing weirdly at some point in the script, let's just make
all paths passed to this script absolute by calling realpath on them.

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

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index c501feb..6e25549 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -8,9 +8,9 @@ set -u
set -o pipefail
set -x

-builddir=$1
-ypdocs=$2/documentation/
-bbdocs=$3/doc/
+builddir=$(realpath "$1")
+ypdocs=$(realpath "$2/documentation/")
+bbdocs=$(realpath "$3/doc/")
docs_buildtools=/srv/autobuilder/autobuilder.yocto.io/pub/buildtools/x86_64-buildtools-docs-nativesdk-standalone-3.2+snapshot-20201105.sh
outputdir=$builddir/output
scriptdir="$(dirname "$(readlink -f "${BASH_SOURCE[0]}")")"
--
2.35.1


[RFC PATCH] docs: update Bitbake objects.inv location for master branch

Quentin Schulz
 

From: Quentin Schulz <quentin.schulz@...>

master branch of Bitbake is now located at docs.yoctoproject.org/dev
instead of docs.yoctoproject.org so let's update the switchers and
set_versions.py to reflect that change.

Cc: Quentin Schulz <foss+yocto@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>
---
documentation/set_versions.py | 2 +-
documentation/sphinx-static/switchers.js.in | 6 ++----
2 files changed, 3 insertions(+), 5 deletions(-)

diff --git a/documentation/set_versions.py b/documentation/set_versions.py
index 8ae02b11f..0086e9bea 100755
--- a/documentation/set_versions.py
+++ b/documentation/set_versions.py
@@ -128,7 +128,7 @@ else:
if branch == "master":
ourseries = devbranch
docconfver = "dev"
- bitbakeversion = ""
+ bitbakeversion = "dev"
elif branch in release_series:
ourseries = branch
if branch in bitbake_mapping:
diff --git a/documentation/sphinx-static/switchers.js.in b/documentation/sphinx-static/switchers.js.in
index 408e23a71..4966b3033 100644
--- a/documentation/sphinx-static/switchers.js.in
+++ b/documentation/sphinx-static/switchers.js.in
@@ -149,11 +149,9 @@ by https://git.yoctoproject.org/yocto-autobuilder-helper/tree/scripts/run-docs-b
var docroot = get_docroot_url()

var new_versionpath = selected_version + '/';
- if (selected_version == "dev")
- new_versionpath = '';

- // dev versions have no version prefix
- if (current_version == "dev") {
+ // latest tag is also the default page (without version information)
+ if (docroot.endsWith(current_version + '/') == false) {
var new_url = docroot + new_versionpath + url.replace(docroot, "");
var fallback_url = docroot + new_versionpath;
} else {
--
2.35.1


Yocto Project Status WW16`22

Richard Purdie
 

Current Dev Position: YP 4.0 rc3
Next Deadline: 29th April 2022 YP 4.0 final release

Next Team Meetings:

Key Status/Updates:
  • The next release, kirkstone will be 4.0 (previously known as 3.5) and will be bitbake 2.0 based.
  • The third release candidate build for YP 4.0 (3.5) is now in QA.
  • rc1 had several issues such as edgerouter not booting, a uninative gcc 12 issue and broken icons in sato that made it inappropriate for release. rc2 triggered a number of autobuilder intermittent issues, there were tweaks to some of the rc1 fixes needed, several CVEs and a systemd/bluetooth issue that resulted in an rc3.
  • YP 3.3.6, the final hardknott release will build after 4.0.
  • If people see intermittent issues in their own builds, particularly if they’re the same as intermittent issues seen on the autobuilder, please do comment in the bugs mentioning when they happen as the frequency information does help us prioritize fixing the most common issues.
  • Intermittent issues continue to be at high levels and help is very much welcome in trying to resolve them. 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.0 Milestone Dates:
  • YP 4.0 is in QA
  • YP 4.0 Release date 2022/04/29

YP 4.1 Milestone Dates:
  • YP 4.1 M1 build date 2022/05/30
  • YP 4.1 M1 Release date 2022/06/10
  • 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.3.6 build date 2022/03/28
  • YP 3.3.6 Release date 2022/04/08
  • YP 3.1.16 build date 2022/04/25
  • YP 3.1.16 Release date 2022/05/06
  • YP 3.4.4 build date 2022/05/02
  • YP 3.4.4 Release date 2022/05/13
  • YP 4.0.1 build date 2022/05/16
  • YP 4.0.1 Release date 2022/05/27
  • YP 3.1.17 build date 2022/06/06
  • YP 3.1.17 Release date 2022/06/17
  • 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:

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!]



Archived content:

Tip of the Week:
  • The scripts in ${WORKDIR}/temp/run.XXX for shell tasks can be quickly hacked and used for standalone debugging by replacing the function call at the end with “bash -i” which will then drop you into a shell environment matching the task being debugged (minus the fakeroot context). 
  • Bonus marks for anyone sending a patch to add the fakeroot context as comments at the start of the scripts.
  • (send any tips you’d like to see here to Stephen or Richard)


Re: NPM support on Dunfell

Joel Winarske
 

The takeaways using inherit npm:

1. Does not support 'scoped packages'

2. fetching is not multi-threaded.  A NPM based recipe will run uni-proc with a considerable amount of overhead; each package is pulled and cached independently.  Whereas "npm install" or "npm ci" runs multi-threaded.

For my use case I used base.bbclass, and implemented it all manually.  The downside with this approach is there is no long term support via DL_DIR.

A reference for others that might hit this:

Cheers,
Joel


On Mon, Apr 11, 2022 at 7:18 PM Joel Winarske <joel.winarske@...> wrote:
I'm seeing some gaps and performance issues.

Examples:
1. Setting NPM_INSTALL_DEV = "1" I am rewarded with:

169npm ERR! Could not install from "../../__w/meta-flutter/rpi4-drm-dunfell-latest/raspberrypi4-64/tmp/work/aarch64-poky-linux/webthings-gateway/1.0.0+gitAUTOINC+4c600fc973-r0/git/node_modules/@babel/compat-data" as it does not contain a package.json file.
The upstream build uses equivalent to:
    npm --user root --cache "${NPM_CACHE}" ci
    ./node_modules/.bin/webpack
    npm --cache "${NPM_CACHE}" prune --production

2. Running npm_do_configure is taking 48+ minutes.  Granted it's a large project, but basically the configure task is running uni-proc.

Who is the POC supporting NPM on Dunfell?

Thanks,
Joel


M+ & H bugs with Milestone Movements WW16

Stephen Jolley
 

All,

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

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

12279

enhance manifest not found warning

randy.macleod@...

kai.kang@...

3.5 M4

3.6 M1

 

12368

persistent bitbake server does not re-parse if previous build was ctrl+C'd

richard.purdie@...

richard.purdie@...

3.5 M4

3.6 M1

 

13123

package.PackageTests.test_gdb_hardlink_debug failed

randy.macleod@...

randy.macleod@...

3.5 M4

3.6 M1

 

13278

If git protocol doesn't work, you get a tar.gz clone from PREMIRROR which has git protocol origin

richard.purdie@...

richard.purdie@...

3.5 M4

3.6 M1

 

13311

xargs: fdleak.c:396: complain_about_leaky_fds: Assertion `no_leaks' failed.

randy.macleod@...

unassigned@...

3.5 M4

3.6 M2

 

13417

Development manual coverage of devtool

randy.macleod@...

michael.opdenacker@...

3.6

3.6 M1

 

13424

devupstream doesn't work with mutilib

richard.purdie@...

richard.purdie@...

3.5 M4

3.6 M1

 

13520

many valgrind tests fail for arm64

randy.macleod@...

randy.macleod@...

3.5 M4

3.6 M1

 

13599

Enhancement: Detect variables that shouldn't be defined in image scope, but in global (distro) scope

richard.purdie@...

richard.purdie@...

3.5 M4

3.6 M1

 

13908

segfault in mb-wm on qemux86-64 intermittently

randy.macleod@...

ross@...

3.5 M4

3.6 M2

 

14118

systemd services not enabled when using package feed

randy.macleod@...

unassigned@...

3.5 M4

3.6 M2

 

14126

resolvconf incompatible with busybox flock

randy.macleod@...

newcomer@...

3.5 M4

3.6 M1

 

14156

fetch/gitsm: submodules are fetched as mirrored and not working as expected

richard.purdie@...

richard.purdie@...

3.5 M4

3.6 M1

 

14201

Bitbake server intermittent timeout

randy.macleod@...

unassigned@...

3.5 M4

3.6 M1

 

14263

AB-INT PTEST: lttng-tools ptest intermittent failure

randy.macleod@...

unassigned@...

3.5 M4

3.6 M1

 

14316

Write a script to populate swatbot from buildbot

randy.macleod@...

alexandre.belloni@...

3.6

3.6 M1

 

14368

Where can I find how to produce containers?

randy.macleod@...

michael.opdenacker@...

3.6

3.6 M2

 

14385

mode of sstate files created under pseudo

richard.purdie@...

richard.purdie@...

3.5 M4

3.6 M1

 

14410

[documentation] clarity regarding specifying license of layer/recipes versus layer/recipe results

randy.macleod@...

michael.opdenacker@...

3.6

3.6 M1

 

14486

qemu rootfs copy is taking too much time

randy.macleod@...

randy.macleod@...

3.5 M4

3.6 M1

 

14493

BB_GIT_SHALLOW is not documented

randy.macleod@...

michael.opdenacker@...

3.6

3.6 M1

 

14509

Add security configuration documentation

randy.macleod@...

michael.opdenacker@...

3.6

3.6 M2

 

14523

oe-pkgdata-util list-pkg-files doesn't ignore target-sdk-provides-dummy.bb

randy.macleod@...

randy.macleod@...

3.5 M4

3.6 M1

 

14536

Dev Manual, "Selecting an Initialization Manager", should mention INIT_MANAGER

randy.macleod@...

michael.opdenacker@...

3.6

3.6 M2

 

14553

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

randy.macleod@...

abongwabonalais@...

3.5 M4

3.6 M1

 

14611

qemuarm64 testimage Target didn't reach login banner

randy.macleod@...

randy.macleod@...

3.5 M4

3.6 M1

 

14620

QA error not seen when reusing SSTATE

richard.purdie@...

richard.purdie@...

3.5 M4

3.6 M1

 

14642

Yocto-check-layer add patch Upstream-Status check

randy.macleod@...

unassigned@...

3.5 M4

3.6 M1

 

14665

AB-INT: prservice.BitbakePrTests.test_import_export_replace_db failure

richard.purdie@...

unassigned@...

3.5 M4

3.6 M1

 

14667

Document variable scope

randy.macleod@...

michael.opdenacker@...

3.6

3.6 M1

 

14670

Promoting a Function to a Task: example is wrong

randy.macleod@...

michael.opdenacker@...

3.6

3.6 M2

 

14677

systemd.SystemdServiceTests.test_systemd_disable_enable intermittent failure: no filesystem space on target

randy.macleod@...

randy.macleod@...

3.5 M4

3.6 M1

 

14694

logrotate.LogrotateTest.test_logrotate_wtmp failure: /var/lib/logrotate.status is already locked

randy.macleod@...

unassigned@...

3.5 M4

3.6 M2

 

14721

Intermittent runqueue issue re-running populate_sysroot_setscene after populate_sysroot

richard.purdie@...

richard.purdie@...

3.5 M4

3.6 M1

 

14783

[QA 4.0.rc1] - Abnormal responsive time for File Manager PCManFM application

randy.macleod@...

jay.shen.teoh@...

Future

3.6 M1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Enhancements/Bugs closed WW16

Stephen Jolley
 

All,

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

Who

Count

richard.purdie@...

15

randy.macleod@...

8

alexandre.belloni@...

2

tim.orling@...

1

gregorylumen@...

1

matthias.schoepfer@...

1

jay.shen.teoh@...

1

Grand Total

29

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 

1901 - 1920 of 58675