Yocto Project - User contributions [en]

3.4 Release Notes WIP

2021-10-22T03:20:40Z

PaulEggleton:

<pre>

--------------
Contributors
--------------

Thanks to the following people who contributed to this release:

Adam Romanek
Alejandro Hernandez Samaniego
Alexander Kanavin
Alexandre Belloni
Alexey Brodkin
Alex Stewart
Alistair Francis
Anatol Belski
Anders Wallin
Andrea Adami
Andreas Müller
Andrej Valek
Andres Beltran
Andrey Zhizhikin
Anibal Limon
Anthony Bagwell
Anton Blanchard
Anuj Mittal
Armin Kuster
Asfak Rahman
Bastian Krause
Bernhard Rosenkränzer
Bruce Ashfield
Carlos Rafael Giani
Chandana kalluri
Changhyeok Bae
Changqing Li
Chanho Park
Chen Qi
Chris Laplante
Christophe Chapuis
Christoph Muellner
Claudius Heine
Damian Wrobel
Daniel Ammann
Daniel Gomez
Daniel McGregor
Daniel Wagenknecht
Denys Dmytriyenko
Devendra Tewari
Diego Sueiro
Dmitry Baryshkov
Douglas Royds
Dragos-Marian Panait
Drew Moseley
Enrico Scholz
Fabio Berton
Florian Amstutz
Gavin Li
Guillaume Champagne
Harald Brinkmann
Henning Schild
He Zhe
Hongxu Jia
Hsia-Jun (Randy) Li
Jean Bouchard
Joe Slater
Jonas Höppner
Jon Mason
Jose Quaresma
Joshua Watt
Justin Bronder
Kai Kang
Kenfe-Mickael Laventure
Kevin Hao
Khairul Rohaizzat Jamaluddin
Khem Raj
Kiran Surendran
Konrad Weihmann
Kristian Klausen
Kyle Russell
Lee Chee Yang
Lei Maohui
Luca Boccassi
Marco Felsch
Marcus Comstedt
Marek Vasut
Mark Hatle
Markus Volk
Marta Rybczynska
Martin Jansa
Matthias Klein
Matthias Schiffer
Matt Madison
Matt Spencer
Max Krummenacher
Michael Halstead
Michael Ho
Michael Opdenacker
Mike Crowe
Mikko Rapeli
Ming Liu
Mingli Yu
Minjae Kim
Nicolas Dechesne
Niels Avonds
Nikolay Papenkov
Nisha Parrakat
Olaf Mandel
Oleksandr Kravchuk
Oleksandr Popovych
Oliver Kranz
Otavio Salvador
Patrick Williams
Paul Barker
Paul Eggleton
Paul Gortmaker
Paulo Cesar Zaneti
Peter Bergin
Peter Budny
Peter Kjellerstedt
Petr Vorel
Przemyslaw Gorszkowski
Purushottam Choudhary
Qiang Zhang
Quentin Schulz
Ralph Siemsen
Randy MacLeod
Ranjitsinh Rathod
Rasmus Villemoes
Reto Schneider
Richard Purdie
Richard Weinberger
Robert Joslyn
Robert P. J. Day
Robert Yang
Romain Naour
Ross Burton
Sakib Sajal
Samuli Piippo
Saul Wold
Scott Murray
Scott Weaver
Stefan Ghinea
Stefan Herbrechtsmeier
Stefano Babic
Stefan Wiehler
Steve Sakoman
Teoh Jay Shen
Thomas Perrot
Tim Orling
Tom Pollard
Tom Rini
Tony Battersby
Tony Tascioglu
Trevor Gamblin
Trevor Woerner
Ulrich Ölmann
Valentin Danaila
Vinay Kumar
Vineela Tummalapalli
Vinícius Ossanes Aquino
Vivien Didelot
Vyacheslav Yurkov
Wang Mingyu
Wes Lindauer
William A. Kennington III
Yanfei Xu
Yann Dirson
Yi Fan Yu
Yi Zhao
Zang Ruochen
Zheng Ruoqin
Zoltán Böszörményi

-----------------------------
New Features / Enhancements
-----------------------------

* Linux kernel 5.14, glibc 2.34 and ~280 other recipe upgrades
* Switched override character to ':' (replacing '_') for more robust parsing and improved performance - see migration guide for help on migrating
* Rust integrated into core, providing rust support for cross-compilation and SDK
* New create-spdx class for creating SPDX SBoM documents
* New recipes: cargo, core-image-ptest-all, core-image-ptest-fast, core-image-weston-sdk, erofs-utils, gcompat, gi-docgen, libmicrohttpd, libseccomp, libstd-rs, perlcross, python3-markdown, python3-pyyaml, python3-smartypants, python3-typogrify, rust, rust-cross, rust-cross-canadian, rust-hello-world, rust-llvm, rust-tools-cross-canadian, rustfmt, xwayland
* Several optimisations to reduce unnecessary task dependencies for faster builds
* seccomp integrated into core, with additional enabling for gnutls, systemd, qemu
* New overlayfs class to help generate overlayfs mount units
* debuginfod support now enabled by default
* Switched several recipes over to using OpenSSL instead of GnuTLS (wpa-supplicant, curl, glib-networking) or disable GnuTLS (cups) by default
* Improvements to LTO plugin installation and reproducibility
* Architecture-specific enhancements:
- glibc: Enable memory tagging for aarch64
- testimage: remove aarch64 xorg exclusion
- arch-arm*: add better support for gcc march extensions
- tune-cortexm*: add support for all Arm Cortex-M processors
- tune-cortexr*: add support for all Arm Cortex-R processors
- arch-armv4: Allow -march=armv4
- qemuarm*: use virtio graphics
- baremetal-helloworld: Enable RISC-V 64/32 port
- ldconfig-native: Add RISC-V support
- qemuriscv: Enable 4 core emulation
- Add ARC support in gdb, dpkg, dhcpcd
- conf/machine-sdk: Add ppc64 SDK machine
- libjpeg-turbo: Handle powerpc64le without Altivec
- pixman: Handle PowerPC without Altivec
- mesa: enable gallium Intel drivers when building for x86
- mesa: enable crocus driver for older Intel graphics
* Kernel-related enhancements:
- Support zstd-compressed modules and initramfs images
- Allow opt-out of split kernel modules
- linux-yocto-dev: base AUTOREV on specified version
- kernel-yocto: provide debug / summary information for metadata
- kernel-uboot: Handle gzip and lzo compression options
- linux-yocto/5.14: added devupstream support
- linux-yocto: add vfat KERNEL_FEATURE when MACHINE_FEATURES include vfat
- linux-yocto: enable TYPEC_TCPCI in usbc fragment
* Image-related enhancements:
- New erofs, erofs-lz4 and erofs-lz4hc image types
- New squashfs-zst and cpio.zst image types
- New lic-pkgs IMAGE_FEATURES item to install all license packages
- Added zsync metadata conversion support
- Use xargs to set file timestamps for significant (>90%) do_image speedup
- Find .ko.gz and .ko.xz kernel modules as well when determining need to run depmod on an image
- Show formatted error messages instead of tracebacks for systemctl errors
- No longer ignore installation failures in complementary package installation
- Remove ldconfig auxiliary cache when not needed
* wic enhancements:
- Added erofs filesystem support
- Added --extra-space argument to leave extra space after last partition
- Added --no-fstab-update part option to allow using the stock fstab
- bootimg-efi: added Unified Kernel Image option
- bootimg-pcbios: use label provided when formatting a DOS partition
* SDK-related enhancements:
- Enable do_populate_sdk with multilibs
- New SDKPATHINSTALL variable decouples default install path from built in path to avoid rebuilding nativesdk components on e.g. DISTRO_VERSION changes
- eSDK: Error if trying to generate an eSDK from a multiconfig
- eSDK: introduce TOOLCHAIN_HOST_TASK_ESDK to be used in place of TOOLCHAIN_HOST_TASK to add components to the host part of the eSDK
* bitbake enhancements:
- New bitbake-getvar helper command to query a variable value (with history)
- bitbake-layers: layerindex-fetch: add --fetchdir parameter to
- bitbake-layers: show-recipes: add skip reason to output
- bitbake-diffsigs: sort diff output for consistency
- Allow setting upstream for local hash equivalence server
- fetch2/s3: allow to use credentials and switch profile from environment variables
- fetch2/s3: Add progress handler for S3 cp command
- fetch2/npm: Support npm archives with missing search directory mode
- fetch2/npmsw: Add support for local tarball and link sources
- fetch2/svn: Allow peg-revision functionality to be disabled
- fetch2/wget: verify certificates for HTTPS/FTPS by default
- fetch2/wget: Enable FTPS
- prserv: added read-only mode
- prserv: replaced XML RPC with modern asyncrpc implementation
- Numerous warning/error message improvements
* New PACKAGECONFIG options in btrfs-tools, ccache, coreutils, cups, dbus, elfutils, ffmpeg, findutils, glib-2.0, gstreamer1.0-plugins-bad, gstreamer1.0-plugins-base, libarchive, libnotify, libpsl, man-db, mesa, ovmf, parted, prelink, qemu, rpm, shadow, systemd, tar, vim, weston
* u-boot enhancements:
- Make SPL suffix configurable
- Make UBOOT_BINARYNAME configurable
- Package extlinux.conf separately
- Allow deploying the u-boot DTB
* opensbi: Add support for specifying a device tree
* busybox enhancements:
- Added tmpdir option into mktemp applet
- Support mounting swap via labels
- Enable long options for enabled applets
* Move tune files to architecture subdirectories
* buildstats: log host data on failure separately to task specific file
* buildstats: collect "at interval" and "on failure" logs in the same file
* Ptest enhancements:
- ptest-runner: install script to collect system data on failure
- Added ptest support to python3-hypothesis, python3-jinja2, python3-markupsafe
- Enhanced ptest support in lttng, util-linux, and others
- New leaner ptest image recipes based upon core-image-minimal
* scripts/contrib/image-manifest: add new script
* Add beginnings of Android target support
* devtool upgrade: rebase override-only patches as well
* devtool: print a warning on upgrades if PREFERRED_VERSION is set
* systemd: set zstd as default compression option
* init-manager-systemd: add a weak VIRTUAL-RUNTIME_dev_manager assignment
* Add proper unpack dependency for .zst compressed archives
* util-linux: build chfn and chsh by default
* qemu: use 4 cores in qemu guests
* runqemu: decouple bios and kernel options
* qemu: add a hint on how to enable CPU render nodes when a suitable GPU is absent
* devupstream: Allow support of native class extensions
* Prelinking now disabled in default configuration
* python3: statistics module moved to its own python3-statistics package
* pypi: allow override of PyPI archive name
* Allow global override of golang GO_DYNLINK
* buildhistory enhancements:
- Add option to strip path prefix
- Add output file listing package information
- Label packages providing per-file dependencies in depends.dot
* New gi-docgen class for GNOME library documentation
* meson.bbclass: Make the default buildtype "debug" if DEBUG_BUILD is 1
* distro_features_check: expand with IMAGE_FEATURES
* Add extended packagedata in JSON format
* local.conf.sample: Update sstate mirror entry with new hash equivalence setting
* poky: Use https in default PREMIRRORS
* reproducible_build.bbclass: Enable -Wdate-time
* yocto-check-layer: ensure that all layer dependencies are tested too
* core-image-multilib-example: base on weston, and not sato
* npm.bbclass: Allow nodedir to be overridden by NPM_NODEDIR
* cve-extra-exclusions.inc: add exclusion list for intractable CVE's
* license_image.bbclass: Detect broken symlinks
* sysstat: make the service start automatically
* sanity: Add error check for '%' in build path
* sanity: Further improve directory sanity tests
* sanity.bbclass: mention CONNECTIVITY_CHECK_URIS in network failure message
* tzdata: Allow controlling zoneinfo binary format
* oe-time-dd-test.sh: add options and refactor
* vim: add option to disable NLS support
* zstd: Include pzstd in the build
* mirrors.bbclass: provide additional rule for git repo fallbacks
* own-mirrors: Add support for s3:// scheme in SOURCE_MIRROR_URL
* common-licenses: add missing SPDX licences
* Add MAINTAINERS.md file to record subsystem maintainers

-------------
Known Issues
-------------

* Build failures have been reported when running on host Linux systems with FIPS enabled (such as RHEL 8.0 with the FIPS mode enabled). For more details please see https://bugzilla.yoctoproject.org/show_bug.cgi?id=14609.

-----------------
Recipe Licenses
-----------------

The following corrections have been made to the LICENSE values set by recipes:

* acpica: correct LICENSE to "Intel | BSD-3-Clause | GPLv2"
* dtc: correct LICENSE to "GPLv2 | BSD-2-Clause"
* e2fsprogs: correct LICENSE to "GPLv2 & LGPLv2 & BSD-3-Clause & MIT"
* ffmpeg: correct LICENSE to "GPLv2+ & LGPLv2.1+ & ISC & MIT & BSD-2-Clause & BSD-3-Clause & IJG"
* flac: correct LICENSE to "GFDL-1.2 & GPLv2+ & LGPLv2.1+ & BSD-3-Clause"
* flex: correct LICENSE to "BSD-3-Clause & LGPL-2.0+"
* font-util: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* glib-2.0: correct LICENSE to "LGPLv2.1+ & BSD-3-Clause & PD"
* gobject-introspection: correct LICENSE to "LGPLv2+ & GPLv2+ & MIT" (add MIT license)
* hdparm: correct LICENSE to "BSD-2-Clause & GPLv2 & hdparm"
* iputils: correct LICENSE to "BSD-3-Clause & GPLv2+"
* libcap: correct LICENSE to "BSD-3-Clause | GPLv2"
* libevent: correct LICENSE to "BSD-3-Clause & MIT"
* libjitterentropy: correct LICENSE to "GPLv2+ | BSD-3-Clause"
* libpam: correct LICENSE to "GPLv2+ | BSD-3-Clause"
* libwpe: correct LICENSE to "BSD-2-Clause"
* libx11-compose-data: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libx11: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libxfont2: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libxfont: correct LICENSE to "MIT & MIT-style & BSD-3-Clause"
* lsof: correct LICENSE to reflect that it uses a BSD-like (but not exactly BSD) license ("Spencer-94")
* nfs-utils: correct LICENSE to "MIT & GPLv2+ & BSD-3-Clause"
* ovmf: correct license to "BSD-2-Clause-Patent"
* ppp: correct LICENSE to "BSD-3-Clause & BSD-3-Clause-Attribution & GPLv2+ & LGPLv2+ & PD"
* python3-packaging: correct LICENSE to "Apache-2.0 | BSD-2-Clause"
* python-async-test: correct LICENSE to "BSD-3-Clause"
* quota: remove BSD license (only BSD licensed part of the code was removed in 4.05)
* shadow: correct LICENSE to "BSD-3-Clause | Artistic-1.0"
* shadow-sysroot: set LICENSE the same as shadow
* sudo: correct LICENSE to "ISC & BSD-3-Clause & BSD-2-Clause & Zlib"
* swig: correct LICENSE to "BSD-3-Clause & GPLv3"
* valgrind: correct license to "GPLv2 & GPLv2+ & BSD-3-Clause"
* webkitgtk: correct LICENSE to "BSD-2-Clause & LGPLv2+"
* wpebackend-fdo: correct LICENSE to "BSD-2-Clause"
* xinetd: correct LICENSE to reflect that it uses a unique BSD-like (but not exactly BSD) license

Other license-related notes:
* When creating recipes for Python software, recipetool will now treat "BSD" as "BSD-3-Clause" for the purposes of setting LICENSE, as that is the most common understanding.
* Please be aware that an initramfs bundled with the kernel using INITRAMFS_IMAGE_BUNDLE should only contain GPLv2-compatible software; this is now mentioned in the documentation.

------------------------
Migration instructions
------------------------

For details on changes that you might need to make when migrating to the Yocto Project 3.4 release from previous releases, please see the following manual:

https://docs.yoctoproject.org/migration-guides/migration-3.4.html

----------------
Security Fixes
----------------

* apr: CVE-2021-35940
* aspell: CVE-2019-25051
* avahi: CVE-2021-3468, CVE-2021-36217
* binutils: CVE-2021-20197
* bluez: CVE-2021-3658
* busybox: CVE-2021-28831
* cairo: CVE-2020-35492
* cpio: CVE-2021-38185
* expat: CVE-2013-0340
* ffmpeg: CVE-2020-20446, CVE-2020-22015, CVE-2020-22021, CVE-2020-22033, CVE-2020-22019, CVE-2021-33815, CVE-2021-38171, CVE-2020-20453
* glibc: CVE-2021-33574, CVE-2021-38604
* inetutils: CVE-2021-40491
* libgcrypt: CVE-2021-40528
* linux-yocto/5.10, 5.14: CVE-2021-3653, CVE-2021-3656
* lz4: CVE-2021-3520
* nettle: CVE-2021-20305
* openssl: CVE-2021-3711, CVE-2021-3712
* perl: CVE-2021-36770
* python3: CVE-2021-29921
* python3-pip: CVE-2021-3572
* qemu: CVE-2020-27821, CVE-2020-29443, CVE-2020-35517, CVE-2021-3392, CVE-2021-3409, CVE-2021-3416, CVE-2021-3527, CVE-2021-3544, CVE-2021-3545, CVE-2021-3546, CVE-2021-3682, CVE-2021-20181, CVE-2021-20221, CVE-2021-20257, CVE-2021-20263
* rpm: CVE-2021-3421, CVE-2021-20271
* rsync: CVE-2020-14387
* util-linux: CVE-2021-37600
* vim: CVE-2021-3770, CVE-2021-3778
* wpa-supplicant: CVE-2021-30004
* xdg-utils: CVE-2020-27748
* xserver-xorg: CVE-2021-3472

-----------------
Recipe Upgrades
-----------------

* acl 2.2.53 -> 2.3.1
* acpica 20210105 -> 20210730
* alsa-lib 1.2.4 -> 1.2.5.1
* alsa-plugins 1.2.2 -> 1.2.5
* alsa-tools 1.2.2 -> 1.2.5
* alsa-topology-conf 1.2.4 -> 1.2.5.1
* alsa-ucm-conf 1.2.4 -> 1.2.5.1
* alsa-utils 1.2.4 -> 1.2.5.1
* alsa-utils-scripts 1.2.4 -> 1.2.5.1
* apt 2.2.2 -> 2.2.4
* at 3.2.1 -> 3.2.2
* at-spi2-core 2.38.0 -> 2.40.3
* autoconf-archive 2019.01.06 -> 2021.02.19
* babeltrace2 2.0.3 -> 2.0.4
* bash 5.1 -> 5.1.8
* bind 9.16.16 -> 9.16.20
* binutils 2.36.1 -> 2.37
* binutils-cross 2.36.1 -> 2.37
* binutils-cross-canadian 2.36.1 -> 2.37
* binutils-cross-testsuite 2.36.1 -> 2.37
* binutils-crosssdk 2.36.1 -> 2.37
* bison 3.7.5 -> 3.7.6
* blktrace 1.2.0+gitX -> 1.3.0+gitX
* bluez5 5.56 -> 5.61
* boost 1.75.0 -> 1.77.0
* boost-build-native 4.3.0 -> 4.4.1
* btrfs-tools 5.10.1 -> 5.13.1
* busybox 1.33.1 -> 1.34.0
* busybox-inittab 1.33.0 -> 1.34.0
* ccache 4.2 -> 4.4
* cmake 3.19.5 -> 3.21.1
* cmake-native 3.19.5 -> 3.21.1
* connman 1.39 -> 1.40
* createrepo-c 0.17.0 -> 0.17.4
* cronie 1.5.5 -> 1.5.7
* cross-localedef-native 2.33 -> 2.34
* cups 2.3.3 -> 2.3.3op2
* curl 7.75.0 -> 7.78.0
* dbus-glib 0.110 -> 0.112
* dejagnu 1.6.2 -> 1.6.3
* diffoscope 172 -> 181
* diffutils 3.7 -> 3.8
* distcc 3.3.5 -> 3.4
* dnf 4.6.0 -> 4.8.0
* dpkg 1.20.7.1 -> 1.20.9
* dtc 1.6.0 -> 1.6.1
* e2fsprogs 1.46.1 -> 1.46.4
* elfutils 0.183 -> 0.185
* ell 0.38 -> 0.43
* enchant2 2.2.15 -> 2.3.1
* epiphany 3.38.2 -> 40.3
* ethtool 5.10 -> 5.13
* expat 2.2.10 -> 2.4.1
* ffmpeg 4.3.2 -> 4.4
* file 5.39 -> 5.40
* freetype 2.10.4 -> 2.11.0
* gcc 10.2.0 -> 11.2.0
* gcc-cross 10.2.0 -> 11.2.0
* gcc-cross-canadian 10.2.0 -> 11.2.0
* gcc-crosssdk 10.2.0 -> 11.2.0
* gcc-runtime 10.2.0 -> 11.2.0
* gcc-sanitizers 10.2.0 -> 11.2.0
* gcc-source 10.2.0 -> 11.2.0
* gcr 3.38.1 -> 3.40.0
* gdb 10.1 -> 10.2
* gdb-cross 10.1 -> 10.2
* gdb-cross-canadian 10.1 -> 10.2
* gdk-pixbuf 2.40.0 -> 2.42.6
* ghostscript 9.53.3 -> 9.54.0
* git 2.31.1 -> 2.33.0
* glib-2.0 2.66.7 -> 2.68.4
* glib-networking 2.66.0 -> 2.68.2
* glibc 2.33 -> 2.34
* glibc-locale 2.33 -> 2.34
* glibc-mtrace 2.33 -> 2.34
* glibc-scripts 2.33 -> 2.34
* glibc-testsuite 2.33 -> 2.34
* glslang 11.2.0 -> 11.5.0
* gnome-desktop-testing 2018.1 -> 2021.1
* gnu-config 20210125+gitX -> 20210722+gitX
* gnu-efi 3.0.12 -> 3.0.14
* gnupg 2.2.27 -> 2.3.1
* gobject-introspection 1.66.1 -> 1.68.0
* gpgme 1.15.1 -> 1.16.0
* gptfdisk 1.0.7 -> 1.0.8
* grep 3.6 -> 3.7
* grub 2.04+2.06~rc1 -> 2.06
* grub-efi 2.04+2.06~rc1 -> 2.06
* gsettings-desktop-schemas 3.38.0 -> 40.0
* gtk+3 3.24.25 -> 3.24.30
* harfbuzz 2.7.4 -> 2.9.0
* hdparm 9.60 -> 9.62
* help2man 1.48.2 -> 1.48.4
* hwlatdetect 1.10 -> 2.1
* i2c-tools 4.2 -> 4.3
* icu 68.2 -> 69.1
* igt-gpu-tools 1.25+gitX -> 1.26
* inetutils 2.0 -> 2.1
* iproute2 5.11.0 -> 5.13.0
* iputils s20200821 -> 20210722
* json-glib 1.6.2 -> 1.6.4
* kexec-tools 2.0.21 -> 2.0.22
* kmod 28 -> 29
* kmod-native 28 -> 29
* less 563 -> 590
* libassuan 2.5.4 -> 2.5.5
* libcap 2.48 -> 2.51
* libcgroup 0.41 -> 2.0
* libcomps 0.1.15 -> 0.1.17
* libconvert-asn1-perl 0.27 -> 0.31
* libdazzle 3.38.0 -> 3.40.0
* libdnf 0.58.0 -> 0.63.1
* libdrm 2.4.104 -> 2.4.107
* libedit 20210216-3.1 -> 20210714-3.1
* libepoxy 1.5.5 -> 1.5.9
* liberation-fonts 2.00.1 -> 2.1.4
* libffi 3.3 -> 3.4.2
* libfm 1.3.1 -> 1.3.2
* libgcc 10.2.0 -> 11.2.0
* libgcc-initial 10.2.0 -> 11.2.0
* libgcrypt 1.9.3 -> 1.9.4
* libgfortran 10.2.0 -> 11.2.0
* libgit2 1.1.0 -> 1.1.1
* libglu 9.0.1 -> 9.0.2
* libgpg-error 1.41 -> 1.42
* libgudev 234 -> 237
* libhandy 1.2.0 -> 1.2.3
* libical 3.0.9 -> 3.0.10
* libidn2 2.3.0 -> 2.3.2
* libinput 1.16.4 -> 1.18.1
* libjitterentropy 3.0.1 -> 3.1.0
* libjpeg-turbo 2.0.6 -> 2.1.1
* libksba 1.5.0 -> 1.6.0
* libmodulemd 2.12.0 -> 2.13.0
* libnsl2 1.3.0 -> 2.0.0
* libnss-mdns 0.14.1 -> 0.15.1
* libogg 1.3.4 -> 1.3.5
* libpcap 1.10.0 -> 1.10.1
* libpcre 8.44 -> 8.45
* libpcre2 10.36 -> 10.37
* libportal 0.3 -> 0.4
* librepo 1.13.0 -> 1.14.1
* libsdl2 2.0.14 -> 2.0.16
* libsolv 0.7.17 -> 0.7.19
* libtasn1 4.16.0 -> 4.17.0
* libtest-needs-perl 0.002006 -> 0.002009
* libtirpc 1.3.1 -> 1.3.2
* libubootenv 0.3.1 -> 0.3.2
* libucontext 0.10+X -> 1.1+X
* liburcu 0.12.2 -> 0.13.0
* libuv 1.41.0 -> 1.42.0
* libva 2.10.0 -> 2.12.0
* libva-initial 2.10.0 -> 2.12.0
* libva-utils 2.10.0 -> 2.12.0
* libwebp 1.2.0 -> 1.2.1
* libwpe 1.8.0 -> 1.10.1
* libx11 1.7.0 -> 1.7.2
* libxcrypt 4.4.18 -> 4.4.25
* libxcrypt-compat 4.4.18 -> 4.4.25
* libxfixes 5.0.3 -> 6.0.0
* libxfont2 2.0.4 -> 2.0.5
* libxft 2.3.3 -> 2.3.4
* libxi 1.7.10 -> 1.7.99.2
* libxkbcommon 1.0.3 -> 1.3.0
* libxml2 2.9.10 -> 2.9.12
* libxres 1.2.0 -> 1.2.1
* linux-libc-headers 5.10 -> 5.14
* linux-yocto 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-dev 5.12++gitX -> 5.15++gitX
* linux-yocto-rt 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-tiny 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* llvm 11.1.0 -> 12.0.1
* log4cplus 2.0.6 -> 2.0.7
* logrotate 3.18.0 -> 3.18.1
* ltp 20210121 -> 20210524
* lttng-modules 2.12.6 -> 2.13.0
* lttng-tools 2.12.4 -> 2.13.0
* lttng-ust 2.12.1 -> 2.13.0
* m4 1.4.18 -> 1.4.19
* m4-native 1.4.18 -> 1.4.19
* man-pages 5.10 -> 5.12
* mc 4.8.26 -> 4.8.27
* mesa 21.0.3 -> 21.2.1
* mesa-gl 21.0.3 -> 21.2.1
* meson 0.57.1 -> 0.58.1
* mmc-utils 0.1+gitX (73d6c59af8d1...) -> 0.1+gitX (43282e80e174...)
* mobile-broadband-provider-info 20201225 -> 20210805
* mpg123 1.26.4 -> 1.28.2
* mtd-utils 2.1.2 -> 2.1.3
* mtools 4.0.26 -> 4.0.35
* musl 1.2.2+gitX (e5d2823631bb...) -> 1.2.2+gitX (3f701faace7a...)
* nativesdk-meson 0.57.1 -> 0.58.1
* netbase 6.2 -> 6.3
* nfs-utils 2.5.3 -> 2.5.4
* ofono 1.31 -> 1.32
* openssh 8.5p1 -> 8.7p1
* opkg 0.4.4 -> 0.4.5
* opkg-utils 0.4.3 -> 0.4.5
* ovmf edk2-stable202102 -> edk2-stable202105
* p11-kit 0.23.22 -> 0.24.0
* pango 1.48.2 -> 1.48.9
* patchelf 0.12 -> 0.13
* perl 5.32.1 -> 5.34.0
* piglit 1.0+gitrX (d4d9353b7290...) -> 1.0+gitrX (6a4be9e9946d...)
* pkgconf 1.7.3 -> 1.8.0
* powertop 2.13 -> 2.14
* pseudo 1.9.0+gitX (b988b0a6b8af...) -> 1.9.0+gitX (0cda3ba5f94a...)
* pulseaudio 14.2 -> 15.0
* puzzles 0.0+gitX (84cb4c6701e0...) -> 0.0+gitX (8f3413c31ffd...)
* python3 3.9.5 -> 3.9.6
* python3-attrs 20.3.0 -> 21.2.0
* python3-cython 0.29.22 -> 0.29.24
* python3-dbus 1.2.16 -> 1.2.18
* python3-dbusmock 0.22.0 -> 0.23.1
* python3-docutils 0.16 -> 0.17.1
* python3-git 3.1.14 -> 3.1.20
* python3-gitdb 4.0.5 -> 4.0.7
* python3-hypothesis 6.2.0 -> 6.15.0
* python3-importlib-metadata 3.4.0 -> 4.6.4
* python3-iniparse 0.4 -> 0.5
* python3-jinja2 2.11.3 -> 3.0.1
* python3-libarchive-c 2.9 -> 3.1
* python3-magic 0.4.22 -> 0.4.24
* python3-mako 1.1.4 -> 1.1.5
* python3-markupsafe 1.1.1 -> 2.0.1
* python3-more-itertools 8.7.0 -> 8.8.0
* python3-numpy 1.20.1 -> 1.21.2
* python3-packaging 20.9 -> 21.0
* python3-pathlib2 2.3.5 -> 2.3.6
* python3-pbr 5.4.4 -> 5.6.0
* python3-pip 20.0.2 -> 21.2.4
* python3-pluggy 0.13.1 -> 1.0.0
* python3-pycairo 1.20.0 -> 1.20.1
* python3-pygments 2.8.1 -> 2.10.0
* python3-pygobject 3.38.0 -> 3.40.1
* python3-pytest 6.2.2 -> 6.2.4
* python3-scons 3.1.2 -> 4.2.0
* python3-scons-native 3.1.2 -> 4.2.0
* python3-setuptools 54.1.1 -> 57.4.0
* python3-setuptools-scm 5.0.1 -> 6.0.1
* python3-six 1.15.0 -> 1.16.0
* python3-sortedcontainers 2.3.0 -> 2.4.0
* python3-testtools 2.4.0 -> 2.5.0
* python3-zipp 3.4.1 -> 3.5.0
* qemu 5.2.0 -> 6.0.0
* qemu-native 5.2.0 -> 6.0.0
* qemu-system-native 5.2.0 -> 6.0.0
* re2c 2.0.3 -> 2.2
* rng-tools 6.11 -> 6.14
* rpcbind 1.2.5 -> 1.2.6
* rt-tests 1.10 -> 2.1
* ruby 3.0.1 -> 3.0.2
* rxvt-unicode 9.22 -> 9.26
* shaderc 2020.5 -> 2021.1
* shadow 4.8.1 -> 4.9
* spirv-tools 2020.7 -> 2021.2
* sqlite3 3.35.0 -> 3.36.0
* squashfs-tools 4.4 -> 4.5
* strace 5.11 -> 5.14
* stress-ng 0.12.05 -> 0.13.00
* sudo 1.9.6p1 -> 1.9.7p2
* swig 3.0.12 -> 4.0.2
* sysklogd 2.2.2 -> 2.2.3
* systemd 247.6 -> 249.3
* systemd-boot 247.6 -> 249.3
* systemd-conf 247.6 -> 1.0
* systemtap 4.4 -> 4.5
* systemtap-native 4.4 -> 4.5
* systemtap-uprobes 4.4 -> 4.5
* tcf-agent 1.7.0+gitX (a022ef2f1acf...) -> 1.7.0+gitX (2735e3d6b7ec...)
* texinfo 6.7 -> 6.8
* tiff 4.2.0 -> 4.3.0
* u-boot 2021.01 -> 2021.07
* u-boot-tools 2021.01 -> 2021.07
* usbutils 013 -> 014
* util-linux 2.36.2 -> 2.37.2
* util-linux-libuuid 2.36.2 -> 2.37.2
* vala 0.50.4 -> 0.52.5
* valgrind 3.16.1 -> 3.17.0
* virglrenderer 0.8.2 -> 0.9.1
* vte 0.62.2 -> 0.64.2
* vulkan-headers 1.2.170.0 -> 1.2.182.0
* vulkan-loader 1.2.170.0 -> 1.2.182.0
* vulkan-samples git (55cebd9e7cc4...) -> git (d2187278cb66...)
* vulkan-tools 1.2.170.0 -> 1.2.182.0
* wayland-protocols 1.20 -> 1.21
* webkitgtk 2.30.5 -> 2.32.3
* wireless-regdb 2021.04.21 -> 2021.07.14
* wpebackend-fdo 1.8.0 -> 1.10.0
* x264 r3039+gitX (544c61f08219...) -> r3039+gitX (5db6aa6cab1b...)
* xeyes 1.1.2 -> 1.2.0
* xf86-input-libinput 0.30.0 -> 1.1.0
* xkbcomp 1.4.4 -> 1.4.5
* xkeyboard-config 2.32 -> 2.33
* xorgproto 2020.1 -> 2021.4.99.2
* xserver-xorg 1.20.10 -> 1.20.13
* zstd 1.4.9 -> 1.5.0

</pre>

3.4 Release Notes WIP

2021-10-22T03:17:46Z

PaulEggleton:

<pre>

--------------
Contributors
--------------

Thanks to the following people who contributed to this release:

Adam Romanek
Alejandro Hernandez Samaniego
Alexander Kanavin
Alexandre Belloni
Alexey Brodkin
Alex Stewart
Alistair Francis
Anatol Belski
Anders Wallin
Andrea Adami
Andreas Müller
Andrej Valek
Andres Beltran
Andrey Zhizhikin
Anibal Limon
Anthony Bagwell
Anton Blanchard
Anuj Mittal
Armin Kuster
Asfak Rahman
Bastian Krause
Bernhard Rosenkränzer
Bruce Ashfield
Carlos Rafael Giani
Chandana kalluri
Changhyeok Bae
Changqing Li
Chanho Park
Chen Qi
Chris Laplante
Christophe Chapuis
Christoph Muellner
Claudius Heine
Damian Wrobel
Daniel Ammann
Daniel Gomez
Daniel McGregor
Daniel Wagenknecht
Denys Dmytriyenko
Devendra Tewari
Diego Sueiro
Dmitry Baryshkov
Douglas Royds
Dragos-Marian Panait
Drew Moseley
Enrico Scholz
Fabio Berton
Florian Amstutz
Gavin Li
Guillaume Champagne
Harald Brinkmann
Henning Schild
He Zhe
Hongxu Jia
Hsia-Jun (Randy) Li
Jean Bouchard
Joe Slater
Jonas Höppner
Jon Mason
Jose Quaresma
Joshua Watt
Justin Bronder
Kai Kang
Kenfe-Mickael Laventure
Kevin Hao
Khairul Rohaizzat Jamaluddin
Khem Raj
Kiran Surendran
Konrad Weihmann
Kristian Klausen
Kyle Russell
Lee Chee Yang
Lei Maohui
Luca Boccassi
Marco Felsch
Marcus Comstedt
Marek Vasut
Mark Hatle
Markus Volk
Marta Rybczynska
Martin Jansa
Matthias Klein
Matthias Schiffer
Matt Madison
Matt Spencer
Max Krummenacher
Michael Halstead
Michael Ho
Michael Opdenacker
Mike Crowe
Mikko Rapeli
Ming Liu
Mingli Yu
Minjae Kim
Nicolas Dechesne
Niels Avonds
Nikolay Papenkov
Nisha Parrakat
Olaf Mandel
Oleksandr Kravchuk
Oleksandr Popovych
Oliver Kranz
Otavio Salvador
Patrick Williams
Paul Barker
Paul Eggleton
Paul Gortmaker
Paulo Cesar Zaneti
Peter Bergin
Peter Budny
Peter Kjellerstedt
Petr Vorel
Przemyslaw Gorszkowski
Purushottam Choudhary
Qiang Zhang
Quentin Schulz
Ralph Siemsen
Randy MacLeod
Ranjitsinh Rathod
Rasmus Villemoes
Reto Schneider
Richard Purdie
Richard Weinberger
Robert Joslyn
Robert P. J. Day
Robert Yang
Romain Naour
Ross Burton
Sakib Sajal
Samuli Piippo
Saul Wold
Scott Murray
Scott Weaver
Stefan Ghinea
Stefan Herbrechtsmeier
Stefano Babic
Stefan Wiehler
Steve Sakoman
Teoh Jay Shen
Thomas Perrot
Tim Orling
Tom Pollard
Tom Rini
Tony Battersby
Tony Tascioglu
Trevor Gamblin
Trevor Woerner
Ulrich Ölmann
Valentin Danaila
Vinay Kumar
Vineela Tummalapalli
Vinícius Ossanes Aquino
Vivien Didelot
Vyacheslav Yurkov
Wang Mingyu
Wes Lindauer
William A. Kennington III
Yanfei Xu
Yann Dirson
Yi Fan Yu
Yi Zhao
Zang Ruochen
Zheng Ruoqin
Zoltán Böszörményi

-----------------------------
New Features / Enhancements
-----------------------------

* Linux kernel 5.14, glibc 2.34 and ~280 other recipe upgrades
* Switched override character to ':' (replacing '_') for more robust parsing and improved performance - see migration guide for help on migrating
* Rust integrated into core, providing rust support for cross-compilation and SDK
* New create-spdx class for creating SPDX SBoM documents
* New recipes: cargo, core-image-ptest-all, core-image-ptest-fast, core-image-weston-sdk, erofs-utils, gcompat, gi-docgen, libmicrohttpd, libseccomp, libstd-rs, perlcross, python3-markdown, python3-pyyaml, python3-smartypants, python3-typogrify, rust, rust-cross, rust-cross-canadian, rust-hello-world, rust-llvm, rust-tools-cross-canadian, rustfmt, xwayland
* Several optimisations to reduce unnecessary task dependencies for faster builds
* seccomp integrated into core, with additional enabling for gnutls, systemd, qemu
* New overlayfs class to help generate overlayfs mount units
* debuginfod support now enabled by default
* Switched several recipes over to using OpenSSL instead of GnuTLS (wpa-supplicant, curl, glib-networking) or disable GnuTLS (cups) by default
* Improvements to LTO plugin installation and reproducibility
* Architecture-specific enhancements:
- glibc: Enable memory tagging for aarch64
- testimage: remove aarch64 xorg exclusion
- arch-arm*: add better support for gcc march extensions
- tune-cortexm*: add support for all Arm Cortex-M processors
- tune-cortexr*: add support for all Arm Cortex-R processors
- arch-armv4: Allow -march=armv4
- qemuarm*: use virtio graphics
- baremetal-helloworld: Enable RISC-V 64/32 port
- ldconfig-native: Add RISC-V support
- qemuriscv: Enable 4 core emulation
- Add ARC support in gdb, dpkg, dhcpcd
- conf/machine-sdk: Add ppc64 SDK machine
- libjpeg-turbo: Handle powerpc64le without Altivec
- pixman: Handle PowerPC without Altivec
- mesa: enable gallium Intel drivers when building for x86
- mesa: enable crocus driver for older Intel graphics
* Kernel-related enhancements:
- Support zstd-compressed modules and initramfs images
- Allow opt-out of split kernel modules
- linux-yocto-dev: base AUTOREV on specified version
- kernel-yocto: provide debug / summary information for metadata
- kernel-uboot: Handle gzip and lzo compression options
- linux-yocto/5.14: added devupstream support
- linux-yocto: add vfat KERNEL_FEATURE when MACHINE_FEATURES include vfat
- linux-yocto: enable TYPEC_TCPCI in usbc fragment
* Image-related enhancements:
- New erofs, erofs-lz4 and erofs-lz4hc image types
- New squashfs-zst and cpio.zst image types
- New lic-pkgs IMAGE_FEATURES item to install all license packages
- Added zsync metadata conversion support
- Use xargs to set file timestamps for significant (>90%) do_image speedup
- Find .ko.gz and .ko.xz kernel modules as well when determining need to run depmod on an image
- Show formatted error messages instead of tracebacks for systemctl errors
- No longer ignore installation failures in complementary package installation
- Remove ldconfig auxiliary cache when not needed
* wic enhancements:
- Added erofs filesystem support
- Added --extra-space argument to leave extra space after last partition
- Added --no-fstab-update part option to allow using the stock fstab
- bootimg-efi: added Unified Kernel Image option
- bootimg-pcbios: use label provided when formatting a DOS partition
* SDK-related enhancements:
- Enable do_populate_sdk with multilibs
- New SDKPATHINSTALL variable decouples default install path from built in path to avoid rebuilding nativesdk components on e.g. DISTRO_VERSION changes
- eSDK: Error if trying to generate an eSDK from a multiconfig
- eSDK: introduce TOOLCHAIN_HOST_TASK_ESDK to be used in place of TOOLCHAIN_HOST_TASK to add components to the host part of the eSDK
* bitbake enhancements:
- New bitbake-getvar helper command to query a variable value (with history)
- bitbake-layers: layerindex-fetch: add --fetchdir parameter to
- bitbake-layers: show-recipes: add skip reason to output
- bitbake-diffsigs: sort diff output for consistency
- Allow setting upstream for local hash equivalence server
- fetch2/s3: allow to use credentials and switch profile from environment variables
- fetch2/s3: Add progress handler for S3 cp command
- fetch2/npm: Support npm archives with missing search directory mode
- fetch2/npmsw: Add support for local tarball and link sources
- fetch2/svn: Allow peg-revision functionality to be disabled
- fetch2/wget: verify certificates for HTTPS/FTPS by default
- fetch2/wget: Enable FTPS
- prserv: added read-only mode
- prserv: replaced XML RPC with modern asyncrpc implementation
- Numerous warning/error message improvements
* New PACKAGECONFIG options in btrfs-tools, ccache, coreutils, cups, dbus, elfutils, ffmpeg, findutils, glib-2.0, gstreamer1.0-plugins-bad, gstreamer1.0-plugins-base, libarchive, libnotify, libpsl, man-db, mesa, ovmf, parted, prelink, qemu, rpm, shadow, systemd, tar, vim, weston
* u-boot enhancements:
- Make SPL suffix configurable
- Make UBOOT_BINARYNAME configurable
- Package extlinux.conf separately
- Allow deploying the u-boot DTB
* opensbi: Add support for specifying a device tree
* busybox enhancements:
- Added tmpdir option into mktemp applet
- Support mounting swap via labels
- Enable long options for enabled applets
* Move tune files to architecture subdirectories
* buildstats: log host data on failure separately to task specific file
* buildstats: collect "at interval" and "on failure" logs in the same file
* Ptest enhancements:
- ptest-runner: install script to collect system data on failure
- Added ptest support to python3-hypothesis, python3-jinja2, python3-markupsafe
- Enhanced ptest support in lttng, util-linux, and others
- New leaner ptest image recipes based upon core-image-minimal
* scripts/contrib/image-manifest: add new script
* Add beginnings of Android target support
* devtool upgrade: rebase override-only patches as well
* devtool: print a warning on upgrades if PREFERRED_VERSION is set
* systemd: set zstd as default compression option
* init-manager-systemd: add a weak VIRTUAL-RUNTIME_dev_manager assignment
* Add proper unpack dependency for .zst compressed archives
* util-linux: build chfn and chsh by default
* qemu: use 4 cores in qemu guests
* runqemu: decouple bios and kernel options
* qemu: add a hint on how to enable CPU render nodes when a suitable GPU is absent
* devupstream: Allow support of native class extensions
* Prelinking now disabled in default configuration
* python3: statistics module moved to its own python3-statistics package
* pypi: allow override of PyPI archive name
* Allow global override of golang GO_DYNLINK
* buildhistory enhancements:
- Add option to strip path prefix
- Add output file listing package information
- Label packages providing per-file dependencies in depends.dot
* New gi-docgen class for GNOME library documentation
* meson.bbclass: Make the default buildtype "debug" if DEBUG_BUILD is 1
* distro_features_check: expand with IMAGE_FEATURES
* Add extended packagedata in JSON format
* poky: Use https in default PREMIRRORS
* cross-canadian: make android pass target sys check
* local.conf.sample: Update sstate mirror entry with new hash equivalence setting
* tzdata: Allow controlling zoneinfo binary format
* core-image-multilib-example: base on weston, and not sato
* reproducible_build.bbclass: Enable -Wdate-time
* yocto-check-layer: ensure that all layer dependencies are tested too
* npm.bbclass: Allow nodedir to be overridden by NPM_NODEDIR
* cve-extra-exclusions.inc: add exclusion list for intractable CVE's
* license_image.bbclass: Detect broken symlinks
* sysstat: make the service start automatically
* sanity: Add error check for '%' in build path
* sanity: Further improve directory sanity tests
* sanity.bbclass: mention CONNECTIVITY_CHECK_URIS in network failure message
* oe-time-dd-test.sh: add options and refactor
* vim: add option to disable NLS support
* zstd: Include pzstd in the build
* mirrors.bbclass: provide additional rule for git repo fallbacks
* own-mirrors: Add support for s3:// scheme in SOURCE_MIRROR_URL
* common-licenses: add missing SPDX licences
* Add MAINTAINERS.md file to record subsystem maintainers

-------------
Known Issues
-------------

* Build failures have been reported when running on host Linux systems with FIPS enabled (such as RHEL 8.0 with the FIPS mode enabled). For more details please see https://bugzilla.yoctoproject.org/show_bug.cgi?id=14609.

-----------------
Recipe Licenses
-----------------

The following corrections have been made to the LICENSE values set by recipes:

* acpica: correct LICENSE to "Intel | BSD-3-Clause | GPLv2"
* dtc: correct LICENSE to "GPLv2 | BSD-2-Clause"
* e2fsprogs: correct LICENSE to "GPLv2 & LGPLv2 & BSD-3-Clause & MIT"
* ffmpeg: correct LICENSE to "GPLv2+ & LGPLv2.1+ & ISC & MIT & BSD-2-Clause & BSD-3-Clause & IJG"
* flac: correct LICENSE to "GFDL-1.2 & GPLv2+ & LGPLv2.1+ & BSD-3-Clause"
* flex: correct LICENSE to "BSD-3-Clause & LGPL-2.0+"
* font-util: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* glib-2.0: correct LICENSE to "LGPLv2.1+ & BSD-3-Clause & PD"
* gobject-introspection: correct LICENSE to "LGPLv2+ & GPLv2+ & MIT" (add MIT license)
* hdparm: correct LICENSE to "BSD-2-Clause & GPLv2 & hdparm"
* iputils: correct LICENSE to "BSD-3-Clause & GPLv2+"
* libcap: correct LICENSE to "BSD-3-Clause | GPLv2"
* libevent: correct LICENSE to "BSD-3-Clause & MIT"
* libjitterentropy: correct LICENSE to "GPLv2+ | BSD-3-Clause"
* libpam: correct LICENSE to "GPLv2+ | BSD-3-Clause"
* libwpe: correct LICENSE to "BSD-2-Clause"
* libx11-compose-data: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libx11: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libxfont2: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libxfont: correct LICENSE to "MIT & MIT-style & BSD-3-Clause"
* lsof: correct LICENSE to reflect that it uses a BSD-like (but not exactly BSD) license ("Spencer-94")
* nfs-utils: correct LICENSE to "MIT & GPLv2+ & BSD-3-Clause"
* ovmf: correct license to "BSD-2-Clause-Patent"
* ppp: correct LICENSE to "BSD-3-Clause & BSD-3-Clause-Attribution & GPLv2+ & LGPLv2+ & PD"
* python3-packaging: correct LICENSE to "Apache-2.0 | BSD-2-Clause"
* python-async-test: correct LICENSE to "BSD-3-Clause"
* quota: remove BSD license (only BSD licensed part of the code was removed in 4.05)
* shadow: correct LICENSE to "BSD-3-Clause | Artistic-1.0"
* shadow-sysroot: set LICENSE the same as shadow
* sudo: correct LICENSE to "ISC & BSD-3-Clause & BSD-2-Clause & Zlib"
* swig: correct LICENSE to "BSD-3-Clause & GPLv3"
* valgrind: correct license to "GPLv2 & GPLv2+ & BSD-3-Clause"
* webkitgtk: correct LICENSE to "BSD-2-Clause & LGPLv2+"
* wpebackend-fdo: correct LICENSE to "BSD-2-Clause"
* xinetd: correct LICENSE to reflect that it uses a unique BSD-like (but not exactly BSD) license

Other license-related notes:
* When creating recipes for Python software, recipetool will now treat "BSD" as "BSD-3-Clause" for the purposes of setting LICENSE, as that is the most common understanding.
* Please be aware that an initramfs bundled with the kernel using INITRAMFS_IMAGE_BUNDLE should only contain GPLv2-compatible software; this is now mentioned in the documentation.

------------------------
Migration instructions
------------------------

For details on changes that you might need to make when migrating to the Yocto Project 3.4 release from previous releases, please see the following manual:

https://docs.yoctoproject.org/migration-guides/migration-3.4.html

----------------
Security Fixes
----------------

* apr: CVE-2021-35940
* aspell: CVE-2019-25051
* avahi: CVE-2021-3468, CVE-2021-36217
* binutils: CVE-2021-20197
* bluez: CVE-2021-3658
* busybox: CVE-2021-28831
* cairo: CVE-2020-35492
* cpio: CVE-2021-38185
* expat: CVE-2013-0340
* ffmpeg: CVE-2020-20446, CVE-2020-22015, CVE-2020-22021, CVE-2020-22033, CVE-2020-22019, CVE-2021-33815, CVE-2021-38171, CVE-2020-20453
* glibc: CVE-2021-33574, CVE-2021-38604
* inetutils: CVE-2021-40491
* libgcrypt: CVE-2021-40528
* linux-yocto/5.10, 5.14: CVE-2021-3653, CVE-2021-3656
* lz4: CVE-2021-3520
* nettle: CVE-2021-20305
* openssl: CVE-2021-3711, CVE-2021-3712
* perl: CVE-2021-36770
* python3: CVE-2021-29921
* python3-pip: CVE-2021-3572
* qemu: CVE-2020-27821, CVE-2020-29443, CVE-2020-35517, CVE-2021-3392, CVE-2021-3409, CVE-2021-3416, CVE-2021-3527, CVE-2021-3544, CVE-2021-3545, CVE-2021-3546, CVE-2021-3682, CVE-2021-20181, CVE-2021-20221, CVE-2021-20257, CVE-2021-20263
* rpm: CVE-2021-3421, CVE-2021-20271
* rsync: CVE-2020-14387
* util-linux: CVE-2021-37600
* vim: CVE-2021-3770, CVE-2021-3778
* wpa-supplicant: CVE-2021-30004
* xdg-utils: CVE-2020-27748
* xserver-xorg: CVE-2021-3472

-----------------
Recipe Upgrades
-----------------

* acl 2.2.53 -> 2.3.1
* acpica 20210105 -> 20210730
* alsa-lib 1.2.4 -> 1.2.5.1
* alsa-plugins 1.2.2 -> 1.2.5
* alsa-tools 1.2.2 -> 1.2.5
* alsa-topology-conf 1.2.4 -> 1.2.5.1
* alsa-ucm-conf 1.2.4 -> 1.2.5.1
* alsa-utils 1.2.4 -> 1.2.5.1
* alsa-utils-scripts 1.2.4 -> 1.2.5.1
* apt 2.2.2 -> 2.2.4
* at 3.2.1 -> 3.2.2
* at-spi2-core 2.38.0 -> 2.40.3
* autoconf-archive 2019.01.06 -> 2021.02.19
* babeltrace2 2.0.3 -> 2.0.4
* bash 5.1 -> 5.1.8
* bind 9.16.16 -> 9.16.20
* binutils 2.36.1 -> 2.37
* binutils-cross 2.36.1 -> 2.37
* binutils-cross-canadian 2.36.1 -> 2.37
* binutils-cross-testsuite 2.36.1 -> 2.37
* binutils-crosssdk 2.36.1 -> 2.37
* bison 3.7.5 -> 3.7.6
* blktrace 1.2.0+gitX -> 1.3.0+gitX
* bluez5 5.56 -> 5.61
* boost 1.75.0 -> 1.77.0
* boost-build-native 4.3.0 -> 4.4.1
* btrfs-tools 5.10.1 -> 5.13.1
* busybox 1.33.1 -> 1.34.0
* busybox-inittab 1.33.0 -> 1.34.0
* ccache 4.2 -> 4.4
* cmake 3.19.5 -> 3.21.1
* cmake-native 3.19.5 -> 3.21.1
* connman 1.39 -> 1.40
* createrepo-c 0.17.0 -> 0.17.4
* cronie 1.5.5 -> 1.5.7
* cross-localedef-native 2.33 -> 2.34
* cups 2.3.3 -> 2.3.3op2
* curl 7.75.0 -> 7.78.0
* dbus-glib 0.110 -> 0.112
* dejagnu 1.6.2 -> 1.6.3
* diffoscope 172 -> 181
* diffutils 3.7 -> 3.8
* distcc 3.3.5 -> 3.4
* dnf 4.6.0 -> 4.8.0
* dpkg 1.20.7.1 -> 1.20.9
* dtc 1.6.0 -> 1.6.1
* e2fsprogs 1.46.1 -> 1.46.4
* elfutils 0.183 -> 0.185
* ell 0.38 -> 0.43
* enchant2 2.2.15 -> 2.3.1
* epiphany 3.38.2 -> 40.3
* ethtool 5.10 -> 5.13
* expat 2.2.10 -> 2.4.1
* ffmpeg 4.3.2 -> 4.4
* file 5.39 -> 5.40
* freetype 2.10.4 -> 2.11.0
* gcc 10.2.0 -> 11.2.0
* gcc-cross 10.2.0 -> 11.2.0
* gcc-cross-canadian 10.2.0 -> 11.2.0
* gcc-crosssdk 10.2.0 -> 11.2.0
* gcc-runtime 10.2.0 -> 11.2.0
* gcc-sanitizers 10.2.0 -> 11.2.0
* gcc-source 10.2.0 -> 11.2.0
* gcr 3.38.1 -> 3.40.0
* gdb 10.1 -> 10.2
* gdb-cross 10.1 -> 10.2
* gdb-cross-canadian 10.1 -> 10.2
* gdk-pixbuf 2.40.0 -> 2.42.6
* ghostscript 9.53.3 -> 9.54.0
* git 2.31.1 -> 2.33.0
* glib-2.0 2.66.7 -> 2.68.4
* glib-networking 2.66.0 -> 2.68.2
* glibc 2.33 -> 2.34
* glibc-locale 2.33 -> 2.34
* glibc-mtrace 2.33 -> 2.34
* glibc-scripts 2.33 -> 2.34
* glibc-testsuite 2.33 -> 2.34
* glslang 11.2.0 -> 11.5.0
* gnome-desktop-testing 2018.1 -> 2021.1
* gnu-config 20210125+gitX -> 20210722+gitX
* gnu-efi 3.0.12 -> 3.0.14
* gnupg 2.2.27 -> 2.3.1
* gobject-introspection 1.66.1 -> 1.68.0
* gpgme 1.15.1 -> 1.16.0
* gptfdisk 1.0.7 -> 1.0.8
* grep 3.6 -> 3.7
* grub 2.04+2.06~rc1 -> 2.06
* grub-efi 2.04+2.06~rc1 -> 2.06
* gsettings-desktop-schemas 3.38.0 -> 40.0
* gtk+3 3.24.25 -> 3.24.30
* harfbuzz 2.7.4 -> 2.9.0
* hdparm 9.60 -> 9.62
* help2man 1.48.2 -> 1.48.4
* hwlatdetect 1.10 -> 2.1
* i2c-tools 4.2 -> 4.3
* icu 68.2 -> 69.1
* igt-gpu-tools 1.25+gitX -> 1.26
* inetutils 2.0 -> 2.1
* iproute2 5.11.0 -> 5.13.0
* iputils s20200821 -> 20210722
* json-glib 1.6.2 -> 1.6.4
* kexec-tools 2.0.21 -> 2.0.22
* kmod 28 -> 29
* kmod-native 28 -> 29
* less 563 -> 590
* libassuan 2.5.4 -> 2.5.5
* libcap 2.48 -> 2.51
* libcgroup 0.41 -> 2.0
* libcomps 0.1.15 -> 0.1.17
* libconvert-asn1-perl 0.27 -> 0.31
* libdazzle 3.38.0 -> 3.40.0
* libdnf 0.58.0 -> 0.63.1
* libdrm 2.4.104 -> 2.4.107
* libedit 20210216-3.1 -> 20210714-3.1
* libepoxy 1.5.5 -> 1.5.9
* liberation-fonts 2.00.1 -> 2.1.4
* libffi 3.3 -> 3.4.2
* libfm 1.3.1 -> 1.3.2
* libgcc 10.2.0 -> 11.2.0
* libgcc-initial 10.2.0 -> 11.2.0
* libgcrypt 1.9.3 -> 1.9.4
* libgfortran 10.2.0 -> 11.2.0
* libgit2 1.1.0 -> 1.1.1
* libglu 9.0.1 -> 9.0.2
* libgpg-error 1.41 -> 1.42
* libgudev 234 -> 237
* libhandy 1.2.0 -> 1.2.3
* libical 3.0.9 -> 3.0.10
* libidn2 2.3.0 -> 2.3.2
* libinput 1.16.4 -> 1.18.1
* libjitterentropy 3.0.1 -> 3.1.0
* libjpeg-turbo 2.0.6 -> 2.1.1
* libksba 1.5.0 -> 1.6.0
* libmodulemd 2.12.0 -> 2.13.0
* libnsl2 1.3.0 -> 2.0.0
* libnss-mdns 0.14.1 -> 0.15.1
* libogg 1.3.4 -> 1.3.5
* libpcap 1.10.0 -> 1.10.1
* libpcre 8.44 -> 8.45
* libpcre2 10.36 -> 10.37
* libportal 0.3 -> 0.4
* librepo 1.13.0 -> 1.14.1
* libsdl2 2.0.14 -> 2.0.16
* libsolv 0.7.17 -> 0.7.19
* libtasn1 4.16.0 -> 4.17.0
* libtest-needs-perl 0.002006 -> 0.002009
* libtirpc 1.3.1 -> 1.3.2
* libubootenv 0.3.1 -> 0.3.2
* libucontext 0.10+X -> 1.1+X
* liburcu 0.12.2 -> 0.13.0
* libuv 1.41.0 -> 1.42.0
* libva 2.10.0 -> 2.12.0
* libva-initial 2.10.0 -> 2.12.0
* libva-utils 2.10.0 -> 2.12.0
* libwebp 1.2.0 -> 1.2.1
* libwpe 1.8.0 -> 1.10.1
* libx11 1.7.0 -> 1.7.2
* libxcrypt 4.4.18 -> 4.4.25
* libxcrypt-compat 4.4.18 -> 4.4.25
* libxfixes 5.0.3 -> 6.0.0
* libxfont2 2.0.4 -> 2.0.5
* libxft 2.3.3 -> 2.3.4
* libxi 1.7.10 -> 1.7.99.2
* libxkbcommon 1.0.3 -> 1.3.0
* libxml2 2.9.10 -> 2.9.12
* libxres 1.2.0 -> 1.2.1
* linux-libc-headers 5.10 -> 5.14
* linux-yocto 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-dev 5.12++gitX -> 5.15++gitX
* linux-yocto-rt 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-tiny 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* llvm 11.1.0 -> 12.0.1
* log4cplus 2.0.6 -> 2.0.7
* logrotate 3.18.0 -> 3.18.1
* ltp 20210121 -> 20210524
* lttng-modules 2.12.6 -> 2.13.0
* lttng-tools 2.12.4 -> 2.13.0
* lttng-ust 2.12.1 -> 2.13.0
* m4 1.4.18 -> 1.4.19
* m4-native 1.4.18 -> 1.4.19
* man-pages 5.10 -> 5.12
* mc 4.8.26 -> 4.8.27
* mesa 21.0.3 -> 21.2.1
* mesa-gl 21.0.3 -> 21.2.1
* meson 0.57.1 -> 0.58.1
* mmc-utils 0.1+gitX (73d6c59af8d1...) -> 0.1+gitX (43282e80e174...)
* mobile-broadband-provider-info 20201225 -> 20210805
* mpg123 1.26.4 -> 1.28.2
* mtd-utils 2.1.2 -> 2.1.3
* mtools 4.0.26 -> 4.0.35
* musl 1.2.2+gitX (e5d2823631bb...) -> 1.2.2+gitX (3f701faace7a...)
* nativesdk-meson 0.57.1 -> 0.58.1
* netbase 6.2 -> 6.3
* nfs-utils 2.5.3 -> 2.5.4
* ofono 1.31 -> 1.32
* openssh 8.5p1 -> 8.7p1
* opkg 0.4.4 -> 0.4.5
* opkg-utils 0.4.3 -> 0.4.5
* ovmf edk2-stable202102 -> edk2-stable202105
* p11-kit 0.23.22 -> 0.24.0
* pango 1.48.2 -> 1.48.9
* patchelf 0.12 -> 0.13
* perl 5.32.1 -> 5.34.0
* piglit 1.0+gitrX (d4d9353b7290...) -> 1.0+gitrX (6a4be9e9946d...)
* pkgconf 1.7.3 -> 1.8.0
* powertop 2.13 -> 2.14
* pseudo 1.9.0+gitX (b988b0a6b8af...) -> 1.9.0+gitX (0cda3ba5f94a...)
* pulseaudio 14.2 -> 15.0
* puzzles 0.0+gitX (84cb4c6701e0...) -> 0.0+gitX (8f3413c31ffd...)
* python3 3.9.5 -> 3.9.6
* python3-attrs 20.3.0 -> 21.2.0
* python3-cython 0.29.22 -> 0.29.24
* python3-dbus 1.2.16 -> 1.2.18
* python3-dbusmock 0.22.0 -> 0.23.1
* python3-docutils 0.16 -> 0.17.1
* python3-git 3.1.14 -> 3.1.20
* python3-gitdb 4.0.5 -> 4.0.7
* python3-hypothesis 6.2.0 -> 6.15.0
* python3-importlib-metadata 3.4.0 -> 4.6.4
* python3-iniparse 0.4 -> 0.5
* python3-jinja2 2.11.3 -> 3.0.1
* python3-libarchive-c 2.9 -> 3.1
* python3-magic 0.4.22 -> 0.4.24
* python3-mako 1.1.4 -> 1.1.5
* python3-markupsafe 1.1.1 -> 2.0.1
* python3-more-itertools 8.7.0 -> 8.8.0
* python3-numpy 1.20.1 -> 1.21.2
* python3-packaging 20.9 -> 21.0
* python3-pathlib2 2.3.5 -> 2.3.6
* python3-pbr 5.4.4 -> 5.6.0
* python3-pip 20.0.2 -> 21.2.4
* python3-pluggy 0.13.1 -> 1.0.0
* python3-pycairo 1.20.0 -> 1.20.1
* python3-pygments 2.8.1 -> 2.10.0
* python3-pygobject 3.38.0 -> 3.40.1
* python3-pytest 6.2.2 -> 6.2.4
* python3-scons 3.1.2 -> 4.2.0
* python3-scons-native 3.1.2 -> 4.2.0
* python3-setuptools 54.1.1 -> 57.4.0
* python3-setuptools-scm 5.0.1 -> 6.0.1
* python3-six 1.15.0 -> 1.16.0
* python3-sortedcontainers 2.3.0 -> 2.4.0
* python3-testtools 2.4.0 -> 2.5.0
* python3-zipp 3.4.1 -> 3.5.0
* qemu 5.2.0 -> 6.0.0
* qemu-native 5.2.0 -> 6.0.0
* qemu-system-native 5.2.0 -> 6.0.0
* re2c 2.0.3 -> 2.2
* rng-tools 6.11 -> 6.14
* rpcbind 1.2.5 -> 1.2.6
* rt-tests 1.10 -> 2.1
* ruby 3.0.1 -> 3.0.2
* rxvt-unicode 9.22 -> 9.26
* shaderc 2020.5 -> 2021.1
* shadow 4.8.1 -> 4.9
* spirv-tools 2020.7 -> 2021.2
* sqlite3 3.35.0 -> 3.36.0
* squashfs-tools 4.4 -> 4.5
* strace 5.11 -> 5.14
* stress-ng 0.12.05 -> 0.13.00
* sudo 1.9.6p1 -> 1.9.7p2
* swig 3.0.12 -> 4.0.2
* sysklogd 2.2.2 -> 2.2.3
* systemd 247.6 -> 249.3
* systemd-boot 247.6 -> 249.3
* systemd-conf 247.6 -> 1.0
* systemtap 4.4 -> 4.5
* systemtap-native 4.4 -> 4.5
* systemtap-uprobes 4.4 -> 4.5
* tcf-agent 1.7.0+gitX (a022ef2f1acf...) -> 1.7.0+gitX (2735e3d6b7ec...)
* texinfo 6.7 -> 6.8
* tiff 4.2.0 -> 4.3.0
* u-boot 2021.01 -> 2021.07
* u-boot-tools 2021.01 -> 2021.07
* usbutils 013 -> 014
* util-linux 2.36.2 -> 2.37.2
* util-linux-libuuid 2.36.2 -> 2.37.2
* vala 0.50.4 -> 0.52.5
* valgrind 3.16.1 -> 3.17.0
* virglrenderer 0.8.2 -> 0.9.1
* vte 0.62.2 -> 0.64.2
* vulkan-headers 1.2.170.0 -> 1.2.182.0
* vulkan-loader 1.2.170.0 -> 1.2.182.0
* vulkan-samples git (55cebd9e7cc4...) -> git (d2187278cb66...)
* vulkan-tools 1.2.170.0 -> 1.2.182.0
* wayland-protocols 1.20 -> 1.21
* webkitgtk 2.30.5 -> 2.32.3
* wireless-regdb 2021.04.21 -> 2021.07.14
* wpebackend-fdo 1.8.0 -> 1.10.0
* x264 r3039+gitX (544c61f08219...) -> r3039+gitX (5db6aa6cab1b...)
* xeyes 1.1.2 -> 1.2.0
* xf86-input-libinput 0.30.0 -> 1.1.0
* xkbcomp 1.4.4 -> 1.4.5
* xkeyboard-config 2.32 -> 2.33
* xorgproto 2020.1 -> 2021.4.99.2
* xserver-xorg 1.20.10 -> 1.20.13
* zstd 1.4.9 -> 1.5.0

</pre>

3.4 Release Notes WIP

2021-10-22T01:01:49Z

PaulEggleton:

<pre>

--------------
Contributors
--------------

Thanks to the following people who contributed to this release:

Adam Romanek
Alejandro Hernandez Samaniego
Alexander Kanavin
Alexandre Belloni
Alexey Brodkin
Alex Stewart
Alistair Francis
Anatol Belski
Anders Wallin
Andrea Adami
Andreas Müller
Andrej Valek
Andres Beltran
Andrey Zhizhikin
Anibal Limon
Anthony Bagwell
Anton Blanchard
Anuj Mittal
Armin Kuster
Asfak Rahman
Bastian Krause
Bernhard Rosenkränzer
Bruce Ashfield
Carlos Rafael Giani
Chandana kalluri
Changhyeok Bae
Changqing Li
Chanho Park
Chen Qi
Chris Laplante
Christophe Chapuis
Christoph Muellner
Claudius Heine
Damian Wrobel
Daniel Ammann
Daniel Gomez
Daniel McGregor
Daniel Wagenknecht
Denys Dmytriyenko
Devendra Tewari
Diego Sueiro
Dmitry Baryshkov
Douglas Royds
Dragos-Marian Panait
Drew Moseley
Enrico Scholz
Fabio Berton
Florian Amstutz
Gavin Li
Guillaume Champagne
Harald Brinkmann
Henning Schild
He Zhe
Hongxu Jia
Hsia-Jun (Randy) Li
Jean Bouchard
Joe Slater
Jonas Höppner
Jon Mason
Jose Quaresma
Joshua Watt
Justin Bronder
Kai Kang
Kenfe-Mickael Laventure
Kevin Hao
Khairul Rohaizzat Jamaluddin
Khem Raj
Kiran Surendran
Konrad Weihmann
Kristian Klausen
Kyle Russell
Lee Chee Yang
Lei Maohui
Luca Boccassi
Marco Felsch
Marcus Comstedt
Marek Vasut
Mark Hatle
Markus Volk
Marta Rybczynska
Martin Jansa
Matthias Klein
Matthias Schiffer
Matt Madison
Matt Spencer
Max Krummenacher
Michael Halstead
Michael Ho
Michael Opdenacker
Mike Crowe
Mikko Rapeli
Ming Liu
Mingli Yu
Minjae Kim
Nicolas Dechesne
Niels Avonds
Nikolay Papenkov
Nisha Parrakat
Olaf Mandel
Oleksandr Kravchuk
Oleksandr Popovych
Oliver Kranz
Otavio Salvador
Patrick Williams
Paul Barker
Paul Eggleton
Paul Gortmaker
Paulo Cesar Zaneti
Peter Bergin
Peter Budny
Peter Kjellerstedt
Petr Vorel
Przemyslaw Gorszkowski
Purushottam Choudhary
Qiang Zhang
Quentin Schulz
Ralph Siemsen
Randy MacLeod
Ranjitsinh Rathod
Rasmus Villemoes
Reto Schneider
Richard Purdie
Richard Weinberger
Robert Joslyn
Robert P. J. Day
Robert Yang
Romain Naour
Ross Burton
Sakib Sajal
Samuli Piippo
Saul Wold
Scott Murray
Scott Weaver
Stefan Ghinea
Stefan Herbrechtsmeier
Stefano Babic
Stefan Wiehler
Steve Sakoman
Teoh Jay Shen
Thomas Perrot
Tim Orling
Tom Pollard
Tom Rini
Tony Battersby
Tony Tascioglu
Trevor Gamblin
Trevor Woerner
Ulrich Ölmann
Valentin Danaila
Vinay Kumar
Vineela Tummalapalli
Vinícius Ossanes Aquino
Vivien Didelot
Vyacheslav Yurkov
Wang Mingyu
Wes Lindauer
William A. Kennington III
Yanfei Xu
Yann Dirson
Yi Fan Yu
Yi Zhao
Zang Ruochen
Zheng Ruoqin
Zoltán Böszörményi

-----------------------------
New Features / Enhancements
-----------------------------

* Linux kernel 5.14, glibc 2.34 and ~280 other recipe upgrades
* Switched override character to ':' (replacing '_') for more robust parsing and improved performance - see migration guide for help on migrating
* Rust integrated into core, providing rust support for cross-compilation and SDK
* New create-spdx class for creating SPDX SBoM documents
* New recipes: cargo, core-image-ptest-all, core-image-ptest-fast, core-image-weston-sdk, erofs-utils, gcompat, gi-docgen, libmicrohttpd, libseccomp, libstd-rs, perlcross, python3-markdown, python3-pyyaml, python3-smartypants, python3-typogrify, rust, rust-cross, rust-cross-canadian, rust-hello-world, rust-llvm, rust-tools-cross-canadian, rustfmt, xwayland
* Several optimisations to reduce unnecessary task dependencies for faster builds
* seccomp integrated into core, with additional enabling for gnutls, systemd, qemu
* New overlayfs class to help generate overlayfs mount units
* debuginfod support now enabled by default
* Switched several recipes over to using OpenSSL instead of GnuTLS (wpa-supplicant, curl, glib-networking) or disable GnuTLS (cups) by default
* Improvements to LTO plugin installation and reproducibility
* Architecture-specific enhancements:
- glibc: Enable memory tagging for aarch64
- testimage: remove aarch64 xorg exclusion
- arch-arm*: add better support for gcc march extensions
- tune-cortexm*: add support for all Arm Cortex-M processors
- tune-cortexr*: add support for all Arm Cortex-R processors
- arch-armv4: Allow -march=armv4
- qemuarm*: use virtio graphics
- baremetal-helloworld: Enable RISC-V 64/32 port
- ldconfig-native: Add RISC-V support
- qemuriscv: Enable 4 core emulation
- Add ARC support in gdb, dpkg, dhcpcd
- conf/machine-sdk: Add ppc64 SDK machine
- libjpeg-turbo: Handle powerpc64le without Altivec
- pixman: Handle PowerPC without Altivec
- mesa: enable gallium Intel drivers when building for x86
- mesa: enable crocus driver for older Intel graphics
* Kernel-related enhancements:
- Support zstd-compressed modules and initramfs images
- Allow opt-out of split kernel modules
- linux-yocto-dev: base AUTOREV on specified version
- kernel-yocto: provide debug / summary information for metadata
- kernel-uboot: Handle gzip and lzo compression options
- linux-yocto/5.14: added devupstream support
- linux-yocto: add vfat KERNEL_FEATURE when MACHINE_FEATURES include vfat
- linux-yocto: enable TYPEC_TCPCI in usbc fragment
* Image-related enhancements:
- New erofs, erofs-lz4 and erofs-lz4hc image types
- New squashfs-zst and cpio.zst image types
- New lic-pkgs IMAGE_FEATURES item to install all license packages
- Added zsync metadata conversion support
- Use xargs to set file timestamps for significant (>90%) do_image speedup
- Find .ko.gz and .ko.xz kernel modules as well when determining need to run depmod on an image
- Show formatted error messages instead of tracebacks for systemctl errors
- No longer ignore installation failures in complementary package installation
- Remove ldconfig auxiliary cache when not needed
* wic enhancements:
- Added erofs filesystem support
- Added --extra-space argument to leave extra space after last partition
- Added --no-fstab-update part option to allow using the stock fstab
- bootimg-efi: added Unified Kernel Image option
- bootimg-pcbios: use label provided when formatting a DOS partition
* SDK-related enhancements:
- Enable do_populate_sdk with multilibs
- New SDKPATHINSTALL variable decouples default install path from built in path to avoid rebuilding nativesdk components on e.g. DISTRO_VERSION changes
- eSDK: Error if trying to generate an eSDK from a multiconfig
- eSDK: introduce TOOLCHAIN_HOST_TASK_ESDK to be used in place of TOOLCHAIN_HOST_TASK to add components to the host part of the eSDK
* bitbake enhancements:
- New bitbake-getvar helper command to query a variable value (with history)
- bitbake-layers: layerindex-fetch: add --fetchdir parameter to
- bitbake-layers: show-recipes: add skip reason to output
- bitbake-diffsigs: sort diff output for consistency
- Allow setting upstream for local hash equivalence server
- fetch2/s3: allow to use credentials and switch profile from environment variables
- fetch2/s3: Add progress handler for S3 cp command
- fetch2/npm: Support npm archives with missing search directory mode
- fetch2/npmsw: Add support for local tarball and link sources
- fetch2/svn: Allow peg-revision functionality to be disabled
- fetch2/wget: verify certificates for HTTPS/FTPS by default
- fetch2/wget: Enable FTPS
- prserv: added read-only mode
- prserv: replaced XML RPC with modern asyncrpc implementation
- Numerous warning/error message improvements
* New PACKAGECONFIG options in btrfs-tools, ccache, coreutils, cups, dbus, elfutils, ffmpeg, findutils, glib-2.0, gstreamer1.0-plugins-bad, gstreamer1.0-plugins-base, libarchive, libnotify, libpsl, man-db, mesa, ovmf, parted, prelink, qemu, rpm, shadow, systemd, tar, vim, weston
* u-boot enhancements:
- Make SPL suffix configurable
- Make UBOOT_BINARYNAME configurable
- Package extlinux.conf separately
- Allow deploying the u-boot DTB
* opensbi: Add support for specifying a device tree
* busybox enhancements:
- Added tmpdir option into mktemp applet
- Support mounting swap via labels
- Enable long options for enabled applets
* Move tune files to architecture subdirectories
* buildstats: log host data on failure separately to task specific file
* buildstats: collect "at interval" and "on failure" logs in the same file
* Ptest enhancements:
- ptest-runner: install script to collect system data on failure
- Added ptest support to python3-hypothesis, python3-jinja2, python3-markupsafe
- Enhanced ptest support in lttng, util-linux, and others
- New leaner ptest image recipes based upon core-image-minimal
* scripts/contrib/image-manifest: add new script
* Add beginnings of Android target support
* devtool upgrade: rebase override-only patches as well
* devtool: print a warning on upgrades if PREFERRED_VERSION is set
* systemd: set zstd as default compression option
* init-manager-systemd: add a weak VIRTUAL-RUNTIME_dev_manager assignment
* Add proper unpack dependency for .zst compressed archives
* util-linux: build chfn and chsh by default
* qemu: use 4 cores in qemu guests
* runqemu: decouple bios and kernel options
* qemu: add a hint on how to enable CPU render nodes when a suitable GPU is absent
* devupstream: Allow support of native class extensions
* python3-manifest: add statistics subpackage
* pypi: Allow override of PyPI archive name
* Allow global override of golang GO_DYNLINK
* New gi-docgen class for GNOME library documentation
* meson.bbclass: Make the default buildtype "debug" if DEBUG_BUILD is 1
* buildhistory enhancements:
- Add option to strip path prefix
- Add output file listing package information
- Label packages providing per-file dependencies in depends.dot
* distro_features_check: expand with IMAGE_FEATURES
* Add extended packagedata in JSON format
* poky: Use https in default PREMIRRORS
* cross-canadian: make android pass target sys check
* local.conf.sample: Update sstate mirror entry with new hash equivalence setting
* tzdata: Allow controlling zoneinfo binary format
* core-image-multilib-example: base on weston, and not sato
* reproducible_build.bbclass: Enable -Wdate-time
* yocto-check-layer: ensure that all layer dependencies are tested too
* npm.bbclass: Allow nodedir to be overridden by NPM_NODEDIR
* cve-extra-exclusions.inc: add exclusion list for intractable CVE's
* license_image.bbclass: Detect broken symlinks
* sysstat: make the service start automatically
* sanity: Add error check for '%' in build path
* sanity: Further improve directory sanity tests
* sanity.bbclass: mention CONNECTIVITY_CHECK_URIS in network failure message
* oe-time-dd-test.sh: add options and refactor
* vim: add option to disable NLS support
* zstd: Include pzstd in the build
* mirrors.bbclass: provide additional rule for git repo fallbacks
* own-mirrors: Add support for s3:// scheme in SOURCE_MIRROR_URL
* common-licenses: add missing SPDX licences
* Add MAINTAINERS.md file

* pulseaudio: Drop pulseaudio-conf
* rpm: do not RRECOMMEND rpm-build

-------------
Known Issues
-------------

* Build failures have been reported when running on host Linux systems with FIPS enabled (such as RHEL 8.0 with the FIPS mode enabled). For more details please see https://bugzilla.yoctoproject.org/show_bug.cgi?id=14609.

-----------------
Recipe Licenses
-----------------

The following corrections have been made to the LICENSE values set by recipes:

* acpica: correct LICENSE to "Intel | BSD-3-Clause | GPLv2"
* dtc: correct LICENSE to "GPLv2 | BSD-2-Clause"
* e2fsprogs: correct LICENSE to "GPLv2 & LGPLv2 & BSD-3-Clause & MIT"
* ffmpeg: correct LICENSE to "GPLv2+ & LGPLv2.1+ & ISC & MIT & BSD-2-Clause & BSD-3-Clause & IJG"
* flac: correct LICENSE to "GFDL-1.2 & GPLv2+ & LGPLv2.1+ & BSD-3-Clause"
* flex: correct LICENSE to "BSD-3-Clause & LGPL-2.0+"
* font-util: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* glib-2.0: correct LICENSE to "LGPLv2.1+ & BSD-3-Clause & PD"
* gobject-introspection: correct LICENSE to "LGPLv2+ & GPLv2+ & MIT" (add MIT license)
* hdparm: correct LICENSE to "BSD-2-Clause & GPLv2 & hdparm"
* iputils: correct LICENSE to "BSD-3-Clause & GPLv2+"
* libcap: correct LICENSE to "BSD-3-Clause | GPLv2"
* libevent: correct LICENSE to "BSD-3-Clause & MIT"
* libjitterentropy: correct LICENSE to "GPLv2+ | BSD-3-Clause"
* libpam: correct LICENSE to "GPLv2+ | BSD-3-Clause"
* libwpe: correct LICENSE to "BSD-2-Clause"
* libx11-compose-data: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libx11: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libxfont2: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libxfont: correct LICENSE to "MIT & MIT-style & BSD-3-Clause"
* lsof: correct LICENSE to reflect that it uses a BSD-like (but not exactly BSD) license ("Spencer-94")
* nfs-utils: correct LICENSE to "MIT & GPLv2+ & BSD-3-Clause"
* ovmf: correct license to "BSD-2-Clause-Patent"
* ppp: correct LICENSE to "BSD-3-Clause & BSD-3-Clause-Attribution & GPLv2+ & LGPLv2+ & PD"
* python3-packaging: correct LICENSE to "Apache-2.0 | BSD-2-Clause"
* python-async-test: correct LICENSE to "BSD-3-Clause"
* quota: remove BSD license (only BSD licensed part of the code was removed in 4.05)
* shadow: correct LICENSE to "BSD-3-Clause | Artistic-1.0"
* shadow-sysroot: set LICENSE the same as shadow
* sudo: correct LICENSE to "ISC & BSD-3-Clause & BSD-2-Clause & Zlib"
* swig: correct LICENSE to "BSD-3-Clause & GPLv3"
* valgrind: correct license to "GPLv2 & GPLv2+ & BSD-3-Clause"
* webkitgtk: correct LICENSE to "BSD-2-Clause & LGPLv2+"
* wpebackend-fdo: correct LICENSE to "BSD-2-Clause"
* xinetd: correct LICENSE to reflect that it uses a unique BSD-like (but not exactly BSD) license

Other license-related notes:
* When creating recipes for Python software, recipetool will now treat "BSD" as "BSD-3-Clause" for the purposes of setting LICENSE, as that is the most common understanding.
* Please be aware that an initramfs bundled with the kernel using INITRAMFS_IMAGE_BUNDLE should only contain GPLv2-compatible software; this is now mentioned in the documentation.

------------------------
Migration instructions
------------------------

For details on changes that you might need to make when migrating to the Yocto Project 3.4 release from previous releases, please see the following manual:

https://docs.yoctoproject.org/migration-guides/migration-3.4.html

----------------
Security Fixes
----------------

* apr: CVE-2021-35940
* aspell: CVE-2019-25051
* avahi: CVE-2021-3468, CVE-2021-36217
* binutils: CVE-2021-20197
* bluez: CVE-2021-3658
* busybox: CVE-2021-28831
* cairo: CVE-2020-35492
* cpio: CVE-2021-38185
* expat: CVE-2013-0340
* ffmpeg: CVE-2020-20446, CVE-2020-22015, CVE-2020-22021, CVE-2020-22033, CVE-2020-22019, CVE-2021-33815, CVE-2021-38171, CVE-2020-20453
* glibc: CVE-2021-33574, CVE-2021-38604
* inetutils: CVE-2021-40491
* libgcrypt: CVE-2021-40528
* linux-yocto/5.10, 5.14: CVE-2021-3653, CVE-2021-3656
* lz4: CVE-2021-3520
* nettle: CVE-2021-20305
* openssl: CVE-2021-3711, CVE-2021-3712
* perl: CVE-2021-36770
* python3: CVE-2021-29921
* python3-pip: CVE-2021-3572
* qemu: CVE-2020-27821, CVE-2020-29443, CVE-2020-35517, CVE-2021-3392, CVE-2021-3409, CVE-2021-3416, CVE-2021-3527, CVE-2021-3544, CVE-2021-3545, CVE-2021-3546, CVE-2021-3682, CVE-2021-20181, CVE-2021-20221, CVE-2021-20257, CVE-2021-20263
* rpm: CVE-2021-3421, CVE-2021-20271
* rsync: CVE-2020-14387
* util-linux: CVE-2021-37600
* vim: CVE-2021-3770, CVE-2021-3778
* wpa-supplicant: CVE-2021-30004
* xdg-utils: CVE-2020-27748
* xserver-xorg: CVE-2021-3472

-----------------
Recipe Upgrades
-----------------

* acl 2.2.53 -> 2.3.1
* acpica 20210105 -> 20210730
* alsa-lib 1.2.4 -> 1.2.5.1
* alsa-plugins 1.2.2 -> 1.2.5
* alsa-tools 1.2.2 -> 1.2.5
* alsa-topology-conf 1.2.4 -> 1.2.5.1
* alsa-ucm-conf 1.2.4 -> 1.2.5.1
* alsa-utils 1.2.4 -> 1.2.5.1
* alsa-utils-scripts 1.2.4 -> 1.2.5.1
* apt 2.2.2 -> 2.2.4
* at 3.2.1 -> 3.2.2
* at-spi2-core 2.38.0 -> 2.40.3
* autoconf-archive 2019.01.06 -> 2021.02.19
* babeltrace2 2.0.3 -> 2.0.4
* bash 5.1 -> 5.1.8
* bind 9.16.16 -> 9.16.20
* binutils 2.36.1 -> 2.37
* binutils-cross 2.36.1 -> 2.37
* binutils-cross-canadian 2.36.1 -> 2.37
* binutils-cross-testsuite 2.36.1 -> 2.37
* binutils-crosssdk 2.36.1 -> 2.37
* bison 3.7.5 -> 3.7.6
* blktrace 1.2.0+gitX -> 1.3.0+gitX
* bluez5 5.56 -> 5.61
* boost 1.75.0 -> 1.77.0
* boost-build-native 4.3.0 -> 4.4.1
* btrfs-tools 5.10.1 -> 5.13.1
* busybox 1.33.1 -> 1.34.0
* busybox-inittab 1.33.0 -> 1.34.0
* ccache 4.2 -> 4.4
* cmake 3.19.5 -> 3.21.1
* cmake-native 3.19.5 -> 3.21.1
* connman 1.39 -> 1.40
* createrepo-c 0.17.0 -> 0.17.4
* cronie 1.5.5 -> 1.5.7
* cross-localedef-native 2.33 -> 2.34
* cups 2.3.3 -> 2.3.3op2
* curl 7.75.0 -> 7.78.0
* dbus-glib 0.110 -> 0.112
* dejagnu 1.6.2 -> 1.6.3
* diffoscope 172 -> 181
* diffutils 3.7 -> 3.8
* distcc 3.3.5 -> 3.4
* dnf 4.6.0 -> 4.8.0
* dpkg 1.20.7.1 -> 1.20.9
* dtc 1.6.0 -> 1.6.1
* e2fsprogs 1.46.1 -> 1.46.4
* elfutils 0.183 -> 0.185
* ell 0.38 -> 0.43
* enchant2 2.2.15 -> 2.3.1
* epiphany 3.38.2 -> 40.3
* ethtool 5.10 -> 5.13
* expat 2.2.10 -> 2.4.1
* ffmpeg 4.3.2 -> 4.4
* file 5.39 -> 5.40
* freetype 2.10.4 -> 2.11.0
* gcc 10.2.0 -> 11.2.0
* gcc-cross 10.2.0 -> 11.2.0
* gcc-cross-canadian 10.2.0 -> 11.2.0
* gcc-crosssdk 10.2.0 -> 11.2.0
* gcc-runtime 10.2.0 -> 11.2.0
* gcc-sanitizers 10.2.0 -> 11.2.0
* gcc-source 10.2.0 -> 11.2.0
* gcr 3.38.1 -> 3.40.0
* gdb 10.1 -> 10.2
* gdb-cross 10.1 -> 10.2
* gdb-cross-canadian 10.1 -> 10.2
* gdk-pixbuf 2.40.0 -> 2.42.6
* ghostscript 9.53.3 -> 9.54.0
* git 2.31.1 -> 2.33.0
* glib-2.0 2.66.7 -> 2.68.4
* glib-networking 2.66.0 -> 2.68.2
* glibc 2.33 -> 2.34
* glibc-locale 2.33 -> 2.34
* glibc-mtrace 2.33 -> 2.34
* glibc-scripts 2.33 -> 2.34
* glibc-testsuite 2.33 -> 2.34
* glslang 11.2.0 -> 11.5.0
* gnome-desktop-testing 2018.1 -> 2021.1
* gnu-config 20210125+gitX -> 20210722+gitX
* gnu-efi 3.0.12 -> 3.0.14
* gnupg 2.2.27 -> 2.3.1
* gobject-introspection 1.66.1 -> 1.68.0
* gpgme 1.15.1 -> 1.16.0
* gptfdisk 1.0.7 -> 1.0.8
* grep 3.6 -> 3.7
* grub 2.04+2.06~rc1 -> 2.06
* grub-efi 2.04+2.06~rc1 -> 2.06
* gsettings-desktop-schemas 3.38.0 -> 40.0
* gtk+3 3.24.25 -> 3.24.30
* harfbuzz 2.7.4 -> 2.9.0
* hdparm 9.60 -> 9.62
* help2man 1.48.2 -> 1.48.4
* hwlatdetect 1.10 -> 2.1
* i2c-tools 4.2 -> 4.3
* icu 68.2 -> 69.1
* igt-gpu-tools 1.25+gitX -> 1.26
* inetutils 2.0 -> 2.1
* iproute2 5.11.0 -> 5.13.0
* iputils s20200821 -> 20210722
* json-glib 1.6.2 -> 1.6.4
* kexec-tools 2.0.21 -> 2.0.22
* kmod 28 -> 29
* kmod-native 28 -> 29
* less 563 -> 590
* libassuan 2.5.4 -> 2.5.5
* libcap 2.48 -> 2.51
* libcgroup 0.41 -> 2.0
* libcomps 0.1.15 -> 0.1.17
* libconvert-asn1-perl 0.27 -> 0.31
* libdazzle 3.38.0 -> 3.40.0
* libdnf 0.58.0 -> 0.63.1
* libdrm 2.4.104 -> 2.4.107
* libedit 20210216-3.1 -> 20210714-3.1
* libepoxy 1.5.5 -> 1.5.9
* liberation-fonts 2.00.1 -> 2.1.4
* libffi 3.3 -> 3.4.2
* libfm 1.3.1 -> 1.3.2
* libgcc 10.2.0 -> 11.2.0
* libgcc-initial 10.2.0 -> 11.2.0
* libgcrypt 1.9.3 -> 1.9.4
* libgfortran 10.2.0 -> 11.2.0
* libgit2 1.1.0 -> 1.1.1
* libglu 9.0.1 -> 9.0.2
* libgpg-error 1.41 -> 1.42
* libgudev 234 -> 237
* libhandy 1.2.0 -> 1.2.3
* libical 3.0.9 -> 3.0.10
* libidn2 2.3.0 -> 2.3.2
* libinput 1.16.4 -> 1.18.1
* libjitterentropy 3.0.1 -> 3.1.0
* libjpeg-turbo 2.0.6 -> 2.1.1
* libksba 1.5.0 -> 1.6.0
* libmodulemd 2.12.0 -> 2.13.0
* libnsl2 1.3.0 -> 2.0.0
* libnss-mdns 0.14.1 -> 0.15.1
* libogg 1.3.4 -> 1.3.5
* libpcap 1.10.0 -> 1.10.1
* libpcre 8.44 -> 8.45
* libpcre2 10.36 -> 10.37
* libportal 0.3 -> 0.4
* librepo 1.13.0 -> 1.14.1
* libsdl2 2.0.14 -> 2.0.16
* libsolv 0.7.17 -> 0.7.19
* libtasn1 4.16.0 -> 4.17.0
* libtest-needs-perl 0.002006 -> 0.002009
* libtirpc 1.3.1 -> 1.3.2
* libubootenv 0.3.1 -> 0.3.2
* libucontext 0.10+X -> 1.1+X
* liburcu 0.12.2 -> 0.13.0
* libuv 1.41.0 -> 1.42.0
* libva 2.10.0 -> 2.12.0
* libva-initial 2.10.0 -> 2.12.0
* libva-utils 2.10.0 -> 2.12.0
* libwebp 1.2.0 -> 1.2.1
* libwpe 1.8.0 -> 1.10.1
* libx11 1.7.0 -> 1.7.2
* libxcrypt 4.4.18 -> 4.4.25
* libxcrypt-compat 4.4.18 -> 4.4.25
* libxfixes 5.0.3 -> 6.0.0
* libxfont2 2.0.4 -> 2.0.5
* libxft 2.3.3 -> 2.3.4
* libxi 1.7.10 -> 1.7.99.2
* libxkbcommon 1.0.3 -> 1.3.0
* libxml2 2.9.10 -> 2.9.12
* libxres 1.2.0 -> 1.2.1
* linux-libc-headers 5.10 -> 5.14
* linux-yocto 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-dev 5.12++gitX -> 5.15++gitX
* linux-yocto-rt 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-tiny 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* llvm 11.1.0 -> 12.0.1
* log4cplus 2.0.6 -> 2.0.7
* logrotate 3.18.0 -> 3.18.1
* ltp 20210121 -> 20210524
* lttng-modules 2.12.6 -> 2.13.0
* lttng-tools 2.12.4 -> 2.13.0
* lttng-ust 2.12.1 -> 2.13.0
* m4 1.4.18 -> 1.4.19
* m4-native 1.4.18 -> 1.4.19
* man-pages 5.10 -> 5.12
* mc 4.8.26 -> 4.8.27
* mesa 21.0.3 -> 21.2.1
* mesa-gl 21.0.3 -> 21.2.1
* meson 0.57.1 -> 0.58.1
* mmc-utils 0.1+gitX (73d6c59af8d1...) -> 0.1+gitX (43282e80e174...)
* mobile-broadband-provider-info 20201225 -> 20210805
* mpg123 1.26.4 -> 1.28.2
* mtd-utils 2.1.2 -> 2.1.3
* mtools 4.0.26 -> 4.0.35
* musl 1.2.2+gitX (e5d2823631bb...) -> 1.2.2+gitX (3f701faace7a...)
* nativesdk-meson 0.57.1 -> 0.58.1
* netbase 6.2 -> 6.3
* nfs-utils 2.5.3 -> 2.5.4
* ofono 1.31 -> 1.32
* openssh 8.5p1 -> 8.7p1
* opkg 0.4.4 -> 0.4.5
* opkg-utils 0.4.3 -> 0.4.5
* ovmf edk2-stable202102 -> edk2-stable202105
* p11-kit 0.23.22 -> 0.24.0
* pango 1.48.2 -> 1.48.9
* patchelf 0.12 -> 0.13
* perl 5.32.1 -> 5.34.0
* piglit 1.0+gitrX (d4d9353b7290...) -> 1.0+gitrX (6a4be9e9946d...)
* pkgconf 1.7.3 -> 1.8.0
* powertop 2.13 -> 2.14
* pseudo 1.9.0+gitX (b988b0a6b8af...) -> 1.9.0+gitX (0cda3ba5f94a...)
* pulseaudio 14.2 -> 15.0
* puzzles 0.0+gitX (84cb4c6701e0...) -> 0.0+gitX (8f3413c31ffd...)
* python3 3.9.5 -> 3.9.6
* python3-attrs 20.3.0 -> 21.2.0
* python3-cython 0.29.22 -> 0.29.24
* python3-dbus 1.2.16 -> 1.2.18
* python3-dbusmock 0.22.0 -> 0.23.1
* python3-docutils 0.16 -> 0.17.1
* python3-git 3.1.14 -> 3.1.20
* python3-gitdb 4.0.5 -> 4.0.7
* python3-hypothesis 6.2.0 -> 6.15.0
* python3-importlib-metadata 3.4.0 -> 4.6.4
* python3-iniparse 0.4 -> 0.5
* python3-jinja2 2.11.3 -> 3.0.1
* python3-libarchive-c 2.9 -> 3.1
* python3-magic 0.4.22 -> 0.4.24
* python3-mako 1.1.4 -> 1.1.5
* python3-markupsafe 1.1.1 -> 2.0.1
* python3-more-itertools 8.7.0 -> 8.8.0
* python3-numpy 1.20.1 -> 1.21.2
* python3-packaging 20.9 -> 21.0
* python3-pathlib2 2.3.5 -> 2.3.6
* python3-pbr 5.4.4 -> 5.6.0
* python3-pip 20.0.2 -> 21.2.4
* python3-pluggy 0.13.1 -> 1.0.0
* python3-pycairo 1.20.0 -> 1.20.1
* python3-pygments 2.8.1 -> 2.10.0
* python3-pygobject 3.38.0 -> 3.40.1
* python3-pytest 6.2.2 -> 6.2.4
* python3-scons 3.1.2 -> 4.2.0
* python3-scons-native 3.1.2 -> 4.2.0
* python3-setuptools 54.1.1 -> 57.4.0
* python3-setuptools-scm 5.0.1 -> 6.0.1
* python3-six 1.15.0 -> 1.16.0
* python3-sortedcontainers 2.3.0 -> 2.4.0
* python3-testtools 2.4.0 -> 2.5.0
* python3-zipp 3.4.1 -> 3.5.0
* qemu 5.2.0 -> 6.0.0
* qemu-native 5.2.0 -> 6.0.0
* qemu-system-native 5.2.0 -> 6.0.0
* re2c 2.0.3 -> 2.2
* rng-tools 6.11 -> 6.14
* rpcbind 1.2.5 -> 1.2.6
* rt-tests 1.10 -> 2.1
* ruby 3.0.1 -> 3.0.2
* rxvt-unicode 9.22 -> 9.26
* shaderc 2020.5 -> 2021.1
* shadow 4.8.1 -> 4.9
* spirv-tools 2020.7 -> 2021.2
* sqlite3 3.35.0 -> 3.36.0
* squashfs-tools 4.4 -> 4.5
* strace 5.11 -> 5.14
* stress-ng 0.12.05 -> 0.13.00
* sudo 1.9.6p1 -> 1.9.7p2
* swig 3.0.12 -> 4.0.2
* sysklogd 2.2.2 -> 2.2.3
* systemd 247.6 -> 249.3
* systemd-boot 247.6 -> 249.3
* systemd-conf 247.6 -> 1.0
* systemtap 4.4 -> 4.5
* systemtap-native 4.4 -> 4.5
* systemtap-uprobes 4.4 -> 4.5
* tcf-agent 1.7.0+gitX (a022ef2f1acf...) -> 1.7.0+gitX (2735e3d6b7ec...)
* texinfo 6.7 -> 6.8
* tiff 4.2.0 -> 4.3.0
* u-boot 2021.01 -> 2021.07
* u-boot-tools 2021.01 -> 2021.07
* usbutils 013 -> 014
* util-linux 2.36.2 -> 2.37.2
* util-linux-libuuid 2.36.2 -> 2.37.2
* vala 0.50.4 -> 0.52.5
* valgrind 3.16.1 -> 3.17.0
* virglrenderer 0.8.2 -> 0.9.1
* vte 0.62.2 -> 0.64.2
* vulkan-headers 1.2.170.0 -> 1.2.182.0
* vulkan-loader 1.2.170.0 -> 1.2.182.0
* vulkan-samples git (55cebd9e7cc4...) -> git (d2187278cb66...)
* vulkan-tools 1.2.170.0 -> 1.2.182.0
* wayland-protocols 1.20 -> 1.21
* webkitgtk 2.30.5 -> 2.32.3
* wireless-regdb 2021.04.21 -> 2021.07.14
* wpebackend-fdo 1.8.0 -> 1.10.0
* x264 r3039+gitX (544c61f08219...) -> r3039+gitX (5db6aa6cab1b...)
* xeyes 1.1.2 -> 1.2.0
* xf86-input-libinput 0.30.0 -> 1.1.0
* xkbcomp 1.4.4 -> 1.4.5
* xkeyboard-config 2.32 -> 2.33
* xorgproto 2020.1 -> 2021.4.99.2
* xserver-xorg 1.20.10 -> 1.20.13
* zstd 1.4.9 -> 1.5.0

</pre>

3.4 Release Notes WIP

2021-10-22T00:45:03Z

PaulEggleton:

<pre>

--------------
Contributors
--------------

Thanks to the following people who contributed to this release:

Adam Romanek
Alejandro Hernandez Samaniego
Alexander Kanavin
Alexandre Belloni
Alexey Brodkin
Alex Stewart
Alistair Francis
Anatol Belski
Anders Wallin
Andrea Adami
Andreas Müller
Andrej Valek
Andres Beltran
Andrey Zhizhikin
Anibal Limon
Anthony Bagwell
Anton Blanchard
Anuj Mittal
Armin Kuster
Asfak Rahman
Bastian Krause
Bernhard Rosenkränzer
Bruce Ashfield
Carlos Rafael Giani
Chandana kalluri
Changhyeok Bae
Changqing Li
Chanho Park
Chen Qi
Chris Laplante
Christophe Chapuis
Christoph Muellner
Claudius Heine
Damian Wrobel
Daniel Ammann
Daniel Gomez
Daniel McGregor
Daniel Wagenknecht
Denys Dmytriyenko
Devendra Tewari
Diego Sueiro
Dmitry Baryshkov
Douglas Royds
Dragos-Marian Panait
Drew Moseley
Enrico Scholz
Fabio Berton
Florian Amstutz
Gavin Li
Guillaume Champagne
Harald Brinkmann
Henning Schild
He Zhe
Hongxu Jia
Hsia-Jun (Randy) Li
Jean Bouchard
Joe Slater
Jonas Höppner
Jon Mason
Jose Quaresma
Joshua Watt
Justin Bronder
Kai Kang
Kenfe-Mickael Laventure
Kevin Hao
Khairul Rohaizzat Jamaluddin
Khem Raj
Kiran Surendran
Konrad Weihmann
Kristian Klausen
Kyle Russell
Lee Chee Yang
Lei Maohui
Luca Boccassi
Marco Felsch
Marcus Comstedt
Marek Vasut
Mark Hatle
Markus Volk
Marta Rybczynska
Martin Jansa
Matthias Klein
Matthias Schiffer
Matt Madison
Matt Spencer
Max Krummenacher
Michael Halstead
Michael Ho
Michael Opdenacker
Mike Crowe
Mikko Rapeli
Ming Liu
Mingli Yu
Minjae Kim
Nicolas Dechesne
Niels Avonds
Nikolay Papenkov
Nisha Parrakat
Olaf Mandel
Oleksandr Kravchuk
Oleksandr Popovych
Oliver Kranz
Otavio Salvador
Patrick Williams
Paul Barker
Paul Eggleton
Paul Gortmaker
Paulo Cesar Zaneti
Peter Bergin
Peter Budny
Peter Kjellerstedt
Petr Vorel
Przemyslaw Gorszkowski
Purushottam Choudhary
Qiang Zhang
Quentin Schulz
Ralph Siemsen
Randy MacLeod
Ranjitsinh Rathod
Rasmus Villemoes
Reto Schneider
Richard Purdie
Richard Weinberger
Robert Joslyn
Robert P. J. Day
Robert Yang
Romain Naour
Ross Burton
Sakib Sajal
Samuli Piippo
Saul Wold
Scott Murray
Scott Weaver
Stefan Ghinea
Stefan Herbrechtsmeier
Stefano Babic
Stefan Wiehler
Steve Sakoman
Teoh Jay Shen
Thomas Perrot
Tim Orling
Tom Pollard
Tom Rini
Tony Battersby
Tony Tascioglu
Trevor Gamblin
Trevor Woerner
Ulrich Ölmann
Valentin Danaila
Vinay Kumar
Vineela Tummalapalli
Vinícius Ossanes Aquino
Vivien Didelot
Vyacheslav Yurkov
Wang Mingyu
Wes Lindauer
William A. Kennington III
Yanfei Xu
Yann Dirson
Yi Fan Yu
Yi Zhao
Zang Ruochen
Zheng Ruoqin
Zoltán Böszörményi

-----------------------------
New Features / Enhancements
-----------------------------

* Linux kernel 5.14, glibc 2.34 and ~280 other recipe upgrades
* Switched override character to ':' (replacing '_') for more robust parsing and improved performance - see migration guide for help on migrating
* Rust integrated into core, providing rust support for cross-compilation and SDK
* New create-spdx class for creating SPDX SBoM documents
* New recipes: cargo, core-image-ptest-all, core-image-ptest-fast, core-image-weston-sdk, erofs-utils, gcompat, gi-docgen, libmicrohttpd, libseccomp, libstd-rs, perlcross, python3-markdown, python3-pyyaml, python3-smartypants, python3-typogrify, rust, rust-cross, rust-cross-canadian, rust-hello-world, rust-llvm, rust-tools-cross-canadian, rustfmt, xwayland
* Several optimisations to reduce unnecessary task dependencies for faster builds
* seccomp integrated into core, with additional enabling for gnutls, systemd, qemu
* New overlayfs class to help generate overlayfs mount units
* debuginfod support now enabled by default
* Switched several recipes over to using OpenSSL instead of GnuTLS (wpa-supplicant, curl, glib-networking) or disable GnuTLS (cups) by default
* Improvements to LTO plugin installation and reproducibility
* Architecture-specific enhancements:
- glibc: Enable memory tagging for aarch64
- testimage: remove aarch64 xorg exclusion
- arch-arm*: add better support for gcc march extensions
- tune-cortexm*: add support for all Arm Cortex-M processors
- tune-cortexr*: add support for all Arm Cortex-R processors
- arch-armv4: Allow -march=armv4
- qemuarm*: use virtio graphics
- baremetal-helloworld: Enable RISC-V 64/32 port
- ldconfig-native: Add RISC-V support
- qemuriscv: Enable 4 core emulation
- Add ARC support in gdb, dpkg, dhcpcd
- conf/machine-sdk: Add ppc64 SDK machine
- libjpeg-turbo: Handle powerpc64le without Altivec
- pixman: Handle PowerPC without Altivec
- mesa: enable gallium intel drivers when building for x86
- mesa: enable crocus driver for older intel graphics
* Kernel-related enhancements:
- Support zstd-compressed modules and initramfs images
- Allow opt-out of split kernel modules
- linux-yocto-dev: base AUTOREV on specified version
- kernel-yocto: provide debug / summary information for metadata
- kernel-uboot: Handle gzip and lzo compression options
- linux-yocto/5.14: added devupstream support
- linux-yocto: add vfat KERNEL_FEATURE when MACHINE_FEATURES include vfat
- linux-yocto: enable TYPEC_TCPCI in usbc fragment
* Image-related enhancements:
- New erofs, erofs-lz4 and erofs-lz4hc image types
- New squashfs-zst and cpio.zst image types
- New lic-pkgs IMAGE_FEATURES item to install all license packages
- Added zsync metadata conversion support
- Use xargs to set file timestamps for significant (>90%) do_image speedup
- Find .ko.gz and .ko.xz kernel modules as well when determining need to run depmod on an image
- Show formatted error messages instead of tracebacks for systemctl errors
- No longer ignore installation failures in complementary package installation
- Remove ldconfig auxiliary cache when not needed
* wic enhancements:
- Added erofs filesystem support
- Added --extra-space argument to leave extra space after last partition
- Added --no-fstab-update part option to allow using the stock fstab
- bootimg-efi: added Unified Kernel Image option
- bootimg-pcbios: use label provided when formatting a DOS partition
* SDK-related enhancements:
- Enable do_populate_sdk with multilibs
- New SDKPATHINSTALL variable decouples default install path from built in path to avoid rebuilding nativesdk components on e.g. DISTRO_VERSION changes
- eSDK: Error if trying to generate an eSDK from a multiconfig
- eSDK: introduce TOOLCHAIN_HOST_TASK_ESDK to be used in place of TOOLCHAIN_HOST_TASK to add components to the host part of the eSDK
* New PACKAGECONFIG options in btrfs-tools, ccache, coreutils, cups, dbus, elfutils, ffmpeg, findutils, glib-2.0, gstreamer1.0-plugins-bad, gstreamer1.0-plugins-base, libarchive, libnotify, libpsl, man-db, mesa, ovmf, parted, prelink, qemu, rpm, shadow, systemd, tar, vim, weston
* busybox enhancements:
- Added tmpdir option into mktemp applet
- Support mounting swap via labels
- Enable long options for enabled applets
* Move tune files to architecture subdirectories
* buildstats: log host data on failure separately to task specific file
* buildstats: collect "at interval" and "on failure" logs in the same file
* Ptest enhancements:
- ptest-runner: install script to collect system data on failure
- Added ptest support to python3-hypothesis, python3-jinja2, python3-markupsafe
- Enhanced ptest support in lttng, util-linux, and others
- New leaner ptest image recipes based upon core-image-minimal
* scripts/contrib/image-manifest: add new script
* Add beginnings of Android target support
* devtool upgrade: rebase override-only patches as well
* devtool: print a warning on upgrades if PREFERRED_VERSION is set
* systemd: set zstd as default compression option
* init-manager-systemd: add a weak VIRTUAL-RUNTIME_dev_manager assignment
* Add proper unpack dependency for .zst compressed archives
* util-linux: build chfn and chsh by default
* qemu: use 4 cores in qemu guests
* runqemu: decouple bios and kernel options
* qemu: add a hint on how to enable CPU render nodes when a suitable GPU is absent
* devupstream: Allow support of native class extensions
* python3-manifest: add statistics subpackage
* pypi: Allow override of PyPI archive name
* Allow global override of golang GO_DYNLINK
* New gi-docgen class for GNOME library documentation
* meson.bbclass: Make the default buildtype "debug" if DEBUG_BUILD is 1
* buildhistory enhancements:
- Add option to strip path prefix
- Add output file listing package information
- Label packages providing per-file dependencies in depends.dot
* distro_features_check: expand with IMAGE_FEATURES
* u-boot enhancements:
- Make SPL suffix configurable
- Make UBOOT_BINARYNAME configurable
- Package extlinux.conf separately
- Allow deploying the u-boot DTB
* opensbi: Add support for specifying a device tree
* Add extended packagedata in JSON format
* poky: Use https in default PREMIRRORS
* cross-canadian: make android pass target sys check
* local.conf.sample: Update sstate mirror entry with new hash equivalence setting
* tzdata: Allow controlling zoneinfo binary format
* bitbake enhancements:
- New bitbake-getvar helper command to query a variable value (with history)
- bitbake-layers: add --fetchdir parameter to layerindex-fetch
- bitbake-layers: add skip reason to output
- bitbake-diffsigs: sort diff output for consistency
- cooker: Allow upstream for local hash equivalence server
- fetch2/s3: allow to use credentials and switch profile from environment variables
- fetch2/s3: Add progress handler for S3 cp command
- fetch2/wget: fetch securely by default
- fetch2/wget: Enable ftps
- fetch2/svn: Allow peg-revision functionality to be disabled
- fetch2: npm: Support npm archives with missing search directory mode
- fetch2: npmsw: Add support for local tarball and link sources
- prserv: added read-only mode
- prserv: replaced XML RPC with modern asyncrpc implementation
- Numerous warning/error message improvements
* core-image-multilib-example: base on weston, and not sato
* reproducible_build.bbclass: Enable -Wdate-time
* yocto-check-layer: ensure that all layer dependencies are tested too
* npm.bbclass: Allow nodedir to be overridden by NPM_NODEDIR
* cve-extra-exclusions.inc: add exclusion list for intractable CVE's
* license_image.bbclass: Detect broken symlinks
* sysstat: make the service start automatically
* sanity: Add error check for '%' in build path
* sanity: Further improve directory sanity tests
* sanity.bbclass: mention CONNECTIVITY_CHECK_URIS in network failure message
* oe-time-dd-test.sh: add options and refactor
* vim: add option to disable NLS support
* zstd: Include pzstd in the build
* mirrors.bbclass: provide additional rule for git repo fallbacks
* own-mirrors: Add support for s3:// scheme in SOURCE_MIRROR_URL
* common-licenses: add missing SPDX licences
* Add MAINTAINERS.md file

* pulseaudio: Drop pulseaudio-conf
* rpm: do not RRECOMMEND rpm-build

-------------
Known Issues
-------------

* Build failures have been reported when running on host Linux systems with FIPS enabled (such as RHEL 8.0 with the FIPS mode enabled). For more details please see https://bugzilla.yoctoproject.org/show_bug.cgi?id=14609.

-----------------
Recipe Licenses
-----------------

The following corrections have been made to the LICENSE values set by recipes:

* acpica: correct LICENSE to "Intel | BSD-3-Clause | GPLv2"
* dtc: correct LICENSE to "GPLv2 | BSD-2-Clause"
* e2fsprogs: correct LICENSE to "GPLv2 & LGPLv2 & BSD-3-Clause & MIT"
* ffmpeg: correct LICENSE to "GPLv2+ & LGPLv2.1+ & ISC & MIT & BSD-2-Clause & BSD-3-Clause & IJG"
* flac: correct LICENSE to "GFDL-1.2 & GPLv2+ & LGPLv2.1+ & BSD-3-Clause"
* flex: correct LICENSE to "BSD-3-Clause & LGPL-2.0+"
* font-util: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* glib-2.0: correct LICENSE to "LGPLv2.1+ & BSD-3-Clause & PD"
* gobject-introspection: correct LICENSE to "LGPLv2+ & GPLv2+ & MIT" (add MIT license)
* hdparm: correct LICENSE to "BSD-2-Clause & GPLv2 & hdparm"
* iputils: correct LICENSE to "BSD-3-Clause & GPLv2+"
* libcap: correct LICENSE to "BSD-3-Clause | GPLv2"
* libevent: correct LICENSE to "BSD-3-Clause & MIT"
* libjitterentropy: correct LICENSE to "GPLv2+ | BSD-3-Clause"
* libpam: correct LICENSE to "GPLv2+ | BSD-3-Clause"
* libwpe: correct LICENSE to "BSD-2-Clause"
* libx11-compose-data: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libx11: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libxfont2: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libxfont: correct LICENSE to "MIT & MIT-style & BSD-3-Clause"
* lsof: correct LICENSE to reflect that it uses a BSD-like (but not exactly BSD) license ("Spencer-94")
* nfs-utils: correct LICENSE to "MIT & GPLv2+ & BSD-3-Clause"
* ovmf: correct license to "BSD-2-Clause-Patent"
* ppp: correct LICENSE to "BSD-3-Clause & BSD-3-Clause-Attribution & GPLv2+ & LGPLv2+ & PD"
* python3-packaging: correct LICENSE to "Apache-2.0 | BSD-2-Clause"
* python-async-test: correct LICENSE to "BSD-3-Clause"
* quota: remove BSD license (only BSD licensed part of the code was removed in 4.05)
* shadow: correct LICENSE to "BSD-3-Clause | Artistic-1.0"
* shadow-sysroot: set LICENSE the same as shadow
* sudo: correct LICENSE to "ISC & BSD-3-Clause & BSD-2-Clause & Zlib"
* swig: correct LICENSE to "BSD-3-Clause & GPLv3"
* valgrind: correct license to "GPLv2 & GPLv2+ & BSD-3-Clause"
* webkitgtk: correct LICENSE to "BSD-2-Clause & LGPLv2+"
* wpebackend-fdo: correct LICENSE to "BSD-2-Clause"
* xinetd: correct LICENSE to reflect that it uses a unique BSD-like (but not exactly BSD) license

Other license-related notes:
* When creating recipes for Python software, recipetool will now treat "BSD" as "BSD-3-Clause" for the purposes of setting LICENSE, as that is the most common understanding.
* Please be aware that an initramfs bundled with the kernel using INITRAMFS_IMAGE_BUNDLE should only contain GPLv2-compatible software; this is now mentioned in the documentation.

------------------------
Migration instructions
------------------------

For details on changes that you might need to make when migrating to the Yocto Project 3.4 release from previous releases, please see the following manual:

https://docs.yoctoproject.org/migration-guides/migration-3.4.html

----------------
Security Fixes
----------------

* apr: CVE-2021-35940
* aspell: CVE-2019-25051
* avahi: CVE-2021-3468, CVE-2021-36217
* binutils: CVE-2021-20197
* bluez: CVE-2021-3658
* busybox: CVE-2021-28831
* cairo: CVE-2020-35492
* cpio: CVE-2021-38185
* expat: CVE-2013-0340
* ffmpeg: CVE-2020-20446, CVE-2020-22015, CVE-2020-22021, CVE-2020-22033, CVE-2020-22019, CVE-2021-33815, CVE-2021-38171, CVE-2020-20453
* glibc: CVE-2021-33574, CVE-2021-38604
* inetutils: CVE-2021-40491
* libgcrypt: CVE-2021-40528
* linux-yocto/5.10, 5.14: CVE-2021-3653, CVE-2021-3656
* lz4: CVE-2021-3520
* nettle: CVE-2021-20305
* openssl: CVE-2021-3711, CVE-2021-3712
* perl: CVE-2021-36770
* python3: CVE-2021-29921
* python3-pip: CVE-2021-3572
* qemu: CVE-2020-27821, CVE-2020-29443, CVE-2020-35517, CVE-2021-3392, CVE-2021-3409, CVE-2021-3416, CVE-2021-3527, CVE-2021-3544, CVE-2021-3545, CVE-2021-3546, CVE-2021-3682, CVE-2021-20181, CVE-2021-20221, CVE-2021-20257, CVE-2021-20263
* rpm: CVE-2021-3421, CVE-2021-20271
* rsync: CVE-2020-14387
* util-linux: CVE-2021-37600
* vim: CVE-2021-3770, CVE-2021-3778
* wpa-supplicant: CVE-2021-30004
* xdg-utils: CVE-2020-27748
* xserver-xorg: CVE-2021-3472

-----------------
Recipe Upgrades
-----------------

* acl 2.2.53 -> 2.3.1
* acpica 20210105 -> 20210730
* alsa-lib 1.2.4 -> 1.2.5.1
* alsa-plugins 1.2.2 -> 1.2.5
* alsa-tools 1.2.2 -> 1.2.5
* alsa-topology-conf 1.2.4 -> 1.2.5.1
* alsa-ucm-conf 1.2.4 -> 1.2.5.1
* alsa-utils 1.2.4 -> 1.2.5.1
* alsa-utils-scripts 1.2.4 -> 1.2.5.1
* apt 2.2.2 -> 2.2.4
* at 3.2.1 -> 3.2.2
* at-spi2-core 2.38.0 -> 2.40.3
* autoconf-archive 2019.01.06 -> 2021.02.19
* babeltrace2 2.0.3 -> 2.0.4
* bash 5.1 -> 5.1.8
* bind 9.16.16 -> 9.16.20
* binutils 2.36.1 -> 2.37
* binutils-cross 2.36.1 -> 2.37
* binutils-cross-canadian 2.36.1 -> 2.37
* binutils-cross-testsuite 2.36.1 -> 2.37
* binutils-crosssdk 2.36.1 -> 2.37
* bison 3.7.5 -> 3.7.6
* blktrace 1.2.0+gitX -> 1.3.0+gitX
* bluez5 5.56 -> 5.61
* boost 1.75.0 -> 1.77.0
* boost-build-native 4.3.0 -> 4.4.1
* btrfs-tools 5.10.1 -> 5.13.1
* busybox 1.33.1 -> 1.34.0
* busybox-inittab 1.33.0 -> 1.34.0
* ccache 4.2 -> 4.4
* cmake 3.19.5 -> 3.21.1
* cmake-native 3.19.5 -> 3.21.1
* connman 1.39 -> 1.40
* createrepo-c 0.17.0 -> 0.17.4
* cronie 1.5.5 -> 1.5.7
* cross-localedef-native 2.33 -> 2.34
* cups 2.3.3 -> 2.3.3op2
* curl 7.75.0 -> 7.78.0
* dbus-glib 0.110 -> 0.112
* dejagnu 1.6.2 -> 1.6.3
* diffoscope 172 -> 181
* diffutils 3.7 -> 3.8
* distcc 3.3.5 -> 3.4
* dnf 4.6.0 -> 4.8.0
* dpkg 1.20.7.1 -> 1.20.9
* dtc 1.6.0 -> 1.6.1
* e2fsprogs 1.46.1 -> 1.46.4
* elfutils 0.183 -> 0.185
* ell 0.38 -> 0.43
* enchant2 2.2.15 -> 2.3.1
* epiphany 3.38.2 -> 40.3
* ethtool 5.10 -> 5.13
* expat 2.2.10 -> 2.4.1
* ffmpeg 4.3.2 -> 4.4
* file 5.39 -> 5.40
* freetype 2.10.4 -> 2.11.0
* gcc 10.2.0 -> 11.2.0
* gcc-cross 10.2.0 -> 11.2.0
* gcc-cross-canadian 10.2.0 -> 11.2.0
* gcc-crosssdk 10.2.0 -> 11.2.0
* gcc-runtime 10.2.0 -> 11.2.0
* gcc-sanitizers 10.2.0 -> 11.2.0
* gcc-source 10.2.0 -> 11.2.0
* gcr 3.38.1 -> 3.40.0
* gdb 10.1 -> 10.2
* gdb-cross 10.1 -> 10.2
* gdb-cross-canadian 10.1 -> 10.2
* gdk-pixbuf 2.40.0 -> 2.42.6
* ghostscript 9.53.3 -> 9.54.0
* git 2.31.1 -> 2.33.0
* glib-2.0 2.66.7 -> 2.68.4
* glib-networking 2.66.0 -> 2.68.2
* glibc 2.33 -> 2.34
* glibc-locale 2.33 -> 2.34
* glibc-mtrace 2.33 -> 2.34
* glibc-scripts 2.33 -> 2.34
* glibc-testsuite 2.33 -> 2.34
* glslang 11.2.0 -> 11.5.0
* gnome-desktop-testing 2018.1 -> 2021.1
* gnu-config 20210125+gitX -> 20210722+gitX
* gnu-efi 3.0.12 -> 3.0.14
* gnupg 2.2.27 -> 2.3.1
* gobject-introspection 1.66.1 -> 1.68.0
* gpgme 1.15.1 -> 1.16.0
* gptfdisk 1.0.7 -> 1.0.8
* grep 3.6 -> 3.7
* grub 2.04+2.06~rc1 -> 2.06
* grub-efi 2.04+2.06~rc1 -> 2.06
* gsettings-desktop-schemas 3.38.0 -> 40.0
* gtk+3 3.24.25 -> 3.24.30
* harfbuzz 2.7.4 -> 2.9.0
* hdparm 9.60 -> 9.62
* help2man 1.48.2 -> 1.48.4
* hwlatdetect 1.10 -> 2.1
* i2c-tools 4.2 -> 4.3
* icu 68.2 -> 69.1
* igt-gpu-tools 1.25+gitX -> 1.26
* inetutils 2.0 -> 2.1
* iproute2 5.11.0 -> 5.13.0
* iputils s20200821 -> 20210722
* json-glib 1.6.2 -> 1.6.4
* kexec-tools 2.0.21 -> 2.0.22
* kmod 28 -> 29
* kmod-native 28 -> 29
* less 563 -> 590
* libassuan 2.5.4 -> 2.5.5
* libcap 2.48 -> 2.51
* libcgroup 0.41 -> 2.0
* libcomps 0.1.15 -> 0.1.17
* libconvert-asn1-perl 0.27 -> 0.31
* libdazzle 3.38.0 -> 3.40.0
* libdnf 0.58.0 -> 0.63.1
* libdrm 2.4.104 -> 2.4.107
* libedit 20210216-3.1 -> 20210714-3.1
* libepoxy 1.5.5 -> 1.5.9
* liberation-fonts 2.00.1 -> 2.1.4
* libffi 3.3 -> 3.4.2
* libfm 1.3.1 -> 1.3.2
* libgcc 10.2.0 -> 11.2.0
* libgcc-initial 10.2.0 -> 11.2.0
* libgcrypt 1.9.3 -> 1.9.4
* libgfortran 10.2.0 -> 11.2.0
* libgit2 1.1.0 -> 1.1.1
* libglu 9.0.1 -> 9.0.2
* libgpg-error 1.41 -> 1.42
* libgudev 234 -> 237
* libhandy 1.2.0 -> 1.2.3
* libical 3.0.9 -> 3.0.10
* libidn2 2.3.0 -> 2.3.2
* libinput 1.16.4 -> 1.18.1
* libjitterentropy 3.0.1 -> 3.1.0
* libjpeg-turbo 2.0.6 -> 2.1.1
* libksba 1.5.0 -> 1.6.0
* libmodulemd 2.12.0 -> 2.13.0
* libnsl2 1.3.0 -> 2.0.0
* libnss-mdns 0.14.1 -> 0.15.1
* libogg 1.3.4 -> 1.3.5
* libpcap 1.10.0 -> 1.10.1
* libpcre 8.44 -> 8.45
* libpcre2 10.36 -> 10.37
* libportal 0.3 -> 0.4
* librepo 1.13.0 -> 1.14.1
* libsdl2 2.0.14 -> 2.0.16
* libsolv 0.7.17 -> 0.7.19
* libtasn1 4.16.0 -> 4.17.0
* libtest-needs-perl 0.002006 -> 0.002009
* libtirpc 1.3.1 -> 1.3.2
* libubootenv 0.3.1 -> 0.3.2
* libucontext 0.10+X -> 1.1+X
* liburcu 0.12.2 -> 0.13.0
* libuv 1.41.0 -> 1.42.0
* libva 2.10.0 -> 2.12.0
* libva-initial 2.10.0 -> 2.12.0
* libva-utils 2.10.0 -> 2.12.0
* libwebp 1.2.0 -> 1.2.1
* libwpe 1.8.0 -> 1.10.1
* libx11 1.7.0 -> 1.7.2
* libxcrypt 4.4.18 -> 4.4.25
* libxcrypt-compat 4.4.18 -> 4.4.25
* libxfixes 5.0.3 -> 6.0.0
* libxfont2 2.0.4 -> 2.0.5
* libxft 2.3.3 -> 2.3.4
* libxi 1.7.10 -> 1.7.99.2
* libxkbcommon 1.0.3 -> 1.3.0
* libxml2 2.9.10 -> 2.9.12
* libxres 1.2.0 -> 1.2.1
* linux-libc-headers 5.10 -> 5.14
* linux-yocto 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-dev 5.12++gitX -> 5.15++gitX
* linux-yocto-rt 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-tiny 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* llvm 11.1.0 -> 12.0.1
* log4cplus 2.0.6 -> 2.0.7
* logrotate 3.18.0 -> 3.18.1
* ltp 20210121 -> 20210524
* lttng-modules 2.12.6 -> 2.13.0
* lttng-tools 2.12.4 -> 2.13.0
* lttng-ust 2.12.1 -> 2.13.0
* m4 1.4.18 -> 1.4.19
* m4-native 1.4.18 -> 1.4.19
* man-pages 5.10 -> 5.12
* mc 4.8.26 -> 4.8.27
* mesa 21.0.3 -> 21.2.1
* mesa-gl 21.0.3 -> 21.2.1
* meson 0.57.1 -> 0.58.1
* mmc-utils 0.1+gitX (73d6c59af8d1...) -> 0.1+gitX (43282e80e174...)
* mobile-broadband-provider-info 20201225 -> 20210805
* mpg123 1.26.4 -> 1.28.2
* mtd-utils 2.1.2 -> 2.1.3
* mtools 4.0.26 -> 4.0.35
* musl 1.2.2+gitX (e5d2823631bb...) -> 1.2.2+gitX (3f701faace7a...)
* nativesdk-meson 0.57.1 -> 0.58.1
* netbase 6.2 -> 6.3
* nfs-utils 2.5.3 -> 2.5.4
* ofono 1.31 -> 1.32
* openssh 8.5p1 -> 8.7p1
* opkg 0.4.4 -> 0.4.5
* opkg-utils 0.4.3 -> 0.4.5
* ovmf edk2-stable202102 -> edk2-stable202105
* p11-kit 0.23.22 -> 0.24.0
* pango 1.48.2 -> 1.48.9
* patchelf 0.12 -> 0.13
* perl 5.32.1 -> 5.34.0
* piglit 1.0+gitrX (d4d9353b7290...) -> 1.0+gitrX (6a4be9e9946d...)
* pkgconf 1.7.3 -> 1.8.0
* powertop 2.13 -> 2.14
* pseudo 1.9.0+gitX (b988b0a6b8af...) -> 1.9.0+gitX (0cda3ba5f94a...)
* pulseaudio 14.2 -> 15.0
* puzzles 0.0+gitX (84cb4c6701e0...) -> 0.0+gitX (8f3413c31ffd...)
* python3 3.9.5 -> 3.9.6
* python3-attrs 20.3.0 -> 21.2.0
* python3-cython 0.29.22 -> 0.29.24
* python3-dbus 1.2.16 -> 1.2.18
* python3-dbusmock 0.22.0 -> 0.23.1
* python3-docutils 0.16 -> 0.17.1
* python3-git 3.1.14 -> 3.1.20
* python3-gitdb 4.0.5 -> 4.0.7
* python3-hypothesis 6.2.0 -> 6.15.0
* python3-importlib-metadata 3.4.0 -> 4.6.4
* python3-iniparse 0.4 -> 0.5
* python3-jinja2 2.11.3 -> 3.0.1
* python3-libarchive-c 2.9 -> 3.1
* python3-magic 0.4.22 -> 0.4.24
* python3-mako 1.1.4 -> 1.1.5
* python3-markupsafe 1.1.1 -> 2.0.1
* python3-more-itertools 8.7.0 -> 8.8.0
* python3-numpy 1.20.1 -> 1.21.2
* python3-packaging 20.9 -> 21.0
* python3-pathlib2 2.3.5 -> 2.3.6
* python3-pbr 5.4.4 -> 5.6.0
* python3-pip 20.0.2 -> 21.2.4
* python3-pluggy 0.13.1 -> 1.0.0
* python3-pycairo 1.20.0 -> 1.20.1
* python3-pygments 2.8.1 -> 2.10.0
* python3-pygobject 3.38.0 -> 3.40.1
* python3-pytest 6.2.2 -> 6.2.4
* python3-scons 3.1.2 -> 4.2.0
* python3-scons-native 3.1.2 -> 4.2.0
* python3-setuptools 54.1.1 -> 57.4.0
* python3-setuptools-scm 5.0.1 -> 6.0.1
* python3-six 1.15.0 -> 1.16.0
* python3-sortedcontainers 2.3.0 -> 2.4.0
* python3-testtools 2.4.0 -> 2.5.0
* python3-zipp 3.4.1 -> 3.5.0
* qemu 5.2.0 -> 6.0.0
* qemu-native 5.2.0 -> 6.0.0
* qemu-system-native 5.2.0 -> 6.0.0
* re2c 2.0.3 -> 2.2
* rng-tools 6.11 -> 6.14
* rpcbind 1.2.5 -> 1.2.6
* rt-tests 1.10 -> 2.1
* ruby 3.0.1 -> 3.0.2
* rxvt-unicode 9.22 -> 9.26
* shaderc 2020.5 -> 2021.1
* shadow 4.8.1 -> 4.9
* spirv-tools 2020.7 -> 2021.2
* sqlite3 3.35.0 -> 3.36.0
* squashfs-tools 4.4 -> 4.5
* strace 5.11 -> 5.14
* stress-ng 0.12.05 -> 0.13.00
* sudo 1.9.6p1 -> 1.9.7p2
* swig 3.0.12 -> 4.0.2
* sysklogd 2.2.2 -> 2.2.3
* systemd 247.6 -> 249.3
* systemd-boot 247.6 -> 249.3
* systemd-conf 247.6 -> 1.0
* systemtap 4.4 -> 4.5
* systemtap-native 4.4 -> 4.5
* systemtap-uprobes 4.4 -> 4.5
* tcf-agent 1.7.0+gitX (a022ef2f1acf...) -> 1.7.0+gitX (2735e3d6b7ec...)
* texinfo 6.7 -> 6.8
* tiff 4.2.0 -> 4.3.0
* u-boot 2021.01 -> 2021.07
* u-boot-tools 2021.01 -> 2021.07
* usbutils 013 -> 014
* util-linux 2.36.2 -> 2.37.2
* util-linux-libuuid 2.36.2 -> 2.37.2
* vala 0.50.4 -> 0.52.5
* valgrind 3.16.1 -> 3.17.0
* virglrenderer 0.8.2 -> 0.9.1
* vte 0.62.2 -> 0.64.2
* vulkan-headers 1.2.170.0 -> 1.2.182.0
* vulkan-loader 1.2.170.0 -> 1.2.182.0
* vulkan-samples git (55cebd9e7cc4...) -> git (d2187278cb66...)
* vulkan-tools 1.2.170.0 -> 1.2.182.0
* wayland-protocols 1.20 -> 1.21
* webkitgtk 2.30.5 -> 2.32.3
* wireless-regdb 2021.04.21 -> 2021.07.14
* wpebackend-fdo 1.8.0 -> 1.10.0
* x264 r3039+gitX (544c61f08219...) -> r3039+gitX (5db6aa6cab1b...)
* xeyes 1.1.2 -> 1.2.0
* xf86-input-libinput 0.30.0 -> 1.1.0
* xkbcomp 1.4.4 -> 1.4.5
* xkeyboard-config 2.32 -> 2.33
* xorgproto 2020.1 -> 2021.4.99.2
* xserver-xorg 1.20.10 -> 1.20.13
* zstd 1.4.9 -> 1.5.0

</pre>

3.4 Release Notes WIP

2021-10-21T21:29:46Z

PaulEggleton:

<pre>

--------------
Contributors
--------------

Thanks to the following people who contributed to this release:

Adam Romanek
Alejandro Hernandez Samaniego
Alexander Kanavin
Alexandre Belloni
Alexey Brodkin
Alex Stewart
Alistair Francis
Anatol Belski
Anders Wallin
Andrea Adami
Andreas Müller
Andrej Valek
Andres Beltran
Andrey Zhizhikin
Anibal Limon
Anthony Bagwell
Anton Blanchard
Anuj Mittal
Armin Kuster
Asfak Rahman
Bastian Krause
Bernhard Rosenkränzer
Bruce Ashfield
Carlos Rafael Giani
Chandana kalluri
Changhyeok Bae
Changqing Li
Chanho Park
Chen Qi
Chris Laplante
Christophe Chapuis
Christoph Muellner
Claudius Heine
Damian Wrobel
Daniel Ammann
Daniel Gomez
Daniel McGregor
Daniel Wagenknecht
Denys Dmytriyenko
Devendra Tewari
Diego Sueiro
Dmitry Baryshkov
Douglas Royds
Dragos-Marian Panait
Drew Moseley
Enrico Scholz
Fabio Berton
Florian Amstutz
Gavin Li
Guillaume Champagne
Harald Brinkmann
Henning Schild
He Zhe
Hongxu Jia
Hsia-Jun (Randy) Li
Jean Bouchard
Joe Slater
Jonas Höppner
Jon Mason
Jose Quaresma
Joshua Watt
Justin Bronder
Kai Kang
Kenfe-Mickael Laventure
Kevin Hao
Khairul Rohaizzat Jamaluddin
Khem Raj
Kiran Surendran
Konrad Weihmann
Kristian Klausen
Kyle Russell
Lee Chee Yang
Lei Maohui
Luca Boccassi
Marco Felsch
Marcus Comstedt
Marek Vasut
Mark Hatle
Markus Volk
Marta Rybczynska
Martin Jansa
Matthias Klein
Matthias Schiffer
Matt Madison
Matt Spencer
Max Krummenacher
Michael Halstead
Michael Ho
Michael Opdenacker
Mike Crowe
Mikko Rapeli
Ming Liu
Mingli Yu
Minjae Kim
Nicolas Dechesne
Niels Avonds
Nikolay Papenkov
Nisha Parrakat
Olaf Mandel
Oleksandr Kravchuk
Oleksandr Popovych
Oliver Kranz
Otavio Salvador
Patrick Williams
Paul Barker
Paul Eggleton
Paul Gortmaker
Paulo Cesar Zaneti
Peter Bergin
Peter Budny
Peter Kjellerstedt
Petr Vorel
Przemyslaw Gorszkowski
Purushottam Choudhary
Qiang Zhang
Quentin Schulz
Ralph Siemsen
Randy MacLeod
Ranjitsinh Rathod
Rasmus Villemoes
Reto Schneider
Richard Purdie
Richard Weinberger
Robert Joslyn
Robert P. J. Day
Robert Yang
Romain Naour
Ross Burton
Sakib Sajal
Samuli Piippo
Saul Wold
Scott Murray
Scott Weaver
Stefan Ghinea
Stefan Herbrechtsmeier
Stefano Babic
Stefan Wiehler
Steve Sakoman
Teoh Jay Shen
Thomas Perrot
Tim Orling
Tom Pollard
Tom Rini
Tony Battersby
Tony Tascioglu
Trevor Gamblin
Trevor Woerner
Ulrich Ölmann
Valentin Danaila
Vinay Kumar
Vineela Tummalapalli
Vinícius Ossanes Aquino
Vivien Didelot
Vyacheslav Yurkov
Wang Mingyu
Wes Lindauer
William A. Kennington III
Yanfei Xu
Yann Dirson
Yi Fan Yu
Yi Zhao
Zang Ruochen
Zheng Ruoqin
Zoltán Böszörményi

-----------------------------
New Features / Enhancements
-----------------------------

* Linux kernel 5.14, glibc 2.34 and ~280 other recipe upgrades
* Switched override character to ':' (replacing '_') for more robust parsing and improved performance - see migration guide for help on migrating
* Rust integrated into core, providing rust support for cross-compilation and SDK
* New create-spdx class for creating SPDX SBoM documents
* New recipes: cargo, core-image-ptest-all, core-image-ptest-fast, core-image-weston-sdk, erofs-utils, gcompat, gi-docgen, libmicrohttpd, libseccomp, libstd-rs, perlcross, python3-markdown, python3-pyyaml, python3-smartypants, python3-typogrify, rust, rust-cross, rust-cross-canadian, rust-hello-world, rust-llvm, rust-tools-cross-canadian, rustfmt, xwayland
* Several optimisations to reduce unnecessary task dependencies for faster builds
* seccomp integrated into core, with additional enabling for gnutls, systemd, qemu
* New overlayfs class to help generate overlayfs mount units
* debuginfod support now enabled by default
* Switched several recipes over to using OpenSSL instead of GnuTLS (wpa-supplicant, curl, glib-networking) or disable GnuTLS (cups) by default
* Improvements to LTO plugin installation and reproducibility
* Architecture-specific improvements:
- glibc: Enable memory tagging for aarch64
- testimage: remove aarch64 xorg exclusion
- arch-arm*: add better support for gcc march extensions
- tune-cortexm*: add support for all Arm Cortex-M processors
- tune-cortexr*: add support for all Arm Cortex-R processors
- arch-armv4: Allow -march=armv4
- qemuarm*: use virtio graphics
- baremetal-helloworld: Enable RISC-V 64/32 port
- ldconfig-native: Add RISC-V support
- qemuriscv: Enable 4 core emulation
- Add ARC support in gdb, dpkg, dhcpcd
- conf/machine-sdk: Add ppc64 SDK machine
- libjpeg-turbo: Handle powerpc64le without Altivec
- pixman: Handle PowerPC without Altivec
- mesa: enable gallium intel drivers when building for x86
- mesa: enable crocus driver for older intel graphics
* Kernel-related changes:
- Support zstd-compressed modules and initramfs images
- Allow opt-out of split kernel modules
- linux-yocto-dev: base AUTOREV on specified version
- kernel-yocto: provide debug / summary information for metadata
- kernel-uboot: Handle gzip and lzo compression options
- linux-yocto/5.14: added devupstream support
- linux-yocto: add vfat KERNEL_FEATURE when MACHINE_FEATURES include vfat
- linux-yocto: enable TYPEC_TCPCI in usbc fragment
* Image-related improvements
- New erofs, erofs-lz4 and erofs-lz4hc image types
- New squashfs-zst and cpio.zst image types
- New lic-pkgs IMAGE_FEATURES item to install all license packages
- Added zsync metadata conversion support
- Use xargs to set file timestamps for significant (>90%) do_image speedup
- Find .ko.gz and .ko.xz kernel modules as well when determining need to run depmod on an image
- Show formatted error messages instead of tracebacks for systemctl errors
- No longer ignore installation failures in complementary package installation
- Remove ldconfig auxiliary cache when not needed
* wic enhancements:
- Added erofs filesystem support
- Added --extra-space argument to leave extra space after last partition
- Added --no-fstab-update part option to allow using the stock fstab
- bootimg-efi: added Unified Kernel Image option
- bootimg-pcbios: use label provided when formatting a DOS partition
* SDK-related changes:
- Enable do_populate_sdk with multilibs
- New SDKPATHINSTALL variable decouples default install path from built in path to avoid rebuilding nativesdk components on e.g. DISTRO_VERSION changes
- eSDK: Error if trying to generate an eSDK from a multiconfig
- eSDK: introduce TOOLCHAIN_HOST_TASK_ESDK to be used in place of TOOLCHAIN_HOST_TASK to add components to the host part of the eSDK
* New PACKAGECONFIG options in btrfs-tools, ccache, coreutils, cups, dbus, elfutils, ffmpeg, findutils, glib-2.0, gstreamer1.0-plugins-bad, gstreamer1.0-plugins-base, libarchive, libnotify, libpsl, man-db, mesa, ovmf, parted, prelink, qemu, rpm, shadow, systemd, tar, vim, weston
* busybox improvements:
- Added tmpdir option into mktemp applet
- Support mounting swap via labels
- Enable long options for enabled applets
* util-linux: build chfn and chsh by default
* buildstats.bbclass: log host data on failure to task specific file
* buildstats.bbclass: collect data in the same file.
* init-manager-systemd: define weak dev manager
* Add proper unpack dependency for .zst compressed archives
* systemd: set zstd as default compression option
* Ptest enhancements:
- ptest-runner: install script to collect system data on failure
- Added ptest support to python3-hypothesis, python3-jinja2, python3-markupsafe;
- Enhanced ptest support in lttng, util-linux, and others
- New leaner ptest image recipes based upon core-image-minimal
* scripts/contrib/image-manifest: add new script
* devtool upgrade: rebase override-only patches as well
* devtool: print a warning on upgrades if PREFERRED_VERSION is set
* conf/machine: move tune files to architecture directories
* python3-manifest: add statistics subpackage
* qemu: use 4 cores in qemu guests
* runqemu: decouple bios and kernel options
* qemu: add a hint on how to enable CPU render nodes when a suitable GPU is absent
* devupstream: Allow support of native class extensions
* New gi-docgen class for GNOME library documentation
* pypi: Allow override of PyPI archive name
* Allow global override of golang GO_DYNLINK
* lib/oe/elf: Add Android OS to machine_dict
* meson.bbclass: Make the default buildtype "debug" if DEBUG_BUILD is 1
* vim: add option to disable NLS support
* buildhistory: Add option to strip path prefix
* buildhistory: Add output file listing package information
* buildhistory: Label packages providing per-file dependencies in depends.dot
* distro_features_check: expand with IMAGE_FEATURES
* u-boot enhancements:
- Make SPL suffix configurable
- Make UBOOT_BINARYNAME configurable
- Package extlinux.conf separately
- Allow deploying the u-boot DTB
* opensbi: Add support for specifying a device tree
* Add extended packagedata in JSON format
* poky: Use https in default PREMIRRORS
* cross-canadian: make android pass target sys check
* local.conf.sample: Update sstate mirror entry with new hash equivalence setting
* tzdata: Allow controlling zoneinfo binary format
* bitbake improvements:
- New bitbake-getvar helper command to query a variable value (with history)
- bitbake-layers: add --fetchdir parameter to layerindex-fetch
- bitbake-layers: add skip reason to output
- bitbake-diffsigs: sort diff output for consistency
- cooker: Allow upstream for local hash equivalence server
- fetch2/s3: allow to use credentials and switch profile from environment variables
- fetch2/s3: Add progress handler for S3 cp command
- fetch2/wget: fetch securely by default
- fetch2/wget: Enable ftps
- fetch2/svn: Allow peg-revision functionality to be disabled
- fetch2: npm: Support npm archives with missing search directory mode
- fetch2: npmsw: Add support for local tarball and link sources
- prserv: added read-only mode
- prserv: replaced XML RPC with modern asyncrpc implementation
- Numerous warning/error message improvements
* core-image-multilib-example: base on weston, and not sato
* reproducible_build.bbclass: Enable -Wdate-time
* yocto-check-layer: ensure that all layer dependencies are tested too
* npm.bbclass: Allow nodedir to be overridden by NPM_NODEDIR
* cve-extra-exclusions.inc: add exclusion list for intractable CVE's
* license_image.bbclass: Detect broken symlinks
* sysstat: make the service start automatically
* sanity: Add error check for '%' in build path
* sanity: Further improve directory sanity tests
* sanity.bbclass: mention CONNECTIVITY_CHECK_URIS in network failure message
* oe-time-dd-test.sh: add options and refactor
* zstd: Include pzstd in the build
* mirrors.bbclass: provide additional rule for git repo fallbacks
* own-mirrors: Add support for s3:// scheme in SOURCE_MIRROR_URL
* common-licenses: add missing SPDX licences
* Add MAINTAINERS.md file

* pulseaudio: Drop pulseaudio-conf
* rpm: do not RRECOMMEND rpm-build

-------------
Known Issues
-------------

* Build failures have been reported when running on host Linux systems with FIPS enabled (such as RHEL 8.0 with the FIPS mode enabled). For more details please see https://bugzilla.yoctoproject.org/show_bug.cgi?id=14609.

-----------------
Recipe Licenses
-----------------

The following corrections have been made to the LICENSE values set by recipes:

* acpica: correct LICENSE to "Intel | BSD-3-Clause | GPLv2"
* dtc: correct LICENSE to "GPLv2 | BSD-2-Clause"
* e2fsprogs: correct LICENSE to "GPLv2 & LGPLv2 & BSD-3-Clause & MIT"
* ffmpeg: correct LICENSE to "GPLv2+ & LGPLv2.1+ & ISC & MIT & BSD-2-Clause & BSD-3-Clause & IJG"
* flac: correct LICENSE to "GFDL-1.2 & GPLv2+ & LGPLv2.1+ & BSD-3-Clause"
* flex: correct LICENSE to "BSD-3-Clause & LGPL-2.0+"
* font-util: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* glib-2.0: correct LICENSE to "LGPLv2.1+ & BSD-3-Clause & PD"
* gobject-introspection: correct LICENSE to "LGPLv2+ & GPLv2+ & MIT" (add MIT license)
* hdparm: correct LICENSE to "BSD-2-Clause & GPLv2 & hdparm"
* iputils: correct LICENSE to "BSD-3-Clause & GPLv2+"
* libcap: correct LICENSE to "BSD-3-Clause | GPLv2"
* libevent: correct LICENSE to "BSD-3-Clause & MIT"
* libjitterentropy: correct LICENSE to "GPLv2+ | BSD-3-Clause"
* libpam: correct LICENSE to "GPLv2+ | BSD-3-Clause"
* libwpe: correct LICENSE to "BSD-2-Clause"
* libx11-compose-data: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libx11: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libxfont2: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libxfont: correct LICENSE to "MIT & MIT-style & BSD-3-Clause"
* lsof: correct LICENSE to reflect that it uses a BSD-like (but not exactly BSD) license ("Spencer-94")
* nfs-utils: correct LICENSE to "MIT & GPLv2+ & BSD-3-Clause"
* ovmf: correct license to "BSD-2-Clause-Patent"
* ppp: correct LICENSE to "BSD-3-Clause & BSD-3-Clause-Attribution & GPLv2+ & LGPLv2+ & PD"
* python3-packaging: correct LICENSE to "Apache-2.0 | BSD-2-Clause"
* python-async-test: correct LICENSE to "BSD-3-Clause"
* quota: remove BSD license (only BSD licensed part of the code was removed in 4.05)
* shadow: correct LICENSE to "BSD-3-Clause | Artistic-1.0"
* shadow-sysroot: set LICENSE the same as shadow
* sudo: correct LICENSE to "ISC & BSD-3-Clause & BSD-2-Clause & Zlib"
* swig: correct LICENSE to "BSD-3-Clause & GPLv3"
* valgrind: correct license to "GPLv2 & GPLv2+ & BSD-3-Clause"
* webkitgtk: correct LICENSE to "BSD-2-Clause & LGPLv2+"
* wpebackend-fdo: correct LICENSE to "BSD-2-Clause"
* xinetd: correct LICENSE to reflect that it uses a unique BSD-like (but not exactly BSD) license

Other license-related notes:
* When creating recipes for Python software, recipetool will now treat "BSD" as "BSD-3-Clause" for the purposes of setting LICENSE, as that is the most common understanding.
* Please be aware that an initramfs bundled with the kernel using INITRAMFS_IMAGE_BUNDLE should only contain GPLv2-compatible software; this is now mentioned in the documentation.

------------------------
Migration instructions
------------------------

For details on changes that you might need to make when migrating to the Yocto Project 3.4 release from previous releases, please see the following manual:

https://docs.yoctoproject.org/migration-guides/migration-3.4.html

----------------
Security Fixes
----------------

* apr: CVE-2021-35940
* aspell: CVE-2019-25051
* avahi: CVE-2021-3468, CVE-2021-36217
* binutils: CVE-2021-20197
* bluez: CVE-2021-3658
* busybox: CVE-2021-28831
* cairo: CVE-2020-35492
* cpio: CVE-2021-38185
* expat: CVE-2013-0340
* ffmpeg: CVE-2020-20446, CVE-2020-22015, CVE-2020-22021, CVE-2020-22033, CVE-2020-22019, CVE-2021-33815, CVE-2021-38171, CVE-2020-20453
* glibc: CVE-2021-33574, CVE-2021-38604
* inetutils: CVE-2021-40491
* libgcrypt: CVE-2021-40528
* linux-yocto/5.10, 5.14: CVE-2021-3653, CVE-2021-3656
* lz4: CVE-2021-3520
* nettle: CVE-2021-20305
* openssl: CVE-2021-3711, CVE-2021-3712
* perl: CVE-2021-36770
* python3: CVE-2021-29921
* python3-pip: CVE-2021-3572
* qemu: CVE-2020-27821, CVE-2020-29443, CVE-2020-35517, CVE-2021-3392, CVE-2021-3409, CVE-2021-3416, CVE-2021-3527, CVE-2021-3544, CVE-2021-3545, CVE-2021-3546, CVE-2021-3682, CVE-2021-20181, CVE-2021-20221, CVE-2021-20257, CVE-2021-20263
* rpm: CVE-2021-3421, CVE-2021-20271
* rsync: CVE-2020-14387
* util-linux: CVE-2021-37600
* vim: CVE-2021-3770, CVE-2021-3778
* wpa-supplicant: CVE-2021-30004
* xdg-utils: CVE-2020-27748
* xserver-xorg: CVE-2021-3472

-----------------
Recipe Upgrades
-----------------

* acl 2.2.53 -> 2.3.1
* acpica 20210105 -> 20210730
* alsa-lib 1.2.4 -> 1.2.5.1
* alsa-plugins 1.2.2 -> 1.2.5
* alsa-tools 1.2.2 -> 1.2.5
* alsa-topology-conf 1.2.4 -> 1.2.5.1
* alsa-ucm-conf 1.2.4 -> 1.2.5.1
* alsa-utils 1.2.4 -> 1.2.5.1
* alsa-utils-scripts 1.2.4 -> 1.2.5.1
* apt 2.2.2 -> 2.2.4
* at 3.2.1 -> 3.2.2
* at-spi2-core 2.38.0 -> 2.40.3
* autoconf-archive 2019.01.06 -> 2021.02.19
* babeltrace2 2.0.3 -> 2.0.4
* bash 5.1 -> 5.1.8
* bind 9.16.16 -> 9.16.20
* binutils 2.36.1 -> 2.37
* binutils-cross 2.36.1 -> 2.37
* binutils-cross-canadian 2.36.1 -> 2.37
* binutils-cross-testsuite 2.36.1 -> 2.37
* binutils-crosssdk 2.36.1 -> 2.37
* bison 3.7.5 -> 3.7.6
* blktrace 1.2.0+gitX -> 1.3.0+gitX
* bluez5 5.56 -> 5.61
* boost 1.75.0 -> 1.77.0
* boost-build-native 4.3.0 -> 4.4.1
* btrfs-tools 5.10.1 -> 5.13.1
* busybox 1.33.1 -> 1.34.0
* busybox-inittab 1.33.0 -> 1.34.0
* ccache 4.2 -> 4.4
* cmake 3.19.5 -> 3.21.1
* cmake-native 3.19.5 -> 3.21.1
* connman 1.39 -> 1.40
* createrepo-c 0.17.0 -> 0.17.4
* cronie 1.5.5 -> 1.5.7
* cross-localedef-native 2.33 -> 2.34
* cups 2.3.3 -> 2.3.3op2
* curl 7.75.0 -> 7.78.0
* dbus-glib 0.110 -> 0.112
* dejagnu 1.6.2 -> 1.6.3
* diffoscope 172 -> 181
* diffutils 3.7 -> 3.8
* distcc 3.3.5 -> 3.4
* dnf 4.6.0 -> 4.8.0
* dpkg 1.20.7.1 -> 1.20.9
* dtc 1.6.0 -> 1.6.1
* e2fsprogs 1.46.1 -> 1.46.4
* elfutils 0.183 -> 0.185
* ell 0.38 -> 0.43
* enchant2 2.2.15 -> 2.3.1
* epiphany 3.38.2 -> 40.3
* ethtool 5.10 -> 5.13
* expat 2.2.10 -> 2.4.1
* ffmpeg 4.3.2 -> 4.4
* file 5.39 -> 5.40
* freetype 2.10.4 -> 2.11.0
* gcc 10.2.0 -> 11.2.0
* gcc-cross 10.2.0 -> 11.2.0
* gcc-cross-canadian 10.2.0 -> 11.2.0
* gcc-crosssdk 10.2.0 -> 11.2.0
* gcc-runtime 10.2.0 -> 11.2.0
* gcc-sanitizers 10.2.0 -> 11.2.0
* gcc-source 10.2.0 -> 11.2.0
* gcr 3.38.1 -> 3.40.0
* gdb 10.1 -> 10.2
* gdb-cross 10.1 -> 10.2
* gdb-cross-canadian 10.1 -> 10.2
* gdk-pixbuf 2.40.0 -> 2.42.6
* ghostscript 9.53.3 -> 9.54.0
* git 2.31.1 -> 2.33.0
* glib-2.0 2.66.7 -> 2.68.4
* glib-networking 2.66.0 -> 2.68.2
* glibc 2.33 -> 2.34
* glibc-locale 2.33 -> 2.34
* glibc-mtrace 2.33 -> 2.34
* glibc-scripts 2.33 -> 2.34
* glibc-testsuite 2.33 -> 2.34
* glslang 11.2.0 -> 11.5.0
* gnome-desktop-testing 2018.1 -> 2021.1
* gnu-config 20210125+gitX -> 20210722+gitX
* gnu-efi 3.0.12 -> 3.0.14
* gnupg 2.2.27 -> 2.3.1
* gobject-introspection 1.66.1 -> 1.68.0
* gpgme 1.15.1 -> 1.16.0
* gptfdisk 1.0.7 -> 1.0.8
* grep 3.6 -> 3.7
* grub 2.04+2.06~rc1 -> 2.06
* grub-efi 2.04+2.06~rc1 -> 2.06
* gsettings-desktop-schemas 3.38.0 -> 40.0
* gtk+3 3.24.25 -> 3.24.30
* harfbuzz 2.7.4 -> 2.9.0
* hdparm 9.60 -> 9.62
* help2man 1.48.2 -> 1.48.4
* hwlatdetect 1.10 -> 2.1
* i2c-tools 4.2 -> 4.3
* icu 68.2 -> 69.1
* igt-gpu-tools 1.25+gitX -> 1.26
* inetutils 2.0 -> 2.1
* iproute2 5.11.0 -> 5.13.0
* iputils s20200821 -> 20210722
* json-glib 1.6.2 -> 1.6.4
* kexec-tools 2.0.21 -> 2.0.22
* kmod 28 -> 29
* kmod-native 28 -> 29
* less 563 -> 590
* libassuan 2.5.4 -> 2.5.5
* libcap 2.48 -> 2.51
* libcgroup 0.41 -> 2.0
* libcomps 0.1.15 -> 0.1.17
* libconvert-asn1-perl 0.27 -> 0.31
* libdazzle 3.38.0 -> 3.40.0
* libdnf 0.58.0 -> 0.63.1
* libdrm 2.4.104 -> 2.4.107
* libedit 20210216-3.1 -> 20210714-3.1
* libepoxy 1.5.5 -> 1.5.9
* liberation-fonts 2.00.1 -> 2.1.4
* libffi 3.3 -> 3.4.2
* libfm 1.3.1 -> 1.3.2
* libgcc 10.2.0 -> 11.2.0
* libgcc-initial 10.2.0 -> 11.2.0
* libgcrypt 1.9.3 -> 1.9.4
* libgfortran 10.2.0 -> 11.2.0
* libgit2 1.1.0 -> 1.1.1
* libglu 9.0.1 -> 9.0.2
* libgpg-error 1.41 -> 1.42
* libgudev 234 -> 237
* libhandy 1.2.0 -> 1.2.3
* libical 3.0.9 -> 3.0.10
* libidn2 2.3.0 -> 2.3.2
* libinput 1.16.4 -> 1.18.1
* libjitterentropy 3.0.1 -> 3.1.0
* libjpeg-turbo 2.0.6 -> 2.1.1
* libksba 1.5.0 -> 1.6.0
* libmodulemd 2.12.0 -> 2.13.0
* libnsl2 1.3.0 -> 2.0.0
* libnss-mdns 0.14.1 -> 0.15.1
* libogg 1.3.4 -> 1.3.5
* libpcap 1.10.0 -> 1.10.1
* libpcre 8.44 -> 8.45
* libpcre2 10.36 -> 10.37
* libportal 0.3 -> 0.4
* librepo 1.13.0 -> 1.14.1
* libsdl2 2.0.14 -> 2.0.16
* libsolv 0.7.17 -> 0.7.19
* libtasn1 4.16.0 -> 4.17.0
* libtest-needs-perl 0.002006 -> 0.002009
* libtirpc 1.3.1 -> 1.3.2
* libubootenv 0.3.1 -> 0.3.2
* libucontext 0.10+X -> 1.1+X
* liburcu 0.12.2 -> 0.13.0
* libuv 1.41.0 -> 1.42.0
* libva 2.10.0 -> 2.12.0
* libva-initial 2.10.0 -> 2.12.0
* libva-utils 2.10.0 -> 2.12.0
* libwebp 1.2.0 -> 1.2.1
* libwpe 1.8.0 -> 1.10.1
* libx11 1.7.0 -> 1.7.2
* libxcrypt 4.4.18 -> 4.4.25
* libxcrypt-compat 4.4.18 -> 4.4.25
* libxfixes 5.0.3 -> 6.0.0
* libxfont2 2.0.4 -> 2.0.5
* libxft 2.3.3 -> 2.3.4
* libxi 1.7.10 -> 1.7.99.2
* libxkbcommon 1.0.3 -> 1.3.0
* libxml2 2.9.10 -> 2.9.12
* libxres 1.2.0 -> 1.2.1
* linux-libc-headers 5.10 -> 5.14
* linux-yocto 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-dev 5.12++gitX -> 5.15++gitX
* linux-yocto-rt 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-tiny 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* llvm 11.1.0 -> 12.0.1
* log4cplus 2.0.6 -> 2.0.7
* logrotate 3.18.0 -> 3.18.1
* ltp 20210121 -> 20210524
* lttng-modules 2.12.6 -> 2.13.0
* lttng-tools 2.12.4 -> 2.13.0
* lttng-ust 2.12.1 -> 2.13.0
* m4 1.4.18 -> 1.4.19
* m4-native 1.4.18 -> 1.4.19
* man-pages 5.10 -> 5.12
* mc 4.8.26 -> 4.8.27
* mesa 21.0.3 -> 21.2.1
* mesa-gl 21.0.3 -> 21.2.1
* meson 0.57.1 -> 0.58.1
* mmc-utils 0.1+gitX (73d6c59af8d1...) -> 0.1+gitX (43282e80e174...)
* mobile-broadband-provider-info 20201225 -> 20210805
* mpg123 1.26.4 -> 1.28.2
* mtd-utils 2.1.2 -> 2.1.3
* mtools 4.0.26 -> 4.0.35
* musl 1.2.2+gitX (e5d2823631bb...) -> 1.2.2+gitX (3f701faace7a...)
* nativesdk-meson 0.57.1 -> 0.58.1
* netbase 6.2 -> 6.3
* nfs-utils 2.5.3 -> 2.5.4
* ofono 1.31 -> 1.32
* openssh 8.5p1 -> 8.7p1
* opkg 0.4.4 -> 0.4.5
* opkg-utils 0.4.3 -> 0.4.5
* ovmf edk2-stable202102 -> edk2-stable202105
* p11-kit 0.23.22 -> 0.24.0
* pango 1.48.2 -> 1.48.9
* patchelf 0.12 -> 0.13
* perl 5.32.1 -> 5.34.0
* piglit 1.0+gitrX (d4d9353b7290...) -> 1.0+gitrX (6a4be9e9946d...)
* pkgconf 1.7.3 -> 1.8.0
* powertop 2.13 -> 2.14
* pseudo 1.9.0+gitX (b988b0a6b8af...) -> 1.9.0+gitX (0cda3ba5f94a...)
* pulseaudio 14.2 -> 15.0
* puzzles 0.0+gitX (84cb4c6701e0...) -> 0.0+gitX (8f3413c31ffd...)
* python3 3.9.5 -> 3.9.6
* python3-attrs 20.3.0 -> 21.2.0
* python3-cython 0.29.22 -> 0.29.24
* python3-dbus 1.2.16 -> 1.2.18
* python3-dbusmock 0.22.0 -> 0.23.1
* python3-docutils 0.16 -> 0.17.1
* python3-git 3.1.14 -> 3.1.20
* python3-gitdb 4.0.5 -> 4.0.7
* python3-hypothesis 6.2.0 -> 6.15.0
* python3-importlib-metadata 3.4.0 -> 4.6.4
* python3-iniparse 0.4 -> 0.5
* python3-jinja2 2.11.3 -> 3.0.1
* python3-libarchive-c 2.9 -> 3.1
* python3-magic 0.4.22 -> 0.4.24
* python3-mako 1.1.4 -> 1.1.5
* python3-markupsafe 1.1.1 -> 2.0.1
* python3-more-itertools 8.7.0 -> 8.8.0
* python3-numpy 1.20.1 -> 1.21.2
* python3-packaging 20.9 -> 21.0
* python3-pathlib2 2.3.5 -> 2.3.6
* python3-pbr 5.4.4 -> 5.6.0
* python3-pip 20.0.2 -> 21.2.4
* python3-pluggy 0.13.1 -> 1.0.0
* python3-pycairo 1.20.0 -> 1.20.1
* python3-pygments 2.8.1 -> 2.10.0
* python3-pygobject 3.38.0 -> 3.40.1
* python3-pytest 6.2.2 -> 6.2.4
* python3-scons 3.1.2 -> 4.2.0
* python3-scons-native 3.1.2 -> 4.2.0
* python3-setuptools 54.1.1 -> 57.4.0
* python3-setuptools-scm 5.0.1 -> 6.0.1
* python3-six 1.15.0 -> 1.16.0
* python3-sortedcontainers 2.3.0 -> 2.4.0
* python3-testtools 2.4.0 -> 2.5.0
* python3-zipp 3.4.1 -> 3.5.0
* qemu 5.2.0 -> 6.0.0
* qemu-native 5.2.0 -> 6.0.0
* qemu-system-native 5.2.0 -> 6.0.0
* re2c 2.0.3 -> 2.2
* rng-tools 6.11 -> 6.14
* rpcbind 1.2.5 -> 1.2.6
* rt-tests 1.10 -> 2.1
* ruby 3.0.1 -> 3.0.2
* rxvt-unicode 9.22 -> 9.26
* shaderc 2020.5 -> 2021.1
* shadow 4.8.1 -> 4.9
* spirv-tools 2020.7 -> 2021.2
* sqlite3 3.35.0 -> 3.36.0
* squashfs-tools 4.4 -> 4.5
* strace 5.11 -> 5.14
* stress-ng 0.12.05 -> 0.13.00
* sudo 1.9.6p1 -> 1.9.7p2
* swig 3.0.12 -> 4.0.2
* sysklogd 2.2.2 -> 2.2.3
* systemd 247.6 -> 249.3
* systemd-boot 247.6 -> 249.3
* systemd-conf 247.6 -> 1.0
* systemtap 4.4 -> 4.5
* systemtap-native 4.4 -> 4.5
* systemtap-uprobes 4.4 -> 4.5
* tcf-agent 1.7.0+gitX (a022ef2f1acf...) -> 1.7.0+gitX (2735e3d6b7ec...)
* texinfo 6.7 -> 6.8
* tiff 4.2.0 -> 4.3.0
* u-boot 2021.01 -> 2021.07
* u-boot-tools 2021.01 -> 2021.07
* usbutils 013 -> 014
* util-linux 2.36.2 -> 2.37.2
* util-linux-libuuid 2.36.2 -> 2.37.2
* vala 0.50.4 -> 0.52.5
* valgrind 3.16.1 -> 3.17.0
* virglrenderer 0.8.2 -> 0.9.1
* vte 0.62.2 -> 0.64.2
* vulkan-headers 1.2.170.0 -> 1.2.182.0
* vulkan-loader 1.2.170.0 -> 1.2.182.0
* vulkan-samples git (55cebd9e7cc4...) -> git (d2187278cb66...)
* vulkan-tools 1.2.170.0 -> 1.2.182.0
* wayland-protocols 1.20 -> 1.21
* webkitgtk 2.30.5 -> 2.32.3
* wireless-regdb 2021.04.21 -> 2021.07.14
* wpebackend-fdo 1.8.0 -> 1.10.0
* x264 r3039+gitX (544c61f08219...) -> r3039+gitX (5db6aa6cab1b...)
* xeyes 1.1.2 -> 1.2.0
* xf86-input-libinput 0.30.0 -> 1.1.0
* xkbcomp 1.4.4 -> 1.4.5
* xkeyboard-config 2.32 -> 2.33
* xorgproto 2020.1 -> 2021.4.99.2
* xserver-xorg 1.20.10 -> 1.20.13
* zstd 1.4.9 -> 1.5.0

</pre>

3.4 Release Notes WIP

2021-10-21T21:07:57Z

PaulEggleton:

<pre>

--------------
Contributors
--------------

Thanks to the following people who contributed to this release:

Adam Romanek
Alejandro Hernandez Samaniego
Alexander Kanavin
Alexandre Belloni
Alexey Brodkin
Alex Stewart
Alistair Francis
Anatol Belski
Anders Wallin
Andrea Adami
Andreas Müller
Andrej Valek
Andres Beltran
Andrey Zhizhikin
Anibal Limon
Anthony Bagwell
Anton Blanchard
Anuj Mittal
Armin Kuster
Asfak Rahman
Bastian Krause
Bernhard Rosenkränzer
Bruce Ashfield
Carlos Rafael Giani
Chandana kalluri
Changhyeok Bae
Changqing Li
Chanho Park
Chen Qi
Chris Laplante
Christophe Chapuis
Christoph Muellner
Claudius Heine
Damian Wrobel
Daniel Ammann
Daniel Gomez
Daniel McGregor
Daniel Wagenknecht
Denys Dmytriyenko
Devendra Tewari
Diego Sueiro
Dmitry Baryshkov
Douglas Royds
Dragos-Marian Panait
Drew Moseley
Enrico Scholz
Fabio Berton
Florian Amstutz
Gavin Li
Guillaume Champagne
Harald Brinkmann
Henning Schild
He Zhe
Hongxu Jia
Hsia-Jun (Randy) Li
Jean Bouchard
Joe Slater
Jonas Höppner
Jon Mason
Jose Quaresma
Joshua Watt
Justin Bronder
Kai Kang
Kenfe-Mickael Laventure
Kevin Hao
Khairul Rohaizzat Jamaluddin
Khem Raj
Kiran Surendran
Konrad Weihmann
Kristian Klausen
Kyle Russell
Lee Chee Yang
Lei Maohui
Luca Boccassi
Marco Felsch
Marcus Comstedt
Marek Vasut
Mark Hatle
Markus Volk
Marta Rybczynska
Martin Jansa
Matthias Klein
Matthias Schiffer
Matt Madison
Matt Spencer
Max Krummenacher
Michael Halstead
Michael Ho
Michael Opdenacker
Mike Crowe
Mikko Rapeli
Ming Liu
Mingli Yu
Minjae Kim
Nicolas Dechesne
Niels Avonds
Nikolay Papenkov
Nisha Parrakat
Olaf Mandel
Oleksandr Kravchuk
Oleksandr Popovych
Oliver Kranz
Otavio Salvador
Patrick Williams
Paul Barker
Paul Eggleton
Paul Gortmaker
Paulo Cesar Zaneti
Peter Bergin
Peter Budny
Peter Kjellerstedt
Petr Vorel
Przemyslaw Gorszkowski
Purushottam Choudhary
Qiang Zhang
Quentin Schulz
Ralph Siemsen
Randy MacLeod
Ranjitsinh Rathod
Rasmus Villemoes
Reto Schneider
Richard Purdie
Richard Weinberger
Robert Joslyn
Robert P. J. Day
Robert Yang
Romain Naour
Ross Burton
Sakib Sajal
Samuli Piippo
Saul Wold
Scott Murray
Scott Weaver
Stefan Ghinea
Stefan Herbrechtsmeier
Stefano Babic
Stefan Wiehler
Steve Sakoman
Teoh Jay Shen
Thomas Perrot
Tim Orling
Tom Pollard
Tom Rini
Tony Battersby
Tony Tascioglu
Trevor Gamblin
Trevor Woerner
Ulrich Ölmann
Valentin Danaila
Vinay Kumar
Vineela Tummalapalli
Vinícius Ossanes Aquino
Vivien Didelot
Vyacheslav Yurkov
Wang Mingyu
Wes Lindauer
William A. Kennington III
Yanfei Xu
Yann Dirson
Yi Fan Yu
Yi Zhao
Zang Ruochen
Zheng Ruoqin
Zoltán Böszörményi

-----------------------------
New Features / Enhancements
-----------------------------

* Linux kernel 5.14, glibc 2.34 and ~280 other recipe upgrades
* Switched override character to ':' (replacing '_') for more robust parsing and improved performance - see migration guide for help on migrating
* Rust integrated into core, providing rust support for cross-compilation and SDK
* New create-spdx class for creating SPDX SBoM documents
* New recipes: cargo, core-image-ptest-all, core-image-ptest-fast, core-image-weston-sdk, erofs-utils, gcompat, gi-docgen, libmicrohttpd, libseccomp, libstd-rs, perlcross, python3-markdown, python3-pyyaml, python3-smartypants, python3-typogrify, rust, rust-cross, rust-cross-canadian, rust-hello-world, rust-llvm, rust-tools-cross-canadian, rustfmt, xwayland
* Several optimisations to reduce unnecessary task dependencies for faster builds
* seccomp integrated into core, with additional enabling for gnutls, systemd, qemu
* debuginfod support now enabled by default
* Switched several recipes over to using OpenSSL instead of GnuTLS (wpa-supplicant, curl, glib-networking) or disable GnuTLS (cups) by default
* Improvements to LTO plugin installation and reproducibility
* Architecture-specific improvements:
- glibc: Enable memory tagging for aarch64
- testimage: remove aarch64 xorg exclusion
- arch-arm*: add better support for gcc march extensions
- tune-cortexm*: add support for all Arm Cortex-M processors
- tune-cortexr*: add support for all Arm Cortex-R processors
- arch-armv4: Allow -march=armv4
- qemuarm*: use virtio graphics
- baremetal-helloworld: Enable RISC-V 64/32 port
- ldconfig-native: Add RISC-V support
- qemuriscv: Enable 4 core emulation
- Add ARC support in gdb, dpkg, dhcpcd
- conf/machine-sdk: Add ppc64 SDK machine
- libjpeg-turbo: Handle powerpc64le without Altivec
- pixman: Handle PowerPC without Altivec
- mesa: enable gallium intel drivers when building for x86
- mesa: enable crocus driver for older intel graphics
* Kernel-related changes:
- Support zstd-compressed modules and initramfs images
- Allow opt-out of split kernel modules
- linux-yocto-dev: base AUTOREV on specified version
- kernel-yocto: provide debug / summary information for metadata
- kernel-uboot: Handle gzip and lzo compression options
- linux-yocto/5.14: added devupstream support
- linux-yocto: add vfat KERNEL_FEATURE when MACHINE_FEATURES include vfat
- linux-yocto: enable TYPEC_TCPCI in usbc fragment
* Image-related improvements
- New erofs, erofs-lz4 and erofs-lz4hc image types
- New squashfs-zst and cpio.zst image types
- New lic-pkgs IMAGE_FEATURES item to install all license packages
- Added zsync metadata conversion support
- Use xargs to set file timestamps for significant (>90%) do_image speedup
- Find .ko.gz and .ko.xz kernel modules as well when determining need to run depmod on an image
- Show formatted error messages instead of tracebacks for systemctl errors
- No longer ignore installation failures in complementary package installation
- Remove ldconfig auxiliary cache when not needed
* wic enhancements:
- Added erofs filesystem support
- Added --extra-space argument to leave extra space after last partition
- Added --no-fstab-update part option to allow using the stock fstab
- bootimg-efi: added Unified Kernel Image option
- bootimg-pcbios: use label provided when formatting a DOS partition
* New PACKAGECONFIG options in btrfs-tools, ccache, coreutils, cups, dbus, elfutils, ffmpeg, findutils, glib-2.0, gstreamer1.0-plugins-bad, gstreamer1.0-plugins-base, libarchive, libnotify, libpsl, man-db, mesa, ovmf, parted, prelink, qemu, rpm, shadow, systemd, tar, vim, weston
* scripts/contrib/image-manifest: add new script
* New gi-docgen class for GNOME library documentation
* sdk: Enable do_populate_sdk with multilibs
* sdk: Decouple default install path from built in path
* poky: Use SDKPATHINSTALL instead of SDKPATH
* deb: apply postinstall on sdk
* populate_sdk_ext: Error if trying to generate an eSDK from a multiconfig
* populate_sdk_ext: Fix handling of TOOLCHAIN_HOST_TASK in the eSDK case
* devtool upgrade: rebase override-only patches as well
* devtool: print a warning on upgrades if PREFERRED_VERSION is set
* busybox: add tmpdir option into mktemp applet
* busybox: support mounting swap via labels
* busybox: Enable long options for enabled applets
* testimage.bbclass: Add dump-guest-memory cmd
* util-linux: build chfn and chsh by default
* buildstats.bbclass: log host data on failure to task specific file
* buildstats.bbclass: collect data in the same file.
* init-manager-systemd: define weak dev manager
* Add proper unpack dependency for .zst compressed archives
* systemd: set zstd as default compression option
* Ptest enhancements:
- ptest-runner: install script to collect system data on failure
- Added ptest support to python3-hypothesis, python3-jinja2, python3-markupsafe;
- Enhanced ptest support in lttng, util-linux, and others
- New leaner ptest image recipes based upon core-image-minimal
* conf/machine: move tune files to architecture directories
* python3-manifest: add statistics subpackage
* qemurunner: Add support for qmp commands
* runqemu: decouple bios and kernel options
* qemu: add a hint on how to enable CPU render nodes when a suitable GPU is absent
* qemu: use 4 cores in qemu guests
* devupstream: Allow support of native class extensions
* overlayfs.bbclass: generate overlayfs mount units
* rootfs-postcommands: add QA check for overlayfs
* pypi: Allow override of PyPI archive name
* Allow global override of golang GO_DYNLINK
* lib/oe/elf: Add Android OS to machine_dict
* meson.bbclass: Make the default buildtype "debug" if DEBUG_BUILD is 1
* vim: add option to disable NLS support
* buildhistory: Add option to strip path prefix
* buildhistory: Add output file listing package information
* buildhistory: Label packages providing per-file dependencies in depends.dot
* distro_features_check: expand with IMAGE_FEATURES
* u-boot enhancements:
- Make SPL suffix configurable
- Make UBOOT_BINARYNAME configurable
- Package extlinux.conf separately
- Allow deploying the u-boot DTB
* opensbi: Add support for specifying a device tree
* classes/package: Add extended packagedata
* poky: Use https in PREMIRRORS
* cross-canadian: make android pass target sys check
* local.conf.sample: Update sstate mirror entry with new hash equivalence setting
* tzdata: Allow controlling zoneinfo binary format
* bitbake improvements:
- New bitbake-getvar helper command to query a variable value (with history)
- bitbake-layers: add --fetchdir parameter to layerindex-fetch
- bitbake-layers: add skip reason to output
- bitbake-diffsigs: sort diff output for consistency
- cooker: Allow upstream for local hash equivalence server
- fetch2/s3: allow to use credentials and switch profile from environment variables
- fetch2/s3: Add progress handler for S3 cp command
- fetch2/wget: fetch securely by default
- fetch2/wget: Enable ftps
- fetch2/svn: Allow peg-revision functionality to be disabled
- fetch2: npm: Support npm archives with missing search directory mode
- fetch2: npmsw: Add support for local tarball and link sources
- prserv: added read-only mode
- prserv: replaced XML RPC with modern asyncrpc implementation
- Numerous warning/error message improvements
* core-image-multilib-example: base on weston, and not sato
* reproducible_build.bbclass: Enable -Wdate-time
* yocto-check-layer: ensure that all layer dependencies are tested too
* npm.bbclass: Allow nodedir to be overridden by NPM_NODEDIR
* cve-extra-exclusions.inc: add exclusion list for intractable CVE's
* license_image.bbclass: Detect broken symlinks
* sysstat: make the service start automatically
* sanity: Add error check for '%' in build path
* sanity: Further improve directory sanity tests
* sanity.bbclass: mention CONNECTIVITY_CHECK_URIS in network failure message
* oe-time-dd-test.sh: add options and refactor
* zstd: Include pzstd in the build
* mirrors.bbclass: provide additional rule for git repo fallbacks
* own-mirrors: Add support for s3:// scheme in SOURCE_MIRROR_URL
* common-licenses: add missing SPDX licences
* Add MAINTAINERS.md file

* pulseaudio: Drop pulseaudio-conf
* rpm: do not RRECOMMEND rpm-build

-------------
Known Issues
-------------

* Build failures have been reported when running on host Linux systems with FIPS enabled (such as RHEL 8.0 with the FIPS mode enabled). For more details please see https://bugzilla.yoctoproject.org/show_bug.cgi?id=14609.

-----------------
Recipe Licenses
-----------------

The following corrections have been made to the LICENSE values set by recipes:

* acpica: correct LICENSE to "Intel | BSD-3-Clause | GPLv2"
* dtc: correct LICENSE to "GPLv2 | BSD-2-Clause"
* e2fsprogs: correct LICENSE to "GPLv2 & LGPLv2 & BSD-3-Clause & MIT"
* ffmpeg: correct LICENSE to "GPLv2+ & LGPLv2.1+ & ISC & MIT & BSD-2-Clause & BSD-3-Clause & IJG"
* flac: correct LICENSE to "GFDL-1.2 & GPLv2+ & LGPLv2.1+ & BSD-3-Clause"
* flex: correct LICENSE to "BSD-3-Clause & LGPL-2.0+"
* font-util: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* glib-2.0: correct LICENSE to "LGPLv2.1+ & BSD-3-Clause & PD"
* gobject-introspection: correct LICENSE to "LGPLv2+ & GPLv2+ & MIT" (add MIT license)
* hdparm: correct LICENSE to "BSD-2-Clause & GPLv2 & hdparm"
* iputils: correct LICENSE to "BSD-3-Clause & GPLv2+"
* libcap: correct LICENSE to "BSD-3-Clause | GPLv2"
* libevent: correct LICENSE to "BSD-3-Clause & MIT"
* libjitterentropy: correct LICENSE to "GPLv2+ | BSD-3-Clause"
* libpam: correct LICENSE to "GPLv2+ | BSD-3-Clause"
* libwpe: correct LICENSE to "BSD-2-Clause"
* libx11-compose-data: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libx11: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libxfont2: correct LICENSE to "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
* libxfont: correct LICENSE to "MIT & MIT-style & BSD-3-Clause"
* lsof: correct LICENSE to reflect that it uses a BSD-like (but not exactly BSD) license ("Spencer-94")
* nfs-utils: correct LICENSE to "MIT & GPLv2+ & BSD-3-Clause"
* ovmf: correct license to "BSD-2-Clause-Patent"
* ppp: correct LICENSE to "BSD-3-Clause & BSD-3-Clause-Attribution & GPLv2+ & LGPLv2+ & PD"
* python3-packaging: correct LICENSE to "Apache-2.0 | BSD-2-Clause"
* python-async-test: correct LICENSE to "BSD-3-Clause"
* quota: remove BSD license (only BSD licensed part of the code was removed in 4.05)
* shadow: correct LICENSE to "BSD-3-Clause | Artistic-1.0"
* shadow-sysroot: set LICENSE the same as shadow
* sudo: correct LICENSE to "ISC & BSD-3-Clause & BSD-2-Clause & Zlib"
* swig: correct LICENSE to "BSD-3-Clause & GPLv3"
* valgrind: correct license to "GPLv2 & GPLv2+ & BSD-3-Clause"
* webkitgtk: correct LICENSE to "BSD-2-Clause & LGPLv2+"
* wpebackend-fdo: correct LICENSE to "BSD-2-Clause"
* xinetd: correct LICENSE to reflect that it uses a unique BSD-like (but not exactly BSD) license

Other license-related notes:
* When creating recipes for Python software, recipetool will now treat "BSD" as "BSD-3-Clause" for the purposes of setting LICENSE, as that is the most common understanding.
* Please be aware that an initramfs bundled with the kernel using INITRAMFS_IMAGE_BUNDLE should only contain GPLv2-compatible software; this is now mentioned in the documentation.

------------------------
Migration instructions
------------------------

For details on changes that you might need to make when migrating to the Yocto Project 3.4 release from previous releases, please see the following manual:

https://docs.yoctoproject.org/migration-guides/migration-3.4.html

----------------
Security Fixes
----------------

* apr: CVE-2021-35940
* aspell: CVE-2019-25051
* avahi: CVE-2021-3468, CVE-2021-36217
* binutils: CVE-2021-20197
* bluez: CVE-2021-3658
* busybox: CVE-2021-28831
* cairo: CVE-2020-35492
* cpio: CVE-2021-38185
* expat: CVE-2013-0340
* ffmpeg: CVE-2020-20446, CVE-2020-22015, CVE-2020-22021, CVE-2020-22033, CVE-2020-22019, CVE-2021-33815, CVE-2021-38171, CVE-2020-20453
* glibc: CVE-2021-33574, CVE-2021-38604
* inetutils: CVE-2021-40491
* libgcrypt: CVE-2021-40528
* linux-yocto/5.10, 5.14: CVE-2021-3653, CVE-2021-3656
* lz4: CVE-2021-3520
* nettle: CVE-2021-20305
* openssl: CVE-2021-3711, CVE-2021-3712
* perl: CVE-2021-36770
* python3: CVE-2021-29921
* python3-pip: CVE-2021-3572
* qemu: CVE-2020-27821, CVE-2020-29443, CVE-2020-35517, CVE-2021-3392, CVE-2021-3409, CVE-2021-3416, CVE-2021-3527, CVE-2021-3544, CVE-2021-3545, CVE-2021-3546, CVE-2021-3682, CVE-2021-20181, CVE-2021-20221, CVE-2021-20257, CVE-2021-20263
* rpm: CVE-2021-3421, CVE-2021-20271
* rsync: CVE-2020-14387
* util-linux: CVE-2021-37600
* vim: CVE-2021-3770, CVE-2021-3778
* wpa-supplicant: CVE-2021-30004
* xdg-utils: CVE-2020-27748
* xserver-xorg: CVE-2021-3472

-----------------
Recipe Upgrades
-----------------

* acl 2.2.53 -> 2.3.1
* acpica 20210105 -> 20210730
* alsa-lib 1.2.4 -> 1.2.5.1
* alsa-plugins 1.2.2 -> 1.2.5
* alsa-tools 1.2.2 -> 1.2.5
* alsa-topology-conf 1.2.4 -> 1.2.5.1
* alsa-ucm-conf 1.2.4 -> 1.2.5.1
* alsa-utils 1.2.4 -> 1.2.5.1
* alsa-utils-scripts 1.2.4 -> 1.2.5.1
* apt 2.2.2 -> 2.2.4
* at 3.2.1 -> 3.2.2
* at-spi2-core 2.38.0 -> 2.40.3
* autoconf-archive 2019.01.06 -> 2021.02.19
* babeltrace2 2.0.3 -> 2.0.4
* bash 5.1 -> 5.1.8
* bind 9.16.16 -> 9.16.20
* binutils 2.36.1 -> 2.37
* binutils-cross 2.36.1 -> 2.37
* binutils-cross-canadian 2.36.1 -> 2.37
* binutils-cross-testsuite 2.36.1 -> 2.37
* binutils-crosssdk 2.36.1 -> 2.37
* bison 3.7.5 -> 3.7.6
* blktrace 1.2.0+gitX -> 1.3.0+gitX
* bluez5 5.56 -> 5.61
* boost 1.75.0 -> 1.77.0
* boost-build-native 4.3.0 -> 4.4.1
* btrfs-tools 5.10.1 -> 5.13.1
* busybox 1.33.1 -> 1.34.0
* busybox-inittab 1.33.0 -> 1.34.0
* ccache 4.2 -> 4.4
* cmake 3.19.5 -> 3.21.1
* cmake-native 3.19.5 -> 3.21.1
* connman 1.39 -> 1.40
* createrepo-c 0.17.0 -> 0.17.4
* cronie 1.5.5 -> 1.5.7
* cross-localedef-native 2.33 -> 2.34
* cups 2.3.3 -> 2.3.3op2
* curl 7.75.0 -> 7.78.0
* dbus-glib 0.110 -> 0.112
* dejagnu 1.6.2 -> 1.6.3
* diffoscope 172 -> 181
* diffutils 3.7 -> 3.8
* distcc 3.3.5 -> 3.4
* dnf 4.6.0 -> 4.8.0
* dpkg 1.20.7.1 -> 1.20.9
* dtc 1.6.0 -> 1.6.1
* e2fsprogs 1.46.1 -> 1.46.4
* elfutils 0.183 -> 0.185
* ell 0.38 -> 0.43
* enchant2 2.2.15 -> 2.3.1
* epiphany 3.38.2 -> 40.3
* ethtool 5.10 -> 5.13
* expat 2.2.10 -> 2.4.1
* ffmpeg 4.3.2 -> 4.4
* file 5.39 -> 5.40
* freetype 2.10.4 -> 2.11.0
* gcc 10.2.0 -> 11.2.0
* gcc-cross 10.2.0 -> 11.2.0
* gcc-cross-canadian 10.2.0 -> 11.2.0
* gcc-crosssdk 10.2.0 -> 11.2.0
* gcc-runtime 10.2.0 -> 11.2.0
* gcc-sanitizers 10.2.0 -> 11.2.0
* gcc-source 10.2.0 -> 11.2.0
* gcr 3.38.1 -> 3.40.0
* gdb 10.1 -> 10.2
* gdb-cross 10.1 -> 10.2
* gdb-cross-canadian 10.1 -> 10.2
* gdk-pixbuf 2.40.0 -> 2.42.6
* ghostscript 9.53.3 -> 9.54.0
* git 2.31.1 -> 2.33.0
* glib-2.0 2.66.7 -> 2.68.4
* glib-networking 2.66.0 -> 2.68.2
* glibc 2.33 -> 2.34
* glibc-locale 2.33 -> 2.34
* glibc-mtrace 2.33 -> 2.34
* glibc-scripts 2.33 -> 2.34
* glibc-testsuite 2.33 -> 2.34
* glslang 11.2.0 -> 11.5.0
* gnome-desktop-testing 2018.1 -> 2021.1
* gnu-config 20210125+gitX -> 20210722+gitX
* gnu-efi 3.0.12 -> 3.0.14
* gnupg 2.2.27 -> 2.3.1
* gobject-introspection 1.66.1 -> 1.68.0
* gpgme 1.15.1 -> 1.16.0
* gptfdisk 1.0.7 -> 1.0.8
* grep 3.6 -> 3.7
* grub 2.04+2.06~rc1 -> 2.06
* grub-efi 2.04+2.06~rc1 -> 2.06
* gsettings-desktop-schemas 3.38.0 -> 40.0
* gtk+3 3.24.25 -> 3.24.30
* harfbuzz 2.7.4 -> 2.9.0
* hdparm 9.60 -> 9.62
* help2man 1.48.2 -> 1.48.4
* hwlatdetect 1.10 -> 2.1
* i2c-tools 4.2 -> 4.3
* icu 68.2 -> 69.1
* igt-gpu-tools 1.25+gitX -> 1.26
* inetutils 2.0 -> 2.1
* iproute2 5.11.0 -> 5.13.0
* iputils s20200821 -> 20210722
* json-glib 1.6.2 -> 1.6.4
* kexec-tools 2.0.21 -> 2.0.22
* kmod 28 -> 29
* kmod-native 28 -> 29
* less 563 -> 590
* libassuan 2.5.4 -> 2.5.5
* libcap 2.48 -> 2.51
* libcgroup 0.41 -> 2.0
* libcomps 0.1.15 -> 0.1.17
* libconvert-asn1-perl 0.27 -> 0.31
* libdazzle 3.38.0 -> 3.40.0
* libdnf 0.58.0 -> 0.63.1
* libdrm 2.4.104 -> 2.4.107
* libedit 20210216-3.1 -> 20210714-3.1
* libepoxy 1.5.5 -> 1.5.9
* liberation-fonts 2.00.1 -> 2.1.4
* libffi 3.3 -> 3.4.2
* libfm 1.3.1 -> 1.3.2
* libgcc 10.2.0 -> 11.2.0
* libgcc-initial 10.2.0 -> 11.2.0
* libgcrypt 1.9.3 -> 1.9.4
* libgfortran 10.2.0 -> 11.2.0
* libgit2 1.1.0 -> 1.1.1
* libglu 9.0.1 -> 9.0.2
* libgpg-error 1.41 -> 1.42
* libgudev 234 -> 237
* libhandy 1.2.0 -> 1.2.3
* libical 3.0.9 -> 3.0.10
* libidn2 2.3.0 -> 2.3.2
* libinput 1.16.4 -> 1.18.1
* libjitterentropy 3.0.1 -> 3.1.0
* libjpeg-turbo 2.0.6 -> 2.1.1
* libksba 1.5.0 -> 1.6.0
* libmodulemd 2.12.0 -> 2.13.0
* libnsl2 1.3.0 -> 2.0.0
* libnss-mdns 0.14.1 -> 0.15.1
* libogg 1.3.4 -> 1.3.5
* libpcap 1.10.0 -> 1.10.1
* libpcre 8.44 -> 8.45
* libpcre2 10.36 -> 10.37
* libportal 0.3 -> 0.4
* librepo 1.13.0 -> 1.14.1
* libsdl2 2.0.14 -> 2.0.16
* libsolv 0.7.17 -> 0.7.19
* libtasn1 4.16.0 -> 4.17.0
* libtest-needs-perl 0.002006 -> 0.002009
* libtirpc 1.3.1 -> 1.3.2
* libubootenv 0.3.1 -> 0.3.2
* libucontext 0.10+X -> 1.1+X
* liburcu 0.12.2 -> 0.13.0
* libuv 1.41.0 -> 1.42.0
* libva 2.10.0 -> 2.12.0
* libva-initial 2.10.0 -> 2.12.0
* libva-utils 2.10.0 -> 2.12.0
* libwebp 1.2.0 -> 1.2.1
* libwpe 1.8.0 -> 1.10.1
* libx11 1.7.0 -> 1.7.2
* libxcrypt 4.4.18 -> 4.4.25
* libxcrypt-compat 4.4.18 -> 4.4.25
* libxfixes 5.0.3 -> 6.0.0
* libxfont2 2.0.4 -> 2.0.5
* libxft 2.3.3 -> 2.3.4
* libxi 1.7.10 -> 1.7.99.2
* libxkbcommon 1.0.3 -> 1.3.0
* libxml2 2.9.10 -> 2.9.12
* libxres 1.2.0 -> 1.2.1
* linux-libc-headers 5.10 -> 5.14
* linux-yocto 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-dev 5.12++gitX -> 5.15++gitX
* linux-yocto-rt 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-tiny 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* llvm 11.1.0 -> 12.0.1
* log4cplus 2.0.6 -> 2.0.7
* logrotate 3.18.0 -> 3.18.1
* ltp 20210121 -> 20210524
* lttng-modules 2.12.6 -> 2.13.0
* lttng-tools 2.12.4 -> 2.13.0
* lttng-ust 2.12.1 -> 2.13.0
* m4 1.4.18 -> 1.4.19
* m4-native 1.4.18 -> 1.4.19
* man-pages 5.10 -> 5.12
* mc 4.8.26 -> 4.8.27
* mesa 21.0.3 -> 21.2.1
* mesa-gl 21.0.3 -> 21.2.1
* meson 0.57.1 -> 0.58.1
* mmc-utils 0.1+gitX (73d6c59af8d1...) -> 0.1+gitX (43282e80e174...)
* mobile-broadband-provider-info 20201225 -> 20210805
* mpg123 1.26.4 -> 1.28.2
* mtd-utils 2.1.2 -> 2.1.3
* mtools 4.0.26 -> 4.0.35
* musl 1.2.2+gitX (e5d2823631bb...) -> 1.2.2+gitX (3f701faace7a...)
* nativesdk-meson 0.57.1 -> 0.58.1
* netbase 6.2 -> 6.3
* nfs-utils 2.5.3 -> 2.5.4
* ofono 1.31 -> 1.32
* openssh 8.5p1 -> 8.7p1
* opkg 0.4.4 -> 0.4.5
* opkg-utils 0.4.3 -> 0.4.5
* ovmf edk2-stable202102 -> edk2-stable202105
* p11-kit 0.23.22 -> 0.24.0
* pango 1.48.2 -> 1.48.9
* patchelf 0.12 -> 0.13
* perl 5.32.1 -> 5.34.0
* piglit 1.0+gitrX (d4d9353b7290...) -> 1.0+gitrX (6a4be9e9946d...)
* pkgconf 1.7.3 -> 1.8.0
* powertop 2.13 -> 2.14
* pseudo 1.9.0+gitX (b988b0a6b8af...) -> 1.9.0+gitX (0cda3ba5f94a...)
* pulseaudio 14.2 -> 15.0
* puzzles 0.0+gitX (84cb4c6701e0...) -> 0.0+gitX (8f3413c31ffd...)
* python3 3.9.5 -> 3.9.6
* python3-attrs 20.3.0 -> 21.2.0
* python3-cython 0.29.22 -> 0.29.24
* python3-dbus 1.2.16 -> 1.2.18
* python3-dbusmock 0.22.0 -> 0.23.1
* python3-docutils 0.16 -> 0.17.1
* python3-git 3.1.14 -> 3.1.20
* python3-gitdb 4.0.5 -> 4.0.7
* python3-hypothesis 6.2.0 -> 6.15.0
* python3-importlib-metadata 3.4.0 -> 4.6.4
* python3-iniparse 0.4 -> 0.5
* python3-jinja2 2.11.3 -> 3.0.1
* python3-libarchive-c 2.9 -> 3.1
* python3-magic 0.4.22 -> 0.4.24
* python3-mako 1.1.4 -> 1.1.5
* python3-markupsafe 1.1.1 -> 2.0.1
* python3-more-itertools 8.7.0 -> 8.8.0
* python3-numpy 1.20.1 -> 1.21.2
* python3-packaging 20.9 -> 21.0
* python3-pathlib2 2.3.5 -> 2.3.6
* python3-pbr 5.4.4 -> 5.6.0
* python3-pip 20.0.2 -> 21.2.4
* python3-pluggy 0.13.1 -> 1.0.0
* python3-pycairo 1.20.0 -> 1.20.1
* python3-pygments 2.8.1 -> 2.10.0
* python3-pygobject 3.38.0 -> 3.40.1
* python3-pytest 6.2.2 -> 6.2.4
* python3-scons 3.1.2 -> 4.2.0
* python3-scons-native 3.1.2 -> 4.2.0
* python3-setuptools 54.1.1 -> 57.4.0
* python3-setuptools-scm 5.0.1 -> 6.0.1
* python3-six 1.15.0 -> 1.16.0
* python3-sortedcontainers 2.3.0 -> 2.4.0
* python3-testtools 2.4.0 -> 2.5.0
* python3-zipp 3.4.1 -> 3.5.0
* qemu 5.2.0 -> 6.0.0
* qemu-native 5.2.0 -> 6.0.0
* qemu-system-native 5.2.0 -> 6.0.0
* re2c 2.0.3 -> 2.2
* rng-tools 6.11 -> 6.14
* rpcbind 1.2.5 -> 1.2.6
* rt-tests 1.10 -> 2.1
* ruby 3.0.1 -> 3.0.2
* rxvt-unicode 9.22 -> 9.26
* shaderc 2020.5 -> 2021.1
* shadow 4.8.1 -> 4.9
* spirv-tools 2020.7 -> 2021.2
* sqlite3 3.35.0 -> 3.36.0
* squashfs-tools 4.4 -> 4.5
* strace 5.11 -> 5.14
* stress-ng 0.12.05 -> 0.13.00
* sudo 1.9.6p1 -> 1.9.7p2
* swig 3.0.12 -> 4.0.2
* sysklogd 2.2.2 -> 2.2.3
* systemd 247.6 -> 249.3
* systemd-boot 247.6 -> 249.3
* systemd-conf 247.6 -> 1.0
* systemtap 4.4 -> 4.5
* systemtap-native 4.4 -> 4.5
* systemtap-uprobes 4.4 -> 4.5
* tcf-agent 1.7.0+gitX (a022ef2f1acf...) -> 1.7.0+gitX (2735e3d6b7ec...)
* texinfo 6.7 -> 6.8
* tiff 4.2.0 -> 4.3.0
* u-boot 2021.01 -> 2021.07
* u-boot-tools 2021.01 -> 2021.07
* usbutils 013 -> 014
* util-linux 2.36.2 -> 2.37.2
* util-linux-libuuid 2.36.2 -> 2.37.2
* vala 0.50.4 -> 0.52.5
* valgrind 3.16.1 -> 3.17.0
* virglrenderer 0.8.2 -> 0.9.1
* vte 0.62.2 -> 0.64.2
* vulkan-headers 1.2.170.0 -> 1.2.182.0
* vulkan-loader 1.2.170.0 -> 1.2.182.0
* vulkan-samples git (55cebd9e7cc4...) -> git (d2187278cb66...)
* vulkan-tools 1.2.170.0 -> 1.2.182.0
* wayland-protocols 1.20 -> 1.21
* webkitgtk 2.30.5 -> 2.32.3
* wireless-regdb 2021.04.21 -> 2021.07.14
* wpebackend-fdo 1.8.0 -> 1.10.0
* x264 r3039+gitX (544c61f08219...) -> r3039+gitX (5db6aa6cab1b...)
* xeyes 1.1.2 -> 1.2.0
* xf86-input-libinput 0.30.0 -> 1.1.0
* xkbcomp 1.4.4 -> 1.4.5
* xkeyboard-config 2.32 -> 2.33
* xorgproto 2020.1 -> 2021.4.99.2
* xserver-xorg 1.20.10 -> 1.20.13
* zstd 1.4.9 -> 1.5.0

</pre>

3.4 Release Notes WIP

2021-10-21T17:10:05Z

PaulEggleton:

<pre>

--------------
Contributors
--------------

Thanks to the following people who contributed to this release:

Adam Romanek
Alejandro Hernandez Samaniego
Alexander Kanavin
Alexandre Belloni
Alexey Brodkin
Alex Stewart
Alistair Francis
Anatol Belski
Anders Wallin
Andrea Adami
Andreas Müller
Andrej Valek
Andres Beltran
Andrey Zhizhikin
Anibal Limon
Anthony Bagwell
Anton Blanchard
Anuj Mittal
Armin Kuster
Asfak Rahman
Bastian Krause
Bernhard Rosenkränzer
Bruce Ashfield
Carlos Rafael Giani
Chandana kalluri
Changhyeok Bae
Changqing Li
Chanho Park
Chen Qi
Chris Laplante
Christophe Chapuis
Christoph Muellner
Claudius Heine
Damian Wrobel
Daniel Ammann
Daniel Gomez
Daniel McGregor
Daniel Wagenknecht
Denys Dmytriyenko
Devendra Tewari
Diego Sueiro
Dmitry Baryshkov
Douglas Royds
Dragos-Marian Panait
Drew Moseley
Enrico Scholz
Fabio Berton
Florian Amstutz
Gavin Li
Guillaume Champagne
Harald Brinkmann
Henning Schild
He Zhe
Hongxu Jia
Hsia-Jun (Randy) Li
Jean Bouchard
Joe Slater
Jonas Höppner
Jon Mason
Jose Quaresma
Joshua Watt
Justin Bronder
Kai Kang
Kenfe-Mickael Laventure
Kevin Hao
Khairul Rohaizzat Jamaluddin
Khem Raj
Kiran Surendran
Konrad Weihmann
Kristian Klausen
Kyle Russell
Lee Chee Yang
Lei Maohui
Luca Boccassi
Marco Felsch
Marcus Comstedt
Marek Vasut
Mark Hatle
Markus Volk
Marta Rybczynska
Martin Jansa
Matthias Klein
Matthias Schiffer
Matt Madison
Matt Spencer
Max Krummenacher
Michael Halstead
Michael Ho
Michael Opdenacker
Mike Crowe
Mikko Rapeli
Ming Liu
Mingli Yu
Minjae Kim
Nicolas Dechesne
Niels Avonds
Nikolay Papenkov
Nisha Parrakat
Olaf Mandel
Oleksandr Kravchuk
Oleksandr Popovych
Oliver Kranz
Otavio Salvador
Patrick Williams
Paul Barker
Paul Eggleton
Paul Gortmaker
Paulo Cesar Zaneti
Peter Bergin
Peter Budny
Peter Kjellerstedt
Petr Vorel
Przemyslaw Gorszkowski
Purushottam Choudhary
Qiang Zhang
Quentin Schulz
Ralph Siemsen
Randy MacLeod
Ranjitsinh Rathod
Rasmus Villemoes
Reto Schneider
Richard Purdie
Richard Weinberger
Robert Joslyn
Robert P. J. Day
Robert Yang
Romain Naour
Ross Burton
Sakib Sajal
Samuli Piippo
Saul Wold
Scott Murray
Scott Weaver
Stefan Ghinea
Stefan Herbrechtsmeier
Stefano Babic
Stefan Wiehler
Steve Sakoman
Teoh Jay Shen
Thomas Perrot
Tim Orling
Tom Pollard
Tom Rini
Tony Battersby
Tony Tascioglu
Trevor Gamblin
Trevor Woerner
Ulrich Ölmann
Valentin Danaila
Vinay Kumar
Vineela Tummalapalli
Vinícius Ossanes Aquino
Vivien Didelot
Vyacheslav Yurkov
Wang Mingyu
Wes Lindauer
William A. Kennington III
Yanfei Xu
Yann Dirson
Yi Fan Yu
Yi Zhao
Zang Ruochen
Zheng Ruoqin
Zoltán Böszörményi

-----------------------------
New Features / Enhancements
-----------------------------

* Linux kernel 5.14, glibc 2.34 and ~280 other recipe upgrades
* Switched override character to ':' (replacing '_') for more robust parsing and improved performance - see migration guide for help on migrating
* Rust integrated into core, providing rust support for cross-compilation and SDK
* New create-spdx class for creating SPDX SBoM documents
* New recipes: cargo, core-image-ptest-all, core-image-ptest-fast, core-image-weston-sdk, erofs-utils, gcompat, gi-docgen, libmicrohttpd, libseccomp, libstd-rs, perlcross, python3-markdown, python3-pyyaml, python3-smartypants, python3-typogrify, rust, rust-cross, rust-cross-canadian, rust-hello-world, rust-llvm, rust-tools-cross-canadian, rustfmt, xwayland
* Several optimisations to reduce unnecessary task dependencies for faster builds
* seccomp integrated into core, with additional enabling for gnutls, systemd, qemu
* debuginfod support now enabled by default
* Switched several recipes over to using OpenSSL instead of GnuTLS (wpa-supplicant, curl, glib-networking) or disable GnuTLS (cups) by default
* Improvements to LTO plugin installation and reproducibility
* Architecture-specific improvements:
- glibc: Enable memory tagging for aarch64
- testimage: remove aarch64 xorg exclusion
- arch-arm*: add better support for gcc march extensions
- tune-cortexm*: add support for all Arm Cortex-M processors
- tune-cortexr*: add support for all Arm Cortex-R processors
- arch-armv4: Allow -march=armv4
- qemuarm*: use virtio graphics
- baremetal-helloworld: Enable RISC-V 64/32 port
- ldconfig-native: Add RISC-V support
- qemuriscv: Enable 4 core emulation
- Add ARC support in gdb, dpkg, dhcpcd
- conf/machine-sdk: Add ppc64 SDK machine
- libjpeg-turbo: Handle powerpc64le without Altivec
- pixman: Handle PowerPC without Altivec
- mesa: enable gallium intel drivers when building for x86
- mesa: enable crocus driver for older intel graphics
* Kernel-related changes:
- Support zstd-compressed modules and initramfs images
- Allow opt-out of split kernel modules
- linux-yocto-dev: base AUTOREV on specified version
- kernel-yocto: provide debug / summary information for metadata
- kernel-uboot: Handle gzip and lzo compression options
- linux-yocto/5.14: added devupstream support
- linux-yocto: add vfat KERNEL_FEATURE when MACHINE_FEATURES include vfat
- linux-yocto: enable TYPEC_TCPCI in usbc fragment
* Image-related improvements
- New erofs, erofs-lz4 and erofs-lz4hc image types
- New squashfs-zst and cpio.zst image types
- New lic-pkgs IMAGE_FEATURES item to install all license packages
- Added zsync metadata conversion support
- Use xargs to set file timestamps for significant (>90%) do_image speedup
- Find .ko.gz and .ko.xz kernel modules as well when determining need to run depmod on an image
- Show formatted error messages instead of tracebacks for systemctl errors
- No longer ignore installation failures in complementary package installation
- Remove ldconfig auxiliary cache when not needed
* wic enhancements:
- Added erofs filesystem support
- Added --extra-space argument to leave extra space after last partition
- Added --no-fstab-update part option to allow using the stock fstab
- bootimg-efi: added Unified Kernel Image option
- bootimg-pcbios: use label provided when formatting a DOS partition
* New PACKAGECONFIG options in btrfs-tools, ccache, coreutils, cups, dbus, elfutils, ffmpeg, findutils, glib-2.0, gstreamer1.0-plugins-bad, gstreamer1.0-plugins-base, libarchive, libnotify, libpsl, man-db, mesa, ovmf, parted, prelink, qemu, rpm, shadow, systemd, tar, vim, weston
* scripts/contrib/image-manifest: add new script
* New gi-docgen class for GNOME library documentation
* sdk: Enable do_populate_sdk with multilibs
* sdk: Decouple default install path from built in path
* poky: Use SDKPATHINSTALL instead of SDKPATH
* deb: apply postinstall on sdk
* populate_sdk_ext: Error if trying to generate an eSDK from a multiconfig
* populate_sdk_ext: Fix handling of TOOLCHAIN_HOST_TASK in the eSDK case
* devtool upgrade: rebase override-only patches as well
* devtool: print a warning on upgrades if PREFERRED_VERSION is set
* recipetool/create_buildsys_python: treat BSD as BSD-3-Clause
* busybox: add tmpdir option into mktemp applet
* busybox: support mounting swap via labels
* busybox: Enable long options for enabled applets
* testimage.bbclass: Add dump-guest-memory cmd
* util-linux: build chfn and chsh by default
* buildstats.bbclass: log host data on failure to task specific file
* buildstats.bbclass: collect data in the same file.
* init-manager-systemd: define weak dev manager
* Add proper unpack dependency for .zst compressed archives
* systemd: set zstd as default compression option
* Ptest enhancements:
- ptest-runner: install script to collect system data on failure
- Added ptest support to python3-hypothesis, python3-jinja2, python3-markupsafe;
- Enhanced ptest support in lttng, util-linux, and others
- New leaner ptest image recipes based upon core-image-minimal
* conf/machine: move tune files to architecture directories
* python3-manifest: add statistics subpackage
* qemurunner: Add support for qmp commands
* runqemu: decouple bios and kernel options
* qemu: add a hint on how to enable CPU render nodes when a suitable GPU is absent
* qemu: use 4 cores in qemu guests
* devupstream: Allow support of native class extensions
* overlayfs.bbclass: generate overlayfs mount units
* rootfs-postcommands: add QA check for overlayfs
* pypi: Allow override of PyPI archive name
* Allow global override of golang GO_DYNLINK
* lib/oe/elf: Add Android OS to machine_dict
* meson.bbclass: Make the default buildtype "debug" if DEBUG_BUILD is 1
* vim: add option to disable NLS support
* buildhistory: Add option to strip path prefix
* buildhistory: Add output file listing package information
* buildhistory: Label packages providing per-file dependencies in depends.dot
* distro_features_check: expand with IMAGE_FEATURES
* u-boot enhancements:
- Make SPL suffix configurable
- Make UBOOT_BINARYNAME configurable
- Package extlinux.conf separately
- Allow deploying the u-boot DTB
* opensbi: Add support for specifying a device tree
* classes/package: Add extended packagedata
* poky: Use https in PREMIRRORS
* cross-canadian: make android pass target sys check
* local.conf.sample: Update sstate mirror entry with new hash equivalence setting
* tzdata: Allow controlling zoneinfo binary format
* bitbake improvements:
- New bitbake-getvar helper command to query a variable value (with history)
- bitbake-layers: add --fetchdir parameter to layerindex-fetch
- bitbake-layers: add skip reason to output
- bitbake-diffsigs: sort diff output for consistency
- cooker: Allow upstream for local hash equivalence server
- fetch2/s3: allow to use credentials and switch profile from environment variables
- fetch2/s3: Add progress handler for S3 cp command
- fetch2/wget: fetch securely by default
- fetch2/wget: Enable ftps
- fetch2/svn: Allow peg-revision functionality to be disabled
- fetch2: npm: Support npm archives with missing search directory mode
- fetch2: npmsw: Add support for local tarball and link sources
- prserv: added read-only mode
- prserv: replaced XML RPC with modern asyncrpc implementation
- Numerous warning/error message improvements
* core-image-multilib-example: base on weston, and not sato
* reproducible_build.bbclass: Enable -Wdate-time
* yocto-check-layer: ensure that all layer dependencies are tested too
* npm.bbclass: Allow nodedir to be overridden by NPM_NODEDIR
* cve-extra-exclusions.inc: add exclusion list for intractable CVE's
* license_image.bbclass: Detect broken symlinks
* sysstat: make the service start automatically
* sanity: Add error check for '%' in build path
* sanity: Further improve directory sanity tests
* sanity.bbclass: mention CONNECTIVITY_CHECK_URIS in network failure message
* oe-time-dd-test.sh: add options and refactor
* zstd: Include pzstd in the build
* mirrors.bbclass: provide additional rule for git repo fallbacks
* own-mirrors: Add support for s3:// scheme in SOURCE_MIRROR_URL
* common-licenses: add missing SPDX licences
* Add MAINTAINERS.md file

* pulseaudio: Drop pulseaudio-conf
* rpm: do not RRECOMMEND rpm-build

-----------------
Recipe Licenses
-----------------

The following corrections have been made to the LICENSE values set by recipes:

------------------------
Migration instructions
------------------------

For details on changes that you might need to make when migrating to the Yocto Project 3.4 release from previous releases, please see the following manual:

https://docs.yoctoproject.org/migration-guides/migration-3.4.html

----------------
Security Fixes
----------------

* apr: CVE-2021-35940
* aspell: CVE-2019-25051
* avahi: CVE-2021-3468, CVE-2021-36217
* binutils: CVE-2021-20197
* bluez: CVE-2021-3658
* busybox: CVE-2021-28831
* cairo: CVE-2020-35492
* cpio: CVE-2021-38185
* expat: CVE-2013-0340
* ffmpeg: CVE-2020-20446, CVE-2020-22015, CVE-2020-22021, CVE-2020-22033, CVE-2020-22019, CVE-2021-33815, CVE-2021-38171, CVE-2020-20453
* glibc: CVE-2021-33574, CVE-2021-38604
* inetutils: CVE-2021-40491
* libgcrypt: CVE-2021-40528
* linux-yocto/5.10, 5.14: CVE-2021-3653, CVE-2021-3656
* lz4: CVE-2021-3520
* nettle: CVE-2021-20305
* openssl: CVE-2021-3711, CVE-2021-3712
* perl: CVE-2021-36770
* python3: CVE-2021-29921
* python3-pip: CVE-2021-3572
* qemu: CVE-2020-27821, CVE-2020-29443, CVE-2020-35517, CVE-2021-3392, CVE-2021-3409, CVE-2021-3416, CVE-2021-3527, CVE-2021-3544, CVE-2021-3545, CVE-2021-3546, CVE-2021-3682, CVE-2021-20181, CVE-2021-20221, CVE-2021-20257, CVE-2021-20263
* rpm: CVE-2021-3421, CVE-2021-20271
* rsync: CVE-2020-14387
* util-linux: CVE-2021-37600
* vim: CVE-2021-3770, CVE-2021-3778
* wpa-supplicant: CVE-2021-30004
* xdg-utils: CVE-2020-27748
* xserver-xorg: CVE-2021-3472

-----------------
Recipe Upgrades
-----------------

* acl 2.2.53 -> 2.3.1
* acpica 20210105 -> 20210730
* alsa-lib 1.2.4 -> 1.2.5.1
* alsa-plugins 1.2.2 -> 1.2.5
* alsa-tools 1.2.2 -> 1.2.5
* alsa-topology-conf 1.2.4 -> 1.2.5.1
* alsa-ucm-conf 1.2.4 -> 1.2.5.1
* alsa-utils 1.2.4 -> 1.2.5.1
* alsa-utils-scripts 1.2.4 -> 1.2.5.1
* apt 2.2.2 -> 2.2.4
* at 3.2.1 -> 3.2.2
* at-spi2-core 2.38.0 -> 2.40.3
* autoconf-archive 2019.01.06 -> 2021.02.19
* babeltrace2 2.0.3 -> 2.0.4
* bash 5.1 -> 5.1.8
* bind 9.16.16 -> 9.16.20
* binutils 2.36.1 -> 2.37
* binutils-cross 2.36.1 -> 2.37
* binutils-cross-canadian 2.36.1 -> 2.37
* binutils-cross-testsuite 2.36.1 -> 2.37
* binutils-crosssdk 2.36.1 -> 2.37
* bison 3.7.5 -> 3.7.6
* blktrace 1.2.0+gitX -> 1.3.0+gitX
* bluez5 5.56 -> 5.61
* boost 1.75.0 -> 1.77.0
* boost-build-native 4.3.0 -> 4.4.1
* btrfs-tools 5.10.1 -> 5.13.1
* busybox 1.33.1 -> 1.34.0
* busybox-inittab 1.33.0 -> 1.34.0
* ccache 4.2 -> 4.4
* cmake 3.19.5 -> 3.21.1
* cmake-native 3.19.5 -> 3.21.1
* connman 1.39 -> 1.40
* createrepo-c 0.17.0 -> 0.17.4
* cronie 1.5.5 -> 1.5.7
* cross-localedef-native 2.33 -> 2.34
* cups 2.3.3 -> 2.3.3op2
* curl 7.75.0 -> 7.78.0
* dbus-glib 0.110 -> 0.112
* dejagnu 1.6.2 -> 1.6.3
* diffoscope 172 -> 181
* diffutils 3.7 -> 3.8
* distcc 3.3.5 -> 3.4
* dnf 4.6.0 -> 4.8.0
* dpkg 1.20.7.1 -> 1.20.9
* dtc 1.6.0 -> 1.6.1
* e2fsprogs 1.46.1 -> 1.46.4
* elfutils 0.183 -> 0.185
* ell 0.38 -> 0.43
* enchant2 2.2.15 -> 2.3.1
* epiphany 3.38.2 -> 40.3
* ethtool 5.10 -> 5.13
* expat 2.2.10 -> 2.4.1
* ffmpeg 4.3.2 -> 4.4
* file 5.39 -> 5.40
* freetype 2.10.4 -> 2.11.0
* gcc 10.2.0 -> 11.2.0
* gcc-cross 10.2.0 -> 11.2.0
* gcc-cross-canadian 10.2.0 -> 11.2.0
* gcc-crosssdk 10.2.0 -> 11.2.0
* gcc-runtime 10.2.0 -> 11.2.0
* gcc-sanitizers 10.2.0 -> 11.2.0
* gcc-source 10.2.0 -> 11.2.0
* gcr 3.38.1 -> 3.40.0
* gdb 10.1 -> 10.2
* gdb-cross 10.1 -> 10.2
* gdb-cross-canadian 10.1 -> 10.2
* gdk-pixbuf 2.40.0 -> 2.42.6
* ghostscript 9.53.3 -> 9.54.0
* git 2.31.1 -> 2.33.0
* glib-2.0 2.66.7 -> 2.68.4
* glib-networking 2.66.0 -> 2.68.2
* glibc 2.33 -> 2.34
* glibc-locale 2.33 -> 2.34
* glibc-mtrace 2.33 -> 2.34
* glibc-scripts 2.33 -> 2.34
* glibc-testsuite 2.33 -> 2.34
* glslang 11.2.0 -> 11.5.0
* gnome-desktop-testing 2018.1 -> 2021.1
* gnu-config 20210125+gitX -> 20210722+gitX
* gnu-efi 3.0.12 -> 3.0.14
* gnupg 2.2.27 -> 2.3.1
* gobject-introspection 1.66.1 -> 1.68.0
* gpgme 1.15.1 -> 1.16.0
* gptfdisk 1.0.7 -> 1.0.8
* grep 3.6 -> 3.7
* grub 2.04+2.06~rc1 -> 2.06
* grub-efi 2.04+2.06~rc1 -> 2.06
* gsettings-desktop-schemas 3.38.0 -> 40.0
* gtk+3 3.24.25 -> 3.24.30
* harfbuzz 2.7.4 -> 2.9.0
* hdparm 9.60 -> 9.62
* help2man 1.48.2 -> 1.48.4
* hwlatdetect 1.10 -> 2.1
* i2c-tools 4.2 -> 4.3
* icu 68.2 -> 69.1
* igt-gpu-tools 1.25+gitX -> 1.26
* inetutils 2.0 -> 2.1
* iproute2 5.11.0 -> 5.13.0
* iputils s20200821 -> 20210722
* json-glib 1.6.2 -> 1.6.4
* kexec-tools 2.0.21 -> 2.0.22
* kmod 28 -> 29
* kmod-native 28 -> 29
* less 563 -> 590
* libassuan 2.5.4 -> 2.5.5
* libcap 2.48 -> 2.51
* libcgroup 0.41 -> 2.0
* libcomps 0.1.15 -> 0.1.17
* libconvert-asn1-perl 0.27 -> 0.31
* libdazzle 3.38.0 -> 3.40.0
* libdnf 0.58.0 -> 0.63.1
* libdrm 2.4.104 -> 2.4.107
* libedit 20210216-3.1 -> 20210714-3.1
* libepoxy 1.5.5 -> 1.5.9
* liberation-fonts 2.00.1 -> 2.1.4
* libffi 3.3 -> 3.4.2
* libfm 1.3.1 -> 1.3.2
* libgcc 10.2.0 -> 11.2.0
* libgcc-initial 10.2.0 -> 11.2.0
* libgcrypt 1.9.3 -> 1.9.4
* libgfortran 10.2.0 -> 11.2.0
* libgit2 1.1.0 -> 1.1.1
* libglu 9.0.1 -> 9.0.2
* libgpg-error 1.41 -> 1.42
* libgudev 234 -> 237
* libhandy 1.2.0 -> 1.2.3
* libical 3.0.9 -> 3.0.10
* libidn2 2.3.0 -> 2.3.2
* libinput 1.16.4 -> 1.18.1
* libjitterentropy 3.0.1 -> 3.1.0
* libjpeg-turbo 2.0.6 -> 2.1.1
* libksba 1.5.0 -> 1.6.0
* libmodulemd 2.12.0 -> 2.13.0
* libnsl2 1.3.0 -> 2.0.0
* libnss-mdns 0.14.1 -> 0.15.1
* libogg 1.3.4 -> 1.3.5
* libpcap 1.10.0 -> 1.10.1
* libpcre 8.44 -> 8.45
* libpcre2 10.36 -> 10.37
* libportal 0.3 -> 0.4
* librepo 1.13.0 -> 1.14.1
* libsdl2 2.0.14 -> 2.0.16
* libsolv 0.7.17 -> 0.7.19
* libtasn1 4.16.0 -> 4.17.0
* libtest-needs-perl 0.002006 -> 0.002009
* libtirpc 1.3.1 -> 1.3.2
* libubootenv 0.3.1 -> 0.3.2
* libucontext 0.10+X -> 1.1+X
* liburcu 0.12.2 -> 0.13.0
* libuv 1.41.0 -> 1.42.0
* libva 2.10.0 -> 2.12.0
* libva-initial 2.10.0 -> 2.12.0
* libva-utils 2.10.0 -> 2.12.0
* libwebp 1.2.0 -> 1.2.1
* libwpe 1.8.0 -> 1.10.1
* libx11 1.7.0 -> 1.7.2
* libxcrypt 4.4.18 -> 4.4.25
* libxcrypt-compat 4.4.18 -> 4.4.25
* libxfixes 5.0.3 -> 6.0.0
* libxfont2 2.0.4 -> 2.0.5
* libxft 2.3.3 -> 2.3.4
* libxi 1.7.10 -> 1.7.99.2
* libxkbcommon 1.0.3 -> 1.3.0
* libxml2 2.9.10 -> 2.9.12
* libxres 1.2.0 -> 1.2.1
* linux-libc-headers 5.10 -> 5.14
* linux-yocto 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-dev 5.12++gitX -> 5.15++gitX
* linux-yocto-rt 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-tiny 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* llvm 11.1.0 -> 12.0.1
* log4cplus 2.0.6 -> 2.0.7
* logrotate 3.18.0 -> 3.18.1
* ltp 20210121 -> 20210524
* lttng-modules 2.12.6 -> 2.13.0
* lttng-tools 2.12.4 -> 2.13.0
* lttng-ust 2.12.1 -> 2.13.0
* m4 1.4.18 -> 1.4.19
* m4-native 1.4.18 -> 1.4.19
* man-pages 5.10 -> 5.12
* mc 4.8.26 -> 4.8.27
* mesa 21.0.3 -> 21.2.1
* mesa-gl 21.0.3 -> 21.2.1
* meson 0.57.1 -> 0.58.1
* mmc-utils 0.1+gitX (73d6c59af8d1...) -> 0.1+gitX (43282e80e174...)
* mobile-broadband-provider-info 20201225 -> 20210805
* mpg123 1.26.4 -> 1.28.2
* mtd-utils 2.1.2 -> 2.1.3
* mtools 4.0.26 -> 4.0.35
* musl 1.2.2+gitX (e5d2823631bb...) -> 1.2.2+gitX (3f701faace7a...)
* nativesdk-meson 0.57.1 -> 0.58.1
* netbase 6.2 -> 6.3
* nfs-utils 2.5.3 -> 2.5.4
* ofono 1.31 -> 1.32
* openssh 8.5p1 -> 8.7p1
* opkg 0.4.4 -> 0.4.5
* opkg-utils 0.4.3 -> 0.4.5
* ovmf edk2-stable202102 -> edk2-stable202105
* p11-kit 0.23.22 -> 0.24.0
* pango 1.48.2 -> 1.48.9
* patchelf 0.12 -> 0.13
* perl 5.32.1 -> 5.34.0
* piglit 1.0+gitrX (d4d9353b7290...) -> 1.0+gitrX (6a4be9e9946d...)
* pkgconf 1.7.3 -> 1.8.0
* powertop 2.13 -> 2.14
* pseudo 1.9.0+gitX (b988b0a6b8af...) -> 1.9.0+gitX (0cda3ba5f94a...)
* pulseaudio 14.2 -> 15.0
* puzzles 0.0+gitX (84cb4c6701e0...) -> 0.0+gitX (8f3413c31ffd...)
* python3 3.9.5 -> 3.9.6
* python3-attrs 20.3.0 -> 21.2.0
* python3-cython 0.29.22 -> 0.29.24
* python3-dbus 1.2.16 -> 1.2.18
* python3-dbusmock 0.22.0 -> 0.23.1
* python3-docutils 0.16 -> 0.17.1
* python3-git 3.1.14 -> 3.1.20
* python3-gitdb 4.0.5 -> 4.0.7
* python3-hypothesis 6.2.0 -> 6.15.0
* python3-importlib-metadata 3.4.0 -> 4.6.4
* python3-iniparse 0.4 -> 0.5
* python3-jinja2 2.11.3 -> 3.0.1
* python3-libarchive-c 2.9 -> 3.1
* python3-magic 0.4.22 -> 0.4.24
* python3-mako 1.1.4 -> 1.1.5
* python3-markupsafe 1.1.1 -> 2.0.1
* python3-more-itertools 8.7.0 -> 8.8.0
* python3-numpy 1.20.1 -> 1.21.2
* python3-packaging 20.9 -> 21.0
* python3-pathlib2 2.3.5 -> 2.3.6
* python3-pbr 5.4.4 -> 5.6.0
* python3-pip 20.0.2 -> 21.2.4
* python3-pluggy 0.13.1 -> 1.0.0
* python3-pycairo 1.20.0 -> 1.20.1
* python3-pygments 2.8.1 -> 2.10.0
* python3-pygobject 3.38.0 -> 3.40.1
* python3-pytest 6.2.2 -> 6.2.4
* python3-scons 3.1.2 -> 4.2.0
* python3-scons-native 3.1.2 -> 4.2.0
* python3-setuptools 54.1.1 -> 57.4.0
* python3-setuptools-scm 5.0.1 -> 6.0.1
* python3-six 1.15.0 -> 1.16.0
* python3-sortedcontainers 2.3.0 -> 2.4.0
* python3-testtools 2.4.0 -> 2.5.0
* python3-zipp 3.4.1 -> 3.5.0
* qemu 5.2.0 -> 6.0.0
* qemu-native 5.2.0 -> 6.0.0
* qemu-system-native 5.2.0 -> 6.0.0
* re2c 2.0.3 -> 2.2
* rng-tools 6.11 -> 6.14
* rpcbind 1.2.5 -> 1.2.6
* rt-tests 1.10 -> 2.1
* ruby 3.0.1 -> 3.0.2
* rxvt-unicode 9.22 -> 9.26
* shaderc 2020.5 -> 2021.1
* shadow 4.8.1 -> 4.9
* spirv-tools 2020.7 -> 2021.2
* sqlite3 3.35.0 -> 3.36.0
* squashfs-tools 4.4 -> 4.5
* strace 5.11 -> 5.14
* stress-ng 0.12.05 -> 0.13.00
* sudo 1.9.6p1 -> 1.9.7p2
* swig 3.0.12 -> 4.0.2
* sysklogd 2.2.2 -> 2.2.3
* systemd 247.6 -> 249.3
* systemd-boot 247.6 -> 249.3
* systemd-conf 247.6 -> 1.0
* systemtap 4.4 -> 4.5
* systemtap-native 4.4 -> 4.5
* systemtap-uprobes 4.4 -> 4.5
* tcf-agent 1.7.0+gitX (a022ef2f1acf...) -> 1.7.0+gitX (2735e3d6b7ec...)
* texinfo 6.7 -> 6.8
* tiff 4.2.0 -> 4.3.0
* u-boot 2021.01 -> 2021.07
* u-boot-tools 2021.01 -> 2021.07
* usbutils 013 -> 014
* util-linux 2.36.2 -> 2.37.2
* util-linux-libuuid 2.36.2 -> 2.37.2
* vala 0.50.4 -> 0.52.5
* valgrind 3.16.1 -> 3.17.0
* virglrenderer 0.8.2 -> 0.9.1
* vte 0.62.2 -> 0.64.2
* vulkan-headers 1.2.170.0 -> 1.2.182.0
* vulkan-loader 1.2.170.0 -> 1.2.182.0
* vulkan-samples git (55cebd9e7cc4...) -> git (d2187278cb66...)
* vulkan-tools 1.2.170.0 -> 1.2.182.0
* wayland-protocols 1.20 -> 1.21
* webkitgtk 2.30.5 -> 2.32.3
* wireless-regdb 2021.04.21 -> 2021.07.14
* wpebackend-fdo 1.8.0 -> 1.10.0
* x264 r3039+gitX (544c61f08219...) -> r3039+gitX (5db6aa6cab1b...)
* xeyes 1.1.2 -> 1.2.0
* xf86-input-libinput 0.30.0 -> 1.1.0
* xkbcomp 1.4.4 -> 1.4.5
* xkeyboard-config 2.32 -> 2.33
* xorgproto 2020.1 -> 2021.4.99.2
* xserver-xorg 1.20.10 -> 1.20.13
* zstd 1.4.9 -> 1.5.0

</pre>

3.4 Release Notes WIP

2021-10-21T16:42:27Z

PaulEggleton:

<pre>

--------------
Contributors
--------------

Thanks to the following people who contributed to this release:

Adam Romanek
Alejandro Hernandez Samaniego
Alexander Kanavin
Alexandre Belloni
Alexey Brodkin
Alex Stewart
Alistair Francis
Anatol Belski
Anders Wallin
Andrea Adami
Andreas Müller
Andrej Valek
Andres Beltran
Andrey Zhizhikin
Anibal Limon
Anthony Bagwell
Anton Blanchard
Anuj Mittal
Armin Kuster
Asfak Rahman
Bastian Krause
Bernhard Rosenkränzer
Bruce Ashfield
Carlos Rafael Giani
Chandana kalluri
Changhyeok Bae
Changqing Li
Chanho Park
Chen Qi
Chris Laplante
Christophe Chapuis
Christoph Muellner
Claudius Heine
Damian Wrobel
Daniel Ammann
Daniel Gomez
Daniel McGregor
Daniel Wagenknecht
Denys Dmytriyenko
Devendra Tewari
Diego Sueiro
Dmitry Baryshkov
Douglas Royds
Dragos-Marian Panait
Drew Moseley
Enrico Scholz
Fabio Berton
Florian Amstutz
Gavin Li
Guillaume Champagne
Harald Brinkmann
Henning Schild
He Zhe
Hongxu Jia
Hsia-Jun (Randy) Li
Jean Bouchard
Joe Slater
Jonas Höppner
Jon Mason
Jose Quaresma
Joshua Watt
Justin Bronder
Kai Kang
Kenfe-Mickael Laventure
Kevin Hao
Khairul Rohaizzat Jamaluddin
Khem Raj
Kiran Surendran
Konrad Weihmann
Kristian Klausen
Kyle Russell
Lee Chee Yang
Lei Maohui
Luca Boccassi
Marco Felsch
Marcus Comstedt
Marek Vasut
Mark Hatle
Markus Volk
Marta Rybczynska
Martin Jansa
Matthias Klein
Matthias Schiffer
Matt Madison
Matt Spencer
Max Krummenacher
Michael Halstead
Michael Ho
Michael Opdenacker
Mike Crowe
Mikko Rapeli
Ming Liu
Mingli Yu
Minjae Kim
Nicolas Dechesne
Niels Avonds
Nikolay Papenkov
Nisha Parrakat
Olaf Mandel
Oleksandr Kravchuk
Oleksandr Popovych
Oliver Kranz
Otavio Salvador
Patrick Williams
Paul Barker
Paul Eggleton
Paul Gortmaker
Paulo Cesar Zaneti
Peter Bergin
Peter Budny
Peter Kjellerstedt
Petr Vorel
Przemyslaw Gorszkowski
Purushottam Choudhary
Qiang Zhang
Quentin Schulz
Ralph Siemsen
Randy MacLeod
Ranjitsinh Rathod
Rasmus Villemoes
Reto Schneider
Richard Purdie
Richard Weinberger
Robert Joslyn
Robert P. J. Day
Robert Yang
Romain Naour
Ross Burton
Sakib Sajal
Samuli Piippo
Saul Wold
Scott Murray
Scott Weaver
Stefan Ghinea
Stefan Herbrechtsmeier
Stefano Babic
Stefan Wiehler
Steve Sakoman
Teoh Jay Shen
Thomas Perrot
Tim Orling
Tom Pollard
Tom Rini
Tony Battersby
Tony Tascioglu
Trevor Gamblin
Trevor Woerner
Ulrich Ölmann
Valentin Danaila
Vinay Kumar
Vineela Tummalapalli
Vinícius Ossanes Aquino
Vivien Didelot
Vyacheslav Yurkov
Wang Mingyu
Wes Lindauer
William A. Kennington III
Yanfei Xu
Yann Dirson
Yi Fan Yu
Yi Zhao
Zang Ruochen
Zheng Ruoqin
Zoltán Böszörményi

-----------------------------
New Features / Enhancements
-----------------------------

* Linux kernel 5.14, glibc 2.34 and ~280 other recipe upgrades
* Switched override character to ':' (replacing '_') for more robust parsing and improved performance - see migration guide for help on migrating
* Rust integrated into core, providing rust support for cross-compilation and SDK
* New recipes: cargo, core-image-ptest-all, core-image-ptest-fast, core-image-weston-sdk, erofs-utils, gcompat, gi-docgen, libmicrohttpd, libseccomp, libstd-rs, perlcross, python3-markdown, python3-pyyaml, python3-smartypants, python3-typogrify, rust, rust-cross, rust-cross-canadian, rust-hello-world, rust-llvm, rust-tools-cross-canadian, rustfmt, xwayland
* seccomp integrated into core, with additional enabling for gnutls, systemd, qemu
* New create-spdx class for creating SPDX SBoM documents
* New gi-docgen class for GNOME library documentation
* scripts/contrib/image-manifest: add new script
* Several optimisations to reduce unnecessary task dependencies for faster builds
* deb: apply postinstall on sdk
* Switch several recipes over to using OpenSSL instead of GnuTLS (wpa-supplicant, curl, glib-networking) or disable GnuTLS (cups) by default
* default-distrovars.inc: add debuginfod to default DISTRO_FEATURES
* Improvements to LTO plugin installation and reproducibility
* license_image.bbclass: Detect broken symlinks
* core-image-multilib-example: base on weston, and not sato
* reproducible_build.bbclass: Enable -Wdate-time
* yocto-check-layer: Only note a layer without a conf/layer.conf (versus error)
* yocto-check-layer: ensure that all layer dependencies are tested too
* npm.bbclass: Allow nodedir to be overridden by NPM_NODEDIR
* cve-extra-exclusions.inc: add exclusion list for intractable CVE's
* sysstat: make the service start automatically
* sanity: Add error check for '%' in build path
* sanity: Further improve directory sanity tests
* sanity.bbclass: mention CONNECTIVITY_CHECK_URIS in network failure message
* Architecture-specific improvements:
- glibc: Enable memory tagging for aarch64
- testimage: remove aarch64 xorg exclusion
- arch-arm*: add better support for gcc march extensions
- tune-cortexm*: add support for all Arm Cortex-M processors
- tune-cortexr*: add support for all Arm Cortex-R processors
- arch-armv4: Allow -march=armv4
- qemuarm*: use virtio graphics
- baremetal-helloworld: Enable RISC-V 64/32 port
- ldconfig-native: Add RISC-V support
- qemuriscv: Enable 4 core emulation
- Add ARC support in gdb, dpkg, dhcpcd
- conf/machine-sdk: Add ppc64 SDK machine
- libjpeg-turbo: Handle powerpc64le without Altivec
- pixman: Handle PowerPC without Altivec
- mesa: enable gallium intel drivers when building for x86
- mesa: enable crocus driver for older intel graphics
* Kernel-related changes:
- Support zstd-compressed modules and initramfs images
- Allow opt-out of split kernel modules
- linux-yocto-dev: base AUTOREV on specified version
- kernel-yocto: provide debug / summary information for metadata
- kernel-uboot: Handle gzip and lzo compression options
- linux-yocto/5.13: add devupstream support
- linux-yocto: add vfat KERNEL_FEATURE when MACHINE_FEATURES include vfat
- linux-yocto/5.13: enable TYPEC_TCPCI in usbc fragment
- linux-yocto/5.10: enable TYPEC_TCPCI in usbc fragment
* Image-related improvements
- New erofs, erofs-lz4 and erofs-lz4hc image types
- New squashfs-zst and cpio.zst image types
- New lic-pkgs IMAGE_FEATURES item to install all license packages
- Added zsync metadata conversion support
- Use xargs to set file timestamps for significant (>90%) do_image speedup
- Find .ko.gz and .ko.xz kernel modules as well when determining need to run depmod on an image
- Show formatted error messages instead of tracebacks for systemctl errors
- No longer ignore installation failures in complementary package installation
- Remove ldconfig auxiliary cache when not needed
* wic enhancements:
- Added erofs filesystem support
- Added --extra-space argument to leave extra space after last partition
- Added --no-fstab-update part option to allow using the stock fstab
- bootimg-efi: added Unified Kernel Image option
* New PACKAGECONFIG options in btrfs-tools, ccache, coreutils, cups, dbus, elfutils, ffmpeg, findutils, glib-2.0, gstreamer1.0-plugins-bad, gstreamer1.0-plugins-base, libarchive, libnotify, libpsl, man-db, mesa, ovmf, parted, prelink, qemu, rpm, shadow, systemd, tar, vim, weston
* bitbake.conf: enable debuginfod in native/nativesdk
* gdb-cross: enable debuginfod
* sdk: Enable do_populate_sdk with multilibs
* sdk: Decouple default install path from built in path
* poky: Use SDKPATHINSTALL instead of SDKPATH
* populate_sdk_ext: Error if trying to generate an eSDK from a mulitconfig
* populate_sdk_ext: Fix handling of TOOLCHAIN_HOST_TASK in the eSDK case
* devtool upgrade: rebase override-only patches as well
* devtool: print a warning on upgrades if PREFERRED_VERSION is set
* recipetool/create_buildsys_python: treat BSD as BSD-3-Clause
* busybox: add tmpdir option into mktemp applet
* busybox: support mounting swap via labels
* busybox: Enable long options for enabled applets
* Use the label provided when formating a dos partition
* testimage.bbclass: Add dump-guest-memory cmd
* util-linux: build chfn and chsh
* buildstats.bbclass: log host data on failure to task specific file
* buildstats.bbclass: collect data in the same file.
* oe-time-dd-test.sh: add options and refactor
* pseudo: Add uninative configuration sanity check
* own-mirrors: Add support for s3:// scheme in SOURCE_MIRROR_URL
* zstd: Include pzstd in the build
* init-manager-systemd: define weak dev manager
* Add proper unpack dependency for .zst compressed archives
* systemd: set zstd as default compression option
* Ptest enhancements:
- ptest-runner: install script to collect system data on failure
- Added ptest support to python3-hypothesis, python3-jinja2, python3-markupsafe;
- Enhanced ptest support in lttng, util-linux, and others
- New leaner ptest image recipes based upon core-image-minimal
* conf/machine: move tune files to architecture directories
* python3-manifest: add statistics subpackage
* qemurunner: Add support for qmp commands
* qemurunner: change warning to info
* runqemu: decouple bios and kernel options
* qemu: add a hint on how to enable CPU render nodes when a suitable GPU is absent
* qemu: use 4 cores in qemu guests
* devupstream: Allow support of native class extensions
* overlayfs.bbclass: generate overlayfs mount units
* rootfs-postcommands: add QA check for overlayfs
* pypi: Allow override of PyPI archive name
* Allow global override of golang GO_DYNLINK
* lib/oe/elf: Add Android OS to machine_dict
* meson.bbclass: Make the default buildtype "debug" if DEBUG_BUILD is 1
* vim: add option to disable NLS support
* buildhistory: Add option to strip path prefix
* buildhistory: Add output file listing package information
* buildhistory: Label packages providing per-file dependencies in depends.dot
* distro_features_check: expand with IMAGE_FEATURES
* u-boot enhancements:
- Make SPL suffix configurable
- Make UBOOT_BINARYNAME configurable
- Package extlinux.conf separately
- Allow deploying the u-boot DTB
* opensbi: Add support for specifying a device tree
* common-licenses: add missing SPDX licences
* classes/package: Add extended packaged data
* mirrors.bbclass: provide additional rule for git repo fallbacks
* poky: Use https in PREMIRRORS
* cross-canadian: make android pass target sys check
* spdx.py: Add SPDXAnnotation Object (to help mark native recipes)
* local.conf.sample: Update sstate mirror entry with new hash equivalence setting
* tzdata: Allow controlling zoneinfo binary format
* bitbake improvements:
- New bitbake-getvar helper command to query a variable value (with history)
- bitbake-layers: add --fetchdir parameter to layerindex-fetch
- bitbake-layers: add skip reason to output
- bitbake-diffsigs: sort diff output for consistency
- cooker: Allow upstream for local hash equivalence server
- fetch2/s3: allow to use credentials and switch profile from environment variables
- fetch2/s3: Add progress handler for S3 cp command
- fetch2/wget: fetch securely by default
- fetch2/wget: Enable ftps
- fetch2/svn: Allow peg-revision functionality to be disabled
- fetch2: npm: Support npm archives with missing search directory mode
- fetch2: npmsw: Add support for local tarball and link sources
- prserv: added read-only mode
- prserv: replaced XML RPC with modern asyncrpc implementation
- Numerous warning/error message improvements
* Add MAINTAINERS.md file

* pulseaudio: Drop pulseaudio-conf
* rpm: do not RRECOMMEND rpm-build

-----------------
Recipe Licenses
-----------------

The following corrections have been made to the LICENSE values set by recipes:

------------------------
Migration instructions
------------------------

For details on changes that you might need to make when migrating to the Yocto Project 3.4 release from previous releases, please see the following manual:

https://docs.yoctoproject.org/migration-guides/migration-3.4.html

----------------
Security Fixes
----------------

* apr: CVE-2021-35940
* aspell: CVE-2019-25051
* avahi: CVE-2021-3468, CVE-2021-36217
* binutils: CVE-2021-20197
* bluez: CVE-2021-3658
* busybox: CVE-2021-28831
* cairo: CVE-2020-35492
* cpio: CVE-2021-38185
* expat: CVE-2013-0340
* ffmpeg: CVE-2020-20446, CVE-2020-22015, CVE-2020-22021, CVE-2020-22033, CVE-2020-22019, CVE-2021-33815, CVE-2021-38171, CVE-2020-20453
* glibc: CVE-2021-33574, CVE-2021-38604
* inetutils: CVE-2021-40491
* libgcrypt: CVE-2021-40528
* linux-yocto/5.10, 5.14: CVE-2021-3653, CVE-2021-3656
* lz4: CVE-2021-3520
* nettle: CVE-2021-20305
* openssl: CVE-2021-3711, CVE-2021-3712
* perl: CVE-2021-36770
* python3: CVE-2021-29921
* python3-pip: CVE-2021-3572
* qemu: CVE-2020-27821, CVE-2020-29443, CVE-2020-35517, CVE-2021-3392, CVE-2021-3409, CVE-2021-3416, CVE-2021-3527, CVE-2021-3544, CVE-2021-3545, CVE-2021-3546, CVE-2021-3682, CVE-2021-20181, CVE-2021-20221, CVE-2021-20257, CVE-2021-20263
* rpm: CVE-2021-3421, CVE-2021-20271
* rsync: CVE-2020-14387
* util-linux: CVE-2021-37600
* vim: CVE-2021-3770, CVE-2021-3778
* wpa-supplicant: CVE-2021-30004
* xdg-utils: CVE-2020-27748
* xserver-xorg: CVE-2021-3472

-----------------
Recipe Upgrades
-----------------

* acl 2.2.53 -> 2.3.1
* acpica 20210105 -> 20210730
* alsa-lib 1.2.4 -> 1.2.5.1
* alsa-plugins 1.2.2 -> 1.2.5
* alsa-tools 1.2.2 -> 1.2.5
* alsa-topology-conf 1.2.4 -> 1.2.5.1
* alsa-ucm-conf 1.2.4 -> 1.2.5.1
* alsa-utils 1.2.4 -> 1.2.5.1
* alsa-utils-scripts 1.2.4 -> 1.2.5.1
* apt 2.2.2 -> 2.2.4
* at 3.2.1 -> 3.2.2
* at-spi2-core 2.38.0 -> 2.40.3
* autoconf-archive 2019.01.06 -> 2021.02.19
* babeltrace2 2.0.3 -> 2.0.4
* bash 5.1 -> 5.1.8
* bind 9.16.16 -> 9.16.20
* binutils 2.36.1 -> 2.37
* binutils-cross 2.36.1 -> 2.37
* binutils-cross-canadian 2.36.1 -> 2.37
* binutils-cross-testsuite 2.36.1 -> 2.37
* binutils-crosssdk 2.36.1 -> 2.37
* bison 3.7.5 -> 3.7.6
* blktrace 1.2.0+gitX -> 1.3.0+gitX
* bluez5 5.56 -> 5.61
* boost 1.75.0 -> 1.77.0
* boost-build-native 4.3.0 -> 4.4.1
* btrfs-tools 5.10.1 -> 5.13.1
* busybox 1.33.1 -> 1.34.0
* busybox-inittab 1.33.0 -> 1.34.0
* ccache 4.2 -> 4.4
* cmake 3.19.5 -> 3.21.1
* cmake-native 3.19.5 -> 3.21.1
* connman 1.39 -> 1.40
* createrepo-c 0.17.0 -> 0.17.4
* cronie 1.5.5 -> 1.5.7
* cross-localedef-native 2.33 -> 2.34
* cups 2.3.3 -> 2.3.3op2
* curl 7.75.0 -> 7.78.0
* dbus-glib 0.110 -> 0.112
* dejagnu 1.6.2 -> 1.6.3
* diffoscope 172 -> 181
* diffutils 3.7 -> 3.8
* distcc 3.3.5 -> 3.4
* dnf 4.6.0 -> 4.8.0
* dpkg 1.20.7.1 -> 1.20.9
* dtc 1.6.0 -> 1.6.1
* e2fsprogs 1.46.1 -> 1.46.4
* elfutils 0.183 -> 0.185
* ell 0.38 -> 0.43
* enchant2 2.2.15 -> 2.3.1
* epiphany 3.38.2 -> 40.3
* ethtool 5.10 -> 5.13
* expat 2.2.10 -> 2.4.1
* ffmpeg 4.3.2 -> 4.4
* file 5.39 -> 5.40
* freetype 2.10.4 -> 2.11.0
* gcc 10.2.0 -> 11.2.0
* gcc-cross 10.2.0 -> 11.2.0
* gcc-cross-canadian 10.2.0 -> 11.2.0
* gcc-crosssdk 10.2.0 -> 11.2.0
* gcc-runtime 10.2.0 -> 11.2.0
* gcc-sanitizers 10.2.0 -> 11.2.0
* gcc-source 10.2.0 -> 11.2.0
* gcr 3.38.1 -> 3.40.0
* gdb 10.1 -> 10.2
* gdb-cross 10.1 -> 10.2
* gdb-cross-canadian 10.1 -> 10.2
* gdk-pixbuf 2.40.0 -> 2.42.6
* ghostscript 9.53.3 -> 9.54.0
* git 2.31.1 -> 2.33.0
* glib-2.0 2.66.7 -> 2.68.4
* glib-networking 2.66.0 -> 2.68.2
* glibc 2.33 -> 2.34
* glibc-locale 2.33 -> 2.34
* glibc-mtrace 2.33 -> 2.34
* glibc-scripts 2.33 -> 2.34
* glibc-testsuite 2.33 -> 2.34
* glslang 11.2.0 -> 11.5.0
* gnome-desktop-testing 2018.1 -> 2021.1
* gnu-config 20210125+gitX -> 20210722+gitX
* gnu-efi 3.0.12 -> 3.0.14
* gnupg 2.2.27 -> 2.3.1
* gobject-introspection 1.66.1 -> 1.68.0
* gpgme 1.15.1 -> 1.16.0
* gptfdisk 1.0.7 -> 1.0.8
* grep 3.6 -> 3.7
* grub 2.04+2.06~rc1 -> 2.06
* grub-efi 2.04+2.06~rc1 -> 2.06
* gsettings-desktop-schemas 3.38.0 -> 40.0
* gtk+3 3.24.25 -> 3.24.30
* harfbuzz 2.7.4 -> 2.9.0
* hdparm 9.60 -> 9.62
* help2man 1.48.2 -> 1.48.4
* hwlatdetect 1.10 -> 2.1
* i2c-tools 4.2 -> 4.3
* icu 68.2 -> 69.1
* igt-gpu-tools 1.25+gitX -> 1.26
* inetutils 2.0 -> 2.1
* iproute2 5.11.0 -> 5.13.0
* iputils s20200821 -> 20210722
* json-glib 1.6.2 -> 1.6.4
* kexec-tools 2.0.21 -> 2.0.22
* kmod 28 -> 29
* kmod-native 28 -> 29
* less 563 -> 590
* libassuan 2.5.4 -> 2.5.5
* libcap 2.48 -> 2.51
* libcgroup 0.41 -> 2.0
* libcomps 0.1.15 -> 0.1.17
* libconvert-asn1-perl 0.27 -> 0.31
* libdazzle 3.38.0 -> 3.40.0
* libdnf 0.58.0 -> 0.63.1
* libdrm 2.4.104 -> 2.4.107
* libedit 20210216-3.1 -> 20210714-3.1
* libepoxy 1.5.5 -> 1.5.9
* liberation-fonts 2.00.1 -> 2.1.4
* libffi 3.3 -> 3.4.2
* libfm 1.3.1 -> 1.3.2
* libgcc 10.2.0 -> 11.2.0
* libgcc-initial 10.2.0 -> 11.2.0
* libgcrypt 1.9.3 -> 1.9.4
* libgfortran 10.2.0 -> 11.2.0
* libgit2 1.1.0 -> 1.1.1
* libglu 9.0.1 -> 9.0.2
* libgpg-error 1.41 -> 1.42
* libgudev 234 -> 237
* libhandy 1.2.0 -> 1.2.3
* libical 3.0.9 -> 3.0.10
* libidn2 2.3.0 -> 2.3.2
* libinput 1.16.4 -> 1.18.1
* libjitterentropy 3.0.1 -> 3.1.0
* libjpeg-turbo 2.0.6 -> 2.1.1
* libksba 1.5.0 -> 1.6.0
* libmodulemd 2.12.0 -> 2.13.0
* libnsl2 1.3.0 -> 2.0.0
* libnss-mdns 0.14.1 -> 0.15.1
* libogg 1.3.4 -> 1.3.5
* libpcap 1.10.0 -> 1.10.1
* libpcre 8.44 -> 8.45
* libpcre2 10.36 -> 10.37
* libportal 0.3 -> 0.4
* librepo 1.13.0 -> 1.14.1
* libsdl2 2.0.14 -> 2.0.16
* libsolv 0.7.17 -> 0.7.19
* libtasn1 4.16.0 -> 4.17.0
* libtest-needs-perl 0.002006 -> 0.002009
* libtirpc 1.3.1 -> 1.3.2
* libubootenv 0.3.1 -> 0.3.2
* libucontext 0.10+X -> 1.1+X
* liburcu 0.12.2 -> 0.13.0
* libuv 1.41.0 -> 1.42.0
* libva 2.10.0 -> 2.12.0
* libva-initial 2.10.0 -> 2.12.0
* libva-utils 2.10.0 -> 2.12.0
* libwebp 1.2.0 -> 1.2.1
* libwpe 1.8.0 -> 1.10.1
* libx11 1.7.0 -> 1.7.2
* libxcrypt 4.4.18 -> 4.4.25
* libxcrypt-compat 4.4.18 -> 4.4.25
* libxfixes 5.0.3 -> 6.0.0
* libxfont2 2.0.4 -> 2.0.5
* libxft 2.3.3 -> 2.3.4
* libxi 1.7.10 -> 1.7.99.2
* libxkbcommon 1.0.3 -> 1.3.0
* libxml2 2.9.10 -> 2.9.12
* libxres 1.2.0 -> 1.2.1
* linux-libc-headers 5.10 -> 5.14
* linux-yocto 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-dev 5.12++gitX -> 5.15++gitX
* linux-yocto-rt 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-tiny 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* llvm 11.1.0 -> 12.0.1
* log4cplus 2.0.6 -> 2.0.7
* logrotate 3.18.0 -> 3.18.1
* ltp 20210121 -> 20210524
* lttng-modules 2.12.6 -> 2.13.0
* lttng-tools 2.12.4 -> 2.13.0
* lttng-ust 2.12.1 -> 2.13.0
* m4 1.4.18 -> 1.4.19
* m4-native 1.4.18 -> 1.4.19
* man-pages 5.10 -> 5.12
* mc 4.8.26 -> 4.8.27
* mesa 21.0.3 -> 21.2.1
* mesa-gl 21.0.3 -> 21.2.1
* meson 0.57.1 -> 0.58.1
* mmc-utils 0.1+gitX (73d6c59af8d1...) -> 0.1+gitX (43282e80e174...)
* mobile-broadband-provider-info 20201225 -> 20210805
* mpg123 1.26.4 -> 1.28.2
* mtd-utils 2.1.2 -> 2.1.3
* mtools 4.0.26 -> 4.0.35
* musl 1.2.2+gitX (e5d2823631bb...) -> 1.2.2+gitX (3f701faace7a...)
* nativesdk-meson 0.57.1 -> 0.58.1
* netbase 6.2 -> 6.3
* nfs-utils 2.5.3 -> 2.5.4
* ofono 1.31 -> 1.32
* openssh 8.5p1 -> 8.7p1
* opkg 0.4.4 -> 0.4.5
* opkg-utils 0.4.3 -> 0.4.5
* ovmf edk2-stable202102 -> edk2-stable202105
* p11-kit 0.23.22 -> 0.24.0
* pango 1.48.2 -> 1.48.9
* patchelf 0.12 -> 0.13
* perl 5.32.1 -> 5.34.0
* piglit 1.0+gitrX (d4d9353b7290...) -> 1.0+gitrX (6a4be9e9946d...)
* pkgconf 1.7.3 -> 1.8.0
* powertop 2.13 -> 2.14
* pseudo 1.9.0+gitX (b988b0a6b8af...) -> 1.9.0+gitX (0cda3ba5f94a...)
* pulseaudio 14.2 -> 15.0
* puzzles 0.0+gitX (84cb4c6701e0...) -> 0.0+gitX (8f3413c31ffd...)
* python3 3.9.5 -> 3.9.6
* python3-attrs 20.3.0 -> 21.2.0
* python3-cython 0.29.22 -> 0.29.24
* python3-dbus 1.2.16 -> 1.2.18
* python3-dbusmock 0.22.0 -> 0.23.1
* python3-docutils 0.16 -> 0.17.1
* python3-git 3.1.14 -> 3.1.20
* python3-gitdb 4.0.5 -> 4.0.7
* python3-hypothesis 6.2.0 -> 6.15.0
* python3-importlib-metadata 3.4.0 -> 4.6.4
* python3-iniparse 0.4 -> 0.5
* python3-jinja2 2.11.3 -> 3.0.1
* python3-libarchive-c 2.9 -> 3.1
* python3-magic 0.4.22 -> 0.4.24
* python3-mako 1.1.4 -> 1.1.5
* python3-markupsafe 1.1.1 -> 2.0.1
* python3-more-itertools 8.7.0 -> 8.8.0
* python3-numpy 1.20.1 -> 1.21.2
* python3-packaging 20.9 -> 21.0
* python3-pathlib2 2.3.5 -> 2.3.6
* python3-pbr 5.4.4 -> 5.6.0
* python3-pip 20.0.2 -> 21.2.4
* python3-pluggy 0.13.1 -> 1.0.0
* python3-pycairo 1.20.0 -> 1.20.1
* python3-pygments 2.8.1 -> 2.10.0
* python3-pygobject 3.38.0 -> 3.40.1
* python3-pytest 6.2.2 -> 6.2.4
* python3-scons 3.1.2 -> 4.2.0
* python3-scons-native 3.1.2 -> 4.2.0
* python3-setuptools 54.1.1 -> 57.4.0
* python3-setuptools-scm 5.0.1 -> 6.0.1
* python3-six 1.15.0 -> 1.16.0
* python3-sortedcontainers 2.3.0 -> 2.4.0
* python3-testtools 2.4.0 -> 2.5.0
* python3-zipp 3.4.1 -> 3.5.0
* qemu 5.2.0 -> 6.0.0
* qemu-native 5.2.0 -> 6.0.0
* qemu-system-native 5.2.0 -> 6.0.0
* re2c 2.0.3 -> 2.2
* rng-tools 6.11 -> 6.14
* rpcbind 1.2.5 -> 1.2.6
* rt-tests 1.10 -> 2.1
* ruby 3.0.1 -> 3.0.2
* rxvt-unicode 9.22 -> 9.26
* shaderc 2020.5 -> 2021.1
* shadow 4.8.1 -> 4.9
* spirv-tools 2020.7 -> 2021.2
* sqlite3 3.35.0 -> 3.36.0
* squashfs-tools 4.4 -> 4.5
* strace 5.11 -> 5.14
* stress-ng 0.12.05 -> 0.13.00
* sudo 1.9.6p1 -> 1.9.7p2
* swig 3.0.12 -> 4.0.2
* sysklogd 2.2.2 -> 2.2.3
* systemd 247.6 -> 249.3
* systemd-boot 247.6 -> 249.3
* systemd-conf 247.6 -> 1.0
* systemtap 4.4 -> 4.5
* systemtap-native 4.4 -> 4.5
* systemtap-uprobes 4.4 -> 4.5
* tcf-agent 1.7.0+gitX (a022ef2f1acf...) -> 1.7.0+gitX (2735e3d6b7ec...)
* texinfo 6.7 -> 6.8
* tiff 4.2.0 -> 4.3.0
* u-boot 2021.01 -> 2021.07
* u-boot-tools 2021.01 -> 2021.07
* usbutils 013 -> 014
* util-linux 2.36.2 -> 2.37.2
* util-linux-libuuid 2.36.2 -> 2.37.2
* vala 0.50.4 -> 0.52.5
* valgrind 3.16.1 -> 3.17.0
* virglrenderer 0.8.2 -> 0.9.1
* vte 0.62.2 -> 0.64.2
* vulkan-headers 1.2.170.0 -> 1.2.182.0
* vulkan-loader 1.2.170.0 -> 1.2.182.0
* vulkan-samples git (55cebd9e7cc4...) -> git (d2187278cb66...)
* vulkan-tools 1.2.170.0 -> 1.2.182.0
* wayland-protocols 1.20 -> 1.21
* webkitgtk 2.30.5 -> 2.32.3
* wireless-regdb 2021.04.21 -> 2021.07.14
* wpebackend-fdo 1.8.0 -> 1.10.0
* x264 r3039+gitX (544c61f08219...) -> r3039+gitX (5db6aa6cab1b...)
* xeyes 1.1.2 -> 1.2.0
* xf86-input-libinput 0.30.0 -> 1.1.0
* xkbcomp 1.4.4 -> 1.4.5
* xkeyboard-config 2.32 -> 2.33
* xorgproto 2020.1 -> 2021.4.99.2
* xserver-xorg 1.20.10 -> 1.20.13
* zstd 1.4.9 -> 1.5.0

</pre>

3.4 Release Notes WIP

2021-10-21T02:03:39Z

PaulEggleton:

<pre>

--------------
Contributors
--------------

Thanks to the following people who contributed to this release:

Adam Romanek
Alejandro Hernandez Samaniego
Alexander Kanavin
Alexandre Belloni
Alexey Brodkin
Alex Stewart
Alistair Francis
Anatol Belski
Anders Wallin
Andrea Adami
Andreas Müller
Andrej Valek
Andres Beltran
Andrey Zhizhikin
Anibal Limon
Anthony Bagwell
Anton Blanchard
Anuj Mittal
Armin Kuster
Asfak Rahman
Bastian Krause
Bernhard Rosenkränzer
Bruce Ashfield
Carlos Rafael Giani
Chandana kalluri
Changhyeok Bae
Changqing Li
Chanho Park
Chen Qi
Chris Laplante
Christophe Chapuis
Christoph Muellner
Claudius Heine
Damian Wrobel
Daniel Ammann
Daniel Gomez
Daniel McGregor
Daniel Wagenknecht
Denys Dmytriyenko
Devendra Tewari
Diego Sueiro
Dmitry Baryshkov
Douglas Royds
Dragos-Marian Panait
Drew Moseley
Enrico Scholz
Fabio Berton
Florian Amstutz
Gavin Li
Guillaume Champagne
Harald Brinkmann
Henning Schild
He Zhe
Hongxu Jia
Hsia-Jun (Randy) Li
Jean Bouchard
Joe Slater
Jonas Höppner
Jon Mason
Jose Quaresma
Joshua Watt
Justin Bronder
Kai Kang
Kenfe-Mickael Laventure
Kevin Hao
Khairul Rohaizzat Jamaluddin
Khem Raj
Kiran Surendran
Konrad Weihmann
Kristian Klausen
Kyle Russell
Lee Chee Yang
Lei Maohui
Luca Boccassi
Marco Felsch
Marcus Comstedt
Marek Vasut
Mark Hatle
Markus Volk
Marta Rybczynska
Martin Jansa
Matthias Klein
Matthias Schiffer
Matt Madison
Matt Spencer
Max Krummenacher
Michael Halstead
Michael Ho
Michael Opdenacker
Mike Crowe
Mikko Rapeli
Ming Liu
Mingli Yu
Minjae Kim
Nicolas Dechesne
Niels Avonds
Nikolay Papenkov
Nisha Parrakat
Olaf Mandel
Oleksandr Kravchuk
Oleksandr Popovych
Oliver Kranz
Otavio Salvador
Patrick Williams
Paul Barker
Paul Eggleton
Paul Gortmaker
Paulo Cesar Zaneti
Peter Bergin
Peter Budny
Peter Kjellerstedt
Petr Vorel
Przemyslaw Gorszkowski
Purushottam Choudhary
Qiang Zhang
Quentin Schulz
Ralph Siemsen
Randy MacLeod
Ranjitsinh Rathod
Rasmus Villemoes
Reto Schneider
Richard Purdie
Richard Weinberger
Robert Joslyn
Robert P. J. Day
Robert Yang
Romain Naour
Ross Burton
Sakib Sajal
Samuli Piippo
Saul Wold
Scott Murray
Scott Weaver
Stefan Ghinea
Stefan Herbrechtsmeier
Stefano Babic
Stefan Wiehler
Steve Sakoman
Teoh Jay Shen
Thomas Perrot
Tim Orling
Tom Pollard
Tom Rini
Tony Battersby
Tony Tascioglu
Trevor Gamblin
Trevor Woerner
Ulrich Ölmann
Valentin Danaila
Vinay Kumar
Vineela Tummalapalli
Vinícius Ossanes Aquino
Vivien Didelot
Vyacheslav Yurkov
Wang Mingyu
Wes Lindauer
William A. Kennington III
Yanfei Xu
Yann Dirson
Yi Fan Yu
Yi Zhao
Zang Ruochen
Zheng Ruoqin
Zoltán Böszörményi

-----------------------------
New Features / Enhancements
-----------------------------

* Linux kernel 5.14, glibc 2.34 and ~280 other recipe upgrades
* Switched override character to ':' (replacing '_') for more robust parsing and improved performance - see migration guide for help on migrating
* Rust integrated into core, providing rust support for cross-compilation and SDK
* New recipes: cargo, core-image-ptest-all, core-image-ptest-fast, core-image-weston-sdk, erofs-utils, gcompat, gi-docgen, libmicrohttpd, libseccomp, libstd-rs, perlcross, python3-markdown, python3-pyyaml, python3-smartypants, python3-typogrify, rust, rust-cross, rust-cross-canadian, rust-hello-world, rust-llvm, rust-tools-cross-canadian, rustfmt, xwayland
* seccomp integrated into core, with additional enabling for gnutls, systemd, qemu
* New create-spdx class for creating SPDX SBoM documents
* New gi-docgen class for GNOME library documentation
* Added support for erofs filesystems
* image_types: add zsync conversions
* scripts/contrib/image-manifest: add new script
* Several optimisations to reduce unnecessary task dependencies for faster builds
* deb: apply postinstall on sdk
* Switch several recipes over to using OpenSSL instead of GnuTLS (wpa-supplicant, curl, glib-networking) or disable GnuTLS (cups) by default
* default-distrovars.inc: add debuginfod to default DISTRO_FEATURES
* Improvements to LTO plugin installation and reproducibility
* license_image.bbclass: Detect broken symlinks
* core-image-multilib-example: base on weston, and not sato
* reproducible_build.bbclass: Enable -Wdate-time
* yocto-check-layer: Only note a layer without a conf/layer.conf (versus error)
* yocto-check-layer: ensure that all layer dependencies are tested too
* npm.bbclass: Allow nodedir to be overridden by NPM_NODEDIR
* cve-extra-exclusions.inc: add exclusion list for intractable CVE's
* sysstat: make the service start automatically
* sanity: Add error check for '%' in build path
* sanity: Further improve directory sanity tests
* sanity.bbclass: mention CONNECTIVITY_CHECK_URIS in network failure message
* Architecture-specific improvements:
- glibc: Enable memory tagging for aarch64
- testimage: remove aarch64 xorg exclusion
- arch-arm*: add better support for gcc march extensions
- tune-cortexm*: add support for all Arm Cortex-M processors
- tune-cortexr*: add support for all Arm Cortex-R processors
- arch-armv4: Allow -march=armv4
- qemuarm*: use virtio graphics
- baremetal-helloworld: Enable RISC-V 64 port
- ldconfig-native: Add RISC-V support
- baremetal-helloworld: Enable RISC-V 32 port
- qemuriscv: Enable 4 core emulation
- Add ARC support in gdb, dpkg, dhcpcd
- conf/machine-sdk: Add ppc64 SDK machine
- libjpeg-turbo: Handle powerpc64le without Altivec
- pixman: Handle PowerPC without Altivec
- mesa: enable gallium intel drivers when building for x86
- mesa: enable crocus driver for older intel graphics
* Kernel-related changes:
- Support zstd-compressed modules and initramfs images
- Allow opt-out of split kernel modules
- linux-yocto-dev: base AUTOREV on specified version
- kernel-yocto: provide debug / summary information for metadata
- kernel-uboot: Handle gzip and lzo compression options
- linux-yocto/5.13: add devupstream support
- linux-yocto: add vfat KERNEL_FEATURE when MACHINE_FEATURES include vfat
- linux-yocto/5.13: enable TYPEC_TCPCI in usbc fragment
- linux-yocto/5.10: enable TYPEC_TCPCI in usbc fragment
* bitbake.conf: enable debuginfod in native/nativesdk
* gdb-cross: enable debuginfod
* sdk: Enable do_populate_sdk with multilibs
* sdk: Decouple default install path from built in path
* poky: Use SDKPATHINSTALL instead of SDKPATH
* populate_sdk_ext: Error if trying to generate an eSDK from a mulitconfig
* populate_sdk_ext: Fix handling of TOOLCHAIN_HOST_TASK in the eSDK case
* devtool upgrade: rebase override-only patches as well
* devtool: print a warning on upgrades if PREFERRED_VERSION is set
* recipetool/create_buildsys_python: treat BSD as BSD-3-Clause
* busybox: add tmpdir option into mktemp applet
* busybox: support mounting swap via labels
* busybox: Enable long options for enabled applets
* Use the label provided when formating a dos partition
* testimage.bbclass: Add dump-guest-memory cmd
* util-linux: build chfn and chsh
* buildstats.bbclass: log host data on failure to task specific file
* buildstats.bbclass: collect data in the same file.
* oe-time-dd-test.sh: add options and refactor
* pseudo: Add uninative configuration sanity check
* own-mirrors: Add support for s3:// scheme in SOURCE_MIRROR_URL
* zstd: Include pzstd in the build
* init-manager-systemd: define weak dev manager
* Add proper unpack dependency for .zst compressed archives
* systemd: set zstd as default compression option
* Image-related improvements
- New squashfs-zst and cpio.zst image types
- New lic-pkgs IMAGE_FEATURES item
- Use xargs to set file timestamps for significant (>90%) do_image speedup
- Find .ko.gz and .ko.xz kernel modules as well when determining need to run depmod on an image
- Show formatted error messages instead of tracebacks for systemctl errors
- No longer ignore installation failures in complementary package installation
- Remove ldconfig auxiliary cache when not needed
* New PACKAGECONFIG options in btrfs-tools, ccache, coreutils, cups, dbus, elfutils, ffmpeg, findutils, glib-2.0, gstreamer1.0-plugins-bad, gstreamer1.0-plugins-base, libarchive, libnotify, libpsl, man-db, mesa, ovmf, parted, prelink, qemu, rpm, shadow, systemd, tar, vim, weston
* Ptest enhancements:
- ptest-runner: install script to collect system data on failure
- Added ptest support to python3-hypothesis, python3-jinja2, python3-markupsafe;
- Enhanced ptest support in lttng, util-linux, and others
- New leaner ptest image recipes based upon core-image-minimal
* conf/machine: move tune files to architecture directories
* python3-manifest: add statistics subpackage
* qemurunner: Add support for qmp commands
* qemurunner: change warning to info
* runqemu: decouple bios and kernel options
* qemu: add a hint on how to enable CPU render nodes when a suitable GPU is absent
* qemu: use 4 cores in qemu guests
* devupstream: Allow support of native class extensions
* overlayfs.bbclass: generate overlayfs mount units
* rootfs-postcommands: add QA check for overlayfs
* pypi: Allow override of PyPI archive name
* Allow global override of golang GO_DYNLINK
* lib/oe/elf: Add Android OS to machine_dict
* meson.bbclass: Make the default buildtype "debug" if DEBUG_BUILD is 1
* vim: add option to disable NLS support
* buildhistory: Add option to strip path prefix
* buildhistory: Add output file listing package information
* buildhistory: Label packages providing per-file dependencies in depends.dot
* distro_features_check: expand with IMAGE_FEATURES
* u-boot enhancements:
- Make SPL suffix configurable
- Make UBOOT_BINARYNAME configurable
- Package extlinux.conf separately
- Allow deploying the u-boot DTB
* opensbi: Add support for specifying a device tree
* common-licenses: add missing SPDX licences
* classes/package: Add extended packaged data
* mirrors.bbclass: provide additional rule for git repo fallbacks
* poky: Use https in PREMIRRORS
* wic enhancements:
- Add --extra-space argument to leave extra space after last partition
- Add --no-fstab-update part option to allow using the stock fstab
- bootimg-efi: add Unified Kernel Image option
* cross-canadian: make android pass target sys check
* spdx.py: Add SPDXAnnotation Object (to help mark native recipes)
* local.conf.sample: Update sstate mirror entry with new hash equivalence setting
* tzdata: Allow controlling zoneinfo binary format
* bitbake improvements:
- New bitbake-getvar helper command to query a variable value (with history)
- bitbake-layers: add --fetchdir parameter to layerindex-fetch
- bitbake-layers: add skip reason to output
- build: Catch and error upon circular task references
- data_smart: Make ExpansionErrors more readable
- data_smart: Improve error display for handled exceptions
- cookerdata: Improve missing core layer error message
- cookerdata: Show error for no BBLAYERS in bblayers.conf
- cookerdata: Show a readable error for invalid multiconfig name
- build: warn on setting noexec/nostamp/fakeroot flag to any value besides '1'
- bitbake: enable python warnings at the first opportunity
- cooker: Allow upstream for local hash equivalence server
- fetch2/s3: allow to use credentials from environment variables
- fetch2/s3: allow to switch profile from environment variable
- fetch2/s3: Add progress handler for S3 cp command
- fetch2: add check for empty SRC_URI hash string
- fetch2: expose environment variable names that need to be exported
- fetch2/wget: fetch securely by default
- fetch2/wget: Enable ftps
- fetch2/svn: Allow peg-revision functionality to be disabled
- fetch2: clarify the command-no-found error message
- fetch2: npm: Support npm archives with missing search directory mode
- fetch2: npmsw: Add support for local tarball and link sources
- build: Ensure python stdout/stderr is logged correctly
- siggen: Fix sorting in diff output
- prserv: Replace XML RPC with modern asyncrpc implementation
- prserv: Add read-only mode
- Add piping compression library
* Add MAINTAINERS.md file

* pulseaudio: Drop pulseaudio-conf
* rpm: do not RRECOMMEND rpm-build

-----------------
Recipe Licenses
-----------------

The following corrections have been made to the LICENSE values set by recipes:

------------------------
Migration instructions
------------------------

For details on changes that you might need to make when migrating to the Yocto Project 3.4 release from previous releases, please see the following manual:

https://docs.yoctoproject.org/migration-guides/migration-3.4.html

----------------
Security Fixes
----------------

* apr: CVE-2021-35940
* aspell: CVE-2019-25051
* avahi: CVE-2021-3468, CVE-2021-36217
* binutils: CVE-2021-20197
* bluez: CVE-2021-3658
* busybox: CVE-2021-28831
* cairo: CVE-2020-35492
* cpio: CVE-2021-38185
* expat: CVE-2013-0340
* ffmpeg: CVE-2020-20446, CVE-2020-22015, CVE-2020-22021, CVE-2020-22033, CVE-2020-22019, CVE-2021-33815, CVE-2021-38171, CVE-2020-20453
* glibc: CVE-2021-33574, CVE-2021-38604
* inetutils: CVE-2021-40491
* libgcrypt: CVE-2021-40528
* linux-yocto/5.10, 5.14: CVE-2021-3653, CVE-2021-3656
* lz4: CVE-2021-3520
* nettle: CVE-2021-20305
* openssl: CVE-2021-3711, CVE-2021-3712
* perl: CVE-2021-36770
* python3: CVE-2021-29921
* python3-pip: CVE-2021-3572
* qemu: CVE-2020-27821, CVE-2020-29443, CVE-2020-35517, CVE-2021-3392, CVE-2021-3409, CVE-2021-3416, CVE-2021-3527, CVE-2021-3544, CVE-2021-3545, CVE-2021-3546, CVE-2021-3682, CVE-2021-20181, CVE-2021-20221, CVE-2021-20257, CVE-2021-20263
* rpm: CVE-2021-3421, CVE-2021-20271
* rsync: CVE-2020-14387
* util-linux: CVE-2021-37600
* vim: CVE-2021-3770, CVE-2021-3778
* wpa-supplicant: CVE-2021-30004
* xdg-utils: CVE-2020-27748
* xserver-xorg: CVE-2021-3472

-----------------
Recipe Upgrades
-----------------

* acl 2.2.53 -> 2.3.1
* acpica 20210105 -> 20210730
* alsa-lib 1.2.4 -> 1.2.5.1
* alsa-plugins 1.2.2 -> 1.2.5
* alsa-tools 1.2.2 -> 1.2.5
* alsa-topology-conf 1.2.4 -> 1.2.5.1
* alsa-ucm-conf 1.2.4 -> 1.2.5.1
* alsa-utils 1.2.4 -> 1.2.5.1
* alsa-utils-scripts 1.2.4 -> 1.2.5.1
* apt 2.2.2 -> 2.2.4
* at 3.2.1 -> 3.2.2
* at-spi2-core 2.38.0 -> 2.40.3
* autoconf-archive 2019.01.06 -> 2021.02.19
* babeltrace2 2.0.3 -> 2.0.4
* bash 5.1 -> 5.1.8
* bind 9.16.16 -> 9.16.20
* binutils 2.36.1 -> 2.37
* binutils-cross 2.36.1 -> 2.37
* binutils-cross-canadian 2.36.1 -> 2.37
* binutils-cross-testsuite 2.36.1 -> 2.37
* binutils-crosssdk 2.36.1 -> 2.37
* bison 3.7.5 -> 3.7.6
* blktrace 1.2.0+gitX -> 1.3.0+gitX
* bluez5 5.56 -> 5.61
* boost 1.75.0 -> 1.77.0
* boost-build-native 4.3.0 -> 4.4.1
* btrfs-tools 5.10.1 -> 5.13.1
* busybox 1.33.1 -> 1.34.0
* busybox-inittab 1.33.0 -> 1.34.0
* ccache 4.2 -> 4.4
* cmake 3.19.5 -> 3.21.1
* cmake-native 3.19.5 -> 3.21.1
* connman 1.39 -> 1.40
* createrepo-c 0.17.0 -> 0.17.4
* cronie 1.5.5 -> 1.5.7
* cross-localedef-native 2.33 -> 2.34
* cups 2.3.3 -> 2.3.3op2
* curl 7.75.0 -> 7.78.0
* dbus-glib 0.110 -> 0.112
* dejagnu 1.6.2 -> 1.6.3
* diffoscope 172 -> 181
* diffutils 3.7 -> 3.8
* distcc 3.3.5 -> 3.4
* dnf 4.6.0 -> 4.8.0
* dpkg 1.20.7.1 -> 1.20.9
* dtc 1.6.0 -> 1.6.1
* e2fsprogs 1.46.1 -> 1.46.4
* elfutils 0.183 -> 0.185
* ell 0.38 -> 0.43
* enchant2 2.2.15 -> 2.3.1
* epiphany 3.38.2 -> 40.3
* ethtool 5.10 -> 5.13
* expat 2.2.10 -> 2.4.1
* ffmpeg 4.3.2 -> 4.4
* file 5.39 -> 5.40
* freetype 2.10.4 -> 2.11.0
* gcc 10.2.0 -> 11.2.0
* gcc-cross 10.2.0 -> 11.2.0
* gcc-cross-canadian 10.2.0 -> 11.2.0
* gcc-crosssdk 10.2.0 -> 11.2.0
* gcc-runtime 10.2.0 -> 11.2.0
* gcc-sanitizers 10.2.0 -> 11.2.0
* gcc-source 10.2.0 -> 11.2.0
* gcr 3.38.1 -> 3.40.0
* gdb 10.1 -> 10.2
* gdb-cross 10.1 -> 10.2
* gdb-cross-canadian 10.1 -> 10.2
* gdk-pixbuf 2.40.0 -> 2.42.6
* ghostscript 9.53.3 -> 9.54.0
* git 2.31.1 -> 2.33.0
* glib-2.0 2.66.7 -> 2.68.4
* glib-networking 2.66.0 -> 2.68.2
* glibc 2.33 -> 2.34
* glibc-locale 2.33 -> 2.34
* glibc-mtrace 2.33 -> 2.34
* glibc-scripts 2.33 -> 2.34
* glibc-testsuite 2.33 -> 2.34
* glslang 11.2.0 -> 11.5.0
* gnome-desktop-testing 2018.1 -> 2021.1
* gnu-config 20210125+gitX -> 20210722+gitX
* gnu-efi 3.0.12 -> 3.0.14
* gnupg 2.2.27 -> 2.3.1
* gobject-introspection 1.66.1 -> 1.68.0
* gpgme 1.15.1 -> 1.16.0
* gptfdisk 1.0.7 -> 1.0.8
* grep 3.6 -> 3.7
* grub 2.04+2.06~rc1 -> 2.06
* grub-efi 2.04+2.06~rc1 -> 2.06
* gsettings-desktop-schemas 3.38.0 -> 40.0
* gtk+3 3.24.25 -> 3.24.30
* harfbuzz 2.7.4 -> 2.9.0
* hdparm 9.60 -> 9.62
* help2man 1.48.2 -> 1.48.4
* hwlatdetect 1.10 -> 2.1
* i2c-tools 4.2 -> 4.3
* icu 68.2 -> 69.1
* igt-gpu-tools 1.25+gitX -> 1.26
* inetutils 2.0 -> 2.1
* iproute2 5.11.0 -> 5.13.0
* iputils s20200821 -> 20210722
* json-glib 1.6.2 -> 1.6.4
* kexec-tools 2.0.21 -> 2.0.22
* kmod 28 -> 29
* kmod-native 28 -> 29
* less 563 -> 590
* libassuan 2.5.4 -> 2.5.5
* libcap 2.48 -> 2.51
* libcgroup 0.41 -> 2.0
* libcomps 0.1.15 -> 0.1.17
* libconvert-asn1-perl 0.27 -> 0.31
* libdazzle 3.38.0 -> 3.40.0
* libdnf 0.58.0 -> 0.63.1
* libdrm 2.4.104 -> 2.4.107
* libedit 20210216-3.1 -> 20210714-3.1
* libepoxy 1.5.5 -> 1.5.9
* liberation-fonts 2.00.1 -> 2.1.4
* libffi 3.3 -> 3.4.2
* libfm 1.3.1 -> 1.3.2
* libgcc 10.2.0 -> 11.2.0
* libgcc-initial 10.2.0 -> 11.2.0
* libgcrypt 1.9.3 -> 1.9.4
* libgfortran 10.2.0 -> 11.2.0
* libgit2 1.1.0 -> 1.1.1
* libglu 9.0.1 -> 9.0.2
* libgpg-error 1.41 -> 1.42
* libgudev 234 -> 237
* libhandy 1.2.0 -> 1.2.3
* libical 3.0.9 -> 3.0.10
* libidn2 2.3.0 -> 2.3.2
* libinput 1.16.4 -> 1.18.1
* libjitterentropy 3.0.1 -> 3.1.0
* libjpeg-turbo 2.0.6 -> 2.1.1
* libksba 1.5.0 -> 1.6.0
* libmodulemd 2.12.0 -> 2.13.0
* libnsl2 1.3.0 -> 2.0.0
* libnss-mdns 0.14.1 -> 0.15.1
* libogg 1.3.4 -> 1.3.5
* libpcap 1.10.0 -> 1.10.1
* libpcre 8.44 -> 8.45
* libpcre2 10.36 -> 10.37
* libportal 0.3 -> 0.4
* librepo 1.13.0 -> 1.14.1
* libsdl2 2.0.14 -> 2.0.16
* libsolv 0.7.17 -> 0.7.19
* libtasn1 4.16.0 -> 4.17.0
* libtest-needs-perl 0.002006 -> 0.002009
* libtirpc 1.3.1 -> 1.3.2
* libubootenv 0.3.1 -> 0.3.2
* libucontext 0.10+X -> 1.1+X
* liburcu 0.12.2 -> 0.13.0
* libuv 1.41.0 -> 1.42.0
* libva 2.10.0 -> 2.12.0
* libva-initial 2.10.0 -> 2.12.0
* libva-utils 2.10.0 -> 2.12.0
* libwebp 1.2.0 -> 1.2.1
* libwpe 1.8.0 -> 1.10.1
* libx11 1.7.0 -> 1.7.2
* libxcrypt 4.4.18 -> 4.4.25
* libxcrypt-compat 4.4.18 -> 4.4.25
* libxfixes 5.0.3 -> 6.0.0
* libxfont2 2.0.4 -> 2.0.5
* libxft 2.3.3 -> 2.3.4
* libxi 1.7.10 -> 1.7.99.2
* libxkbcommon 1.0.3 -> 1.3.0
* libxml2 2.9.10 -> 2.9.12
* libxres 1.2.0 -> 1.2.1
* linux-libc-headers 5.10 -> 5.14
* linux-yocto 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-dev 5.12++gitX -> 5.15++gitX
* linux-yocto-rt 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-tiny 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* llvm 11.1.0 -> 12.0.1
* log4cplus 2.0.6 -> 2.0.7
* logrotate 3.18.0 -> 3.18.1
* ltp 20210121 -> 20210524
* lttng-modules 2.12.6 -> 2.13.0
* lttng-tools 2.12.4 -> 2.13.0
* lttng-ust 2.12.1 -> 2.13.0
* m4 1.4.18 -> 1.4.19
* m4-native 1.4.18 -> 1.4.19
* man-pages 5.10 -> 5.12
* mc 4.8.26 -> 4.8.27
* mesa 21.0.3 -> 21.2.1
* mesa-gl 21.0.3 -> 21.2.1
* meson 0.57.1 -> 0.58.1
* mmc-utils 0.1+gitX (73d6c59af8d1...) -> 0.1+gitX (43282e80e174...)
* mobile-broadband-provider-info 20201225 -> 20210805
* mpg123 1.26.4 -> 1.28.2
* mtd-utils 2.1.2 -> 2.1.3
* mtools 4.0.26 -> 4.0.35
* musl 1.2.2+gitX (e5d2823631bb...) -> 1.2.2+gitX (3f701faace7a...)
* nativesdk-meson 0.57.1 -> 0.58.1
* netbase 6.2 -> 6.3
* nfs-utils 2.5.3 -> 2.5.4
* ofono 1.31 -> 1.32
* openssh 8.5p1 -> 8.7p1
* opkg 0.4.4 -> 0.4.5
* opkg-utils 0.4.3 -> 0.4.5
* ovmf edk2-stable202102 -> edk2-stable202105
* p11-kit 0.23.22 -> 0.24.0
* pango 1.48.2 -> 1.48.9
* patchelf 0.12 -> 0.13
* perl 5.32.1 -> 5.34.0
* piglit 1.0+gitrX (d4d9353b7290...) -> 1.0+gitrX (6a4be9e9946d...)
* pkgconf 1.7.3 -> 1.8.0
* powertop 2.13 -> 2.14
* pseudo 1.9.0+gitX (b988b0a6b8af...) -> 1.9.0+gitX (0cda3ba5f94a...)
* pulseaudio 14.2 -> 15.0
* puzzles 0.0+gitX (84cb4c6701e0...) -> 0.0+gitX (8f3413c31ffd...)
* python3 3.9.5 -> 3.9.6
* python3-attrs 20.3.0 -> 21.2.0
* python3-cython 0.29.22 -> 0.29.24
* python3-dbus 1.2.16 -> 1.2.18
* python3-dbusmock 0.22.0 -> 0.23.1
* python3-docutils 0.16 -> 0.17.1
* python3-git 3.1.14 -> 3.1.20
* python3-gitdb 4.0.5 -> 4.0.7
* python3-hypothesis 6.2.0 -> 6.15.0
* python3-importlib-metadata 3.4.0 -> 4.6.4
* python3-iniparse 0.4 -> 0.5
* python3-jinja2 2.11.3 -> 3.0.1
* python3-libarchive-c 2.9 -> 3.1
* python3-magic 0.4.22 -> 0.4.24
* python3-mako 1.1.4 -> 1.1.5
* python3-markupsafe 1.1.1 -> 2.0.1
* python3-more-itertools 8.7.0 -> 8.8.0
* python3-numpy 1.20.1 -> 1.21.2
* python3-packaging 20.9 -> 21.0
* python3-pathlib2 2.3.5 -> 2.3.6
* python3-pbr 5.4.4 -> 5.6.0
* python3-pip 20.0.2 -> 21.2.4
* python3-pluggy 0.13.1 -> 1.0.0
* python3-pycairo 1.20.0 -> 1.20.1
* python3-pygments 2.8.1 -> 2.10.0
* python3-pygobject 3.38.0 -> 3.40.1
* python3-pytest 6.2.2 -> 6.2.4
* python3-scons 3.1.2 -> 4.2.0
* python3-scons-native 3.1.2 -> 4.2.0
* python3-setuptools 54.1.1 -> 57.4.0
* python3-setuptools-scm 5.0.1 -> 6.0.1
* python3-six 1.15.0 -> 1.16.0
* python3-sortedcontainers 2.3.0 -> 2.4.0
* python3-testtools 2.4.0 -> 2.5.0
* python3-zipp 3.4.1 -> 3.5.0
* qemu 5.2.0 -> 6.0.0
* qemu-native 5.2.0 -> 6.0.0
* qemu-system-native 5.2.0 -> 6.0.0
* re2c 2.0.3 -> 2.2
* rng-tools 6.11 -> 6.14
* rpcbind 1.2.5 -> 1.2.6
* rt-tests 1.10 -> 2.1
* ruby 3.0.1 -> 3.0.2
* rxvt-unicode 9.22 -> 9.26
* shaderc 2020.5 -> 2021.1
* shadow 4.8.1 -> 4.9
* spirv-tools 2020.7 -> 2021.2
* sqlite3 3.35.0 -> 3.36.0
* squashfs-tools 4.4 -> 4.5
* strace 5.11 -> 5.14
* stress-ng 0.12.05 -> 0.13.00
* sudo 1.9.6p1 -> 1.9.7p2
* swig 3.0.12 -> 4.0.2
* sysklogd 2.2.2 -> 2.2.3
* systemd 247.6 -> 249.3
* systemd-boot 247.6 -> 249.3
* systemd-conf 247.6 -> 1.0
* systemtap 4.4 -> 4.5
* systemtap-native 4.4 -> 4.5
* systemtap-uprobes 4.4 -> 4.5
* tcf-agent 1.7.0+gitX (a022ef2f1acf...) -> 1.7.0+gitX (2735e3d6b7ec...)
* texinfo 6.7 -> 6.8
* tiff 4.2.0 -> 4.3.0
* u-boot 2021.01 -> 2021.07
* u-boot-tools 2021.01 -> 2021.07
* usbutils 013 -> 014
* util-linux 2.36.2 -> 2.37.2
* util-linux-libuuid 2.36.2 -> 2.37.2
* vala 0.50.4 -> 0.52.5
* valgrind 3.16.1 -> 3.17.0
* virglrenderer 0.8.2 -> 0.9.1
* vte 0.62.2 -> 0.64.2
* vulkan-headers 1.2.170.0 -> 1.2.182.0
* vulkan-loader 1.2.170.0 -> 1.2.182.0
* vulkan-samples git (55cebd9e7cc4...) -> git (d2187278cb66...)
* vulkan-tools 1.2.170.0 -> 1.2.182.0
* wayland-protocols 1.20 -> 1.21
* webkitgtk 2.30.5 -> 2.32.3
* wireless-regdb 2021.04.21 -> 2021.07.14
* wpebackend-fdo 1.8.0 -> 1.10.0
* x264 r3039+gitX (544c61f08219...) -> r3039+gitX (5db6aa6cab1b...)
* xeyes 1.1.2 -> 1.2.0
* xf86-input-libinput 0.30.0 -> 1.1.0
* xkbcomp 1.4.4 -> 1.4.5
* xkeyboard-config 2.32 -> 2.33
* xorgproto 2020.1 -> 2021.4.99.2
* xserver-xorg 1.20.10 -> 1.20.13
* zstd 1.4.9 -> 1.5.0

</pre>

3.4 Release Notes WIP

2021-10-21T02:03:16Z

PaulEggleton: Created page with "-------------- Contributors -------------- Thanks to the following people who contributed to this release: Adam Romanek Alejandro Hernandez Samaniego Alexander Kanavin Alexa..."

--------------
Contributors
--------------

Thanks to the following people who contributed to this release:

Adam Romanek
Alejandro Hernandez Samaniego
Alexander Kanavin
Alexandre Belloni
Alexey Brodkin
Alex Stewart
Alistair Francis
Anatol Belski
Anders Wallin
Andrea Adami
Andreas Müller
Andrej Valek
Andres Beltran
Andrey Zhizhikin
Anibal Limon
Anthony Bagwell
Anton Blanchard
Anuj Mittal
Armin Kuster
Asfak Rahman
Bastian Krause
Bernhard Rosenkränzer
Bruce Ashfield
Carlos Rafael Giani
Chandana kalluri
Changhyeok Bae
Changqing Li
Chanho Park
Chen Qi
Chris Laplante
Christophe Chapuis
Christoph Muellner
Claudius Heine
Damian Wrobel
Daniel Ammann
Daniel Gomez
Daniel McGregor
Daniel Wagenknecht
Denys Dmytriyenko
Devendra Tewari
Diego Sueiro
Dmitry Baryshkov
Douglas Royds
Dragos-Marian Panait
Drew Moseley
Enrico Scholz
Fabio Berton
Florian Amstutz
Gavin Li
Guillaume Champagne
Harald Brinkmann
Henning Schild
He Zhe
Hongxu Jia
Hsia-Jun (Randy) Li
Jean Bouchard
Joe Slater
Jonas Höppner
Jon Mason
Jose Quaresma
Joshua Watt
Justin Bronder
Kai Kang
Kenfe-Mickael Laventure
Kevin Hao
Khairul Rohaizzat Jamaluddin
Khem Raj
Kiran Surendran
Konrad Weihmann
Kristian Klausen
Kyle Russell
Lee Chee Yang
Lei Maohui
Luca Boccassi
Marco Felsch
Marcus Comstedt
Marek Vasut
Mark Hatle
Markus Volk
Marta Rybczynska
Martin Jansa
Matthias Klein
Matthias Schiffer
Matt Madison
Matt Spencer
Max Krummenacher
Michael Halstead
Michael Ho
Michael Opdenacker
Mike Crowe
Mikko Rapeli
Ming Liu
Mingli Yu
Minjae Kim
Nicolas Dechesne
Niels Avonds
Nikolay Papenkov
Nisha Parrakat
Olaf Mandel
Oleksandr Kravchuk
Oleksandr Popovych
Oliver Kranz
Otavio Salvador
Patrick Williams
Paul Barker
Paul Eggleton
Paul Gortmaker
Paulo Cesar Zaneti
Peter Bergin
Peter Budny
Peter Kjellerstedt
Petr Vorel
Przemyslaw Gorszkowski
Purushottam Choudhary
Qiang Zhang
Quentin Schulz
Ralph Siemsen
Randy MacLeod
Ranjitsinh Rathod
Rasmus Villemoes
Reto Schneider
Richard Purdie
Richard Weinberger
Robert Joslyn
Robert P. J. Day
Robert Yang
Romain Naour
Ross Burton
Sakib Sajal
Samuli Piippo
Saul Wold
Scott Murray
Scott Weaver
Stefan Ghinea
Stefan Herbrechtsmeier
Stefano Babic
Stefan Wiehler
Steve Sakoman
Teoh Jay Shen
Thomas Perrot
Tim Orling
Tom Pollard
Tom Rini
Tony Battersby
Tony Tascioglu
Trevor Gamblin
Trevor Woerner
Ulrich Ölmann
Valentin Danaila
Vinay Kumar
Vineela Tummalapalli
Vinícius Ossanes Aquino
Vivien Didelot
Vyacheslav Yurkov
Wang Mingyu
Wes Lindauer
William A. Kennington III
Yanfei Xu
Yann Dirson
Yi Fan Yu
Yi Zhao
Zang Ruochen
Zheng Ruoqin
Zoltán Böszörményi

-----------------------------
New Features / Enhancements
-----------------------------

* Linux kernel 5.14, glibc 2.34 and ~280 other recipe upgrades
* Switched override character to ':' (replacing '_') for more robust parsing and improved performance - see migration guide for help on migrating
* Rust integrated into core, providing rust support for cross-compilation and SDK
* New recipes: cargo, core-image-ptest-all, core-image-ptest-fast, core-image-weston-sdk, erofs-utils, gcompat, gi-docgen, libmicrohttpd, libseccomp, libstd-rs, perlcross, python3-markdown, python3-pyyaml, python3-smartypants, python3-typogrify, rust, rust-cross, rust-cross-canadian, rust-hello-world, rust-llvm, rust-tools-cross-canadian, rustfmt, xwayland
* seccomp integrated into core, with additional enabling for gnutls, systemd, qemu
* New create-spdx class for creating SPDX SBoM documents
* New gi-docgen class for GNOME library documentation
* Added support for erofs filesystems
* image_types: add zsync conversions
* scripts/contrib/image-manifest: add new script
* Several optimisations to reduce unnecessary task dependencies for faster builds
* deb: apply postinstall on sdk
* Switch several recipes over to using OpenSSL instead of GnuTLS (wpa-supplicant, curl, glib-networking) or disable GnuTLS (cups) by default
* default-distrovars.inc: add debuginfod to default DISTRO_FEATURES
* Improvements to LTO plugin installation and reproducibility
* license_image.bbclass: Detect broken symlinks
* core-image-multilib-example: base on weston, and not sato
* reproducible_build.bbclass: Enable -Wdate-time
* yocto-check-layer: Only note a layer without a conf/layer.conf (versus error)
* yocto-check-layer: ensure that all layer dependencies are tested too
* npm.bbclass: Allow nodedir to be overridden by NPM_NODEDIR
* cve-extra-exclusions.inc: add exclusion list for intractable CVE's
* sysstat: make the service start automatically
* sanity: Add error check for '%' in build path
* sanity: Further improve directory sanity tests
* sanity.bbclass: mention CONNECTIVITY_CHECK_URIS in network failure message
* Architecture-specific improvements:
- glibc: Enable memory tagging for aarch64
- testimage: remove aarch64 xorg exclusion
- arch-arm*: add better support for gcc march extensions
- tune-cortexm*: add support for all Arm Cortex-M processors
- tune-cortexr*: add support for all Arm Cortex-R processors
- arch-armv4: Allow -march=armv4
- qemuarm*: use virtio graphics
- baremetal-helloworld: Enable RISC-V 64 port
- ldconfig-native: Add RISC-V support
- baremetal-helloworld: Enable RISC-V 32 port
- qemuriscv: Enable 4 core emulation
- Add ARC support in gdb, dpkg, dhcpcd
- conf/machine-sdk: Add ppc64 SDK machine
- libjpeg-turbo: Handle powerpc64le without Altivec
- pixman: Handle PowerPC without Altivec
- mesa: enable gallium intel drivers when building for x86
- mesa: enable crocus driver for older intel graphics
* Kernel-related changes:
- Support zstd-compressed modules and initramfs images
- Allow opt-out of split kernel modules
- linux-yocto-dev: base AUTOREV on specified version
- kernel-yocto: provide debug / summary information for metadata
- kernel-uboot: Handle gzip and lzo compression options
- linux-yocto/5.13: add devupstream support
- linux-yocto: add vfat KERNEL_FEATURE when MACHINE_FEATURES include vfat
- linux-yocto/5.13: enable TYPEC_TCPCI in usbc fragment
- linux-yocto/5.10: enable TYPEC_TCPCI in usbc fragment
* bitbake.conf: enable debuginfod in native/nativesdk
* gdb-cross: enable debuginfod
* sdk: Enable do_populate_sdk with multilibs
* sdk: Decouple default install path from built in path
* poky: Use SDKPATHINSTALL instead of SDKPATH
* populate_sdk_ext: Error if trying to generate an eSDK from a mulitconfig
* populate_sdk_ext: Fix handling of TOOLCHAIN_HOST_TASK in the eSDK case
* devtool upgrade: rebase override-only patches as well
* devtool: print a warning on upgrades if PREFERRED_VERSION is set
* recipetool/create_buildsys_python: treat BSD as BSD-3-Clause
* busybox: add tmpdir option into mktemp applet
* busybox: support mounting swap via labels
* busybox: Enable long options for enabled applets
* Use the label provided when formating a dos partition
* testimage.bbclass: Add dump-guest-memory cmd
* util-linux: build chfn and chsh
* buildstats.bbclass: log host data on failure to task specific file
* buildstats.bbclass: collect data in the same file.
* oe-time-dd-test.sh: add options and refactor
* pseudo: Add uninative configuration sanity check
* own-mirrors: Add support for s3:// scheme in SOURCE_MIRROR_URL
* zstd: Include pzstd in the build
* init-manager-systemd: define weak dev manager
* Add proper unpack dependency for .zst compressed archives
* systemd: set zstd as default compression option
* Image-related improvements
- New squashfs-zst and cpio.zst image types
- New lic-pkgs IMAGE_FEATURES item
- Use xargs to set file timestamps for significant (>90%) do_image speedup
- Find .ko.gz and .ko.xz kernel modules as well when determining need to run depmod on an image
- Show formatted error messages instead of tracebacks for systemctl errors
- No longer ignore installation failures in complementary package installation
- Remove ldconfig auxiliary cache when not needed
* New PACKAGECONFIG options in btrfs-tools, ccache, coreutils, cups, dbus, elfutils, ffmpeg, findutils, glib-2.0, gstreamer1.0-plugins-bad, gstreamer1.0-plugins-base, libarchive, libnotify, libpsl, man-db, mesa, ovmf, parted, prelink, qemu, rpm, shadow, systemd, tar, vim, weston
* Ptest enhancements:
- ptest-runner: install script to collect system data on failure
- Added ptest support to python3-hypothesis, python3-jinja2, python3-markupsafe;
- Enhanced ptest support in lttng, util-linux, and others
- New leaner ptest image recipes based upon core-image-minimal
* conf/machine: move tune files to architecture directories
* python3-manifest: add statistics subpackage
* qemurunner: Add support for qmp commands
* qemurunner: change warning to info
* runqemu: decouple bios and kernel options
* qemu: add a hint on how to enable CPU render nodes when a suitable GPU is absent
* qemu: use 4 cores in qemu guests
* devupstream: Allow support of native class extensions
* overlayfs.bbclass: generate overlayfs mount units
* rootfs-postcommands: add QA check for overlayfs
* pypi: Allow override of PyPI archive name
* Allow global override of golang GO_DYNLINK
* lib/oe/elf: Add Android OS to machine_dict
* meson.bbclass: Make the default buildtype "debug" if DEBUG_BUILD is 1
* vim: add option to disable NLS support
* buildhistory: Add option to strip path prefix
* buildhistory: Add output file listing package information
* buildhistory: Label packages providing per-file dependencies in depends.dot
* distro_features_check: expand with IMAGE_FEATURES
* u-boot enhancements:
- Make SPL suffix configurable
- Make UBOOT_BINARYNAME configurable
- Package extlinux.conf separately
- Allow deploying the u-boot DTB
* opensbi: Add support for specifying a device tree
* common-licenses: add missing SPDX licences
* classes/package: Add extended packaged data
* mirrors.bbclass: provide additional rule for git repo fallbacks
* poky: Use https in PREMIRRORS
* wic enhancements:
- Add --extra-space argument to leave extra space after last partition
- Add --no-fstab-update part option to allow using the stock fstab
- bootimg-efi: add Unified Kernel Image option
* cross-canadian: make android pass target sys check
* spdx.py: Add SPDXAnnotation Object (to help mark native recipes)
* local.conf.sample: Update sstate mirror entry with new hash equivalence setting
* tzdata: Allow controlling zoneinfo binary format
* bitbake improvements:
- New bitbake-getvar helper command to query a variable value (with history)
- bitbake-layers: add --fetchdir parameter to layerindex-fetch
- bitbake-layers: add skip reason to output
- build: Catch and error upon circular task references
- data_smart: Make ExpansionErrors more readable
- data_smart: Improve error display for handled exceptions
- cookerdata: Improve missing core layer error message
- cookerdata: Show error for no BBLAYERS in bblayers.conf
- cookerdata: Show a readable error for invalid multiconfig name
- build: warn on setting noexec/nostamp/fakeroot flag to any value besides '1'
- bitbake: enable python warnings at the first opportunity
- cooker: Allow upstream for local hash equivalence server
- fetch2/s3: allow to use credentials from environment variables
- fetch2/s3: allow to switch profile from environment variable
- fetch2/s3: Add progress handler for S3 cp command
- fetch2: add check for empty SRC_URI hash string
- fetch2: expose environment variable names that need to be exported
- fetch2/wget: fetch securely by default
- fetch2/wget: Enable ftps
- fetch2/svn: Allow peg-revision functionality to be disabled
- fetch2: clarify the command-no-found error message
- fetch2: npm: Support npm archives with missing search directory mode
- fetch2: npmsw: Add support for local tarball and link sources
- build: Ensure python stdout/stderr is logged correctly
- siggen: Fix sorting in diff output
- prserv: Replace XML RPC with modern asyncrpc implementation
- prserv: Add read-only mode
- Add piping compression library
* Add MAINTAINERS.md file

* pulseaudio: Drop pulseaudio-conf
* rpm: do not RRECOMMEND rpm-build

-----------------
Recipe Licenses
-----------------

The following corrections have been made to the LICENSE values set by recipes:

------------------------
Migration instructions
------------------------

For details on changes that you might need to make when migrating to the Yocto Project 3.4 release from previous releases, please see the following manual:

https://docs.yoctoproject.org/migration-guides/migration-3.4.html

----------------
Security Fixes
----------------

* apr: CVE-2021-35940
* aspell: CVE-2019-25051
* avahi: CVE-2021-3468, CVE-2021-36217
* binutils: CVE-2021-20197
* bluez: CVE-2021-3658
* busybox: CVE-2021-28831
* cairo: CVE-2020-35492
* cpio: CVE-2021-38185
* expat: CVE-2013-0340
* ffmpeg: CVE-2020-20446, CVE-2020-22015, CVE-2020-22021, CVE-2020-22033, CVE-2020-22019, CVE-2021-33815, CVE-2021-38171, CVE-2020-20453
* glibc: CVE-2021-33574, CVE-2021-38604
* inetutils: CVE-2021-40491
* libgcrypt: CVE-2021-40528
* linux-yocto/5.10, 5.14: CVE-2021-3653, CVE-2021-3656
* lz4: CVE-2021-3520
* nettle: CVE-2021-20305
* openssl: CVE-2021-3711, CVE-2021-3712
* perl: CVE-2021-36770
* python3: CVE-2021-29921
* python3-pip: CVE-2021-3572
* qemu: CVE-2020-27821, CVE-2020-29443, CVE-2020-35517, CVE-2021-3392, CVE-2021-3409, CVE-2021-3416, CVE-2021-3527, CVE-2021-3544, CVE-2021-3545, CVE-2021-3546, CVE-2021-3682, CVE-2021-20181, CVE-2021-20221, CVE-2021-20257, CVE-2021-20263
* rpm: CVE-2021-3421, CVE-2021-20271
* rsync: CVE-2020-14387
* util-linux: CVE-2021-37600
* vim: CVE-2021-3770, CVE-2021-3778
* wpa-supplicant: CVE-2021-30004
* xdg-utils: CVE-2020-27748
* xserver-xorg: CVE-2021-3472

-----------------
Recipe Upgrades
-----------------

* acl 2.2.53 -> 2.3.1
* acpica 20210105 -> 20210730
* alsa-lib 1.2.4 -> 1.2.5.1
* alsa-plugins 1.2.2 -> 1.2.5
* alsa-tools 1.2.2 -> 1.2.5
* alsa-topology-conf 1.2.4 -> 1.2.5.1
* alsa-ucm-conf 1.2.4 -> 1.2.5.1
* alsa-utils 1.2.4 -> 1.2.5.1
* alsa-utils-scripts 1.2.4 -> 1.2.5.1
* apt 2.2.2 -> 2.2.4
* at 3.2.1 -> 3.2.2
* at-spi2-core 2.38.0 -> 2.40.3
* autoconf-archive 2019.01.06 -> 2021.02.19
* babeltrace2 2.0.3 -> 2.0.4
* bash 5.1 -> 5.1.8
* bind 9.16.16 -> 9.16.20
* binutils 2.36.1 -> 2.37
* binutils-cross 2.36.1 -> 2.37
* binutils-cross-canadian 2.36.1 -> 2.37
* binutils-cross-testsuite 2.36.1 -> 2.37
* binutils-crosssdk 2.36.1 -> 2.37
* bison 3.7.5 -> 3.7.6
* blktrace 1.2.0+gitX -> 1.3.0+gitX
* bluez5 5.56 -> 5.61
* boost 1.75.0 -> 1.77.0
* boost-build-native 4.3.0 -> 4.4.1
* btrfs-tools 5.10.1 -> 5.13.1
* busybox 1.33.1 -> 1.34.0
* busybox-inittab 1.33.0 -> 1.34.0
* ccache 4.2 -> 4.4
* cmake 3.19.5 -> 3.21.1
* cmake-native 3.19.5 -> 3.21.1
* connman 1.39 -> 1.40
* createrepo-c 0.17.0 -> 0.17.4
* cronie 1.5.5 -> 1.5.7
* cross-localedef-native 2.33 -> 2.34
* cups 2.3.3 -> 2.3.3op2
* curl 7.75.0 -> 7.78.0
* dbus-glib 0.110 -> 0.112
* dejagnu 1.6.2 -> 1.6.3
* diffoscope 172 -> 181
* diffutils 3.7 -> 3.8
* distcc 3.3.5 -> 3.4
* dnf 4.6.0 -> 4.8.0
* dpkg 1.20.7.1 -> 1.20.9
* dtc 1.6.0 -> 1.6.1
* e2fsprogs 1.46.1 -> 1.46.4
* elfutils 0.183 -> 0.185
* ell 0.38 -> 0.43
* enchant2 2.2.15 -> 2.3.1
* epiphany 3.38.2 -> 40.3
* ethtool 5.10 -> 5.13
* expat 2.2.10 -> 2.4.1
* ffmpeg 4.3.2 -> 4.4
* file 5.39 -> 5.40
* freetype 2.10.4 -> 2.11.0
* gcc 10.2.0 -> 11.2.0
* gcc-cross 10.2.0 -> 11.2.0
* gcc-cross-canadian 10.2.0 -> 11.2.0
* gcc-crosssdk 10.2.0 -> 11.2.0
* gcc-runtime 10.2.0 -> 11.2.0
* gcc-sanitizers 10.2.0 -> 11.2.0
* gcc-source 10.2.0 -> 11.2.0
* gcr 3.38.1 -> 3.40.0
* gdb 10.1 -> 10.2
* gdb-cross 10.1 -> 10.2
* gdb-cross-canadian 10.1 -> 10.2
* gdk-pixbuf 2.40.0 -> 2.42.6
* ghostscript 9.53.3 -> 9.54.0
* git 2.31.1 -> 2.33.0
* glib-2.0 2.66.7 -> 2.68.4
* glib-networking 2.66.0 -> 2.68.2
* glibc 2.33 -> 2.34
* glibc-locale 2.33 -> 2.34
* glibc-mtrace 2.33 -> 2.34
* glibc-scripts 2.33 -> 2.34
* glibc-testsuite 2.33 -> 2.34
* glslang 11.2.0 -> 11.5.0
* gnome-desktop-testing 2018.1 -> 2021.1
* gnu-config 20210125+gitX -> 20210722+gitX
* gnu-efi 3.0.12 -> 3.0.14
* gnupg 2.2.27 -> 2.3.1
* gobject-introspection 1.66.1 -> 1.68.0
* gpgme 1.15.1 -> 1.16.0
* gptfdisk 1.0.7 -> 1.0.8
* grep 3.6 -> 3.7
* grub 2.04+2.06~rc1 -> 2.06
* grub-efi 2.04+2.06~rc1 -> 2.06
* gsettings-desktop-schemas 3.38.0 -> 40.0
* gtk+3 3.24.25 -> 3.24.30
* harfbuzz 2.7.4 -> 2.9.0
* hdparm 9.60 -> 9.62
* help2man 1.48.2 -> 1.48.4
* hwlatdetect 1.10 -> 2.1
* i2c-tools 4.2 -> 4.3
* icu 68.2 -> 69.1
* igt-gpu-tools 1.25+gitX -> 1.26
* inetutils 2.0 -> 2.1
* iproute2 5.11.0 -> 5.13.0
* iputils s20200821 -> 20210722
* json-glib 1.6.2 -> 1.6.4
* kexec-tools 2.0.21 -> 2.0.22
* kmod 28 -> 29
* kmod-native 28 -> 29
* less 563 -> 590
* libassuan 2.5.4 -> 2.5.5
* libcap 2.48 -> 2.51
* libcgroup 0.41 -> 2.0
* libcomps 0.1.15 -> 0.1.17
* libconvert-asn1-perl 0.27 -> 0.31
* libdazzle 3.38.0 -> 3.40.0
* libdnf 0.58.0 -> 0.63.1
* libdrm 2.4.104 -> 2.4.107
* libedit 20210216-3.1 -> 20210714-3.1
* libepoxy 1.5.5 -> 1.5.9
* liberation-fonts 2.00.1 -> 2.1.4
* libffi 3.3 -> 3.4.2
* libfm 1.3.1 -> 1.3.2
* libgcc 10.2.0 -> 11.2.0
* libgcc-initial 10.2.0 -> 11.2.0
* libgcrypt 1.9.3 -> 1.9.4
* libgfortran 10.2.0 -> 11.2.0
* libgit2 1.1.0 -> 1.1.1
* libglu 9.0.1 -> 9.0.2
* libgpg-error 1.41 -> 1.42
* libgudev 234 -> 237
* libhandy 1.2.0 -> 1.2.3
* libical 3.0.9 -> 3.0.10
* libidn2 2.3.0 -> 2.3.2
* libinput 1.16.4 -> 1.18.1
* libjitterentropy 3.0.1 -> 3.1.0
* libjpeg-turbo 2.0.6 -> 2.1.1
* libksba 1.5.0 -> 1.6.0
* libmodulemd 2.12.0 -> 2.13.0
* libnsl2 1.3.0 -> 2.0.0
* libnss-mdns 0.14.1 -> 0.15.1
* libogg 1.3.4 -> 1.3.5
* libpcap 1.10.0 -> 1.10.1
* libpcre 8.44 -> 8.45
* libpcre2 10.36 -> 10.37
* libportal 0.3 -> 0.4
* librepo 1.13.0 -> 1.14.1
* libsdl2 2.0.14 -> 2.0.16
* libsolv 0.7.17 -> 0.7.19
* libtasn1 4.16.0 -> 4.17.0
* libtest-needs-perl 0.002006 -> 0.002009
* libtirpc 1.3.1 -> 1.3.2
* libubootenv 0.3.1 -> 0.3.2
* libucontext 0.10+X -> 1.1+X
* liburcu 0.12.2 -> 0.13.0
* libuv 1.41.0 -> 1.42.0
* libva 2.10.0 -> 2.12.0
* libva-initial 2.10.0 -> 2.12.0
* libva-utils 2.10.0 -> 2.12.0
* libwebp 1.2.0 -> 1.2.1
* libwpe 1.8.0 -> 1.10.1
* libx11 1.7.0 -> 1.7.2
* libxcrypt 4.4.18 -> 4.4.25
* libxcrypt-compat 4.4.18 -> 4.4.25
* libxfixes 5.0.3 -> 6.0.0
* libxfont2 2.0.4 -> 2.0.5
* libxft 2.3.3 -> 2.3.4
* libxi 1.7.10 -> 1.7.99.2
* libxkbcommon 1.0.3 -> 1.3.0
* libxml2 2.9.10 -> 2.9.12
* libxres 1.2.0 -> 1.2.1
* linux-libc-headers 5.10 -> 5.14
* linux-yocto 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-dev 5.12++gitX -> 5.15++gitX
* linux-yocto-rt 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* linux-yocto-tiny 5.4.144+gitX, 5.10.63+gitX -> 5.10.70+gitX, 5.14.9+gitX
* llvm 11.1.0 -> 12.0.1
* log4cplus 2.0.6 -> 2.0.7
* logrotate 3.18.0 -> 3.18.1
* ltp 20210121 -> 20210524
* lttng-modules 2.12.6 -> 2.13.0
* lttng-tools 2.12.4 -> 2.13.0
* lttng-ust 2.12.1 -> 2.13.0
* m4 1.4.18 -> 1.4.19
* m4-native 1.4.18 -> 1.4.19
* man-pages 5.10 -> 5.12
* mc 4.8.26 -> 4.8.27
* mesa 21.0.3 -> 21.2.1
* mesa-gl 21.0.3 -> 21.2.1
* meson 0.57.1 -> 0.58.1
* mmc-utils 0.1+gitX (73d6c59af8d1...) -> 0.1+gitX (43282e80e174...)
* mobile-broadband-provider-info 20201225 -> 20210805
* mpg123 1.26.4 -> 1.28.2
* mtd-utils 2.1.2 -> 2.1.3
* mtools 4.0.26 -> 4.0.35
* musl 1.2.2+gitX (e5d2823631bb...) -> 1.2.2+gitX (3f701faace7a...)
* nativesdk-meson 0.57.1 -> 0.58.1
* netbase 6.2 -> 6.3
* nfs-utils 2.5.3 -> 2.5.4
* ofono 1.31 -> 1.32
* openssh 8.5p1 -> 8.7p1
* opkg 0.4.4 -> 0.4.5
* opkg-utils 0.4.3 -> 0.4.5
* ovmf edk2-stable202102 -> edk2-stable202105
* p11-kit 0.23.22 -> 0.24.0
* pango 1.48.2 -> 1.48.9
* patchelf 0.12 -> 0.13
* perl 5.32.1 -> 5.34.0
* piglit 1.0+gitrX (d4d9353b7290...) -> 1.0+gitrX (6a4be9e9946d...)
* pkgconf 1.7.3 -> 1.8.0
* powertop 2.13 -> 2.14
* pseudo 1.9.0+gitX (b988b0a6b8af...) -> 1.9.0+gitX (0cda3ba5f94a...)
* pulseaudio 14.2 -> 15.0
* puzzles 0.0+gitX (84cb4c6701e0...) -> 0.0+gitX (8f3413c31ffd...)
* python3 3.9.5 -> 3.9.6
* python3-attrs 20.3.0 -> 21.2.0
* python3-cython 0.29.22 -> 0.29.24
* python3-dbus 1.2.16 -> 1.2.18
* python3-dbusmock 0.22.0 -> 0.23.1
* python3-docutils 0.16 -> 0.17.1
* python3-git 3.1.14 -> 3.1.20
* python3-gitdb 4.0.5 -> 4.0.7
* python3-hypothesis 6.2.0 -> 6.15.0
* python3-importlib-metadata 3.4.0 -> 4.6.4
* python3-iniparse 0.4 -> 0.5
* python3-jinja2 2.11.3 -> 3.0.1
* python3-libarchive-c 2.9 -> 3.1
* python3-magic 0.4.22 -> 0.4.24
* python3-mako 1.1.4 -> 1.1.5
* python3-markupsafe 1.1.1 -> 2.0.1
* python3-more-itertools 8.7.0 -> 8.8.0
* python3-numpy 1.20.1 -> 1.21.2
* python3-packaging 20.9 -> 21.0
* python3-pathlib2 2.3.5 -> 2.3.6
* python3-pbr 5.4.4 -> 5.6.0
* python3-pip 20.0.2 -> 21.2.4
* python3-pluggy 0.13.1 -> 1.0.0
* python3-pycairo 1.20.0 -> 1.20.1
* python3-pygments 2.8.1 -> 2.10.0
* python3-pygobject 3.38.0 -> 3.40.1
* python3-pytest 6.2.2 -> 6.2.4
* python3-scons 3.1.2 -> 4.2.0
* python3-scons-native 3.1.2 -> 4.2.0
* python3-setuptools 54.1.1 -> 57.4.0
* python3-setuptools-scm 5.0.1 -> 6.0.1
* python3-six 1.15.0 -> 1.16.0
* python3-sortedcontainers 2.3.0 -> 2.4.0
* python3-testtools 2.4.0 -> 2.5.0
* python3-zipp 3.4.1 -> 3.5.0
* qemu 5.2.0 -> 6.0.0
* qemu-native 5.2.0 -> 6.0.0
* qemu-system-native 5.2.0 -> 6.0.0
* re2c 2.0.3 -> 2.2
* rng-tools 6.11 -> 6.14
* rpcbind 1.2.5 -> 1.2.6
* rt-tests 1.10 -> 2.1
* ruby 3.0.1 -> 3.0.2
* rxvt-unicode 9.22 -> 9.26
* shaderc 2020.5 -> 2021.1
* shadow 4.8.1 -> 4.9
* spirv-tools 2020.7 -> 2021.2
* sqlite3 3.35.0 -> 3.36.0
* squashfs-tools 4.4 -> 4.5
* strace 5.11 -> 5.14
* stress-ng 0.12.05 -> 0.13.00
* sudo 1.9.6p1 -> 1.9.7p2
* swig 3.0.12 -> 4.0.2
* sysklogd 2.2.2 -> 2.2.3
* systemd 247.6 -> 249.3
* systemd-boot 247.6 -> 249.3
* systemd-conf 247.6 -> 1.0
* systemtap 4.4 -> 4.5
* systemtap-native 4.4 -> 4.5
* systemtap-uprobes 4.4 -> 4.5
* tcf-agent 1.7.0+gitX (a022ef2f1acf...) -> 1.7.0+gitX (2735e3d6b7ec...)
* texinfo 6.7 -> 6.8
* tiff 4.2.0 -> 4.3.0
* u-boot 2021.01 -> 2021.07
* u-boot-tools 2021.01 -> 2021.07
* usbutils 013 -> 014
* util-linux 2.36.2 -> 2.37.2
* util-linux-libuuid 2.36.2 -> 2.37.2
* vala 0.50.4 -> 0.52.5
* valgrind 3.16.1 -> 3.17.0
* virglrenderer 0.8.2 -> 0.9.1
* vte 0.62.2 -> 0.64.2
* vulkan-headers 1.2.170.0 -> 1.2.182.0
* vulkan-loader 1.2.170.0 -> 1.2.182.0
* vulkan-samples git (55cebd9e7cc4...) -> git (d2187278cb66...)
* vulkan-tools 1.2.170.0 -> 1.2.182.0
* wayland-protocols 1.20 -> 1.21
* webkitgtk 2.30.5 -> 2.32.3
* wireless-regdb 2021.04.21 -> 2021.07.14
* wpebackend-fdo 1.8.0 -> 1.10.0
* x264 r3039+gitX (544c61f08219...) -> r3039+gitX (5db6aa6cab1b...)
* xeyes 1.1.2 -> 1.2.0
* xf86-input-libinput 0.30.0 -> 1.1.0
* xkbcomp 1.4.4 -> 1.4.5
* xkeyboard-config 2.32 -> 2.33
* xorgproto 2020.1 -> 2021.4.99.2
* xserver-xorg 1.20.10 -> 1.20.13
* zstd 1.4.9 -> 1.5.0

Releases

2021-05-04T22:54:26Z

PaulEggleton: Fix 3.3 release notes link

== Release Activity==

{| class="wikitable" border="2"
!Codename
!Yocto Project Version
!Release Date
!Current Version
!Support Level
!Poky Version
!BitBake branch
! Maintainer
|-
|Kirkstone
|3.5
| April 2022
|
|Future
|27.0
|
|Richard Purdie <richard.purdie@linuxfoundation.org>
|-
|Honister
|3.4
|October 2021
|
|Planning
|26.0
|
|Richard Purdie <richard.purdie@linuxfoundation.org>
|-
|Hardknott
|3.3
|April 2021
|3.3.0 (April 2021)
|Stable
|25.0
|1.50
|Anuj Mittal <anuj.mittal@intel.com>
|-
|Gatesgarth
|3.2
|Oct 2020
|3.2.3 (April 2021)
|Stable
|24.0
|1.48
|Anuj Mittal <anuj.mittal@intel.com>
|-
|Dunfell
|3.1
|April 2020
|3.1.7 (April 2021)
|Long Term Support
|23.0
|1.46
|Steve Sakoman <steve@sakoman.com>
|-style="color: slategray;"
|Zeus
|3.0
|October 2019
|3.0.4 (August 2020)
|EOL
|22.0.3
|1.44
| Anuj/Armin
|-style="color: slategray;"
|Warrior
|2.7
|April 2019
|2.7.4 (June 2020)
|EOL
|21.0
|1.42
|Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Thud
|2.6
|Nov 2018
|2.6.4 (October 2019)
|EOL
|20.0
|1.40
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Sumo
|2.5
|April 2018
|2.5.3 (April 2019)
|EOL
|19.0
|1.38
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Rocko
|2.4
|Oct 2017
|2.4.4 (November 2018)
|EOL
|18.0
|1.36
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Pyro
|2.3
|May 2017
|2.3.4 (July 2018)
|EOL
|17.0
|1.34
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Morty
|2.2
|Nov 2016
|2.2.4 (July 2018)
|EOL
|16.0
|1.32
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Krogoth
|2.1
|Apr 2016
|2.1.3 (July 2017)
|EOL
|15.0
|1.30
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Jethro
|2.0
|Nov 2015
|2.0.3 (January 2016)
|EOL
|14.0
|1.28
|Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Fido
|1.8
|Apr 2015
|1.8.2
|EOL
|13.0
|1.26
|Joshua Lock <joshua.g.lock@intel.com>
|-style="color: slategray;"
|Dizzy
|1.7
|Oct 2014
|1.7.3
|EOL
|12.0
|1.24
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Daisy
|1.6
|Apr 2014
|1.6.3
|EOL
|11.0
|1.22
| Saul Wold <sgw@linux.intel.com>
|-style="color: slategray;"
|Dora
|1.5
|Oct 2013
|1.5.4
|EOL
|10.0
|1.20
| Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Dylan
|1.4
|Apr 2013
|1.4.3[https://lists.yoctoproject.org/pipermail/yocto/2014-July/020699.html *]
|EOL
|9.0
|1.18
| Paul Eggleton <paul.eggleton@linux.intel.com>
|-style="color: slategray;"
|Danny
|1.3
|Oct 2012
|1.3.2
|EOL
|8.0
|1.16
|Ross Burton <ross.burton@intel.com>
|-style="color: slategray;"
|Denzil
|1.2
|Apr 2012
|1.2.2
|EOL
|7.0
|1.15
|-style="color: slategray;"
|Edison
|1.1
|Oct 2011
|1.1.2
|EOL
|6.0
|1.13
|-style="color: slategray;"
|Bernard
|1.0
|Apr 2011
|1.0.2
|EOL
|5.0
|1.11
|-style="color: slategray;"
|Laverne
|0.9
|Oct 2010
|
|
|4.0
|1.11
|-style="color: slategray;"
|Green
|N/A
|11 June 2010
|
|
|3.3
|
|-style="color: slategray;"
|Purple
|N/A
|15 Dec 2009
|
|
|3.2
|
|-style="color: slategray;"
|Pinky
|N/A
|12 Nov 2009
|
|
|3.1
|
|-style="color: slategray;"
|Blinky
|N/A
|1 Aug 2007
|
|
|3.0
|
|-style="color: slategray;"
|Clyde
|N/A
|19 Jan 2007
|
|
|2.0
|
|-style="color: slategray;"
|Inky
|N/A
|10 Feb 2006
|
|
|1.0
|
|}

'''Note:''' see also [[Stable branch maintenance]], [[Linux Yocto]], [[Planning]] and [[Release Feature Table]] pages.

== Releases Links==
{| class="wikitable" border="2"
| align="center" style="background:#f0f0f0;"|'''Yocto Project Release'''
| align="center" style="background:#f0f0f0;"|'''Code Name'''
| align="center" style="background:#f0f0f0;"|'''Poky version'''
| align="center" style="background:#f0f0f0;"|'''Maintainer'''
| align="center" style="background:#f0f0f0;"|'''Features'''
| align="center" style="background:#f0f0f0;"|'''Schedule'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''QA Test Plan'''
| align="center" style="background:#f0f0f0;"|'''QA Test Report'''
| align="center" style="background:#f0f0f0;"|'''Release notes'''

|-valign="top"
| Yocto Project 3.3
| Hardknott
| 25.0
| Anuj Mittal
| [[Yocto_3.3_Features]]
| [[Yocto_3.3_Schedule]]
| [[Yocto_Project_v3.3_Status]]
| [[Yocto_Project_3.3_Release_Test_Plan | Yocto_3.3_Overall_Test_Plan]]
| [[Yocto_Project_3.3_Release_Test_Plan#Execution_History | 3.3 qa run history]]
| [https://lists.yoctoproject.org/g/yocto-announce/message/215 3.3 release notes]
|-
| Yocto Project 3.2
| Gatesgarth
| 24.0
| Anuj Mittal
| [[Yocto_3.2_Features]]
| [[Yocto_3.2_Schedule]]
| [[Yocto_Project_v3.2_Status]]
| [[Yocto_Project_3.2_Release_Test_Plan | Yocto_3.2_Overall_Test_Plan]]
| [[Yocto_Project_3.2_Release_Test_Plan#Execution_History | 3.2 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/51262 3.2 release notes]
|-
|-valign="top"
| Yocto Project 3.1
| Dunfell
| 23.0
| Steve Sakoman
| [[Yocto_3.1_Features]]
| [[Yocto_3.1_Schedule]]
| [[Yocto_Project_v3.1_Status]]
| [[Yocto_Project_3.1_Release_Test_Plan | Yocto_3.1_Overall_Test_Plan]]
| [[Yocto_Project_3.1_Release_Test_Plan#Execution_History | 3.1 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/49201 3.1 release notes]
|-

|-valign="top"
| Yocto Project 3.0
| Zeus
| 22.0
| Armin Kuster/Anuj Mittal
| [[Yocto_2.8_Features]]
| [[Yocto_2.8_Schedule]]
| [[Yocto_Project_v2.8_Status]]
| [[Yocto_Project_2.8_Release_Test_Plan | Yocto_2.8_Overall_Test_Plan]]
| [[Yocto_Project_2.8_Release_Test_Plan#Execution_History | 2.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-October/047111.html 3.0 release notes]
|-
|-valign="top"
| Yocto Project 2.7
| Warrior
| 21.0
| Community
| [[Yocto_2.7_Features]]
| [[Yocto_2.7_Schedule]]
| [[Yocto_Project_v2.7_Status]]
| [[Yocto_Project_2.7_Release_Test_Plan | Yocto_2.7_Overall_Test_Plan]]
| [[Yocto_Project_2.7_Release_Test_Plan#Execution_History | 2.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-May/045028.html 2.7 release notes]
|-
|-valign="top"
| Yocto Project 2.6
| Thud
| 20.0
| Community
| [[Yocto_2.6_Features]]
| [[Yocto_2.6_Schedule]]
| [[Yocto_Project_v2.6_Status]]
| [[Yocto_Project_2.6_Release_Test_Plan | Yocto_2.6_Overall_Test_Plan]]
| [[Yocto_Project_2.6_Release_Test_Plan#Execution_History | 2.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-November/000147.html 2.6 release notes]
|-
|-valign="top"
| Yocto Project 2.5
| Sumo
| 19.0
| Community
| [[Yocto_2.5_Features]]
| [[Yocto_2.5_Schedule]]
| [[Yocto_Project_v2.5_Status]]
| [[Yocto_Project_2.5_Release_Test_Plan | Yocto_2.5_Overall_Test_Plan]]
| [[Yocto_Project_2.5_Release_Test_Plan#Execution_History | 2.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-May/000136.html 2.5 release notes]
|-
|-valign="top"
| Yocto Project 2.4
| Rocko
| 18.0
| Community
| [[Yocto_2.4_Features]]
| [[Yocto_2.4_Schedule]]
| [[Yocto_Project_v2.4_Status]]
| [[Yocto_Project_2.4_Release_Test_Plan | Yocto_2.4_Overall_Test_Plan]]
| [[Yocto_Project_2.4_Release_Test_Plan#Execution_History | 2.4 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-October/000125.html 2.4 release notes]
|-
|-valign="top"
| Yocto Project 2.3
| Pyro
| 17.0
| Community
| [[Yocto_2.3_Features]]
| [[Yocto_2.3_Schedule]]
| [[Yocto_Project_v2.3_Status]]
| [[Yocto_Project_2.3_Release_Test_Plan | Yocto_2.3_Overall_Test_Plan]]
| [[Yocto_Project_2.3_Release_Test_Plan#Execution_History | 2.3 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-May/000112.html 2.3 release notes]
|-
|-valign="top"
| Yocto Project 2.2
| Morty
| 16.0
| Community
| [[Yocto_2.2_Features]]
| [[Yocto_2.2_Schedule]]
| [[Yocto_Project_v2.2_Status]]
| [[Yocto_2.2_Overall_Test_Plan]]
| [[Yocto_Project_2.2_Release_Test_Plan#Execution_History | 2.2 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-November/000101.html 2.2 release notes]
|-
|-valign="top"
| Yocto Project 2.1
| Krogoth
| 15.0
| Community
| [[Yocto_2.1_Features]]
| [[Yocto_2.1_Schedule]]
| [[Yocto_Project_v2.1_Status]]
| [[Yocto_2.1_Overall_Test_Plan]]
| [[2.1 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-May/000089.html 2.1 release notes]
|-
|-valign="top"
| Yocto Project 2.0
| Jethro
| 14.0
| Community
| [[Yocto_1.9_Features]]
| [[Yocto_1.9_Schedule]]
| [[Yocto_Project_v1.9_Status]]
|
| [[1.9 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-November/000076.html 2.0 release notes]
|-valign="top"
| Yocto Project 1.8
| Fido
| 13.0
| Community
| [[Yocto_1.8_Features]]
| [[Yocto_1.8_Schedule]]
| [[Yocto_Project_v1.8_Status]]
| [[Yocto_1.8_Overall_Test_Plan]]
| [[1.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-April/000062.html 1.8 release notes]
|-
| Yocto Project 1.7
| Dizzy
| 12.0
| Community
| [[Yocto_1.7_Features]]
| [[Yocto_1.7_Schedule]]
| [[Yocto_Project_v1.7_Status]]
| [[Yocto_1.7_Overall_Test_Plan]]
| [[1.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-October/000053.html 1.7 release notes]
|-
| Yocto Project 1.6
| Daisy
| 11.0
| Community
| [[Yocto_1.6_Features]]
| [[Yocto_1.6_Schedule]]
| [[Yocto_Project_v1.6_Status]]
| [[Yocto_1.6_Overall_Test_Plan]]
| [[1.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-April/000045.html 1.6 release notes]
|-
| Yocto Project 1.5
| Dora
| 10.0
| Community
| [[Yocto_1.5_Features]]
| [[Yocto_1.5_Schedule]]
| [[Yocto_Project_v1.5_Status]]
| [[Yocto_1.5_Overall_Test_Plan]]
| [[1.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-October/000037.html 1.5 release notes]
|-
| Yocto Project 1.4
| Dylan
| 9.0
| Community
| [[Yocto_1.4_Features]]
| [[Yocto_1.4_Schedule]]
| [[Yocto_Project_v1.4_Status]]
| [[Yocto_1.4_Overall_Test_Plan]]
| [[Yocto_1.4_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-April/000027.html 1.4 release notes]
|-
| Yocto Project 1.3
| Danny
| 8.0
| Community
| [[Yocto_1.3_Features]]
| [[Yocto_1.3_Schedule]]
| [[Yocto_Project_v1.3_Status]]
| [[Yocto_1.3_Overall_Test_Plan]]
| [[Yocto_1.3_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-October/000020.html 1.3 release notes]
|-
| Yocto Project 1.2
| Denzil
| 7.0
| Community
| [[Yocto_1.2_Features]]
| [[Yocto_1.2_Schedule]]
| [[Yocto_Project_v1.2_Status]]
| [[Yocto_1.2_Overall_Test_Plan]]
| [[Yocto_1.2_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-April/000009.html 1.2 release notes]
|-
| Yocto Project 1.1
| Edison
| 6.0
| Community
| [[Yocto_1.1_Features]]
| [[Yocto_1.1_Schedule]]
| [[Yocto_Project_v1.1_Release_Criteria]]
| [[Yocto_1.1_Overall_Test_Plan]]
| [[Yocto_1.1_Milestone_Test_Report]]
|
|-
| Yocto Project 1.0
| Bernard
| 5.0
| Community
| [[Yocto_Features]]
| [[Yocto_1.0_Schedule]]
| [[Yocto_Project_v1.0_Release_Criteria]]
| [[Yocto_1.0_Overall_Test_Plan]]
|
|
|}

BuildLog

2020-12-20T21:14:21Z

PaulEggleton: /* a-full 152633 - master-next aedec61918033e6fa66bc67e64898efe78b503ee on Typhoon-Cluster */

This is a rolling log of builds being run on the autobuilder. The person triggering the build should note here what the expectations of the build are. Anyone following up on that build (such as the SWAT team) should note what they've done about any failures. Ordering is more recent at the top.

New autobuilder log notes: the stdio link will list which steps failed (e.g. 1c or 2b), you can then follow the link to the relevant logs. The errors log is a summary of all lines starting with ERROR:.

* Non-release autobuilder output (and test results index): https://autobuilder.yocto.io/pub/non-release/
* Staging directory for release builds: https://autobuilder.yocto.io/pub/releases/
==[https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1667 oe-selftest-ubuntu 152810 - stable/dunfell-nut 3eada47fba8d4759098d77223f0caa9172f3faa8 on Typhoon-Cluster]==

<div id="152810"></div>
* '''Build ID''' - 3eada47fba8d4759098d77223f0caa9172f3faa8 on Typhoon-Cluster
* Started at: Sun Dec 20 16:49:34 2020
* sakoman
* steve - test additional exclusions to reproducible builds
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1667 oe-selftest-ubuntu] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1667/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1667/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1667/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1667/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1667/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1667/steps/10/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643 oe-selftest-fedora 152811 - stable/dunfell-nut 3eada47fba8d4759098d77223f0caa9172f3faa8 on Typhoon-Cluster]==

<div id="152811"></div>
* '''Build ID''' - 3eada47fba8d4759098d77223f0caa9172f3faa8 on Typhoon-Cluster
* Started at: Sun Dec 20 17:38:25 2020
* sakoman
* steve - test additional exclusions for reproducible builds
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643 oe-selftest-fedora] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/18 auh 152630 - master-next afec39415be67b6985f0a0c3de041b4f302ffff3 on Typhoon-Cluster]==

<div id="152630"></div>
* '''Build ID''' - afec39415be67b6985f0a0c3de041b4f302ffff3 on Typhoon-Cluster
* Started at: Sat Dec 19 17:22:37 2020
* akanavin
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/18 auh] Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/18/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/18/steps/11/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1688 a-full 152752 - master-next 5d98393d78dc8362a0d18d1f688d2aa7a06b1719 on Typhoon-Cluster]==

<div id="152752"></div>
* '''Build ID''' - 5d98393d78dc8362a0d18d1f688d2aa7a06b1719 on Typhoon-Cluster
* Started at: Sun Dec 20 14:50:45 2020
* richard
* Test couple of new patches and some reproducibility fixes for grub and u-boot
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1357 qemuarm64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1357/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1357/steps/12/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1687 a-full 152691 - master 9aae620b9515e925db4a043a96fda2a6b6b0b5bd on Typhoon-Cluster]==

<div id="152691"></div>
* '''Build ID''' - 9aae620b9515e925db4a043a96fda2a6b6b0b5bd on Typhoon-Cluster
* Started at: Sun Dec 20 01:00:00 2020
* Unknown
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2827 qemumips] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2827/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2827/steps/13/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2827/steps/13/logs/errors errors] - appears to be [https://bugzilla.yoctoproject.org/show_bug.cgi?id=13992 #13992]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1658 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1658/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1658/steps/14/logs/errors errors] - filed [https://bugzilla.yoctoproject.org/show_bug.cgi?id=14158 #14158]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1639 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1639/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1639/steps/14/logs/errors errors] - reproducibility failures; RP has sent patches
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1687 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1686 a-full 152633 - master-next aedec61918033e6fa66bc67e64898efe78b503ee on Typhoon-Cluster]==

<div id="152633"></div>
* '''Build ID''' - aedec61918033e6fa66bc67e64898efe78b503ee on Typhoon-Cluster
* Started at: Sat Dec 19 17:35:17 2020
* richard
* Retest with revised systemd fix and other updates
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1355 qemuarm64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1355/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1355/steps/12/logs/warnings warnings] - these don't look new, looks like we have a bug for the valgrind issues [https://bugzilla.yoctoproject.org/show_bug.cgi?id=13520 #13520] but none for libinput as yet (need to file?)
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1657 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1657/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1657/steps/15/logs/errors errors] - filed [https://bugzilla.yoctoproject.org/show_bug.cgi?id=14159 #14159]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1686 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1622 qemux86-64-ptest 152627 - akanavin/package-version-updates b40625c0f5be26fcc34d85eed8187051a4484b08 on Typhoon-Cluster]==

<div id="152627"></div>
* '''Build ID''' - b40625c0f5be26fcc34d85eed8187051a4484b08 on Typhoon-Cluster
* Started at: Sat Dec 19 12:02:57 2020
* akanavin
* test ptest warnings
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1622 qemux86-64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1622/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1622/steps/12/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1685 a-full 152571 - master-next 747d2e057ee738f9d1690fc447b34fbf4d62660b on Typhoon-Cluster]==

<div id="152571"></div>
* '''Build ID''' - 747d2e057ee738f9d1690fc447b34fbf4d62660b on Typhoon-Cluster
* Started at: Sat Dec 19 11:35:59 2020
* richard
* Retest master-next with elf selftest fix, systemd repro fix, kernel patches dropped, minor patch additions
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549 meta-arm] Remove layers failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549 meta-arm] Add layers_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549 meta-arm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549 meta-arm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549 meta-arm] Remove layers_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1639 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1639/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1639/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1663 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1663/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1663/steps/14/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1637 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1637/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1637/steps/14/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1656 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1656/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1656/steps/15/logs/cancelled cancelled]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548 meta-arm 152567 - master-next aad0f6cb0a801e2c1fc25ce39af1a31caab3e492 on Typhoon-Cluster]==

<div id="152567"></div>
* '''Build ID''' - aad0f6cb0a801e2c1fc25ce39af1a31caab3e492 on Typhoon-Cluster
* Started at: Sat Dec 19 08:53:54 2020
* richard
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548 meta-arm] Remove layers failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548 meta-arm] Add layers_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548 meta-arm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548 meta-arm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548 meta-arm] Remove layers_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/19/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1267 a-quick 152522 - master f1a2ee5a18f565c2e63743af3191b6834941bde9 on Typhoon-Cluster]==

<div id="152522"></div>
* '''Build ID''' - f1a2ee5a18f565c2e63743af3191b6834941bde9 on Typhoon-Cluster
* Started at: Sat Dec 19 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1684 a-full 152468 - master-next aad0f6cb0a801e2c1fc25ce39af1a31caab3e492 on Typhoon-Cluster]==

<div id="152468"></div>
* '''Build ID''' - aad0f6cb0a801e2c1fc25ce39af1a31caab3e492 on Typhoon-Cluster
* Started at: Fri Dec 18 23:10:54 2020
* richard
* Test new patch queue
* [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3105 poky-tiny] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3105/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3105/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547 meta-arm] Remove layers failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547 meta-arm] Add layers_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547 meta-arm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547 meta-arm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547 meta-arm] Remove layers_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1020 meta-intel] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1020/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1020/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1655 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1655/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1655/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1638 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1638/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1638/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1636 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1636/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1636/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1662 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1662/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1662/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1684 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1266 a-quick 152426 - zedd/kernel-next 3b24d9b488d4ce0fe73cb39e3229da9d2b0abf3e on Typhoon-Cluster]==

<div id="152426"></div>
* '''Build ID''' - 3b24d9b488d4ce0fe73cb39e3229da9d2b0abf3e on Typhoon-Cluster
* Started at: Fri Dec 18 21:04:05 2020
* zedd
* v5.10 try2
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2825 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2825/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2825/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2825 genericx86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2825/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2825/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1725 genericx86-64-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1725/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1725/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1725 genericx86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1725/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1725/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2832 genericx86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2832/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2832/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2832 genericx86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2832/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2832/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721 qemuarm-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721/steps/11/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721 qemuarm-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839 qemuarm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839/steps/11/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839 qemuarm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797 wic] genericx86 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/14/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797 wic] genericx86 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/15/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797 wic] genericx86-64 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/20/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/20/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797 wic] genericx86-64 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/21/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/21/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/56/builds/1282 oe-selftest] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/56/builds/1282/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/56/builds/1282/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1266 a-quick] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1265 a-quick 152380 - zedd/kernel-next 58efca2b9e820237d23deb48d593b4451fa92def on Typhoon-Cluster]==

<div id="152380"></div>
* '''Build ID''' - 58efca2b9e820237d23deb48d593b4451fa92def on Typhoon-Cluster
* Started at: Fri Dec 18 18:44:33 2020
* zedd
* v5.10-all take 1
* [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3103 poky-tiny] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3103/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3103/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1724 genericx86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1724/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1724/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720 qemuarm-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720/steps/11/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720 qemuarm-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1724 genericx86-64-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1724/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1724/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2831 genericx86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2831/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2831/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2831 genericx86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2831/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2831/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2824 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2824/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2824/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2824 genericx86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2824/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2824/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796 wic] genericx86 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/15/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796 wic] genericx86 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/16/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796 wic] genericx86-64 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/21/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/21/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796 wic] genericx86-64 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/22/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/22/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838 qemuarm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838/steps/11/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838 qemuarm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/56/builds/1281 oe-selftest] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/56/builds/1281/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/56/builds/1281/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1265 a-quick] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1264 a-quick 152330 - zedd/kernel-next caec33dee7b200c4b446152c14f4c697045cf8da on Typhoon-Cluster]==

<div id="152330"></div>
* '''Build ID''' - caec33dee7b200c4b446152c14f4c697045cf8da on Typhoon-Cluster
* Started at: Fri Dec 18 03:11:38 2020
* zedd
* v5.10-all take 1
* [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3102 poky-tiny] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3102/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3102/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2827 non-gpl3] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2827/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2827/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2828 musl-qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2828/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2828/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2824 musl-qemux86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2824/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2824/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2802 qemux86-64-x32] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2802/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2802/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2817 qa-extras] Readonly rootfs: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2817/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2817/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795 wic] qemux86 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795 wic] genericx86 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/14/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795 wic] genericx86 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/15/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795 wic] genericx86-64 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/20/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/20/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795 wic] genericx86-64 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/21/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/21/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2831 meta-mingw] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2831/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2831/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3059 build-appliance] BA image build: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3059/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3059/steps/13/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1723 genericx86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1723/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1723/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815 pkgman-non-rpm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815 pkgman-non-rpm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815 pkgman-non-rpm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/15/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/15/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1723 genericx86-64-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1723/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1723/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819 qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819 qemux86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2823 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2823/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2823/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2823 genericx86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2823/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2823/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2825 no-x11] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2825/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2825/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756 qemux86-64-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756 qemux86-64-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815 qemux86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815 qemux86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713 qemux86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713 qemux86-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815 pkgman-rpm-non-rpm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815 pkgman-rpm-non-rpm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815/steps/13/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819 pkgman-deb-non-deb] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819 pkgman-deb-non-deb] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819/steps/13/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819/steps/13/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2830 genericx86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2830/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2830/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2830 genericx86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2830/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2830/steps/13/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/94/builds/843 qemux86-64-ptest-fast] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/94/builds/843/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/94/builds/843/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837 qemuarm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837 qemuarm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2852 qa-extras2] Test logrotate: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2852/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2852/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805 qemuppc] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805 qemuppc] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144 qemuarm64-armhost] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144 qemuarm64-armhost] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/93/builds/748 qemuarm64-ptest-fast] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/93/builds/748/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/93/builds/748/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853 multilib] x86-64 lib32-img rpm: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853 multilib] x86-64 lib64-img: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853/steps/23/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853/steps/23/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853 multilib] mip64 n32: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853/steps/25/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853/steps/25/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820 qemumips] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820 qemumips] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820/steps/13/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820 qemumips64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820 qemumips64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719 qemuarm-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719/steps/11/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719 qemuarm-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2805 qemux86-world] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2805/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2805/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818 qemuarm64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818 qemuarm64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1264 a-quick] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1263 a-quick 152286 - master 38b45cd73eb360ce6dbe441ea497044acd27d777 on Typhoon-Cluster]==

<div id="152286"></div>
* '''Build ID''' - 38b45cd73eb360ce6dbe441ea497044acd27d777 on Typhoon-Cluster
* Started at: Fri Dec 18 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1683 a-full 152226 - stable/dunfell-nut 31a9e3966f64e1d62f804e6f300dedbccc31827f on Typhoon-Cluster]==

<div id="152226"></div>
* '''Build ID''' - 31a9e3966f64e1d62f804e6f300dedbccc31827f on Typhoon-Cluster
* Started at: Thu Dec 17 16:19:53 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1753 qemux86-64-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1753/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1753/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1753/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1753/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637 oe-selftest-fedora] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661 oe-selftest-ubuntu] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635 oe-selftest-debian] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654 oe-selftest-centos] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1683 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1262 a-quick 152178 - master 38b45cd73eb360ce6dbe441ea497044acd27d777 on Typhoon-Cluster]==

<div id="152178"></div>
* '''Build ID''' - 38b45cd73eb360ce6dbe441ea497044acd27d777 on Typhoon-Cluster
* Started at: Thu Dec 17 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1682 a-full 152121 - master-next 9cda24a1aaff6e6174023dfd8f3864e337e24f0d on Typhoon-Cluster]==

<div id="152121"></div>
* '''Build ID''' - 9cda24a1aaff6e6174023dfd8f3864e337e24f0d on Typhoon-Cluster
* Started at: Wed Dec 16 18:28:44 2020
* richard
* Test master-next, systemd dropped, more patches added
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2848 qa-extras2] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2848/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2848/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1634 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1634/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1634/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1682 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1681 a-full 152067 - stable/dunfell-nut 8c651c739826fa2812c6b5f84fb91b6f99bf1b29 on Typhoon-Cluster]==

<div id="152067"></div>
* '''Build ID''' - 8c651c739826fa2812c6b5f84fb91b6f99bf1b29 on Typhoon-Cluster
* Started at: Wed Dec 16 15:48:23 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/808 meta-oe 152014 - yoe/mut d11dad295ebede21bcc75468935f667858394db7 on Typhoon-Cluster]==

<div id="152014"></div>
* '''Build ID''' - d11dad295ebede21bcc75468935f667858394db7 on Typhoon-Cluster
* Started at: Tue Dec 15 23:41:05 2020
* kraj
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/808 meta-oe] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/808/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/808/steps/12/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1261 a-quick 152015 - master 82b8dc9cccd32197a775800ee0dfc1841ef00e0c on Typhoon-Cluster]==

<div id="152015"></div>
* '''Build ID''' - 82b8dc9cccd32197a775800ee0dfc1841ef00e0c on Typhoon-Cluster
* Started at: Wed Dec 16 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1680 a-full 151960 - master-next 6c2a88144eb00735e4da656bbd7686b9134fde14 on Typhoon-Cluster]==

<div id="151960"></div>
* '''Build ID''' - 6c2a88144eb00735e4da656bbd7686b9134fde14 on Typhoon-Cluster
* Started at: Tue Dec 15 23:13:29 2020
* richard
* Retry master-next build with kern-tools dropped
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1189 qemux86-world-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1189/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1189/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016 meta-intel] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016 meta-intel] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1651 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1651/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1651/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1319 qemuarm64-ltp] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1319/steps/12/logs/stdio stdio]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1348 qemuarm64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1348/steps/12/logs/stdio stdio]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1658 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1658/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1658/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1632 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1632/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1632/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1680 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1679 a-full 151906 - master-next bcc58cf6b62e316669de3c17a713e98703b7d390 on Typhoon-Cluster]==

<div id="151906"></div>
* '''Build ID''' - bcc58cf6b62e316669de3c17a713e98703b7d390 on Typhoon-Cluster
* Started at: Tue Dec 15 23:04:32 2020
* richard
* Test new master-next patch queue
* [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2830 check-layer] Run cmds_2 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2830/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2830/steps/15/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2845 multilib] x86-64 lib32-img rpm: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2845/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2845/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3094 poky-tiny] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3094/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3094/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2819 non-gpl3] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2819/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2819/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2797 qemuppc] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2797/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2797/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2829 qemuarm] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2829/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2829/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2830 qemuarm-oecore] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2830/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2830/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2822 genericx86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2822/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2822/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1633 oe-selftest-fedora] Bitbake Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1633/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1633/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2810 qemuarm64] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2810/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2810/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2807 pkgman-rpm-non-rpm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2807/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2807/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2815 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2815/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2815/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2820 musl-qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2820/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2820/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2794 qemux86-64-x32] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2794/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2794/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1202 qemumips-alt] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1202/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1202/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1650 oe-selftest-centos] Bitbake Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1650/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1650/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2817 no-x11] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2817/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2817/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1191 qemuppc-alt] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1191/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1191/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2822 meta-mingw] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2822/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2822/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2844 qa-extras2] Test logrotate: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2844/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2844/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1715 genericx86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1715/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1715/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2797 qemux86-world] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2797/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2797/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1188 qemux86-world-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1188/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1188/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2838 beaglebone] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2838/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2838/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2816 edgerouter] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2816/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2816/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1198 edgerouter-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1198/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1198/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2816 musl-qemux86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2816/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2816/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2807 qemux86] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2807/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2807/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1711 qemuarm-alt] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1711/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1711/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2812 qemumips64] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2812/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2812/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2811 qemux86-64] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2811/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2811/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2809 qa-extras] Readonly rootfs: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2809/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2809/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1347 qemuarm64-ptest] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1347/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1347/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1318 qemuarm64-ltp] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1318/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1318/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1610 qemux86-64-ptest] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1610/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1610/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3129 buildtools] x86_64 tools: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3129/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3129/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1720 beaglebone-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1720/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1720/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2136 qemuarm64-armhost] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2136/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2136/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2811 pkgman-deb-non-deb] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2811/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2811/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1705 qemux86-alt] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1705/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1705/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/542 meta-arm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/542/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/542/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1747 qemux86-64-alt] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1747/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1747/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3051 build-appliance] Universe fetch: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3051/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3051/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1015 meta-intel] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1015/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1015/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1679 a-full] Sources pre-fetching: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1679/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1679/steps/13/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1679/steps/13/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/15 auh 151852 - master 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster]==

<div id="151852"></div>
* '''Build ID''' - 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster
* Started at: Tue Dec 15 01:00:00 2020
* Unknown
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/15 auh] Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/15/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/15/steps/11/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1260 a-quick 151851 - master 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster]==

<div id="151851"></div>
* '''Build ID''' - 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster
* Started at: Tue Dec 15 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1678 a-full 151793 - stable/dunfell-nut 7756989ce74a4553e692cd067bb8ea881e00fa7e on Typhoon-Cluster]==

<div id="151793"></div>
* '''Build ID''' - 7756989ce74a4553e692cd067bb8ea881e00fa7e on Typhoon-Cluster
* Started at: Mon Dec 14 16:00:46 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1677 a-full 151736 - master-next 08a08d40a1e5e8bd26f13739ac6986c79ea1200f on Typhoon-Cluster]==

<div id="151736"></div>
* '''Build ID''' - 08a08d40a1e5e8bd26f13739ac6986c79ea1200f on Typhoon-Cluster
* Started at: Mon Dec 14 13:39:20 2020
* richard
* Retest master-next with syslinux, systemd-boot and yocto-check-layer changes dropped
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1648 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1648/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1648/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1677 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1259 a-quick 151689 - master 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster]==

<div id="151689"></div>
* '''Build ID''' - 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster
* Started at: Mon Dec 14 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1676 a-full 151635 - master-next 9bebabcf01e41ac957bd4724f18e892d8ab9d457 on Typhoon-Cluster]==

<div id="151635"></div>
* '''Build ID''' - 9bebabcf01e41ac957bd4724f18e892d8ab9d457 on Typhoon-Cluster
* Started at: Mon Dec 14 00:11:34 2020
* richard
* Test revised patch queue (systemd changes dropped, new additions)
* [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825 check-layer] Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825 check-layer] Run cmds_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825 check-layer] Run cmds_2 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825 check-layer] Run cmds_3 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825 check-layer] Sending error reports failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/20/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/20/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012 meta-intel] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012 meta-intel] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1647 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1647/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1647/steps/14/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1647/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1628 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1628/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1628/steps/14/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1628/steps/14/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1630 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1630/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1630/steps/14/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1630/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1654 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1654/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1654/steps/14/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1654/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1676 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1675 a-full 151578 - akanavin/package-version-updates 08cd26dc83d649f6051bc5d4ac1eb53a92a0f6e6 on Typhoon-Cluster]==

<div id="151578"></div>
* '''Build ID''' - 08cd26dc83d649f6051bc5d4ac1eb53a92a0f6e6 on Typhoon-Cluster
* Started at: Sun Dec 13 16:23:19 2020
* akanavin
* ptest fixes/version updates

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1674 a-full 151518 - master 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster]==

<div id="151518"></div>
* '''Build ID''' - 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster
* Started at: Sun Dec 13 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1258 a-quick 151464 - master 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster]==

<div id="151464"></div>
* '''Build ID''' - 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster
* Started at: Sat Dec 12 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1673 a-full 151407 - stable/dunfell-nut a7fa1236a1bdb28c77a3759a9c4957a07ce264a4 on Typhoon-Cluster]==

<div id="151407"></div>
* '''Build ID''' - a7fa1236a1bdb28c77a3759a9c4957a07ce264a4 on Typhoon-Cluster
* Started at: Fri Dec 11 18:02:58 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1442 qemux86-64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1442/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1442/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1442/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1442/steps/10/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1442/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1673 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1672 a-full 151348 - anujm/gatesgarth 8ae61a07f12a385ee27fc82ed5938715bfb4693b on Typhoon-Cluster]==

<div id="151348"></div>
* '''Build ID''' - 8ae61a07f12a385ee27fc82ed5938715bfb4693b on Typhoon-Cluster
* Started at: Fri Dec 11 03:03:33 2020
* anujm
* test gatesgarth patch queue

==[https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/797 meta-oe 151139 - yoe/mut a51b07c50c136495d554b689dfe531f6d2ed9f40 on Typhoon-Cluster]==

<div id="151139"></div>
* '''Build ID''' - a51b07c50c136495d554b689dfe531f6d2ed9f40 on Typhoon-Cluster
* Started at: Thu Dec 10 16:38:32 2020
* kraj
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/797 meta-oe] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/797/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/797/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/797/steps/12/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1257 a-quick 151303 - master 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster]==

<div id="151303"></div>
* '''Build ID''' - 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster
* Started at: Fri Dec 11 01:00:00 2020
* Unknown
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2798 qa-extras] Readonly rootfs: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2798/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2798/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2798/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1257 a-quick] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1671 a-full 151249 - stable/dunfell-nut b895948a6219f4d9f58a379e2eb249cbf1508898 on Typhoon-Cluster]==

<div id="151249"></div>
* '''Build ID''' - b895948a6219f4d9f58a379e2eb249cbf1508898 on Typhoon-Cluster
* Started at: Thu Dec 10 23:00:19 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1693 qemux86-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1693/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1693/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1693/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1693/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2808 musl-qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2808/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2808/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2808/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2808/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2785 qemux86-world] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2785/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2785/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2785/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1180 qemux86-world-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1180/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1180/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1180/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1671 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1670 a-full 151193 - stable/dunfell-nut a78ea1f3b881613f9962b9a2134f103a6a46f495 on Typhoon-Cluster]==

<div id="151193"></div>
* '''Build ID''' - a78ea1f3b881613f9962b9a2134f103a6a46f495 on Typhoon-Cluster
* Started at: Thu Dec 10 19:19:52 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3116 buildtools] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3116/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3116/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3116/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3116/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3116/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3038 build-appliance] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3038/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3038/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3038/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3038/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2807 musl-qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2807/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2807/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2807/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2807/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2804 no-x11] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2804/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2804/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2804/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2804/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2803 musl-qemux86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2803/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2803/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2803/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2803/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798 qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/step3a step3a] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794 qemux86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/step3a step3a] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1309 qemuarm64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1309/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1309/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1309/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1309/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1648 oe-selftest-ubuntu] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1648/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1648/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1648/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1648/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1648/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832 multilib] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step3c step3c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step4b step4b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step4c step4c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step5b step5b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1439 qemux86-64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1439/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1439/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1439/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1439/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1601 qemux86-64-ptest] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1601/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1601/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1601/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1601/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2799 qemumips] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2799/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2799/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2799/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2799/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1640 oe-selftest-centos] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1640/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1640/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1640/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1640/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1640/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2816 qemuarm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2816/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2816/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2816/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1698 qemuarm-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1698/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1698/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1698/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2799 qemumips64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2799/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2799/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2799/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831 qa-extras2] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step3c step3c] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step4a step4a] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step4b step4b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step4c step4c] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step5b step5b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1338 qemuarm64-ptest] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1338/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1338/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1338/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1338/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1622 oe-selftest-debian] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1622/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1622/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1622/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1622/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1622/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2784 qemux86-world] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2784/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2784/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2784/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2784/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1182 qemuppc-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1182/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1182/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1182/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1182/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1193 qemumips-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1193/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1193/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1193/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1193/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1624 oe-selftest-fedora] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1624/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1624/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1624/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1624/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1624/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1179 qemux86-world-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1179/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1179/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1179/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797 qemuarm64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/step3a step3a] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784 qemuppc] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/step3a step3a] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1670 a-full] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1670/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1670/steps/11/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1670/steps/11/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1670/steps/11/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1669 a-full 151138 - master-next a51b07c50c136495d554b689dfe531f6d2ed9f40 on Typhoon-Cluster]==

<div id="151138"></div>
* '''Build ID''' - a51b07c50c136495d554b689dfe531f6d2ed9f40 on Typhoon-Cluster
* Started at: Thu Dec 10 16:31:14 2020
* richard
* Test new patch queue
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2797 qemux86-64] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2797/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2797/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1178 qemux86-world-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1178/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1178/steps/12/logs/errors errors]
* SWAT Follow-up - systemd update to 247 introduced a PAM Packaging issue.
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1639 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1639/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1639/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1669 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1668 a-full 151082 - master-next 30aeddb5cead1d6156aadd633683573910462644 on Typhoon-Cluster]==

<div id="151082"></div>
* '''Build ID''' - 30aeddb5cead1d6156aadd633683573910462644 on Typhoon-Cluster
* Started at: Thu Dec 10 13:48:11 2020
* richard
* Test new patch queue
* [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3079 poky-tiny] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3079/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3079/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2804 non-gpl3] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2804/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2804/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2796 pkgman-deb-non-deb] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2796/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2796/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2796 pkgman-deb-non-deb] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2796/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2796/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] Readonly rootfs: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] Readonly rootfs: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] ROOT_HOME testing: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] ROOT_HOME testing: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] Full eSDK type: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] Prep locked-sigs test: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] Test locked-sigs image: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/24/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/24/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] Test locked-sigs eSDK: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/26/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/26/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3036 build-appliance] BA image build: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3036/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3036/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779 qemux86-64-x32] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779 qemux86-64-x32] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779 qemux86-64-x32] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1599 qemux86-64-ptest] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1599/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1599/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1599 qemux86-64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1599/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1599/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1437 qemux86-64-ltp] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1437/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1437/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1437 qemux86-64-ltp] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1437/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1437/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1191 qemumips-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1191/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1191/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1191 qemumips-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1191/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1191/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2792 pkgman-rpm-non-rpm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2792/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2792/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2792 pkgman-rpm-non-rpm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2792/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2792/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1705 beaglebone-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1705/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1705/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1307 qemuarm64-ltp] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1307/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1307/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1307 qemuarm64-ltp] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1307/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1307/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2800 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2800/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2800/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796 qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796 qemux86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796 qemux86-64] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796 qemux86-64] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796 qemux86-64] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/20/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/20/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815 qemuarm-oecore] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815 qemuarm-oecore] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815 qemuarm-oecore] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815 qemuarm-oecore] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815 qemuarm-oecore] Build targets_2 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815 qemuarm-oecore] QA targets_2 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1732 qemux86-64-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1732/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1732/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1732 qemux86-64-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1732/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1732/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1696 qemuarm-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1696/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1696/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1696 qemuarm-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1696/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1696/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792 qemux86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792 qemux86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792 qemux86] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792 qemux86] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792 qemux86] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1004 meta-intel] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1004/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1004/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] qemux86 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] qemux86 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] genericx86 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] genericx86 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] qemux86-64 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] qemux86-64 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] genericx86-64 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/20/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/20/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] genericx86-64 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/21/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/21/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3114 buildtools] x86_64 tools: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3114/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3114/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3114 buildtools] aarch64 tools: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3114/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3114/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782 qemuppc] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782 qemuppc] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782 qemuppc] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782 qemuppc] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782 qemuppc] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2802 no-x11] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2802/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2802/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2802 no-x11] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2802/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2802/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2801 edgerouter] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2801/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2801/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1336 qemuarm64-ptest] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1336/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1336/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1336 qemuarm64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1336/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1336/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1646 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1646/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1646/steps/14/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1646/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2805 musl-qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2805/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2805/steps/11/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2805/steps/11/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2805/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1620 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1620/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1620/steps/14/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1620/steps/14/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1620/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2782 qemux86-world] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2782/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2782/steps/11/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2782/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1180 qemuppc-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1180/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1180/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1638 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1638/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1638/steps/14/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1638/steps/14/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1638/steps/14/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2823 beaglebone] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2823/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2823/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1187 edgerouter-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1187/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1187/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2795 qemuarm64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2795/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2795/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2801 musl-qemux86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2801/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2801/steps/12/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2801/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2801/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2807 genericx86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2807/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2807/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2807 genericx86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2807/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2807/steps/13/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1622 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1622/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1622/steps/14/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1622/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2797 qemumips] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2797/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2797/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2792 pkgman-non-rpm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2792/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2792/steps/11/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2792/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1177 qemux86-world-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1177/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1177/steps/11/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1177/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1700 genericx86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1700/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1700/steps/11/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1700/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121 qemuarm64-armhost] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121 qemuarm64-armhost] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121/steps/12/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797 qemumips64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797 qemumips64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797 qemumips64] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797 qemumips64] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797 qemumips64] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/19/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1690 qemux86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1690/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1690/steps/12/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1690/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1700 genericx86-64-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1700/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1700/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829 qa-extras2] Test logrotate: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829 qa-extras2] Test logrotate: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829 qa-extras2] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829 qa-extras2] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829 qa-extras2] Test skeletoninit: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/18/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531 meta-arm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531 meta-arm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531 meta-arm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/17/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32-img rpm: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32-img rpm: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32-img ipk: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32-img ipk: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32 rpm: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32 rpm: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32 ipk: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/20/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/20/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32 ipk: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/21/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/21/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib64-img: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/23/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/23/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814 qemuarm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814 qemuarm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814 qemuarm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814 qemuarm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814 qemuarm] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814 qemuarm] Sending error reports failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/23/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/23/logs/cancelled cancelled]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1667 a-full 151081 - master-next YP_CHASH on Typhoon-Cluster]==
<div id="151081"></div>
* '''Build ID''' - YP_CHASH on Typhoon-Cluster
* Started at: Thu Dec 10 13:45:22 2020
* richard
* Test new patch queue

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1666 a-full 151022 - stable/dunfell-nut fa58a40cfc3661103c25a9d33989eabd550dd231 on Typhoon-Cluster]==

<div id="151022"></div>
* '''Build ID''' - fa58a40cfc3661103c25a9d33989eabd550dd231 on Typhoon-Cluster
* Started at: Thu Dec 10 04:05:29 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1256 a-quick 150979 - master f36484e88d21346357bd1fa1bef6fdcc42bed54a on Typhoon-Cluster]==

<div id="150979"></div>
* '''Build ID''' - f36484e88d21346357bd1fa1bef6fdcc42bed54a on Typhoon-Cluster
* Started at: Thu Dec 10 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1665 a-full 150921 - master f36484e88d21346357bd1fa1bef6fdcc42bed54a on Typhoon-Cluster]==

<div id="150921"></div>
* '''Build ID''' - f36484e88d21346357bd1fa1bef6fdcc42bed54a on Typhoon-Cluster
* Started at: Wed Dec 9 17:36:48 2020
* richard
* Build 3.3 M1 rc2
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2779 qemuppc] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2779/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2779/steps/13/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1665 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1664 a-full 150865 - stable/dunfell-nut b1cbb532373e45d341d43e2285ab3262046e9dca on Typhoon-Cluster]==

<div id="150865"></div>
* '''Build ID''' - b1cbb532373e45d341d43e2285ab3262046e9dca on Typhoon-Cluster
* Started at: Wed Dec 9 15:18:35 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1663 a-full 150809 - master 9826881036191be6ffba98c9bc8a86d1b852ff41 on Typhoon-Cluster]==

<div id="150809"></div>
* '''Build ID''' - 9826881036191be6ffba98c9bc8a86d1b852ff41 on Typhoon-Cluster
* Started at: Wed Dec 9 14:46:41 2020
* richard
* Build 3.3 M1
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109 buildtools] x86_64 tools: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109 buildtools] i686 tools: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109 buildtools] aarch64 tools: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109 buildtools] Publishing artefacts failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2802 genericx86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2802/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2802/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2802 genericx86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2802/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2802/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2795 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2795/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2795/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2795 genericx86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2795/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2795/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527 meta-arm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527 meta-arm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527 meta-arm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527 meta-arm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1000 meta-intel] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1000/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1000/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1000 meta-intel] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1000/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1000/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2116 qemuarm64-armhost] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2116/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2116/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2116 qemuarm64-armhost] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2116/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2116/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789 qa-extras] Full eSDK type: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789 qa-extras] Prep locked-sigs test: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789 qa-extras] Test locked-sigs eSDK: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789/steps/26/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789/steps/26/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818 beaglebone] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818 beaglebone] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818 beaglebone] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2825 multilib] mip64 n32: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2825/steps/25/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2825/steps/25/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2825 multilib] mip64 n32: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2825/steps/26/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2825/steps/26/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1618 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1618/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1618/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2796 edgerouter] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2796/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2796/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2796 edgerouter] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2796/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2796/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777 qemuppc] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777 qemuppc] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777 qemuppc] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777 qemuppc] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792 qemumips64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792 qemumips64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792 qemumips64] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792 qemumips64] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1303 qemuarm64-ltp] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1303/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1303/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1616 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1616/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1616/steps/14/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1616/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1595 qemux86-64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1595/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1595/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/92/builds/3925 buildperf-ubuntu1604] Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/92/builds/3925/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/92/builds/3925/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3900 buildperf-centos7] Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3900/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3900/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1634 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1634/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1634/steps/15/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1634/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1642 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1642/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1642/steps/14/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1642/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1332 qemuarm64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1332/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1332/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1433 qemux86-64-ltp] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1433/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1433/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787 qemux86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787 qemux86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787 qemux86] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787 qemux86] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787 qemux86] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/19/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790 qemuarm64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790 qemuarm64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790 qemuarm64] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790 qemuarm64] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790 qemuarm64] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/19/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809 qemuarm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809 qemuarm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809 qemuarm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809 qemuarm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809 qemuarm] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/19/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791 qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791 qemux86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791 qemux86-64] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791 qemux86-64] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791 qemux86-64] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/19/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792 qemumips] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792 qemumips] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792 qemumips] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792 qemumips] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792 qemumips] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/19/logs/cancelled cancelled]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1255 a-quick 150762 - master 64a18762f05dcaf525a2c945908b2747897a79df on Typhoon-Cluster]==

<div id="150762"></div>
* '''Build ID''' - 64a18762f05dcaf525a2c945908b2747897a79df on Typhoon-Cluster
* Started at: Wed Dec 9 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1662 a-full 150705 - stable/dunfell-nut 3d8f58075ad9a94b6a317ca2f58bb65c5c75e6f8 on Typhoon-Cluster]==

<div id="150705"></div>
* '''Build ID''' - 3d8f58075ad9a94b6a317ca2f58bb65c5c75e6f8 on Typhoon-Cluster
* Started at: Tue Dec 8 19:28:15 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1661 a-full 150651 - stable/dunfell-nut 6bec5e677ac85dc4599ef6524d5feefdc1e3a282 on Typhoon-Cluster]==

<div id="150651"></div>
* '''Build ID''' - 6bec5e677ac85dc4599ef6524d5feefdc1e3a282 on Typhoon-Cluster
* Started at: Tue Dec 8 18:44:48 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3071 poky-tiny] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3071/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3071/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3071/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2796 non-gpl3] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2796/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2796/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2796/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2796/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2771 qemux86-64-x32] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2771/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2771/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2771/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2771/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2771/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1431 qemux86-64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1431/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1431/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1431/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1431/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799 meta-mingw] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1724 qemux86-64-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1724/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1724/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1724/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1724/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2794 no-x11] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2794/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2794/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2794/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2794/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764 wic] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1181 edgerouter-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1181/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1181/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1181/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1181/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1330 qemuarm64-ptest] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1330/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1330/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1330/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1330/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1697 beaglebone-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1697/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1697/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1697/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1697/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3106 buildtools] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3106/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3106/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3106/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3106/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3106/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2789 qemumips64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2789/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2789/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2789/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2789/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822 multilib] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3028 build-appliance] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3028/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3028/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3028/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3028/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3028/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2789 qemumips] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2789/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2789/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2789/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2789/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2789/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/998 meta-intel] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/998/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/998/steps/10/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/998/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/998/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/998/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1174 qemuppc-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1174/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1174/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1174/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1174/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2797 musl-qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2797/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2797/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2797/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2797/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1682 qemux86-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1682/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1682/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1682/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1682/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2788 pkgman-deb-non-deb] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2788/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2788/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2788/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2788/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616 oe-selftest-fedora] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2807 qemuarm-oecore] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2807/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2807/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2807/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2807/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2774 qemux86-world] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2774/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2774/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2774/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2774/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2787 qemuarm64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2787/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2787/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2787/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2787/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614 oe-selftest-debian] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1692 genericx86-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1692/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1692/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1692/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1692/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632 oe-selftest-centos] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1692 genericx86-64-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1692/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1692/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1692/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1692/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1171 qemux86-world-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1171/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1171/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1171/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1171/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786 qa-extras] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1688 qemuarm-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1688/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1688/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1688/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1688/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2821 qa-extras2] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2821/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2821/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2821/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2821/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1593 qemux86-64-ptest] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1593/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1593/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1593/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1593/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2784 qemux86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2784/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2784/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2784/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2784/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788 qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2784 pkgman-non-rpm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2784/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2784/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2784/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2784/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640 oe-selftest-ubuntu] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2113 qemuarm64-armhost] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2113/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2113/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2113/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2113/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1301 qemuarm64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1301/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1301/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1301/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1301/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2793 musl-qemux86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2793/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2793/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2793/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2793/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2806 qemuarm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2806/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2806/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2806/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2806/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2793 edgerouter] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2793/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2793/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2793/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2793/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2784 pkgman-rpm-non-rpm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2784/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2784/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2784/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2784/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2799 genericx86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2799/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2799/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2799/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2799/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1185 qemumips-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1185/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1185/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1185/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1185/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2792 genericx86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2792/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2792/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2792/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2792/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2815 beaglebone] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2815/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2815/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2815/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2815/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2774 qemuppc] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2774/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2774/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2774/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2774/steps/10/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1660 a-full 150595 - stable/dunfell-nut 2d64099340d3bcf0e82d744a4b27ba47389e8510 on Typhoon-Cluster]==

<div id="150595"></div>
* '''Build ID''' - 2d64099340d3bcf0e82d744a4b27ba47389e8510 on Typhoon-Cluster
* Started at: Tue Dec 8 14:47:02 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1659 a-full 150541 - master-next be4e442da1b22e4a0d85cc74f11fec4981207684 on Typhoon-Cluster]==

<div id="150541"></div>
* '''Build ID''' - be4e442da1b22e4a0d85cc74f11fec4981207684 on Typhoon-Cluster
* Started at: Tue Dec 8 09:21:04 2020
* richard
* Add missing reproducible patch and retry
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2790 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2790/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2790/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1630 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1630/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1630/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1659 a-full] trigger failed:
* SWAT Bug filed [https://bugzilla.yoctoproject.org/show_bug.cgi?id=14147 here]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/791 meta-oe 150492 - yoe/mut 16fa0ac7947eb848111d2347b9f9017f2f85b7d8 on Typhoon-Cluster]==

<div id="150492"></div>
* '''Build ID''' - 16fa0ac7947eb848111d2347b9f9017f2f85b7d8 on Typhoon-Cluster
* Started at: Mon Dec 7 23:04:24 2020
* kraj
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/791 meta-oe] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/791/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/791/steps/12/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1254 a-quick 150494 - master 64a18762f05dcaf525a2c945908b2747897a79df on Typhoon-Cluster]==

<div id="150494"></div>
* '''Build ID''' - 64a18762f05dcaf525a2c945908b2747897a79df on Typhoon-Cluster
* Started at: Tue Dec 8 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1658 a-full 150435 - master-next 16fa0ac7947eb848111d2347b9f9017f2f85b7d8 on Typhoon-Cluster]==

<div id="150435"></div>
* '''Build ID''' - 16fa0ac7947eb848111d2347b9f9017f2f85b7d8 on Typhoon-Cluster
* Started at: Mon Dec 7 21:53:30 2020
* richard
* Retest patch queue with kea upgarde removed, repro fix added, new patches added
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1613 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1613/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1613/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1629 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1629/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1629/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1611 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1611/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1611/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1637 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1637/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1637/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1658 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1657 a-full 150377 - stable/dunfell-nut 86d6acde11c42a081166dc3019595fe80dc76847 on Typhoon-Cluster]==

<div id="150377"></div>
* '''Build ID''' - 86d6acde11c42a081166dc3019595fe80dc76847 on Typhoon-Cluster
* Started at: Mon Dec 7 16:54:34 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783 qemumips] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/step3a step3a] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783 qemumips64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/step3a step3a] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1657 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1656 a-full 150324 - gatesgarth 943ef2fad8428f002850e3655a3312e13d0dcb2c on Typhoon-Cluster]==

<div id="150324"></div>
* '''Build ID''' - 943ef2fad8428f002850e3655a3312e13d0dcb2c on Typhoon-Cluster
* Started at: Mon Dec 7 16:25:56 2020
* richard
* Build 3.2.1 rc2

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1655 a-full 150268 - stable/dunfell-nut 9354a08235f211e30de79009d308803b7bc4bb27 on Typhoon-Cluster]==

<div id="150268"></div>
* '''Build ID''' - 9354a08235f211e30de79009d308803b7bc4bb27 on Typhoon-Cluster
* Started at: Mon Dec 7 15:28:48 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3099 buildtools] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3099/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3099/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3099/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3099/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3099/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3021 build-appliance] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3021/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3021/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3021/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3021/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2781 pkgman-deb-non-deb] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2781/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2781/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2781/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2781/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2767 qemux86-world] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2767/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2767/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2767/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2777 pkgman-non-rpm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2777/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2777/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2777/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1425 qemux86-64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1425/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1425/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1425/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1425/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2814 qa-extras2] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2814/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2814/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2814/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1634 oe-selftest-ubuntu] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1634/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1634/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1634/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1634/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1634/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2799 qemuarm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2799/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2799/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2799/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2800 qemuarm-oecore] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2800/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2800/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2800/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2800/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2800/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792 meta-mingw] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792/steps/10/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1685 genericx86-64-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1685/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1685/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1685/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1675 qemux86-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1675/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1675/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1675/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2779 qa-extras] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2779/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2779/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2779/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2808 beaglebone] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2808/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2808/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2808/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1179 qemumips-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1179/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1179/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1179/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2785 genericx86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2785/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2785/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2785/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2780 qemuarm64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2780/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2780/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2780/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1681 qemuarm-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1681/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1681/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1681/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2767 qemuppc] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2767/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2767/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2767/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2757 wic] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2757/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2757/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2757/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2757/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2757/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1587 qemux86-64-ptest] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1587/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1587/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1587/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2781 qemumips] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2781/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2781/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2781/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1610 oe-selftest-fedora] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1610/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1610/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1610/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1610/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1610/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1626 oe-selftest-centos] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1626/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1626/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1626/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1626/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1626/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2781 qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2781/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2781/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2781/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2781/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2106 qemuarm64-armhost] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2106/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2106/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2106/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1717 qemux86-64-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1717/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1717/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1717/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1685 genericx86-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1685/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1685/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1685/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2786 edgerouter] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2786/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2786/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2786/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1175 edgerouter-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1175/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1175/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1175/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2781 qemumips64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2781/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2781/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2781/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2777 qemux86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2777/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2777/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2777/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815 multilib] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1324 qemuarm64-ptest] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1324/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1324/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1324/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1295 qemuarm64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1295/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1295/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1295/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1168 qemuppc-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1168/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1168/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1168/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1165 qemux86-world-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1165/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1165/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1165/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2777 pkgman-rpm-non-rpm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2777/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2777/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2777/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/992 meta-intel] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/992/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/992/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/992/steps/10/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/992/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1608 oe-selftest-debian] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1608/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1608/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1608/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1608/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1608/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2787 no-x11] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2787/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2787/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2787/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2790 musl-qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2790/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2790/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2790/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2786 musl-qemux86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2786/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2786/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2786/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2792 genericx86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2792/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2792/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2792/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1690 beaglebone-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1690/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1690/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1690/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1655 a-full] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1655/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1655/steps/11/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1655/steps/11/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1655/steps/11/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654 a-full 150211 - gatesgarth 333f24caec0bb498804dd77cbe762f2f4d9b2225 on Typhoon-Cluster]==

<div id="150211"></div>
* '''Build ID''' - 333f24caec0bb498804dd77cbe762f2f4d9b2225 on Typhoon-Cluster
* Started at: Mon Dec 7 09:00:17 2020
* richard
* Build 3.2.1
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3020 build-appliance] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3020/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3020/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3020/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3020/steps/10/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3020/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633 oe-selftest-ubuntu] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654 a-full] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654/steps/11/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654/steps/11/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654/steps/11/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1253 a-quick 150165 - master 64a18762f05dcaf525a2c945908b2747897a79df on Typhoon-Cluster]==

<div id="150165"></div>
* '''Build ID''' - 64a18762f05dcaf525a2c945908b2747897a79df on Typhoon-Cluster
* Started at: Mon Dec 7 01:00:00 2020
* Unknown
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2775 pkgman-non-rpm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2775/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2775/steps/15/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2775/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1253 a-quick] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1653 a-full 150111 - master-next 1c790e272920e354c270eeaa1fe4f185ce37f60d on Typhoon-Cluster]==

<div id="150111"></div>
* '''Build ID''' - 1c790e272920e354c270eeaa1fe4f185ce37f60d on Typhoon-Cluster
* Started at: Sun Dec 6 23:23:23 2020
* richard
* Test new patch queue
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1608 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1608/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1608/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1624 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1624/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1624/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1632 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1632/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1632/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1606 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1606/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1606/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1653 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1652 a-full 150048 - master 7d7197b28226a9ab39babf5be5c4aa92473a2e60 on Typhoon-Cluster]==

<div id="150048"></div>
* '''Build ID''' - 7d7197b28226a9ab39babf5be5c4aa92473a2e60 on Typhoon-Cluster
* Started at: Sun Dec 6 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1252 a-quick 149998 - master 7d7197b28226a9ab39babf5be5c4aa92473a2e60 on Typhoon-Cluster]==

<div id="149998"></div>
* '''Build ID''' - 7d7197b28226a9ab39babf5be5c4aa92473a2e60 on Typhoon-Cluster
* Started at: Sat Dec 5 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1651 a-full 149939 - akanavin/package-version-updates b0774b94a37346e0fe63f6823a6bc574a2dc2587 on Typhoon-Cluster]==

<div id="149939"></div>
* '''Build ID''' - b0774b94a37346e0fe63f6823a6bc574a2dc2587 on Typhoon-Cluster
* Started at: Fri Dec 4 14:13:37 2020
* akanavin
* package version updates
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783 musl-qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783/steps/11/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783 musl-qemux86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1604 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1604/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1604/steps/14/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1604/steps/14/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1583 qemux86-64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1583/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1583/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1291 qemuarm64-ltp] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1291/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1291/steps/12/logs/cancelled cancelled]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1650 a-full 149882 - master-next aa3a44f4a015feebcf340286f90d236819a6e732 on Typhoon-Cluster]==

<div id="149882"></div>
* '''Build ID''' - aa3a44f4a015feebcf340286f90d236819a6e732 on Typhoon-Cluster
* Started at: Fri Dec 4 05:04:48 2020
* richard
* Retest master-next with container selftest failure fixup

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1251 a-quick 149838 - master 7d7197b28226a9ab39babf5be5c4aa92473a2e60 on Typhoon-Cluster]==

<div id="149838"></div>
* '''Build ID''' - 7d7197b28226a9ab39babf5be5c4aa92473a2e60 on Typhoon-Cluster
* Started at: Fri Dec 4 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1649 a-full 149783 - master-next 804cfd0231281662ce8958195526665cad6500e7 on Typhoon-Cluster]==

<div id="149783"></div>
* '''Build ID''' - 804cfd0231281662ce8958195526665cad6500e7 on Typhoon-Cluster
* Started at: Thu Dec 3 23:11:06 2020
* richard
* Test master-next with new patches and some fixes
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1628 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1628/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1628/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1602 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1602/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1602/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1604 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1604/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1604/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1620 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1620/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1620/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1649 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3874 buildperf-centos7 149723 - master 332159dd3e2621bf7460a85dbb629febd17d1154 on Typhoon-Cluster]==

<div id="149723"></div>
* '''Build ID''' - 332159dd3e2621bf7460a85dbb629febd17d1154 on Typhoon-Cluster
* Started at: Thu Dec 3 15:00:00 2020
* Unknown
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3874 buildperf-centos7] Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3874/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3874/steps/12/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/786 meta-oe 149725 - yoe/mut aa698defff0452381aa4db78d120a12efbed61d4 on Typhoon-Cluster]==

<div id="149725"></div>
* '''Build ID''' - aa698defff0452381aa4db78d120a12efbed61d4 on Typhoon-Cluster
* Started at: Thu Dec 3 17:32:53 2020
* kraj
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/786 meta-oe] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/786/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/786/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/786/steps/12/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1648 a-full 149726 - stable/dunfell-nut b268afcdd8b344088af4b65dfb136a76a08a9cae on Typhoon-Cluster]==

<div id="149726"></div>
* '''Build ID''' - b268afcdd8b344088af4b65dfb136a76a08a9cae on Typhoon-Cluster
* Started at: Thu Dec 3 17:48:53 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1647 a-full 149669 - master-next aa698defff0452381aa4db78d120a12efbed61d4 on Typhoon-Cluster]==

<div id="149669"></div>
* '''Build ID''' - aa698defff0452381aa4db78d120a12efbed61d4 on Typhoon-Cluster
* Started at: Thu Dec 3 12:24:12 2020
* richard
* Retest with nettools split reverted
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1600 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1600/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1600/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1618 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1618/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1618/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1602 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1602/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1602/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1626 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1626/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1626/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1647 a-full] trigger failed:
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1647 a-full] Source Mirror Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1647/steps/23/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1647/steps/23/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1647/steps/23/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1646 a-full 149615 - akanavin/package-version-updates 85b302dd1e4727ec1ce94079b526fed7c8fc3e64 on Typhoon-Cluster]==

<div id="149615"></div>
* '''Build ID''' - 85b302dd1e4727ec1ce94079b526fed7c8fc3e64 on Typhoon-Cluster
* Started at: Thu Dec 3 10:41:44 2020
* akanavin
* package version updates

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1645 a-full 149559 - akanavin/world-repro fdcf7f4b305db70cb4f3b432c8761d323cfce343 on Typhoon-Cluster]==

<div id="149559"></div>
* '''Build ID''' - fdcf7f4b305db70cb4f3b432c8761d323cfce343 on Typhoon-Cluster
* Started at: Thu Dec 3 07:49:38 2020
* akanavin
* testing world reproducibility
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1616 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1616/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1616/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1600 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1600/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1600/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1624 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1624/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1624/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1598 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1598/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1598/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1645 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1250 a-quick 149514 - master 0ac99625bf2c8a19d4ee746dc13e9c6b2e1956e2 on Typhoon-Cluster]==

<div id="149514"></div>
* '''Build ID''' - 0ac99625bf2c8a19d4ee746dc13e9c6b2e1956e2 on Typhoon-Cluster
* Started at: Thu Dec 3 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644 a-full 149457 - stable/dunfell-nut 5070a3a8f4ffe39ad1e481458097fc5c62e08066 on Typhoon-Cluster]==

<div id="149457"></div>
* '''Build ID''' - 5070a3a8f4ffe39ad1e481458097fc5c62e08066 on Typhoon-Cluster
* Started at: Wed Dec 2 22:45:57 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644 a-full] run-config_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644/steps/14/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644/steps/14/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644/steps/14/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644/steps/14/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1643 a-full 149399 - akanavin/package-version-updates 65d17d9749ba4be67595e561422fd5b522cafc92 on Typhoon-Cluster]==

<div id="149399"></div>
* '''Build ID''' - 65d17d9749ba4be67595e561422fd5b522cafc92 on Typhoon-Cluster
* Started at: Wed Dec 2 20:32:59 2020
* akanavin
* package version updates
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2761 pkgman-rpm-non-rpm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2761/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2761/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2761/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/980 meta-intel] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/980/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/980/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1167 qemumips-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1167/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1167/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1167/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1665 qemuarm-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1665/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1665/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1665/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1701 qemux86-64-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1701/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1701/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1701/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1156 qemuppc-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1156/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1156/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1156/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761 pkgman-non-rpm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761 pkgman-non-rpm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761/steps/15/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2765 qemumips64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2765/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2765/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2765/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2751 qemuppc] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2751/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2751/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2751/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2792 beaglebone] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2792/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2792/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/507 meta-arm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/507/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/507/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/507 meta-arm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/507/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/507/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2776 genericx86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2776/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2776/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2770 edgerouter] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2770/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2770/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1598 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1598/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1598/steps/14/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1598/steps/14/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1614 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1614/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1614/steps/14/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1614/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2764 qemuarm64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2764/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2764/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2764/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2783 qemuarm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2783/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2783/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2783/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2090 qemuarm64-armhost] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2090/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2090/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2090/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2765 pkgman-deb-non-deb] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2765/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2765/steps/13/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2765/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1659 qemux86-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1659/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1659/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1659/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2761 qemux86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2761/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2761/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2761/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2765 qemumips] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2765/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2765/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2765/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2769 genericx86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2769/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2769/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2765 qemux86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2765/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2765/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2765/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1643 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1642 a-full 149341 - akanavin/world-repro f020c3cdd0af490913169f2738d46ce9f1cedde4 on Typhoon-Cluster]==

<div id="149341"></div>
* '''Build ID''' - f020c3cdd0af490913169f2738d46ce9f1cedde4 on Typhoon-Cluster
* Started at: Wed Dec 2 10:41:28 2020
* akanavin
* testing world reproducibility
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1595 oe-selftest-debian] Bitbake Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1595/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1595/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1595 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1595/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1595/steps/14/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1613 oe-selftest-centos] Bitbake Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1613/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1613/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1613 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1613/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1613/steps/14/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1597 oe-selftest-fedora] Bitbake Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1597/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1597/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1597 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1597/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1597/steps/14/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1621 oe-selftest-ubuntu] Bitbake Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1621/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1621/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1621 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1621/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1621/steps/14/logs/cancelled cancelled]

==Archived Logs==

Archives of older logs:

* [[BuildLog/Archive/0001]]
* [[BuildLog/Archive/0002]]
* [[BuildLog/Archive/0003]]
* [[BuildLog/Archive/0004]]
* [[BuildLog/Archive/0005]]
* [[BuildLog/Archive/0006]]
* [[BuildLog/Archive/0007]]
* [[BuildLog/Archive/0008]]
* [[BuildLog/Archive/0009]]
* [[BuildLog/Archive/0010]]
* [[BuildLog/Archive/0011]]
* [[BuildLog/Archive/0012]]
* [[BuildLog/Archive/0013]]

BuildLog

2020-12-20T20:56:27Z

PaulEggleton: /* a-full 152691 - master 9aae620b9515e925db4a043a96fda2a6b6b0b5bd on Typhoon-Cluster */

This is a rolling log of builds being run on the autobuilder. The person triggering the build should note here what the expectations of the build are. Anyone following up on that build (such as the SWAT team) should note what they've done about any failures. Ordering is more recent at the top.

New autobuilder log notes: the stdio link will list which steps failed (e.g. 1c or 2b), you can then follow the link to the relevant logs. The errors log is a summary of all lines starting with ERROR:.

* Non-release autobuilder output (and test results index): https://autobuilder.yocto.io/pub/non-release/
* Staging directory for release builds: https://autobuilder.yocto.io/pub/releases/
==[https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643 oe-selftest-fedora 152811 - stable/dunfell-nut 3eada47fba8d4759098d77223f0caa9172f3faa8 on Typhoon-Cluster]==

<div id="152811"></div>
* '''Build ID''' - 3eada47fba8d4759098d77223f0caa9172f3faa8 on Typhoon-Cluster
* Started at: Sun Dec 20 17:38:25 2020
* sakoman
* steve - test additional exclusions for reproducible builds
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643 oe-selftest-fedora] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1643/steps/10/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/18 auh 152630 - master-next afec39415be67b6985f0a0c3de041b4f302ffff3 on Typhoon-Cluster]==

<div id="152630"></div>
* '''Build ID''' - afec39415be67b6985f0a0c3de041b4f302ffff3 on Typhoon-Cluster
* Started at: Sat Dec 19 17:22:37 2020
* akanavin
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/18 auh] Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/18/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/18/steps/11/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1688 a-full 152752 - master-next 5d98393d78dc8362a0d18d1f688d2aa7a06b1719 on Typhoon-Cluster]==

<div id="152752"></div>
* '''Build ID''' - 5d98393d78dc8362a0d18d1f688d2aa7a06b1719 on Typhoon-Cluster
* Started at: Sun Dec 20 14:50:45 2020
* richard
* Test couple of new patches and some reproducibility fixes for grub and u-boot
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1357 qemuarm64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1357/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1357/steps/12/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1687 a-full 152691 - master 9aae620b9515e925db4a043a96fda2a6b6b0b5bd on Typhoon-Cluster]==

<div id="152691"></div>
* '''Build ID''' - 9aae620b9515e925db4a043a96fda2a6b6b0b5bd on Typhoon-Cluster
* Started at: Sun Dec 20 01:00:00 2020
* Unknown
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2827 qemumips] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2827/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2827/steps/13/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2827/steps/13/logs/errors errors] - appears to be [https://bugzilla.yoctoproject.org/show_bug.cgi?id=13992 #13992]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1658 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1658/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1658/steps/14/logs/errors errors] - filed [https://bugzilla.yoctoproject.org/show_bug.cgi?id=14158 #14158]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1639 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1639/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1639/steps/14/logs/errors errors] - reproducibility failures; RP has sent patches
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1687 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1686 a-full 152633 - master-next aedec61918033e6fa66bc67e64898efe78b503ee on Typhoon-Cluster]==

<div id="152633"></div>
* '''Build ID''' - aedec61918033e6fa66bc67e64898efe78b503ee on Typhoon-Cluster
* Started at: Sat Dec 19 17:35:17 2020
* richard
* Retest with revised systemd fix and other updates
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1355 qemuarm64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1355/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1355/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1657 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1657/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1657/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1686 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1622 qemux86-64-ptest 152627 - akanavin/package-version-updates b40625c0f5be26fcc34d85eed8187051a4484b08 on Typhoon-Cluster]==

<div id="152627"></div>
* '''Build ID''' - b40625c0f5be26fcc34d85eed8187051a4484b08 on Typhoon-Cluster
* Started at: Sat Dec 19 12:02:57 2020
* akanavin
* test ptest warnings
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1622 qemux86-64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1622/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1622/steps/12/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1685 a-full 152571 - master-next 747d2e057ee738f9d1690fc447b34fbf4d62660b on Typhoon-Cluster]==

<div id="152571"></div>
* '''Build ID''' - 747d2e057ee738f9d1690fc447b34fbf4d62660b on Typhoon-Cluster
* Started at: Sat Dec 19 11:35:59 2020
* richard
* Retest master-next with elf selftest fix, systemd repro fix, kernel patches dropped, minor patch additions
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549 meta-arm] Remove layers failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549 meta-arm] Add layers_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549 meta-arm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549 meta-arm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549 meta-arm] Remove layers_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/549/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1639 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1639/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1639/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1663 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1663/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1663/steps/14/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1637 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1637/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1637/steps/14/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1656 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1656/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1656/steps/15/logs/cancelled cancelled]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548 meta-arm 152567 - master-next aad0f6cb0a801e2c1fc25ce39af1a31caab3e492 on Typhoon-Cluster]==

<div id="152567"></div>
* '''Build ID''' - aad0f6cb0a801e2c1fc25ce39af1a31caab3e492 on Typhoon-Cluster
* Started at: Sat Dec 19 08:53:54 2020
* richard
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548 meta-arm] Remove layers failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548 meta-arm] Add layers_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548 meta-arm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548 meta-arm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548 meta-arm] Remove layers_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/548/steps/19/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1267 a-quick 152522 - master f1a2ee5a18f565c2e63743af3191b6834941bde9 on Typhoon-Cluster]==

<div id="152522"></div>
* '''Build ID''' - f1a2ee5a18f565c2e63743af3191b6834941bde9 on Typhoon-Cluster
* Started at: Sat Dec 19 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1684 a-full 152468 - master-next aad0f6cb0a801e2c1fc25ce39af1a31caab3e492 on Typhoon-Cluster]==

<div id="152468"></div>
* '''Build ID''' - aad0f6cb0a801e2c1fc25ce39af1a31caab3e492 on Typhoon-Cluster
* Started at: Fri Dec 18 23:10:54 2020
* richard
* Test new patch queue
* [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3105 poky-tiny] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3105/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3105/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547 meta-arm] Remove layers failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547 meta-arm] Add layers_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547 meta-arm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547 meta-arm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547 meta-arm] Remove layers_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/547/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1020 meta-intel] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1020/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1020/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1655 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1655/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1655/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1638 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1638/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1638/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1636 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1636/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1636/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1662 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1662/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1662/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1684 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1266 a-quick 152426 - zedd/kernel-next 3b24d9b488d4ce0fe73cb39e3229da9d2b0abf3e on Typhoon-Cluster]==

<div id="152426"></div>
* '''Build ID''' - 3b24d9b488d4ce0fe73cb39e3229da9d2b0abf3e on Typhoon-Cluster
* Started at: Fri Dec 18 21:04:05 2020
* zedd
* v5.10 try2
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2825 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2825/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2825/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2825 genericx86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2825/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2825/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1725 genericx86-64-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1725/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1725/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1725 genericx86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1725/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1725/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2832 genericx86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2832/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2832/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2832 genericx86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2832/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2832/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721 qemuarm-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721/steps/11/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721 qemuarm-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1721/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839 qemuarm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839/steps/11/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839 qemuarm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2839/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797 wic] genericx86 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/14/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797 wic] genericx86 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/15/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797 wic] genericx86-64 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/20/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/20/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797 wic] genericx86-64 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/21/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2797/steps/21/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/56/builds/1282 oe-selftest] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/56/builds/1282/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/56/builds/1282/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1266 a-quick] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1265 a-quick 152380 - zedd/kernel-next 58efca2b9e820237d23deb48d593b4451fa92def on Typhoon-Cluster]==

<div id="152380"></div>
* '''Build ID''' - 58efca2b9e820237d23deb48d593b4451fa92def on Typhoon-Cluster
* Started at: Fri Dec 18 18:44:33 2020
* zedd
* v5.10-all take 1
* [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3103 poky-tiny] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3103/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3103/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1724 genericx86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1724/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1724/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720 qemuarm-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720/steps/11/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720 qemuarm-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1720/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1724 genericx86-64-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1724/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1724/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2831 genericx86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2831/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2831/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2831 genericx86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2831/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2831/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2824 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2824/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2824/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2824 genericx86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2824/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2824/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796 wic] genericx86 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/15/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796 wic] genericx86 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/16/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796 wic] genericx86-64 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/21/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/21/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796 wic] genericx86-64 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/22/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2796/steps/22/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838 qemuarm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838/steps/11/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838 qemuarm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2838/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/56/builds/1281 oe-selftest] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/56/builds/1281/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/56/builds/1281/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1265 a-quick] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1264 a-quick 152330 - zedd/kernel-next caec33dee7b200c4b446152c14f4c697045cf8da on Typhoon-Cluster]==

<div id="152330"></div>
* '''Build ID''' - caec33dee7b200c4b446152c14f4c697045cf8da on Typhoon-Cluster
* Started at: Fri Dec 18 03:11:38 2020
* zedd
* v5.10-all take 1
* [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3102 poky-tiny] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3102/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3102/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2827 non-gpl3] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2827/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2827/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2828 musl-qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2828/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2828/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2824 musl-qemux86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2824/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2824/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2802 qemux86-64-x32] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2802/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2802/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2817 qa-extras] Readonly rootfs: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2817/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2817/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795 wic] qemux86 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795 wic] genericx86 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/14/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795 wic] genericx86 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/15/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795 wic] genericx86-64 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/20/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/20/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795 wic] genericx86-64 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/21/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2795/steps/21/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2831 meta-mingw] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2831/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2831/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3059 build-appliance] BA image build: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3059/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3059/steps/13/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1723 genericx86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1723/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1723/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815 pkgman-non-rpm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815 pkgman-non-rpm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815 pkgman-non-rpm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/15/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2815/steps/15/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1723 genericx86-64-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1723/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1723/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819 qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819 qemux86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2819/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2823 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2823/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2823/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2823 genericx86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2823/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2823/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2825 no-x11] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2825/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2825/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756 qemux86-64-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756 qemux86-64-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1756/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815 qemux86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815 qemux86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2815/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713 qemux86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713 qemux86-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1713/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815 pkgman-rpm-non-rpm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815 pkgman-rpm-non-rpm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815/steps/13/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2815/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819 pkgman-deb-non-deb] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819 pkgman-deb-non-deb] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819/steps/13/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2819/steps/13/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2830 genericx86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2830/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2830/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2830 genericx86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2830/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2830/steps/13/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/94/builds/843 qemux86-64-ptest-fast] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/94/builds/843/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/94/builds/843/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837 qemuarm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837 qemuarm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2837/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2852 qa-extras2] Test logrotate: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2852/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2852/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805 qemuppc] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805 qemuppc] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2805/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144 qemuarm64-armhost] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144 qemuarm64-armhost] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2144/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/93/builds/748 qemuarm64-ptest-fast] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/93/builds/748/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/93/builds/748/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853 multilib] x86-64 lib32-img rpm: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853 multilib] x86-64 lib64-img: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853/steps/23/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853/steps/23/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853 multilib] mip64 n32: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853/steps/25/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2853/steps/25/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820 qemumips] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820 qemumips] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820/steps/13/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2820/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820 qemumips64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820 qemumips64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2820/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719 qemuarm-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719/steps/11/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719 qemuarm-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1719/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2805 qemux86-world] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2805/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2805/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818 qemuarm64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818/steps/11/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818 qemuarm64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2818/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1264 a-quick] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1263 a-quick 152286 - master 38b45cd73eb360ce6dbe441ea497044acd27d777 on Typhoon-Cluster]==

<div id="152286"></div>
* '''Build ID''' - 38b45cd73eb360ce6dbe441ea497044acd27d777 on Typhoon-Cluster
* Started at: Fri Dec 18 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1683 a-full 152226 - stable/dunfell-nut 31a9e3966f64e1d62f804e6f300dedbccc31827f on Typhoon-Cluster]==

<div id="152226"></div>
* '''Build ID''' - 31a9e3966f64e1d62f804e6f300dedbccc31827f on Typhoon-Cluster
* Started at: Thu Dec 17 16:19:53 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1753 qemux86-64-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1753/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1753/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1753/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1753/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637 oe-selftest-fedora] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1637/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661 oe-selftest-ubuntu] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1661/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635 oe-selftest-debian] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1635/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654 oe-selftest-centos] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1654/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1683 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1262 a-quick 152178 - master 38b45cd73eb360ce6dbe441ea497044acd27d777 on Typhoon-Cluster]==

<div id="152178"></div>
* '''Build ID''' - 38b45cd73eb360ce6dbe441ea497044acd27d777 on Typhoon-Cluster
* Started at: Thu Dec 17 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1682 a-full 152121 - master-next 9cda24a1aaff6e6174023dfd8f3864e337e24f0d on Typhoon-Cluster]==

<div id="152121"></div>
* '''Build ID''' - 9cda24a1aaff6e6174023dfd8f3864e337e24f0d on Typhoon-Cluster
* Started at: Wed Dec 16 18:28:44 2020
* richard
* Test master-next, systemd dropped, more patches added
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2848 qa-extras2] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2848/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2848/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1634 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1634/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1634/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1682 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1681 a-full 152067 - stable/dunfell-nut 8c651c739826fa2812c6b5f84fb91b6f99bf1b29 on Typhoon-Cluster]==

<div id="152067"></div>
* '''Build ID''' - 8c651c739826fa2812c6b5f84fb91b6f99bf1b29 on Typhoon-Cluster
* Started at: Wed Dec 16 15:48:23 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/808 meta-oe 152014 - yoe/mut d11dad295ebede21bcc75468935f667858394db7 on Typhoon-Cluster]==

<div id="152014"></div>
* '''Build ID''' - d11dad295ebede21bcc75468935f667858394db7 on Typhoon-Cluster
* Started at: Tue Dec 15 23:41:05 2020
* kraj
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/808 meta-oe] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/808/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/808/steps/12/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1261 a-quick 152015 - master 82b8dc9cccd32197a775800ee0dfc1841ef00e0c on Typhoon-Cluster]==

<div id="152015"></div>
* '''Build ID''' - 82b8dc9cccd32197a775800ee0dfc1841ef00e0c on Typhoon-Cluster
* Started at: Wed Dec 16 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1680 a-full 151960 - master-next 6c2a88144eb00735e4da656bbd7686b9134fde14 on Typhoon-Cluster]==

<div id="151960"></div>
* '''Build ID''' - 6c2a88144eb00735e4da656bbd7686b9134fde14 on Typhoon-Cluster
* Started at: Tue Dec 15 23:13:29 2020
* richard
* Retry master-next build with kern-tools dropped
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1189 qemux86-world-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1189/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1189/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016 meta-intel] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016 meta-intel] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1016/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1651 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1651/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1651/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1319 qemuarm64-ltp] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1319/steps/12/logs/stdio stdio]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1348 qemuarm64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1348/steps/12/logs/stdio stdio]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1658 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1658/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1658/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1632 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1632/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1632/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1680 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1679 a-full 151906 - master-next bcc58cf6b62e316669de3c17a713e98703b7d390 on Typhoon-Cluster]==

<div id="151906"></div>
* '''Build ID''' - bcc58cf6b62e316669de3c17a713e98703b7d390 on Typhoon-Cluster
* Started at: Tue Dec 15 23:04:32 2020
* richard
* Test new master-next patch queue
* [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2830 check-layer] Run cmds_2 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2830/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2830/steps/15/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2845 multilib] x86-64 lib32-img rpm: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2845/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2845/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3094 poky-tiny] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3094/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3094/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2819 non-gpl3] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2819/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2819/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2797 qemuppc] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2797/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2797/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2829 qemuarm] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2829/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2829/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2830 qemuarm-oecore] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2830/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2830/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2822 genericx86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2822/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2822/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1633 oe-selftest-fedora] Bitbake Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1633/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1633/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2810 qemuarm64] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2810/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2810/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2807 pkgman-rpm-non-rpm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2807/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2807/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2815 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2815/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2815/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2820 musl-qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2820/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2820/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2794 qemux86-64-x32] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2794/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2794/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1202 qemumips-alt] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1202/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1202/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1650 oe-selftest-centos] Bitbake Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1650/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1650/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2817 no-x11] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2817/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2817/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1191 qemuppc-alt] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1191/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1191/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2822 meta-mingw] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2822/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2822/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2844 qa-extras2] Test logrotate: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2844/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2844/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1715 genericx86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1715/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1715/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2797 qemux86-world] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2797/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2797/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1188 qemux86-world-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1188/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1188/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2838 beaglebone] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2838/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2838/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2816 edgerouter] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2816/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2816/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1198 edgerouter-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1198/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1198/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2816 musl-qemux86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2816/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2816/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2807 qemux86] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2807/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2807/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1711 qemuarm-alt] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1711/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1711/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2812 qemumips64] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2812/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2812/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2811 qemux86-64] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2811/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2811/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2809 qa-extras] Readonly rootfs: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2809/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2809/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1347 qemuarm64-ptest] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1347/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1347/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1318 qemuarm64-ltp] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1318/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1318/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1610 qemux86-64-ptest] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1610/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1610/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3129 buildtools] x86_64 tools: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3129/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3129/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1720 beaglebone-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1720/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1720/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2136 qemuarm64-armhost] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2136/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2136/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2811 pkgman-deb-non-deb] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2811/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2811/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1705 qemux86-alt] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1705/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1705/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/542 meta-arm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/542/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/542/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1747 qemux86-64-alt] Initialize buildhistory failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1747/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1747/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3051 build-appliance] Universe fetch: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3051/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3051/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1015 meta-intel] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1015/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1015/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1679 a-full] Sources pre-fetching: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1679/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1679/steps/13/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1679/steps/13/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/15 auh 151852 - master 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster]==

<div id="151852"></div>
* '''Build ID''' - 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster
* Started at: Tue Dec 15 01:00:00 2020
* Unknown
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/15 auh] Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/15/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/112/builds/15/steps/11/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1260 a-quick 151851 - master 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster]==

<div id="151851"></div>
* '''Build ID''' - 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster
* Started at: Tue Dec 15 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1678 a-full 151793 - stable/dunfell-nut 7756989ce74a4553e692cd067bb8ea881e00fa7e on Typhoon-Cluster]==

<div id="151793"></div>
* '''Build ID''' - 7756989ce74a4553e692cd067bb8ea881e00fa7e on Typhoon-Cluster
* Started at: Mon Dec 14 16:00:46 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1677 a-full 151736 - master-next 08a08d40a1e5e8bd26f13739ac6986c79ea1200f on Typhoon-Cluster]==

<div id="151736"></div>
* '''Build ID''' - 08a08d40a1e5e8bd26f13739ac6986c79ea1200f on Typhoon-Cluster
* Started at: Mon Dec 14 13:39:20 2020
* richard
* Retest master-next with syslinux, systemd-boot and yocto-check-layer changes dropped
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1648 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1648/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1648/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1677 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1259 a-quick 151689 - master 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster]==

<div id="151689"></div>
* '''Build ID''' - 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster
* Started at: Mon Dec 14 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1676 a-full 151635 - master-next 9bebabcf01e41ac957bd4724f18e892d8ab9d457 on Typhoon-Cluster]==

<div id="151635"></div>
* '''Build ID''' - 9bebabcf01e41ac957bd4724f18e892d8ab9d457 on Typhoon-Cluster
* Started at: Mon Dec 14 00:11:34 2020
* richard
* Test revised patch queue (systemd changes dropped, new additions)
* [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825 check-layer] Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825 check-layer] Run cmds_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825 check-layer] Run cmds_2 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825 check-layer] Run cmds_3 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825 check-layer] Sending error reports failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/20/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/39/builds/2825/steps/20/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012 meta-intel] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012 meta-intel] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1012/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1647 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1647/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1647/steps/14/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1647/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1628 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1628/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1628/steps/14/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1628/steps/14/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1630 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1630/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1630/steps/14/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1630/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1654 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1654/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1654/steps/14/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1654/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1676 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1675 a-full 151578 - akanavin/package-version-updates 08cd26dc83d649f6051bc5d4ac1eb53a92a0f6e6 on Typhoon-Cluster]==

<div id="151578"></div>
* '''Build ID''' - 08cd26dc83d649f6051bc5d4ac1eb53a92a0f6e6 on Typhoon-Cluster
* Started at: Sun Dec 13 16:23:19 2020
* akanavin
* ptest fixes/version updates

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1674 a-full 151518 - master 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster]==

<div id="151518"></div>
* '''Build ID''' - 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster
* Started at: Sun Dec 13 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1258 a-quick 151464 - master 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster]==

<div id="151464"></div>
* '''Build ID''' - 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster
* Started at: Sat Dec 12 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1673 a-full 151407 - stable/dunfell-nut a7fa1236a1bdb28c77a3759a9c4957a07ce264a4 on Typhoon-Cluster]==

<div id="151407"></div>
* '''Build ID''' - a7fa1236a1bdb28c77a3759a9c4957a07ce264a4 on Typhoon-Cluster
* Started at: Fri Dec 11 18:02:58 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1442 qemux86-64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1442/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1442/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1442/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1442/steps/10/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1442/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1673 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1672 a-full 151348 - anujm/gatesgarth 8ae61a07f12a385ee27fc82ed5938715bfb4693b on Typhoon-Cluster]==

<div id="151348"></div>
* '''Build ID''' - 8ae61a07f12a385ee27fc82ed5938715bfb4693b on Typhoon-Cluster
* Started at: Fri Dec 11 03:03:33 2020
* anujm
* test gatesgarth patch queue

==[https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/797 meta-oe 151139 - yoe/mut a51b07c50c136495d554b689dfe531f6d2ed9f40 on Typhoon-Cluster]==

<div id="151139"></div>
* '''Build ID''' - a51b07c50c136495d554b689dfe531f6d2ed9f40 on Typhoon-Cluster
* Started at: Thu Dec 10 16:38:32 2020
* kraj
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/797 meta-oe] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/797/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/797/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/797/steps/12/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1257 a-quick 151303 - master 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster]==

<div id="151303"></div>
* '''Build ID''' - 796be0593a607938aef3941372a9238b7e895446 on Typhoon-Cluster
* Started at: Fri Dec 11 01:00:00 2020
* Unknown
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2798 qa-extras] Readonly rootfs: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2798/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2798/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2798/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1257 a-quick] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1671 a-full 151249 - stable/dunfell-nut b895948a6219f4d9f58a379e2eb249cbf1508898 on Typhoon-Cluster]==

<div id="151249"></div>
* '''Build ID''' - b895948a6219f4d9f58a379e2eb249cbf1508898 on Typhoon-Cluster
* Started at: Thu Dec 10 23:00:19 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1693 qemux86-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1693/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1693/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1693/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1693/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2808 musl-qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2808/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2808/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2808/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2808/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2785 qemux86-world] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2785/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2785/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2785/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1180 qemux86-world-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1180/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1180/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1180/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1671 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1670 a-full 151193 - stable/dunfell-nut a78ea1f3b881613f9962b9a2134f103a6a46f495 on Typhoon-Cluster]==

<div id="151193"></div>
* '''Build ID''' - a78ea1f3b881613f9962b9a2134f103a6a46f495 on Typhoon-Cluster
* Started at: Thu Dec 10 19:19:52 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3116 buildtools] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3116/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3116/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3116/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3116/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3116/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3038 build-appliance] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3038/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3038/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3038/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3038/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2807 musl-qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2807/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2807/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2807/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2807/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2804 no-x11] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2804/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2804/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2804/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2804/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2803 musl-qemux86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2803/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2803/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2803/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2803/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798 qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/step3a step3a] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2798/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794 qemux86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/step3a step3a] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2794/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1309 qemuarm64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1309/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1309/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1309/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1309/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1648 oe-selftest-ubuntu] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1648/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1648/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1648/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1648/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1648/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832 multilib] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step3c step3c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step4b step4b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step4c step4c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/step5b step5b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2832/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1439 qemux86-64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1439/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1439/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1439/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1439/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1601 qemux86-64-ptest] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1601/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1601/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1601/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1601/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2799 qemumips] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2799/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2799/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2799/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2799/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1640 oe-selftest-centos] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1640/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1640/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1640/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1640/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1640/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2816 qemuarm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2816/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2816/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2816/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1698 qemuarm-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1698/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1698/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1698/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2799 qemumips64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2799/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2799/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2799/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831 qa-extras2] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step3c step3c] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step4a step4a] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step4b step4b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step4c step4c] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/step5b step5b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2831/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1338 qemuarm64-ptest] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1338/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1338/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1338/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1338/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1622 oe-selftest-debian] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1622/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1622/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1622/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1622/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1622/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2784 qemux86-world] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2784/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2784/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2784/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2784/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1182 qemuppc-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1182/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1182/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1182/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1182/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1193 qemumips-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1193/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1193/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1193/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1193/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1624 oe-selftest-fedora] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1624/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1624/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1624/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1624/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1624/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1179 qemux86-world-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1179/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1179/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1179/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797 qemuarm64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/step3a step3a] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2797/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784 qemuppc] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/step3a step3a] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2784/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1670 a-full] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1670/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1670/steps/11/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1670/steps/11/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1670/steps/11/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1669 a-full 151138 - master-next a51b07c50c136495d554b689dfe531f6d2ed9f40 on Typhoon-Cluster]==

<div id="151138"></div>
* '''Build ID''' - a51b07c50c136495d554b689dfe531f6d2ed9f40 on Typhoon-Cluster
* Started at: Thu Dec 10 16:31:14 2020
* richard
* Test new patch queue
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2797 qemux86-64] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2797/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2797/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1178 qemux86-world-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1178/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1178/steps/12/logs/errors errors]
* SWAT Follow-up - systemd update to 247 introduced a PAM Packaging issue.
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1639 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1639/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1639/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1669 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1668 a-full 151082 - master-next 30aeddb5cead1d6156aadd633683573910462644 on Typhoon-Cluster]==

<div id="151082"></div>
* '''Build ID''' - 30aeddb5cead1d6156aadd633683573910462644 on Typhoon-Cluster
* Started at: Thu Dec 10 13:48:11 2020
* richard
* Test new patch queue
* [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3079 poky-tiny] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3079/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3079/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2804 non-gpl3] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2804/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2804/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2796 pkgman-deb-non-deb] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2796/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2796/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2796 pkgman-deb-non-deb] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2796/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2796/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] Readonly rootfs: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] Readonly rootfs: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] ROOT_HOME testing: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] ROOT_HOME testing: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] Full eSDK type: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] Prep locked-sigs test: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] Test locked-sigs image: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/24/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/24/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794 qa-extras] Test locked-sigs eSDK: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/26/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2794/steps/26/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3036 build-appliance] BA image build: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3036/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3036/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779 qemux86-64-x32] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779 qemux86-64-x32] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779 qemux86-64-x32] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2779/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1599 qemux86-64-ptest] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1599/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1599/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1599 qemux86-64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1599/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1599/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1437 qemux86-64-ltp] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1437/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1437/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1437 qemux86-64-ltp] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1437/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1437/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1191 qemumips-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1191/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1191/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1191 qemumips-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1191/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1191/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2792 pkgman-rpm-non-rpm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2792/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2792/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2792 pkgman-rpm-non-rpm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2792/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2792/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1705 beaglebone-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1705/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1705/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1307 qemuarm64-ltp] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1307/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1307/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1307 qemuarm64-ltp] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1307/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1307/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2800 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2800/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2800/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796 qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796 qemux86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796 qemux86-64] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796 qemux86-64] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796 qemux86-64] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/20/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2796/steps/20/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815 qemuarm-oecore] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815 qemuarm-oecore] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815 qemuarm-oecore] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815 qemuarm-oecore] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815 qemuarm-oecore] Build targets_2 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815 qemuarm-oecore] QA targets_2 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2815/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1732 qemux86-64-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1732/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1732/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1732 qemux86-64-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1732/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1732/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1696 qemuarm-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1696/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1696/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1696 qemuarm-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1696/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1696/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792 qemux86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792 qemux86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792 qemux86] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792 qemux86] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792 qemux86] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2792/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1004 meta-intel] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1004/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1004/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] qemux86 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] qemux86 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] genericx86 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] genericx86 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] qemux86-64 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] qemux86-64 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] genericx86-64 wic: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/20/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/20/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772 wic] genericx86-64 wic: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/21/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2772/steps/21/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3114 buildtools] x86_64 tools: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3114/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3114/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3114 buildtools] aarch64 tools: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3114/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3114/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782 qemuppc] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782 qemuppc] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782 qemuppc] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782 qemuppc] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782 qemuppc] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2782/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2802 no-x11] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2802/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2802/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2802 no-x11] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2802/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2802/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2801 edgerouter] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2801/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2801/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1336 qemuarm64-ptest] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1336/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1336/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1336 qemuarm64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1336/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1336/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1646 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1646/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1646/steps/14/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1646/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2805 musl-qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2805/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2805/steps/11/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2805/steps/11/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2805/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1620 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1620/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1620/steps/14/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1620/steps/14/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1620/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2782 qemux86-world] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2782/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2782/steps/11/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2782/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1180 qemuppc-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1180/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1180/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1638 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1638/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1638/steps/14/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1638/steps/14/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1638/steps/14/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2823 beaglebone] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2823/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2823/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1187 edgerouter-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1187/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1187/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2795 qemuarm64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2795/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2795/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2801 musl-qemux86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2801/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2801/steps/12/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2801/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2801/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2807 genericx86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2807/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2807/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2807 genericx86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2807/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2807/steps/13/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1622 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1622/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1622/steps/14/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1622/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2797 qemumips] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2797/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2797/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2792 pkgman-non-rpm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2792/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2792/steps/11/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2792/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1177 qemux86-world-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1177/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1177/steps/11/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1177/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1700 genericx86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1700/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1700/steps/11/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1700/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121 qemuarm64-armhost] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121 qemuarm64-armhost] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121/steps/12/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2121/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797 qemumips64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797 qemumips64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797 qemumips64] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797 qemumips64] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797 qemumips64] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/19/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2797/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1690 qemux86-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1690/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1690/steps/12/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1690/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1700 genericx86-64-alt] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1700/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1700/steps/11/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829 qa-extras2] Test logrotate: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829 qa-extras2] Test logrotate: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829 qa-extras2] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829 qa-extras2] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829 qa-extras2] Test skeletoninit: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2829/steps/18/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531 meta-arm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531 meta-arm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531 meta-arm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/17/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/531/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32-img rpm: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32-img rpm: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32-img ipk: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32-img ipk: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32 rpm: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32 rpm: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32 ipk: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/20/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/20/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib32 ipk: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/21/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/21/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830 multilib] x86-64 lib64-img: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/23/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2830/steps/23/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814 qemuarm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814 qemuarm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814 qemuarm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814 qemuarm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814 qemuarm] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814 qemuarm] Sending error reports failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/23/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2814/steps/23/logs/cancelled cancelled]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1667 a-full 151081 - master-next YP_CHASH on Typhoon-Cluster]==
<div id="151081"></div>
* '''Build ID''' - YP_CHASH on Typhoon-Cluster
* Started at: Thu Dec 10 13:45:22 2020
* richard
* Test new patch queue

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1666 a-full 151022 - stable/dunfell-nut fa58a40cfc3661103c25a9d33989eabd550dd231 on Typhoon-Cluster]==

<div id="151022"></div>
* '''Build ID''' - fa58a40cfc3661103c25a9d33989eabd550dd231 on Typhoon-Cluster
* Started at: Thu Dec 10 04:05:29 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1256 a-quick 150979 - master f36484e88d21346357bd1fa1bef6fdcc42bed54a on Typhoon-Cluster]==

<div id="150979"></div>
* '''Build ID''' - f36484e88d21346357bd1fa1bef6fdcc42bed54a on Typhoon-Cluster
* Started at: Thu Dec 10 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1665 a-full 150921 - master f36484e88d21346357bd1fa1bef6fdcc42bed54a on Typhoon-Cluster]==

<div id="150921"></div>
* '''Build ID''' - f36484e88d21346357bd1fa1bef6fdcc42bed54a on Typhoon-Cluster
* Started at: Wed Dec 9 17:36:48 2020
* richard
* Build 3.3 M1 rc2
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2779 qemuppc] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2779/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2779/steps/13/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1665 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1664 a-full 150865 - stable/dunfell-nut b1cbb532373e45d341d43e2285ab3262046e9dca on Typhoon-Cluster]==

<div id="150865"></div>
* '''Build ID''' - b1cbb532373e45d341d43e2285ab3262046e9dca on Typhoon-Cluster
* Started at: Wed Dec 9 15:18:35 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1663 a-full 150809 - master 9826881036191be6ffba98c9bc8a86d1b852ff41 on Typhoon-Cluster]==

<div id="150809"></div>
* '''Build ID''' - 9826881036191be6ffba98c9bc8a86d1b852ff41 on Typhoon-Cluster
* Started at: Wed Dec 9 14:46:41 2020
* richard
* Build 3.3 M1
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109 buildtools] x86_64 tools: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109 buildtools] i686 tools: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109 buildtools] aarch64 tools: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109 buildtools] Publishing artefacts failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3109/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2802 genericx86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2802/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2802/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2802 genericx86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2802/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2802/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2795 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2795/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2795/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2795 genericx86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2795/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2795/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527 meta-arm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527 meta-arm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527 meta-arm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527 meta-arm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/527/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1000 meta-intel] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1000/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1000/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1000 meta-intel] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1000/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/1000/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2116 qemuarm64-armhost] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2116/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2116/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2116 qemuarm64-armhost] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2116/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2116/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789 qa-extras] Full eSDK type: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789/steps/17/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789/steps/17/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789 qa-extras] Prep locked-sigs test: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789/steps/19/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789 qa-extras] Test locked-sigs eSDK: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789/steps/26/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2789/steps/26/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818 beaglebone] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818 beaglebone] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818 beaglebone] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2818/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2825 multilib] mip64 n32: Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2825/steps/25/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2825/steps/25/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2825 multilib] mip64 n32: QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2825/steps/26/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2825/steps/26/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1618 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1618/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1618/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2796 edgerouter] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2796/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2796/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2796 edgerouter] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2796/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2796/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777 qemuppc] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777 qemuppc] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777 qemuppc] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777 qemuppc] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2777/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792 qemumips64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792 qemumips64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792 qemumips64] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792 qemumips64] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2792/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1303 qemuarm64-ltp] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1303/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1303/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1616 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1616/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1616/steps/14/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1616/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1595 qemux86-64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1595/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1595/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/92/builds/3925 buildperf-ubuntu1604] Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/92/builds/3925/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/92/builds/3925/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3900 buildperf-centos7] Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3900/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3900/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1634 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1634/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1634/steps/15/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1634/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1642 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1642/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1642/steps/14/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1642/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1332 qemuarm64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1332/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1332/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1433 qemux86-64-ltp] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1433/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1433/steps/12/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787 qemux86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787 qemux86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787 qemux86] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787 qemux86] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787 qemux86] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2787/steps/19/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790 qemuarm64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790 qemuarm64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790 qemuarm64] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790 qemuarm64] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790 qemuarm64] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2790/steps/19/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809 qemuarm] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809 qemuarm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809 qemuarm] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809 qemuarm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809 qemuarm] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2809/steps/19/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791 qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791 qemux86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791 qemux86-64] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791 qemux86-64] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791 qemux86-64] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2791/steps/19/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792 qemumips] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792 qemumips] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792 qemumips] Build targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792 qemumips] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/16/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/16/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792 qemumips] Machine oe-selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/19/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2792/steps/19/logs/cancelled cancelled]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1255 a-quick 150762 - master 64a18762f05dcaf525a2c945908b2747897a79df on Typhoon-Cluster]==

<div id="150762"></div>
* '''Build ID''' - 64a18762f05dcaf525a2c945908b2747897a79df on Typhoon-Cluster
* Started at: Wed Dec 9 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1662 a-full 150705 - stable/dunfell-nut 3d8f58075ad9a94b6a317ca2f58bb65c5c75e6f8 on Typhoon-Cluster]==

<div id="150705"></div>
* '''Build ID''' - 3d8f58075ad9a94b6a317ca2f58bb65c5c75e6f8 on Typhoon-Cluster
* Started at: Tue Dec 8 19:28:15 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1661 a-full 150651 - stable/dunfell-nut 6bec5e677ac85dc4599ef6524d5feefdc1e3a282 on Typhoon-Cluster]==

<div id="150651"></div>
* '''Build ID''' - 6bec5e677ac85dc4599ef6524d5feefdc1e3a282 on Typhoon-Cluster
* Started at: Tue Dec 8 18:44:48 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3071 poky-tiny] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3071/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3071/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/15/builds/3071/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2796 non-gpl3] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2796/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2796/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2796/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/75/builds/2796/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2771 qemux86-64-x32] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2771/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2771/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2771/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2771/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/57/builds/2771/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1431 qemux86-64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1431/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1431/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1431/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1431/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799 meta-mingw] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2799/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1724 qemux86-64-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1724/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1724/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1724/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1724/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2794 no-x11] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2794/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2794/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2794/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2794/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764 wic] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2764/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1181 edgerouter-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1181/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1181/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1181/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1181/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1330 qemuarm64-ptest] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1330/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1330/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1330/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1330/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1697 beaglebone-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1697/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1697/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1697/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1697/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3106 buildtools] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3106/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3106/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3106/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3106/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3106/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2789 qemumips64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2789/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2789/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2789/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2789/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822 multilib] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2822/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3028 build-appliance] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3028/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3028/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3028/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3028/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3028/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2789 qemumips] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2789/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2789/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2789/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2789/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2789/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/998 meta-intel] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/998/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/998/steps/10/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/998/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/998/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/998/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1174 qemuppc-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1174/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1174/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1174/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1174/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2797 musl-qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2797/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2797/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2797/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2797/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1682 qemux86-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1682/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1682/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1682/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1682/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2788 pkgman-deb-non-deb] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2788/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2788/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2788/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2788/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616 oe-selftest-fedora] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1616/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2807 qemuarm-oecore] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2807/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2807/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2807/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2807/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2774 qemux86-world] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2774/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2774/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2774/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2774/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2787 qemuarm64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2787/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2787/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2787/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2787/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614 oe-selftest-debian] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1614/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1692 genericx86-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1692/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1692/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1692/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1692/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632 oe-selftest-centos] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1632/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1692 genericx86-64-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1692/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1692/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1692/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1692/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1171 qemux86-world-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1171/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1171/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1171/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1171/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786 qa-extras] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2786/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1688 qemuarm-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1688/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1688/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1688/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1688/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2821 qa-extras2] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2821/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2821/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2821/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2821/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1593 qemux86-64-ptest] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1593/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1593/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1593/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1593/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2784 qemux86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2784/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2784/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2784/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2784/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788 qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2788/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2784 pkgman-non-rpm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2784/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2784/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2784/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2784/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640 oe-selftest-ubuntu] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1640/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2113 qemuarm64-armhost] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2113/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2113/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2113/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2113/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1301 qemuarm64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1301/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1301/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1301/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1301/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2793 musl-qemux86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2793/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2793/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2793/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2793/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2806 qemuarm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2806/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2806/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2806/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2806/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2793 edgerouter] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2793/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2793/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2793/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2793/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2784 pkgman-rpm-non-rpm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2784/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2784/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2784/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2784/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2799 genericx86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2799/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2799/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2799/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2799/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1185 qemumips-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1185/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1185/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1185/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1185/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2792 genericx86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2792/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2792/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2792/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2792/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2815 beaglebone] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2815/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2815/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2815/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2815/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2774 qemuppc] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2774/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2774/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2774/steps/10/logs/cancelled cancelled] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2774/steps/10/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1660 a-full 150595 - stable/dunfell-nut 2d64099340d3bcf0e82d744a4b27ba47389e8510 on Typhoon-Cluster]==

<div id="150595"></div>
* '''Build ID''' - 2d64099340d3bcf0e82d744a4b27ba47389e8510 on Typhoon-Cluster
* Started at: Tue Dec 8 14:47:02 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1659 a-full 150541 - master-next be4e442da1b22e4a0d85cc74f11fec4981207684 on Typhoon-Cluster]==

<div id="150541"></div>
* '''Build ID''' - be4e442da1b22e4a0d85cc74f11fec4981207684 on Typhoon-Cluster
* Started at: Tue Dec 8 09:21:04 2020
* richard
* Add missing reproducible patch and retry
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2790 genericx86] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2790/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2790/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1630 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1630/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1630/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1659 a-full] trigger failed:
* SWAT Bug filed [https://bugzilla.yoctoproject.org/show_bug.cgi?id=14147 here]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/791 meta-oe 150492 - yoe/mut 16fa0ac7947eb848111d2347b9f9017f2f85b7d8 on Typhoon-Cluster]==

<div id="150492"></div>
* '''Build ID''' - 16fa0ac7947eb848111d2347b9f9017f2f85b7d8 on Typhoon-Cluster
* Started at: Mon Dec 7 23:04:24 2020
* kraj
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/791 meta-oe] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/791/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/791/steps/12/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1254 a-quick 150494 - master 64a18762f05dcaf525a2c945908b2747897a79df on Typhoon-Cluster]==

<div id="150494"></div>
* '''Build ID''' - 64a18762f05dcaf525a2c945908b2747897a79df on Typhoon-Cluster
* Started at: Tue Dec 8 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1658 a-full 150435 - master-next 16fa0ac7947eb848111d2347b9f9017f2f85b7d8 on Typhoon-Cluster]==

<div id="150435"></div>
* '''Build ID''' - 16fa0ac7947eb848111d2347b9f9017f2f85b7d8 on Typhoon-Cluster
* Started at: Mon Dec 7 21:53:30 2020
* richard
* Retest patch queue with kea upgarde removed, repro fix added, new patches added
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1613 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1613/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1613/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1629 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1629/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1629/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1611 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1611/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1611/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1637 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1637/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1637/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1658 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1657 a-full 150377 - stable/dunfell-nut 86d6acde11c42a081166dc3019595fe80dc76847 on Typhoon-Cluster]==

<div id="150377"></div>
* '''Build ID''' - 86d6acde11c42a081166dc3019595fe80dc76847 on Typhoon-Cluster
* Started at: Mon Dec 7 16:54:34 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783 qemumips] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/step3a step3a] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2783/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783 qemumips64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/step3a step3a] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2783/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1657 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1656 a-full 150324 - gatesgarth 943ef2fad8428f002850e3655a3312e13d0dcb2c on Typhoon-Cluster]==

<div id="150324"></div>
* '''Build ID''' - 943ef2fad8428f002850e3655a3312e13d0dcb2c on Typhoon-Cluster
* Started at: Mon Dec 7 16:25:56 2020
* richard
* Build 3.2.1 rc2

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1655 a-full 150268 - stable/dunfell-nut 9354a08235f211e30de79009d308803b7bc4bb27 on Typhoon-Cluster]==

<div id="150268"></div>
* '''Build ID''' - 9354a08235f211e30de79009d308803b7bc4bb27 on Typhoon-Cluster
* Started at: Mon Dec 7 15:28:48 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3099 buildtools] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3099/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3099/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3099/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3099/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/20/builds/3099/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3021 build-appliance] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3021/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3021/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3021/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3021/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2781 pkgman-deb-non-deb] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2781/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2781/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2781/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2781/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2767 qemux86-world] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2767/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2767/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/52/builds/2767/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2777 pkgman-non-rpm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2777/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2777/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2777/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1425 qemux86-64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1425/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1425/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1425/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/95/builds/1425/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2814 qa-extras2] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2814/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2814/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/72/builds/2814/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1634 oe-selftest-ubuntu] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1634/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1634/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1634/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1634/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1634/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2799 qemuarm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2799/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2799/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2799/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2800 qemuarm-oecore] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2800/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2800/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2800/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2800/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/47/builds/2800/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792 meta-mingw] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792/steps/10/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/89/builds/2792/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1685 genericx86-64-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1685/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1685/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/104/builds/1685/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1675 qemux86-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1675/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1675/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1675/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2779 qa-extras] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2779/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2779/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/69/builds/2779/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2808 beaglebone] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2808/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2808/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2808/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1179 qemumips-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1179/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1179/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1179/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2785 genericx86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2785/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2785/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2785/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2780 qemuarm64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2780/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2780/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2780/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1681 qemuarm-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1681/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1681/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1681/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2767 qemuppc] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2767/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2767/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2767/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2757 wic] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2757/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2757/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2757/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2757/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/58/builds/2757/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1587 qemux86-64-ptest] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1587/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1587/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1587/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2781 qemumips] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2781/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2781/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2781/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1610 oe-selftest-fedora] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1610/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1610/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1610/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1610/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1610/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1626 oe-selftest-centos] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1626/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1626/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1626/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1626/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1626/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2781 qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2781/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2781/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2781/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2781/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2106 qemuarm64-armhost] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2106/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2106/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2106/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1717 qemux86-64-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1717/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1717/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1717/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1685 genericx86-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1685/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1685/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/103/builds/1685/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2786 edgerouter] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2786/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2786/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2786/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1175 edgerouter-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1175/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1175/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/111/builds/1175/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2781 qemumips64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2781/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2781/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2781/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2777 qemux86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2777/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2777/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2777/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815 multilib] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/step1c step1c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/step2c step2c] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/step3b step3b] [https://autobuilder.yoctoproject.org/typhoon/#builders/44/builds/2815/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1324 qemuarm64-ptest] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1324/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1324/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/82/builds/1324/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1295 qemuarm64-ltp] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1295/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1295/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1295/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1168 qemuppc-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1168/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1168/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1168/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1165 qemux86-world-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1165/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1165/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/108/builds/1165/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2777 pkgman-rpm-non-rpm] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2777/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2777/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2777/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/992 meta-intel] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/992/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/992/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/992/steps/10/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/992/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1608 oe-selftest-debian] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1608/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1608/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1608/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1608/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1608/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2787 no-x11] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2787/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2787/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/40/builds/2787/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2790 musl-qemux86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2790/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2790/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2790/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2786 musl-qemux86] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2786/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2786/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/64/builds/2786/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2792 genericx86-64] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2792/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2792/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2792/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1690 beaglebone-alt] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1690/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1690/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/106/builds/1690/steps/10/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1655 a-full] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1655/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1655/steps/11/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1655/steps/11/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1655/steps/11/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654 a-full 150211 - gatesgarth 333f24caec0bb498804dd77cbe762f2f4d9b2225 on Typhoon-Cluster]==

<div id="150211"></div>
* '''Build ID''' - 333f24caec0bb498804dd77cbe762f2f4d9b2225 on Typhoon-Cluster
* Started at: Mon Dec 7 09:00:17 2020
* richard
* Build 3.2.1
* [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3020 build-appliance] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3020/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3020/steps/10/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3020/steps/10/logs/step2b step2b] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3020/steps/10/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/23/builds/3020/steps/10/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633 oe-selftest-ubuntu] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/step2d step2d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/step2a step2a] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/step3d step3d] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1633/steps/10/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654 a-full] run-config failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654/steps/11/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654/steps/11/logs/step1b step1b] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654/steps/11/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1654 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1253 a-quick 150165 - master 64a18762f05dcaf525a2c945908b2747897a79df on Typhoon-Cluster]==

<div id="150165"></div>
* '''Build ID''' - 64a18762f05dcaf525a2c945908b2747897a79df on Typhoon-Cluster
* Started at: Mon Dec 7 01:00:00 2020
* Unknown
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2775 pkgman-non-rpm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2775/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2775/steps/15/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2775/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1253 a-quick] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1653 a-full 150111 - master-next 1c790e272920e354c270eeaa1fe4f185ce37f60d on Typhoon-Cluster]==

<div id="150111"></div>
* '''Build ID''' - 1c790e272920e354c270eeaa1fe4f185ce37f60d on Typhoon-Cluster
* Started at: Sun Dec 6 23:23:23 2020
* richard
* Test new patch queue
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1608 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1608/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1608/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1624 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1624/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1624/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1632 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1632/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1632/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1606 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1606/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1606/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1653 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1652 a-full 150048 - master 7d7197b28226a9ab39babf5be5c4aa92473a2e60 on Typhoon-Cluster]==

<div id="150048"></div>
* '''Build ID''' - 7d7197b28226a9ab39babf5be5c4aa92473a2e60 on Typhoon-Cluster
* Started at: Sun Dec 6 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1252 a-quick 149998 - master 7d7197b28226a9ab39babf5be5c4aa92473a2e60 on Typhoon-Cluster]==

<div id="149998"></div>
* '''Build ID''' - 7d7197b28226a9ab39babf5be5c4aa92473a2e60 on Typhoon-Cluster
* Started at: Sat Dec 5 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1651 a-full 149939 - akanavin/package-version-updates b0774b94a37346e0fe63f6823a6bc574a2dc2587 on Typhoon-Cluster]==

<div id="149939"></div>
* '''Build ID''' - b0774b94a37346e0fe63f6823a6bc574a2dc2587 on Typhoon-Cluster
* Started at: Fri Dec 4 14:13:37 2020
* akanavin
* package version updates
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783 musl-qemux86-64] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783/steps/11/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783 musl-qemux86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/45/builds/2783/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1604 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1604/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1604/steps/14/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1604/steps/14/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1583 qemux86-64-ptest] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1583/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/81/builds/1583/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1291 qemuarm64-ltp] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1291/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/96/builds/1291/steps/12/logs/cancelled cancelled]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1650 a-full 149882 - master-next aa3a44f4a015feebcf340286f90d236819a6e732 on Typhoon-Cluster]==

<div id="149882"></div>
* '''Build ID''' - aa3a44f4a015feebcf340286f90d236819a6e732 on Typhoon-Cluster
* Started at: Fri Dec 4 05:04:48 2020
* richard
* Retest master-next with container selftest failure fixup

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1251 a-quick 149838 - master 7d7197b28226a9ab39babf5be5c4aa92473a2e60 on Typhoon-Cluster]==

<div id="149838"></div>
* '''Build ID''' - 7d7197b28226a9ab39babf5be5c4aa92473a2e60 on Typhoon-Cluster
* Started at: Fri Dec 4 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1649 a-full 149783 - master-next 804cfd0231281662ce8958195526665cad6500e7 on Typhoon-Cluster]==

<div id="149783"></div>
* '''Build ID''' - 804cfd0231281662ce8958195526665cad6500e7 on Typhoon-Cluster
* Started at: Thu Dec 3 23:11:06 2020
* richard
* Test master-next with new patches and some fixes
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1628 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1628/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1628/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1602 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1602/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1602/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1604 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1604/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1604/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1620 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1620/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1620/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1649 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3874 buildperf-centos7 149723 - master 332159dd3e2621bf7460a85dbb629febd17d1154 on Typhoon-Cluster]==

<div id="149723"></div>
* '''Build ID''' - 332159dd3e2621bf7460a85dbb629febd17d1154 on Typhoon-Cluster
* Started at: Thu Dec 3 15:00:00 2020
* Unknown
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3874 buildperf-centos7] Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3874/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/91/builds/3874/steps/12/logs/errors errors]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/786 meta-oe 149725 - yoe/mut aa698defff0452381aa4db78d120a12efbed61d4 on Typhoon-Cluster]==

<div id="149725"></div>
* '''Build ID''' - aa698defff0452381aa4db78d120a12efbed61d4 on Typhoon-Cluster
* Started at: Thu Dec 3 17:32:53 2020
* kraj
* No reason given
* [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/786 meta-oe] Build targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/786/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/786/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/88/builds/786/steps/12/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1648 a-full 149726 - stable/dunfell-nut b268afcdd8b344088af4b65dfb136a76a08a9cae on Typhoon-Cluster]==

<div id="149726"></div>
* '''Build ID''' - b268afcdd8b344088af4b65dfb136a76a08a9cae on Typhoon-Cluster
* Started at: Thu Dec 3 17:48:53 2020
* sakoman
* steve - stable/dunfell-nut testing

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1647 a-full 149669 - master-next aa698defff0452381aa4db78d120a12efbed61d4 on Typhoon-Cluster]==

<div id="149669"></div>
* '''Build ID''' - aa698defff0452381aa4db78d120a12efbed61d4 on Typhoon-Cluster
* Started at: Thu Dec 3 12:24:12 2020
* richard
* Retest with nettools split reverted
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1600 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1600/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1600/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1618 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1618/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1618/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1602 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1602/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1602/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1626 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1626/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1626/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1647 a-full] trigger failed:
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1647 a-full] Source Mirror Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1647/steps/23/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1647/steps/23/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1647/steps/23/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1646 a-full 149615 - akanavin/package-version-updates 85b302dd1e4727ec1ce94079b526fed7c8fc3e64 on Typhoon-Cluster]==

<div id="149615"></div>
* '''Build ID''' - 85b302dd1e4727ec1ce94079b526fed7c8fc3e64 on Typhoon-Cluster
* Started at: Thu Dec 3 10:41:44 2020
* akanavin
* package version updates

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1645 a-full 149559 - akanavin/world-repro fdcf7f4b305db70cb4f3b432c8761d323cfce343 on Typhoon-Cluster]==

<div id="149559"></div>
* '''Build ID''' - fdcf7f4b305db70cb4f3b432c8761d323cfce343 on Typhoon-Cluster
* Started at: Thu Dec 3 07:49:38 2020
* akanavin
* testing world reproducibility
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1616 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1616/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1616/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1600 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1600/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1600/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1624 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1624/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1624/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1598 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1598/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1598/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1645 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/85/builds/1250 a-quick 149514 - master 0ac99625bf2c8a19d4ee746dc13e9c6b2e1956e2 on Typhoon-Cluster]==

<div id="149514"></div>
* '''Build ID''' - 0ac99625bf2c8a19d4ee746dc13e9c6b2e1956e2 on Typhoon-Cluster
* Started at: Thu Dec 3 01:00:00 2020
* Unknown
* No reason given

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644 a-full 149457 - stable/dunfell-nut 5070a3a8f4ffe39ad1e481458097fc5c62e08066 on Typhoon-Cluster]==

<div id="149457"></div>
* '''Build ID''' - 5070a3a8f4ffe39ad1e481458097fc5c62e08066 on Typhoon-Cluster
* Started at: Wed Dec 2 22:45:57 2020
* sakoman
* steve - stable/dunfell-nut testing
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644 a-full] run-config_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644/steps/14/logs/step1a step1a] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644/steps/14/logs/step1d step1d] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644/steps/14/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1644/steps/14/logs/warnings warnings]

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1643 a-full 149399 - akanavin/package-version-updates 65d17d9749ba4be67595e561422fd5b522cafc92 on Typhoon-Cluster]==

<div id="149399"></div>
* '''Build ID''' - 65d17d9749ba4be67595e561422fd5b522cafc92 on Typhoon-Cluster
* Started at: Wed Dec 2 20:32:59 2020
* akanavin
* package version updates
* [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2761 pkgman-rpm-non-rpm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2761/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2761/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/61/builds/2761/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/980 meta-intel] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/980/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/100/builds/980/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1167 qemumips-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1167/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1167/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/102/builds/1167/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1665 qemuarm-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1665/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1665/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/110/builds/1665/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1701 qemux86-64-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1701/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1701/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/109/builds/1701/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1156 qemuppc-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1156/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1156/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/107/builds/1156/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761 pkgman-non-rpm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761 pkgman-non-rpm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761/steps/15/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761/steps/15/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/76/builds/2761/steps/15/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2765 qemumips64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2765/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2765/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/74/builds/2765/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2751 qemuppc] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2751/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2751/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/63/builds/2751/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2792 beaglebone] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2792/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/65/builds/2792/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/507 meta-arm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/507/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/507/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/507 meta-arm] QA targets_1 failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/507/steps/18/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/113/builds/507/steps/18/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2776 genericx86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2776/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/37/builds/2776/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2770 edgerouter] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2770/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/62/builds/2770/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1598 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1598/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1598/steps/14/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1598/steps/14/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1614 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1614/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1614/steps/14/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1614/steps/14/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2764 qemuarm64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2764/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2764/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/42/builds/2764/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2783 qemuarm] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2783/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2783/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/53/builds/2783/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2090 qemuarm64-armhost] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2090/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2090/steps/12/logs/errors errors] [https://autobuilder.yoctoproject.org/typhoon/#builders/97/builds/2090/steps/12/logs/warnings warnings]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2765 pkgman-deb-non-deb] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2765/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2765/steps/13/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/50/builds/2765/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1659 qemux86-alt] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1659/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1659/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/101/builds/1659/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2761 qemux86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2761/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2761/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/59/builds/2761/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2765 qemumips] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2765/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2765/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/60/builds/2765/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2769 genericx86] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2769/steps/13/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/48/builds/2769/steps/13/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2765 qemux86-64] QA targets failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2765/steps/12/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2765/steps/12/logs/warnings warnings] [https://autobuilder.yoctoproject.org/typhoon/#builders/73/builds/2765/steps/12/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1643 a-full] trigger failed:

==[https://autobuilder.yoctoproject.org/typhoon/#builders/83/builds/1642 a-full 149341 - akanavin/world-repro f020c3cdd0af490913169f2738d46ce9f1cedde4 on Typhoon-Cluster]==

<div id="149341"></div>
* '''Build ID''' - f020c3cdd0af490913169f2738d46ce9f1cedde4 on Typhoon-Cluster
* Started at: Wed Dec 2 10:41:28 2020
* akanavin
* testing world reproducibility
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1595 oe-selftest-debian] Bitbake Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1595/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1595/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1595 oe-selftest-debian] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1595/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/80/builds/1595/steps/14/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1613 oe-selftest-centos] Bitbake Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1613/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1613/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1613 oe-selftest-centos] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1613/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/1613/steps/14/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1597 oe-selftest-fedora] Bitbake Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1597/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1597/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1597 oe-selftest-fedora] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1597/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/1597/steps/14/logs/cancelled cancelled]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1621 oe-selftest-ubuntu] Bitbake Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1621/steps/11/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1621/steps/11/logs/errors errors]
* [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1621 oe-selftest-ubuntu] OE Selftest: Run cmds failed: [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1621/steps/14/logs/stdio stdio] [https://autobuilder.yoctoproject.org/typhoon/#builders/87/builds/1621/steps/14/logs/cancelled cancelled]

==Archived Logs==

Archives of older logs:

* [[BuildLog/Archive/0001]]
* [[BuildLog/Archive/0002]]
* [[BuildLog/Archive/0003]]
* [[BuildLog/Archive/0004]]
* [[BuildLog/Archive/0005]]
* [[BuildLog/Archive/0006]]
* [[BuildLog/Archive/0007]]
* [[BuildLog/Archive/0008]]
* [[BuildLog/Archive/0009]]
* [[BuildLog/Archive/0010]]
* [[BuildLog/Archive/0011]]
* [[BuildLog/Archive/0012]]
* [[BuildLog/Archive/0013]]

User:PaulEggleton

2020-11-09T18:59:06Z

PaulEggleton: Created page with "== About == Software developer based in Auckland, NZ * Involved with OpenEmbedded & Yocto Project for some years, commit access to OE since late 2007. * Working for Microso..."

== About ==

Software developer based in Auckland, NZ

* Involved with OpenEmbedded & Yocto Project for some years, commit access to OE since late 2007.
* Working for Microsoft

== Contact ==

* E-mail: bluelightning@bluelightning.org or paul.eggleton@microsoft.com
* IRC: bluelightning (in #oe and #yocto on freenode)

Yocto Build Failure Swat Team

2020-11-09T18:55:23Z

PaulEggleton: /* Members */

== Overview ==

The role of the SWAT team is to monitor the autobuilder and investigate all failures to ensure that they are logged and brought to the attention of the appropriate owner.

All builds that are run on the [https://autobuilder.yoctoproject.org public autobuilder] are important for the Yocto Project, whether they be a post-merge validation run (for master or a release branch) or a pre-merge test build (for master-next, ross/mut, stable/* and others). SWAT doesn't cover company-internal autobuilders.

Every build should be monitored by the SWAT team unless the [[BuildLog]] entry for that build indicates otherwise. SWAT is opt-out by whomever triggers a build on the autobuilder, not opt-in.

SWAT isn't responsible for resolving any issues encountered on the autobuilder. Their focus is on performing minimal analysis of a failure in order to ensure that it is logged and brought to the attention of a appropriate owner, a process we'll refer to as pre-triage.

== Roles ==

Active member: the currently active member of the SWAT team is expected to monitor the autobuilder and pre-triage failures in a timely fashion. Team members are active for one week at a time and rotation is usually simple round robin through the members list. If for some reason the next person isn't available then they can be defer a week until they are.

SWAT Chair: the SWAT chair provides backup cover for the active member and is a first point of contact for SWAT. [[User:RossBurton | Ross Burton]], Armin Kuster and Richard Purdie are the SWAT Chair people.

SWAT Facilitator: the SWAT facilitator is responsible for managing the rotation process. [[User:Stephen_K._Jolley | Stephen K. Jolley]] is the current SWAT Facilitator.

== Process ==

The [[BuildLog]] wiki page is automatically updated by the autobuilder when a new build is triggered. This often includes guidance for SWAT (the "Reason" field when triggering the build) such as to ignore it (if the build is expected to break and the owner is monitoring themselves) or a request to report failures straight to a specific person (if the build only contains changes from a single person, such as a GCC upgrade). Unless when told otherwise, the usual process is as follows:

For builds against master or a release branch, any issues observed should be [[#Filing_bugs | filed in Bugzilla]].

For builds against other branches (master-next, ross/mut, -next branches for stable releases, etc.), attempt to identify what patch in the branch is likely responsible for the failure. For example, if <tt>wget</tt> fails with <tt>libgnutls</tt> errors and there is a GnuTLS upgrade in the branch, that is the likely candidate. If a patch can be identified that isn't also in master or release branch, reply on the mailing list with the failure details. If it isn't obvious which patch is responsible for the failure then [[#Filing_bugs | file a bug]] and ensure the branch owner is either the assignee or on the CC list.

'''If in doubt, file a bug'''. All observed errors must be actioned unless a patch has already been sent for the issue, in which case please make note of this in the [[BuildLog]].

If the issue is in the infrastructure or autobuilder itself then file a bug against , infrastructure bugs should be assigned to [[User:Halstead| Michael Halstead]] and autobuilder logic bugs to [[User:Rpurdie | Richard Purdie]].

The results of pre-triage for an issue should be added to the corresponding entry in the [[BuildLog]], including a link to the resolution (patch name, bug link, etc) and a brief summary of the issue. Every issue should be added to the build log so it acts as a build status report.

Note that some builds, in particular the "perf" builds are not listed on [[BuildLog]] unless the build fails (to try and reduce noise on the log). Failures in performance test builds should be handled like any other build.

The net result is all failures listed in [[BuildLog]] should have outcomes listed against them from the person on SWAT at the time.

=== Filing bugs ===

When filing the bug two things are required:
* A link to the build failure. This can either be the build page (such as https://autobuilder.yoctoproject.org/typhoon/#/builders/34/builds/168) or the [http://errors.yoctoproject.org/Errors/ error reports] page (such as http://errors.yoctoproject.org/Errors/Details/199667/).
* The error itself. Trim the log down to just the error and any relevant context in the bug description, and also attach the complete log file. Autobuilder logs are not persistent so the full log must be attached.

=== Process summary ===

* Monitor builds via one or more of:
** the autobuilder: [https://autobuilder.yoctoproject.org/typhoon/ main page], [https://autobuilder.yoctoproject.org/typhoon/#/console console view]. Orange builds have warnings, red builds failed with errors.
** the [http://errors.yoctoproject.org/Errors/ Error Reports] web page which has an entry for each recipe that fails. A link to the appropriate search is on the autobuilder's Console View.
** the [[BuildLog]] wiki page. This has links to each build log that wasn't successful.
** the [https://lists.yoctoproject.org/listinfo/yocto-builds yocto-builds] mailing list. This gets a mail for every unsuccessful build.
* Pre-triage each failure:
** File a bug ''or'' respond to a patch ''or'' note known issues
** Update the [[BuildLog]] with the result of pre-triage, linking to the resolution where possible.

== Questions / Contact ==

If you have queries about the SWAT process you may reach out to the SWAT Facilitator [[User:Stephen_K._Jolley | Stephen K. Jolley]] or the SWAT Chair [[User:RossBurton | Ross Burton]].

== Members ==

[[User:Leonardo_Sandoval | Leo Sandoval]]

[[User:SaulWold | Saul Wold]]

[[User:PaulEggleton | Paul Eggleton]]

Technical FAQ

2020-07-09T21:01:45Z

PaulEggleton: Add why not root question

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
| '''NOTE:''' This is currently a draft. Not sure where this should end up but I've been gathering these based on my interactions with people on IRC and email over the years. - [[User:PaulEggleton|PaulEggleton]] ([[User talk:PaulEggleton|talk]]) 21:13, 27 June 2016 (PDT)
|}

== Basics ==

=== How do I figure out which version/codename/bitbake version matches up with which? ===

There is a table in the [http://wiki.yoctoproject.org/wiki/Releases Releases page] on the Yocto Project wiki.

=== How do I control what's in the final image? ===

Each image is defined by its own recipe, and that recipe specifies a list of packages that the image should contain. See [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Customising Images] within the Yocto Project development manual for further details.

Note: if you're doing anything more than basic experimentation / testing then you almost certainly should create your own image recipe rather than using one of the example images e.g. core-image-minimal - though you can certainly start by copying one of the example images. This way you have easier control over what goes into the image.

=== Where do I find build logs? ===

For the overall build, the output of bitbake gets logged to tmp/log/cooker/<machine>.

For each individual recipe, there is a "temp" directory under the work directory for the recipe that contains log.<taskname> and run.<taskname> files - the logs and the runfiles respectively. Within the build system this directory is pointed to by the T variable, so if you need to you can find it by using <code>bitbake -e</code>:

bitbake -e <recipename> | grep ^T=

=== How do I add a patch to a recipe? ===

There are two concerns - how the recipe can fetch the patch and how it can be applied. For fetching, patch files are usually placed in a subdirectory next to the recipe; by default this directory should be named "files" or the the recipe name without any class prefix or suffix (for example for both "xyz" and "xyz-native" the subdirectory would be "xyz"). A pointer to it then needs to be added to <code>SRC_URI</code> within the recipe, which usually takes the form <code>file://<patchname>.patch</code> - i.e. just the filename, no path. If more than one subdirectory needs to be stripped off the paths in the patch (i.e. you need more than the equivalent of the -p1 option to the patch command) then you can add <code>;striplevel=<number></code> to the end of the patch entry in SRC_URI (without any spaces).

As with any modification, if the patch you are applying is a customisation that you do not intend to send to be incorporated in the layer you are modifying, then instead of adding the patch to the recipe directly then you should consider applying it in a bbappend within your own custom layer. This makes things easier if you later want to update the layer in question and the recipe has been modified upstream - you avoid effectively forking the layer.

The <code>devtool</code> utility can help you modify the sources for a recipe and create a patch - basically <code>devtool modify</code>, edit the sources, commit the changes with <code>git commit</code>, then <code>devtool finish</code> (or <code>devtool update-recipe</code> in versions older than 2.2). Since <code>devtool modify</code> gives you a git tree to work with, you can of course use something like <code>git am</code> to apply existing patches this way. For more details see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#devtool-use-devtool-modify-to-enable-work-on-code-associated-with-an-existing-recipe Use devtool modify to Enable Work on Code Associated with an Existing Recipe] within the Yocto Project Development manual.

=== What does "native" mean? ===

The "native" suffix identifies recipes (and variants of recipes) that produce files intended for the build host, as opposed to the target machine. This is usually for tools that are needed during the build process (such as automake).

=== What does "nativesdk" mean? ===

The "nativesdk" prefix identifies recipes (and variants of recipes) that produce files intended for the host portion of the standard SDK, or for things which are constructed like an SDK such as buildtools-tarball. These are built for SDKMACHINE which may or may not be the same architecture as the build host.

=== I have two recipes and one needs to access files provided by another - how can that work? ===

Instead of providing direct access from a recipe to another's build tree (which wouldn't be practical with OpenEmbedded since the build tree (or "workdir") is temporary), we create a "sysroot" where files that are intended to be shared between recipes get copied. The sysroot is managed by the build system and you should not copy files in there directly - instead, you install files under ${D} as normal during do_install and then the build system will copy a subset of those to the sysroot. There is a seperate sysroot for each machine being built for. In a recipe you can get the path of the sysroot and various standard directories under it using the STAGING_* variables.

Often, for commonly-used build systems such as autotools and cmake you don't need to worry about these details - those systems and the environment that OpenEmbedded sets up for them will ensure that files get installed and picked up in the correct locations. However if the software your recipe is building has custom build scripts / makefiles and it takes shortcuts that don't account for cross-compilation or the use of a sysroot, then you will need to make appropriate adjustments.

=== How do I enable package management in the final image? ===

Add <code>package-management</code> to <code>IMAGE_FEATURES</code> (or <code>EXTRA_IMAGE_FEATURES</code>). You should then be able to use dnf/rpm, opkg, or apt-get/dpkg from the running system depending on the packaging format you have selected through PACKAGE_CLASSES. For more information see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-runtime-package-management Using Runtime Package Management] in the Yocto Project Development manual.

=== What do ?=, ??=, := etc. do within a recipe/config file? ===

See the [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#basic-syntax Basic Syntax section of the BitBake manual] for details.

== Layers ==

See http://www.openembedded.org/Layers_FAQ

== Troubleshooting ==

=== I've created a recipe but it's not showing up in my image, what's going on? ===

Creating a recipe (or adding a layer to your configuration with a desired recipe in it) only makes it available to the build system, it doesn't change what goes into the image. For that, see [[#How do I control what's in the final image?|How do I control what's in the final image?]] above.

=== I set a variable but it doesn't seem to be having an effect, how do I fix this? ===

First, double-check that you haven't misspelled the variable name.

The main tool to help troubleshoot any variable-related issue is <code>bitbake -e</code> - this lists all the variables and the complete history of how each one has been set (use <code>bitbake -e <recipename></code> if you're dealing with issues in a variable value within a recipe as opposed to the global level). Usually it's best to pipe this through <code>less</code> so you can easily see the history - within less you can press / to search for the variable name. Often you will be dealing with the behaviour of a variable within the context of a specific recipe, so specify that recipe on the <code>bitbake -e</code> command line to get the variables as set within the context of the recipe rather than the global context.

If you're setting a variable in a bbappend, double-check that the bbappend is actually being applied - see the next question.

=== I've created a bbappend for a recipe but what I'm setting there isn't having any effect, how do I fix this? ===

Here are some things to check:

# Check if the layer the bbappend is in is listed in <code>bitbake-layers show-layers</code>. If it isn't, you need to edit your bblayers.conf and ensure the path to the layer is included in the BBLAYERS value
# Check that the bbappend is being picked up by running <code>bitbake-layers show-appends</code> - if your bbappend file isn't listed, it could be named incorrectly (such that it doesn't match the recipe name) or it may be that the BBFILES value in the conf/layer.conf for the layer containing the bbappend file doesn't include an expression that will match the bbappend files.
# If there are multiple versions of the recipe you have bbappended, it could be that the actual recipe being built is a different version than the one you have bbappended. <code>bitbake-layers show-recipes <recipename></code> will list all the versions, with the first one listed being the one that will be built. If this is the case there are several different solutions to this - (a) Rename your bbappend to match the version being built, (b) use a % wildcard in your bbappend so it will apply to any version, (c) set <code>PREFERRED_VERSION_<recipename></code> in the configuration to select a the version you want to be built.
# Finally, as with any other issue with setting variables, use <code>bitbake -e <recipename> | less</code> and search with <code>/</code> to see the history of how the variable has been set - you may find that the value you're trying set is being overridden.

=== I'm getting warnings that a recipe is tainted - what does this mean? ===

Usually this happens because you have used I used bitbake's <code>-f</code> or <code>-C</code> option to force a task to re-execute. The assumption is that if you forced a task, it is possible that a rebuild from scratch would not include whatever changes you made that necessitated forcing (e.g. if you modified the source in the work directory for the recipe and then ran <code>bitbake -c compile -f</code>). Generally, forcing a task should be reserved for situations where the build system has failed to detect a change you made rather than for everyday usage - if you're finding yourself needing to do it regularly then either there's a bug, you're doing something wrong, or perhaps you're using <code>-f</code> or <code>-C</code> when it's not really needed. Running <code>bitbake -c clean</code> on the recipe will get rid of the taint flag.

There is one other situation where we apply a taint, and that is <code>bitbake -c menuconfig</code> on the kernel (or some other kconfig-using recipe). In this case, the configuration has been saved into the work directory for the kernel, but that is temporary - any rebuild from scratch will use the default configuration, so it is a reminder that you need to take the configuration and apply it back to the metadata and then run <code>bitbake -c clean</code> on the kernel recipe.

=== I'm fetching from a git repository over ssh / http / https but it's not fetching properly, how do I fix this? ===

Bitbake expects the prefix of entries in SRC_URI to specify the fetcher to be used, not the actual protocol. Thus, instead of:

# This will NOT work
SRC_URI = "<nowiki>https://git.example.com/repository</nowiki>"

You should specify:

# This is better
SRC_URI = "<nowiki>git://git.example.com/repository;protocol=https</nowiki>"

The same applies for ssh and of course http.

=== I tried bitbake <some target package name> that I know exists and it told me that nothing PROVIDES this...? ===

There are two namespaces that bitbake concerns itself with - recipe names (a.k.a. build time targets) and package names (a.k.a. runtime targets). You can specify a build time target on the bitbake command line, but not a runtime target; you need to find the recipe that provides the package you are trying to build and build that instead (or simply add that package to your image and build the image). In current versions bitbake will at least tell you which recipes have matching or similar-sounding runtime provides (RPROVIDES) so that you'll usually get a hint on which recipe you need to build.

=== I've included a package in my image but files I expect to be there are missing, what's the issue? ===

Check the simple stuff: verify that the package is really in the image - look at the manifest file next to the image to ensure the package is listed. Also if you're flashing the image, double-check that you did indeed flash the right image and if there are multiple partitions / storage devices on your board or device that you're booting the one that you think you are.

Once you're sure of the above, it may be a matter of the package splitting - a lot of recipes split less commonly used components out to separate packages, so it's possible that the files you are looking for are in a different package. You can look at the recipe for this (look for PACKAGES and FILES statements) or assuming the recipe has been built, you can use <code>oe-pkgdata-util list-pkgs -p <recipename></code> and <code>oe-pkgdata-util list-pkg-files</code> to inspect the packages provided by the recipe and the files they contain. Once you find the right package you can add it to your image.

=== I'm required to set LIC_FILES_CHKSUM but the software I'm building doesn't have a license statement, what do I do? ===

Ideally, all software should come with some kind of license statement so that the terms of distribution are clearly stated (especially if its source code is made publicly available); if not a text file describing the license then at the very least a line or two in the accompanying documentation, README file or source header comments. Assuming there is a license statement somewhere but not in a form you can point to with LIC_FILES_CHKSUM as part of the source tree, you can point LIC_FILES_CHKSUM to one of the generic license files in ${COMMON_LICENSE_DIR} (meta/files/common-licenses/), or alternatively you can include a file containing the license statement in a "files" subdirectory next to the recipe (or subdirectory named the same as the recipe - see how such files are handled in other recipes), point to it in SRC_URI using file://, then add it to LIC_FILES_CHKSUM. It is worth noting however that LIC_FILES_CHKSUM is intended to give you a warning if upstream changes its license terms when you do an upgrade of the recipe, and by pointing it to this common license file that is part of the metadata, that mechanism will not function. You may wish to consider encouraging the upstream provider of the software your recipe is building to follow best practices and include a proper license statement, so that you can point to it in a future version. At minimum if you do use such workarounds, you will need to take extra care when upgrading the recipe in future in case the upstream provider changes the license terms.

If there really is no license stated at all anywhere for the software (and this is unfortunately not uncommon on github, for example) then you should really contact upstream - if there's no license, then technically you really shouldn't be distributing it until that's clarified with the original author(s).

=== I am getting a package QA error / warning when building a recipe, how do I solve it? ===

There are some general and specific recommendations in the [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-errors-and-warnings QA Errors and Warnings] section of the Yocto Project Reference Manual.

=== I am getting "taskhash mismatch" errors, what does this mean and how do I fix it? ===

Bitbake parses the metadata (recipes, classes and configuration) repeatedly during its operation, and this error means that the result of parsing changed between one parse and the next. Two situations that can cause this:
# One of the parsed files changed in between e.g. you edited a recipe or performed a git operation (e.g. git checkout) during the build. '''Do not make changes to the metadata while a build is running.''' If you run the build again the error should not recur.
# Alternatively, there is something in the metadata that results in a variable expanding to a different value each time it is parsed. This is often something time-related e.g. a timestamp which is calculated every time an expression is expanded. The solution is to ensure the value is calculated once per build and then the expression expands to the same value for the duration of the build.

=== Building on a system with a GRSec kernel doesn't work well, is that supported? ===

No, grsec isn't really supported. The list of distros that are supported (tested) is in the Yocto mega manual for each release.
You can refer to the work-around given in this defect: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10885

=== Working around Firejail ===
For users of Parrot OS and other secured Linux distros, you will find that your bitbake fetch commands refuse to work, yet you can manually run wget and retrieve the packages with no problem. This is due to Poky creating links to all the tools it requires, in particular 'wget', 'ssh' and 'strings', using the links to these tools in the /usr/local/bin/ directory which all redirect to firejail. To fix the problem you can cd into <your Yocto install directory>/poky/build/tmp/hosttools directory and replace these links with ones redirecting to the actual executables under the /usr/bin directory.

== Dependencies ==

=== How do I find out why something is being built? ===

<code>bitbake -g <recipe></code> will produce some .dot files that allow you to see the dependency relationships - usually pn-depends.dot holds the answers although sometimes you may need to look at task-depends.dot if the dependency is only in the form of a task dependency. Note that these graphs are much too large for most graphviz visualisation tools to process, so you'll probably find it's easiest to view them with "less" or a text editor and search for the item you're looking for.

=== How do I find out why something is in my image? ===

Enable the buildhistory class and build the image again, and it will write out a depends.dot file containing the relationships between packages in the final image. If the package name isn't mentioned it is probably explicitly mentioned in IMAGE_INSTALL or being brought in via IMAGE_FEATURES.

See [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] in the Yocto Project Reference manual which covers how to enable buildhistory and the output it produces.

=== How do I view the .dot files produced by bitbake -g or buildhistory? ===

The size of some of these .dot graphs (particularly those produced by <code>bitbake -g</code>) is a little large for most viewers / processing tools, and unfortunately this isn't something that can be fixed - it's just the nature of the dependency relationships between targets and tasks within OpenEmbedded. Usually if you're just after answering a simple dependency question you can figure it out by viewing it with <code>less</code> and using its built-in search function (or alternatively your favourite text editor).

You can try [http://github.com/jrfonseca/xdot.py xdot] which will work well for some of the graphs, but the task graph produced by <code>bitbake -g</code> for something like an image in particular is likely to be too large to view within it.

=== Why are all of these -native items being built when my host distro has some of these available? ===

It's complicated. In some cases the software in question isn't widely packaged by common Linux distributions. In other cases we need to apply patches to the software, use a more up-to-date version than commonly packaged or build it with a particular configuration. In general it just helps us isolate ourselves from potential problems caused by differences in host Linux distributions. For the most part the time spent building the native tools that are definitely provided by the host distro are dwarfed by the time spent building things that definitely aren't provided, such as the C library for the target and the cross-compiling toolchain.

=== I disabled runtime package management and yet it still seems to be building rpm/opkg, why? ===

The build system always uses a package manager on the host to assemble images, because it is usually the best tool for this job. This is completely independent of whether the package manager is available in the target image - "package-management" being in IMAGE_FEATURES (possibly indirectly via EXTRA_IMAGE_FEATURES) controls whether the package manager is used at runtime i.e. whether it (and its associated package database) will be present in the target image.

=== Why is opkg-native / opkg-utils being built when I don't have ipk packaging enabled? ===

opkg-utils provides update-alternatives which is the default tool used to manage the alternatives system (for selecting between multiple providers of the same file, e.g. busybox and bash both provide /bin/sh).

=== Why is rpm-native being built when I don't have rpm packaging enabled? ===

rpm-native is needed for two things in the generic packaging code implemented in the package class:

# Debug symbol splitting - rpm-native provides the debugedit tool which this code uses
# Per-file dependencies - although this was originally just feeding into rpm when rpm was being used, it also now gets verified by QA checks regardless of which packaging backend is in use.

=== I see a recipe built, but building an image containing the corresponding package fails at do_rootfs because it can't find the package. How does this happen? ===

(For ipk, the error is "Couldn't find anything to satisfy '<package>'"; for rpm it is "<package> not found in the base feeds (<architecture list>)".)

Usually this is because the recipe claimed to provide the specified package (via PACKAGES or PACKAGES_DYNAMIC) but it wasn't actually produced, possibly because it ended up empty (since by default empty packages aren't produced), but the image or some other package still has a dependency that pulls in the specified package. If this is a recipe you are writing yourself the probable cause is your recipe isn't installing any files and thus the main package for the recipe is empty. Fix do_install (or what do_install is already running, e.g. make install) such that files are installed into the correct location such that they can then subsequently be packaged, and then all should be well.

In other situations the reference to the package in question is spurious and either it should be removed entirely or there's another package that should be used instead. For example, the avahi and dhcp recipes both have an empty main package since the client and server are split out into their own packages, and those are the ones you should be using instead (avahi-daemon, avahi-utils, dhcp-server, dhcp-client - there are other packages as well, please see [[#How_do_I_find_out_what_packages_are_produced_by_a_recipe.3F|How do I find out what packages are produced by a recipe?]].) You could argue that these recipes shouldn't claim to provide the main package, or they should have a main package that depends on all the other packages (as some other recipes do).

=== X11 and various other items are being built but I'm only building core-image-minimal that doesn't have X11 in it - why? ===

This is where it helps to understand the difference between build-time dependencies and runtime dependencies - often, a recipe will require things at build time (for example tools that help the build process, or to satisfy optional dependencies) that it doesn't necessarily need at runtime. The default configuration includes "<code>x11</code>" in <code>DISTRO_FEATURES</code>, and thus anything that can optionally support X11 will have its X11 support enabled; however when it comes to actually producing the image there won't be any X11 packages included as long as there are no hard dependencies and there aren't any X11 packages explicitly requested.

If you never intend to use X11, you can set your own <code>DISTRO_FEATURES</code> value that excludes <code>x11</code> (note lower case, as with all feature names) and then X11 support will be disabled at build time and these items won't even be built.

=== How do I avoid the kernel itself being pulled into my image when installing kernel modules? ===

By default, the kernel class sets a dependency on the kernel-base package (which kernel modules always depend on) onto kernel-image, which contains the actual kernel binary. If you don't want this, set the following either in your kernel recipe or at the configuration level:

RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""

Note: for older releases (pre-2.5) do this instead:

RDEPENDS_kernel-base = ""

== Misc ==

=== How do I remove a value from a list variable? ===

For variables that are expected to contain a space-separated list of items, BitBake supports a _remove operator to remove items from it. See [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#removing-override-style-syntax Removal (override style syntax)] in the BitBake user manual.

'''NOTE:''' the _remove operation is final - you cannot "undo" it with other operations elsewhere, thus you should really only make use of it in your distro / local configuration and not in layers that you expect others to re-use for different purposes (and therefore they may need to undo your changes). An alternative way to effectively remove an item is to set the list outright to include all the items minus the one you want to remove.

=== How do I change how my recipe is built depending on what image I'm building? ===

The short answer is you cannot - the reason is that OpenEmbedded builds packages based on the overall configuration, and then the image only selects which of these packages should go into the final image. However, there are some solutions that do allow you to achieve the desired result:

# Have separate packages for the two different versions. This could take the form of different recipes or you could do it within the same recipe. The two packages do have to have different names however; this may create problems if you have other packages that depend on the package.
# Use a postprocessing function within the image(s) - within the image recipe, define a shell or python function that makes the desired changes to the files in the image and add a call to it to ROOTFS_POSTPROCESS_COMMAND within the image recipe. Note that this may not be appropriate if you have runtime package management enabled since the postprocessing will only happen at image creation time and not if the package is installed later on at runtime - you may need to use a postinstall script instead in this case.
# Use a postinstall script (pkg_postinst_<package> function) within the recipe. In order to work, the postinstall script will need to be able to determine what to do when it's run - this may not be practical depending on what you're trying to achieve.

=== Can I use a toolchain built by OE as the external toolchain? ===

In general, this is not recommended and not something that is tested or directly supported out of the box. If you are wanting to do this solely as a means of speeding up the build, it is strongly suggested that you use shared state instead.

There is a [http://layers.openembedded.org/layerindex/branch/master/layer/meta-sourcery/ meta-sourcery layer] available to enable support for the CodeSourcery toolchain, you may be able to use this as a template for bringing in an external toolchain however there are no guarantees.

=== Why can't I run bitbake as root? ===

If you try to run bitbake as root you may have noticed you get a sanity check failure that prevents the build from continuing. The reason we have this check is that it is very risky to run builds as root; if any build script mistakenly tries to install files to the root path (/) instead of where it is supposed to, you want it to fail immediately and not (in the worst case) overwrite files critical to your Linux system's operation e.g. under /bin or /etc. Thus, we do not support running the build as root. The only time root access is needed is (completely outside of a build) where the runqemu script uses sudo to set up TAP devices for networking.

=== When I run bitbake -c devshell it looks like it's running as root! How is that possible? ===

It's not running as the actual root user, it's just pretending for the benefit of programs that run under it (including your shell) that it is, via pseudo. This is important, because you normally want any owner/group/permission values that you set on files to be reflected in files that the recipe installs and packages and thus reflected in the final image - without this mechanism the actual build would have to run as root which would be very risky (see above). There are no actual elevated privileges through this mechanism however, so you need not be worried.

=== Why does OE use pseudo? Why not use fakeroot / fakechroot instead? ===

Splitting this up into two questions - we use pseudo (not to be confused with sudo!) because we want to be able to create images containing files have the correct permissions and ownership, e.g. files owned by root, without the user running the build system having to have that privilege. By using LD_PRELOAD to intercept function calls, pseudo creates an environment for programs running underneath it where it appears as if the running user has those privileges (and the results of any operations persist within the pseudo environment, i.e. you can write a file as root and it will appear to be owned by root while still running under pseudo). This allows us to run builds entirely as a normal user without needing extra privileges. Without pseudo we would require running the build system under sudo or as root - which would be ill-advised for things such as "make install" in case it happened to be broken and tried to write to / instead of somewhere under the work directory for the recipe; a broken recipe could easily end up destroying your system in that case.

To answer the second part, why we use pseudo instead of fakeroot / fakechroot, see [https://github.com/wrpseudo/pseudo/wiki/WhyNotFakeroot WhyNotFakeroot on the pseudo wiki].

=== How do I find out what packages are produced by a recipe? ===

The Toaster web UI provides easy ways to query this.

In the 1.8 (fido) release and newer you can use the following command, assuming the recipe has already been built:

oe-pkgdata-util list-pkgs -p <recipename>

Alternatively you can look in the "packages-split" subdirectory under the work directory for the recipe - each package produced by the recipe will have a subdirectory under that. If you're not sure how to find the work directory you can run the following command:

bitbake -e <recipename> | grep ^WORKDIR=

Before a recipe gets built it is a bit trickier, since the system often doesn't know exactly which packages will be produced until do_package time; this is particularly true for recipes that package plugins or modules (e.g. kernel modules). You can get a reasonable idea though by looking at the value of PACKAGES (and PACKAGES_DYNAMIC for recipes that produce plugins).

=== How do I find out which package contains a particular file (or python module)? ===

oe-pkgdata-util has a find-path subcommand that will tell you exactly this. For example:

$ oe-pkgdata-util find-path /etc/network/interfaces
init-ifupdown: /etc/network/interfaces

Wildcards are allowed anywhere in the path (but you should enclose such expressions in quotes to avoid the shell itself attempting to expand the wildcard):

$ oe-pkgdata-util find-path "*/fstrim"
util-linux-bash-completion: /usr/share/bash-completion/completions/fstrim
util-linux-ptest: /usr/lib/util-linux/ptest/fstrim
util-linux-dbg: /sbin/.debug/fstrim
util-linux-fstrim: /sbin/fstrim

As a specific example of where this can be useful, our Python packaging is a bit more granular than most typical distributions, allowing you to tune the contents of your image to just what you need. However, that does mean you may have trouble figuring out which package provides a particular module. oe-pkgdata-util find-path can also be used for this. For example, to find the package containing the "shutil" module, run this:

$ oe-pkgdata-util find-path "*/shutil.*"
python3-shell: /usr/lib/python3.5/shutil.py
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-2.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-1.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.pyc

Thus the package you are looking for is python3-shell. (Note that you could use */shutil.py, but if the module you are looking for is written in C as some of them are, that won't match it.)

=== I have a local source tree I want to build instead of the upstream source a recipe normally fetches, how do I do that? ===

If it's for development purposes i.e. you have your own local source tree you want to work on and have built, then run:

devtool modify -n <recipename> path/to/sourcetree/

Once you are done you can use <code>devtool finish</code> or <code>devtool reset</code> (depending on the situation) to return to building the source specified in the recipe.

Alternatively if it's more permanent, use the <code>externalsrc</code> class - you can inherit this in the original recipe or a bbappend:

inherit externalsrc
EXTERNALSRC = "/path/to/sources"

If you're going to use it across a number of recipes you can inherit it globally at the configuration level (perhaps via an inc file that you include/require there):

INHERIT += "externalsrc"
EXTERNALSRC_pn-<recipename> = "/path/to/sources"

=== How do I specify the default shell? (e.g. bash instead of busybox) ===

It depends what you mean. As far as which provides /bin/sh, this is controlled through the alternatives system, and by default bash has a higher priority than busybox, so simply installing bash into your image will automatically have /bin/sh link to bash rather than busybox.

If you mean you want a user's login shell to be a specific shell, you'll need to modify /etc/passwd. One fairly easy way to achieve this is to use the extrausers class in your image recipe:

inherit extrausers
EXTRA_USERS_PARAMS = "usermod -s /bin/bash <username>; "

=== How do I get "full" versions of typical shell commands? ===

Most of the shell commands in our images are provided by busybox by default, and are very much simplified compared to what you would have on a typical Linux system in order to save space. If you need the full versions, most of them are built and packaged by the coreutils recipe (for disk and other typical utilities) and procps (for ps, etc). You may also want to install bash for more typical shell built-in commands. There is also a core-image-full-cmdline image if you want a base image that is already set up to provide a more typical Linux command-line experience. (Note: these will of course use up more disk space and memory.)

=== How do I allow a variable's value through from the external environment? ===

Add the variable's name to the BB_ENV_EXTRAWHITE ''in the external environment'' before running bitbake. Note that the oe-init-build-env script sets a default for this which you will want to preserve, so add to the default value rather than overwriting it.

Alternatively if you just want to get the external value of a variable from python code within the metadata, you can use the BB_ORIGENV variable which itself contains a datastore of the original environment. For example to get the value of the DISPLAY variable from the environment within a python function you would do this:

display = d.getVar("BB_ORIGENV", False).getVar("DISPLAY")

Note that you must specify "false" for the expand parameter when getting the BB_ORIGENV variable, because it's not a string and therefore cannot be expanded in the normal manner.

=== Why is bitbake showing "AUTOINC" in the version for some recipes? ===

Recipes where you see AUTOINC within the version in the console output during a build will be those that set <code>PV</code> to include <code>"${SRCPV}"</code> to get the SCM revision (e.g. the git hash) in the package version. In order to have the version increment properly, there needs to be a number in front of the revision which automatically increments each time the revision changes (assuming you have a PR server enabled), which is where AUTOINC comes in. During the build, AUTOINC is a stand-in for this auto-incrementing number, and later during <code>do_package</code> it gets replaced with the real number so that the packages produced at the end have the full version number.

=== Why are .so files in the -dev package instead of the main package for a recipe? ===

In standard Unix library packaging, non-versioned .so symlinks (e.g. /usr/lib/libgd.so) are intended for development purposes only. At runtime, binaries should be linked to the major-versioned .so file/symlink e.g. /usr/lib/libgd.so.3. This (theoretically) allows multiple major versions of the same library as well as binaries that depend upon each of them to coexist on the same system. If the library is versioned but you have a binary that links to the unversioned .so file, it has almost certainly been linked incorrectly.

Non-symlink .so files on the other hand are sometimes produced and are entirely legal - however these will be picked up in the -dev package in OpenEmbedded simply by virtue of their name, which is almost always not what you want. In this case you can do one of two things:

# Fix the build of the library so it gets versioned. This may not always be appropriate, especially not for things like plugins.
# Set FILES_${PN}-dev within the recipe so that it does not include ${FILES_SOLIBSDEV}. If the software the recipe is building also produces symlink .so files you'll need to set FILES_${PN}-dev such that those do still get packaged in the -dev package though, or you'll get a package QA warning.

=== Can I disable shared state? ===

You cannot, no. Shared state (sstate) is an intrinsic part of staging files into the sysroot. It is possible to construct a recipe that bypasses sstate for some tasks (the kernel does this), however this is quite difficult and if not done properly will lead to many other problems.

Almost always when you are having a problem with shared state the issue is either (a) you're adding/changing files in the sysroot directly (i.e. outside sstate control), or (b) what is being placed into the sysroot isn't relocatable due to hardcoded paths. The solution for (a) is do not do that - files should always be installed under <code>${D}</code> within <code>do_install</code> and then a subset of those are staged into the sysroot automatically. For (b) you need to fix or adapt the hardcoded path(s) - if the program reads (or can be made to read) each path from an environment variable, then you can use the <code>create_wrapper</code> utility function to create a wrapper script that will set the path appropriately. Run <code>git grep create_wrapper</code> in the <code>meta</code> subdirectory to see examples.

=== Files I installed into /opt or some other path never make it into the sysroot but I need them - how do I fix this? ===

OpenEmbedded only stages a subset of files that are installed into <code>${D}</code> by <code>do_install</code> so that the sysroot doesn't fill up with unneeded files. You have two choices in this situation:
# install the files into a more standard location which is part of the subset, or
# adjust the subset to include the paths you are installing to.
Usually option 1 is recommended. If you really do need to adjust the subset, you can append the path (more specifically, the part below <code>${D}</code>) to <code>SYSROOT_DIRS</code> within your recipe. For example:

SYSROOT_DIRS += "/opt"

=== I have some software which needs to build a binary that it then runs as part of its own build process, how do I make this work? ===

Whilst it is possible to do this within a single recipe building for the target, it is tricky to do so because in that context everything is set up for cross-compiling for the target, and you would have to undo all of that to build host tools. The standard and much easier way of handling this is to create a native variant of the recipe using BBCLASSEXTEND and have your host tools built within that, and then have the target variant depend on the native variant. For example, assume your recipe were called xyz (xyz_1.1.bb), then you would include something like this in the recipe:

DEPENDS_append_class-target = " xyz-native"

...

BBCLASSEXTEND += "native"

The host tools will then be built and installed into the sysroot in the native variant ready for when the target variant starts building. If the software you are building didn't intend for those tools to be installed outside of the build tree then you may need to patch the build process (e.g. the makefile) in order to install them and possibly also for the target side to find them in the sysroot. Additionally, for performance since you only need the tools in the native variant, you may also choose to disable building everything except those tools there - e.g. by using _native overrides for variables such as EXTRA_OECONF or functions such as do_configure.

=== How do I fetch from two git repositories in the same recipe? ===

By default, sources fetched from git within a recipe are unpacked into ${WORKDIR}/git, however that only works for a single repository. If you want to fetch from more than one, you need to change the path each repository is unpacked to. This is easy to do, just add <code>;destsuffix=<subdir></code> to the end of each URL in SRC_URI (replacing <code><subdir></code> with the name of the subdirectory). You may then need to change S to match whichever of these you want to be considered the root of the source tree - or alternatively you can specify destsuffix such that repositories beyond the first go into a subdirectory under the default "git" subdirectory. For example, from the gst-libav recipe:

...
SRC_URI = " \
git://anongit.freedesktop.org/gstreamer/gst-libav;branch=1.8;name=base \
git://anongit.freedesktop.org/gstreamer/common;destsuffix=git/common;name=common \
...
"
...
S = "${WORKDIR}/git"
...

(Here we're using the default of "git" for the first repository, so we don't need to specify <code>destsuffix</code> for the first URL.)

=== I'm building a native recipe and I notice that the install path has the full path to the root directory repeated - why? ===

It does look a little odd, but the reason for doing this is that native targets are meant to run on the system they're built on and run in the location they're installed to. This means they install to a destination of "/" and PREFIX is inside the native sysroot directory. We install them to a DESTDIR to allow us to manipulate them before they then get moved to a final DESTDIR of "/".

Most Makefiles handle this correctly by doing:

DESTDIR ?= ""
prefix ?= "/usr"
bindir ?= "$(prefix)/bin"

and then, importantly, install in the form:

install -d $(DESTDIR)$(bindir)

so both prefix and DESTDIR are used. Whilst this is a convention, its a widely adopted and followed one. You can call into a custom makefile and set the variables manually if the makefile doesn't follow the convention.

=== How do I generate static libraries? ===

Its possible you have conf/distro/include/no-static-libs.inc included in your build - poky does this by default. The include list at the top of the bitbake -e output will tell you for certain.

If so, you can remove that or set:

DISABLE_STATIC = ""

as it would currently be set to this if that include file is included:

DISABLE_STATIC = " --disable-static"

Poky disables building static libraries by default as for the most part they're a waste of space/time.

=== Can I conditionally inherit a class in a recipe? ===

Yes, you can. What makes this possible is that the <code>inherit</code> keyword will not complain if what comes after it expands to being empty, so you can use in-line python to do something like this:

<pre><nowiki>
inherit ${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}
</nowiki></pre>

The above example will inherit the <code>perlnative</code> class if "scripting" is in the value of the <code>PACKAGECONFIG</code> variable, otherwise it will do nothing.

You could of course put this into a variable if you prefer:

<pre><nowiki>
SOMEVAR = "${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}"
inherit ${SOMEVAR}
</nowiki></pre>

=== How do I collect the source revisions fetched by each recipe? ===

If you have recipes where <code>SRCREV = "${AUTOREV}"</code> then you won't necessarily know exactly which revisions were built after the fact - it will be whatever was current at the time. You also might alternatively just want to get all of the revisions. Either way, to do this, enable buildhistory by setting the following in your local.conf:

<pre><nowiki>
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
</nowiki></pre>

(The last line is not required with version 2.5 and onwards as it is the default, but will do no harm.)

Once you have enabled buildhistory, you then need to build your image again so that buildhistory has a chance to record history data for it. Following that you can run <code>buildhistory-collect-srcrevs</code> (with <code>-a</code> if you want to see all revisions, not just the ones where AUTOREV was used) and it will output the revisions in a form you can use in a .inc file that you can <code>require</code> from your configuration if you want to fix the build to those revisions.

For more information see the [https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] section of the Yocto Project Development manual, which covers the buildhistory class in detail.

=== How do I do an offline build with recipes that have <code>SRCREV = "${AUTOREV}"</code> set? ===

If you set <code>BB_NO_NETWORK = "1"</code> and you have recipes that have <code>SRCREV = "${AUTOREV}"</code>, you will get an error because the build system will try to check the latest revision on startup and be immediately blocked by <code>BB_NO_NETWORK</code>. There are two ways to handle this:

A) See the previous question "How do I collect the source revisions fetched by each recipe?" and use the output generated by <code>buildhistory-collect-srcrevs</code> as a .inc file in your configuration in order to fix the revisions at the ones which were most recently built.

or

B) Set <code>BB_SRCREV_POLICY = "cache"</code> in your configuration. This will use the last cached revision. (The disadvantage of this method is that it is a little more difficult to preserve or share with others the fixed revisions.)

Note that in either case if you later want to build the latest version again, you will of course need to undo the configuration changes.

=== Is it possible to append a bbclass file (like bbappends do for recipes)? ===

No, see the next question for details.

=== How do I override a bbclass file? ===

This is tricky - bbclass files are found via BBPATH, which is added to by each layer.conf either by prepending or appending. Assuming you are putting your bbclass in a custom layer, you will probably want to have your layer's layer.conf prepend to BBPATH, but then you will also need to make sure that your layer does not appear before any other layer that is also prepending and overriding the same class.

Another alternative is to have an additional class which makes the appropriate changes to the environment, and then you will need to inherit that class after (and in the same manner as) the original class. This is slightly cleaner but can be annoying to enable particularly if the class is inherited by a number of recipes, and won't work if you want to alter the behaviour of a class inherited by recipes you don't control. (If you want a class to be inherited for all images (i.e. all recipes inheriting the <code>image</code> class) you can inject additional classes by setting IMAGE_CLASSES; similarly for the kernel there is KERNEL_CLASSES).

Ultimately, overriding bbclass files is not good practice long term - you are opening yourself up to maintenance issues when the original class changes, and the override is fragile as hinted above. The best solution is to try to get whatever changes you need into the original class; this does of course require additional work and time though.

=== There's a bbappend in a layer I'm using that defines a <code>do_something_append()</code> and I want to append to that function also, how do I do this? ===

Simply create a bbappend in your layer and define your own <code>do_something_append()</code>, and your commands will be executed ''as well as'' those of the other bbappend.

You might assume that defining <code>do_something_append()</code> will overwrite any previously defined <code>do_something_append()</code>, as would be the case with <code>do_something()</code> in the same situation, but that is not the case - the key is that <code>_append</code> (and <code>_prepend</code>, <code>_remove</code>, etc.) are ''operators'' and they will be applied in sequence, where that sequence is the order in which they are parsed (which for bbappends will be in ascending layer priority order).

Technical FAQ

2020-07-01T01:30:56Z

PaulEggleton: Consistency: use <recipename> instead of recipename

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
| '''NOTE:''' This is currently a draft. Not sure where this should end up but I've been gathering these based on my interactions with people on IRC and email over the years. - [[User:PaulEggleton|PaulEggleton]] ([[User talk:PaulEggleton|talk]]) 21:13, 27 June 2016 (PDT)
|}

== Basics ==

=== How do I figure out which version/codename/bitbake version matches up with which? ===

There is a table in the [http://wiki.yoctoproject.org/wiki/Releases Releases page] on the Yocto Project wiki.

=== How do I control what's in the final image? ===

Each image is defined by its own recipe, and that recipe specifies a list of packages that the image should contain. See [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Customising Images] within the Yocto Project development manual for further details.

Note: if you're doing anything more than basic experimentation / testing then you almost certainly should create your own image recipe rather than using one of the example images e.g. core-image-minimal - though you can certainly start by copying one of the example images. This way you have easier control over what goes into the image.

=== Where do I find build logs? ===

For the overall build, the output of bitbake gets logged to tmp/log/cooker/<machine>.

For each individual recipe, there is a "temp" directory under the work directory for the recipe that contains log.<taskname> and run.<taskname> files - the logs and the runfiles respectively. Within the build system this directory is pointed to by the T variable, so if you need to you can find it by using <code>bitbake -e</code>:

bitbake -e <recipename> | grep ^T=

=== How do I add a patch to a recipe? ===

There are two concerns - how the recipe can fetch the patch and how it can be applied. For fetching, patch files are usually placed in a subdirectory next to the recipe; by default this directory should be named "files" or the the recipe name without any class prefix or suffix (for example for both "xyz" and "xyz-native" the subdirectory would be "xyz"). A pointer to it then needs to be added to <code>SRC_URI</code> within the recipe, which usually takes the form <code>file://<patchname>.patch</code> - i.e. just the filename, no path. If more than one subdirectory needs to be stripped off the paths in the patch (i.e. you need more than the equivalent of the -p1 option to the patch command) then you can add <code>;striplevel=<number></code> to the end of the patch entry in SRC_URI (without any spaces).

As with any modification, if the patch you are applying is a customisation that you do not intend to send to be incorporated in the layer you are modifying, then instead of adding the patch to the recipe directly then you should consider applying it in a bbappend within your own custom layer. This makes things easier if you later want to update the layer in question and the recipe has been modified upstream - you avoid effectively forking the layer.

The <code>devtool</code> utility can help you modify the sources for a recipe and create a patch - basically <code>devtool modify</code>, edit the sources, commit the changes with <code>git commit</code>, then <code>devtool finish</code> (or <code>devtool update-recipe</code> in versions older than 2.2). Since <code>devtool modify</code> gives you a git tree to work with, you can of course use something like <code>git am</code> to apply existing patches this way. For more details see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#devtool-use-devtool-modify-to-enable-work-on-code-associated-with-an-existing-recipe Use devtool modify to Enable Work on Code Associated with an Existing Recipe] within the Yocto Project Development manual.

=== What does "native" mean? ===

The "native" suffix identifies recipes (and variants of recipes) that produce files intended for the build host, as opposed to the target machine. This is usually for tools that are needed during the build process (such as automake).

=== What does "nativesdk" mean? ===

The "nativesdk" prefix identifies recipes (and variants of recipes) that produce files intended for the host portion of the standard SDK, or for things which are constructed like an SDK such as buildtools-tarball. These are built for SDKMACHINE which may or may not be the same architecture as the build host.

=== I have two recipes and one needs to access files provided by another - how can that work? ===

Instead of providing direct access from a recipe to another's build tree (which wouldn't be practical with OpenEmbedded since the build tree (or "workdir") is temporary), we create a "sysroot" where files that are intended to be shared between recipes get copied. The sysroot is managed by the build system and you should not copy files in there directly - instead, you install files under ${D} as normal during do_install and then the build system will copy a subset of those to the sysroot. There is a seperate sysroot for each machine being built for. In a recipe you can get the path of the sysroot and various standard directories under it using the STAGING_* variables.

Often, for commonly-used build systems such as autotools and cmake you don't need to worry about these details - those systems and the environment that OpenEmbedded sets up for them will ensure that files get installed and picked up in the correct locations. However if the software your recipe is building has custom build scripts / makefiles and it takes shortcuts that don't account for cross-compilation or the use of a sysroot, then you will need to make appropriate adjustments.

=== How do I enable package management in the final image? ===

Add <code>package-management</code> to <code>IMAGE_FEATURES</code> (or <code>EXTRA_IMAGE_FEATURES</code>). You should then be able to use dnf/rpm, opkg, or apt-get/dpkg from the running system depending on the packaging format you have selected through PACKAGE_CLASSES. For more information see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-runtime-package-management Using Runtime Package Management] in the Yocto Project Development manual.

=== What do ?=, ??=, := etc. do within a recipe/config file? ===

See the [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#basic-syntax Basic Syntax section of the BitBake manual] for details.

== Layers ==

See http://www.openembedded.org/Layers_FAQ

== Troubleshooting ==

=== I've created a recipe but it's not showing up in my image, what's going on? ===

Creating a recipe (or adding a layer to your configuration with a desired recipe in it) only makes it available to the build system, it doesn't change what goes into the image. For that, see [[#How do I control what's in the final image?|How do I control what's in the final image?]] above.

=== I set a variable but it doesn't seem to be having an effect, how do I fix this? ===

First, double-check that you haven't misspelled the variable name.

The main tool to help troubleshoot any variable-related issue is <code>bitbake -e</code> - this lists all the variables and the complete history of how each one has been set (use <code>bitbake -e <recipename></code> if you're dealing with issues in a variable value within a recipe as opposed to the global level). Usually it's best to pipe this through <code>less</code> so you can easily see the history - within less you can press / to search for the variable name. Often you will be dealing with the behaviour of a variable within the context of a specific recipe, so specify that recipe on the <code>bitbake -e</code> command line to get the variables as set within the context of the recipe rather than the global context.

If you're setting a variable in a bbappend, double-check that the bbappend is actually being applied - see the next question.

=== I've created a bbappend for a recipe but what I'm setting there isn't having any effect, how do I fix this? ===

Here are some things to check:

# Check if the layer the bbappend is in is listed in <code>bitbake-layers show-layers</code>. If it isn't, you need to edit your bblayers.conf and ensure the path to the layer is included in the BBLAYERS value
# Check that the bbappend is being picked up by running <code>bitbake-layers show-appends</code> - if your bbappend file isn't listed, it could be named incorrectly (such that it doesn't match the recipe name) or it may be that the BBFILES value in the conf/layer.conf for the layer containing the bbappend file doesn't include an expression that will match the bbappend files.
# If there are multiple versions of the recipe you have bbappended, it could be that the actual recipe being built is a different version than the one you have bbappended. <code>bitbake-layers show-recipes <recipename></code> will list all the versions, with the first one listed being the one that will be built. If this is the case there are several different solutions to this - (a) Rename your bbappend to match the version being built, (b) use a % wildcard in your bbappend so it will apply to any version, (c) set <code>PREFERRED_VERSION_<recipename></code> in the configuration to select a the version you want to be built.
# Finally, as with any other issue with setting variables, use <code>bitbake -e <recipename> | less</code> and search with <code>/</code> to see the history of how the variable has been set - you may find that the value you're trying set is being overridden.

=== I'm getting warnings that a recipe is tainted - what does this mean? ===

Usually this happens because you have used I used bitbake's <code>-f</code> or <code>-C</code> option to force a task to re-execute. The assumption is that if you forced a task, it is possible that a rebuild from scratch would not include whatever changes you made that necessitated forcing (e.g. if you modified the source in the work directory for the recipe and then ran <code>bitbake -c compile -f</code>). Generally, forcing a task should be reserved for situations where the build system has failed to detect a change you made rather than for everyday usage - if you're finding yourself needing to do it regularly then either there's a bug, you're doing something wrong, or perhaps you're using <code>-f</code> or <code>-C</code> when it's not really needed. Running <code>bitbake -c clean</code> on the recipe will get rid of the taint flag.

There is one other situation where we apply a taint, and that is <code>bitbake -c menuconfig</code> on the kernel (or some other kconfig-using recipe). In this case, the configuration has been saved into the work directory for the kernel, but that is temporary - any rebuild from scratch will use the default configuration, so it is a reminder that you need to take the configuration and apply it back to the metadata and then run <code>bitbake -c clean</code> on the kernel recipe.

=== I'm fetching from a git repository over ssh / http / https but it's not fetching properly, how do I fix this? ===

Bitbake expects the prefix of entries in SRC_URI to specify the fetcher to be used, not the actual protocol. Thus, instead of:

# This will NOT work
SRC_URI = "<nowiki>https://git.example.com/repository</nowiki>"

You should specify:

# This is better
SRC_URI = "<nowiki>git://git.example.com/repository;protocol=https</nowiki>"

The same applies for ssh and of course http.

=== I tried bitbake <some target package name> that I know exists and it told me that nothing PROVIDES this...? ===

There are two namespaces that bitbake concerns itself with - recipe names (a.k.a. build time targets) and package names (a.k.a. runtime targets). You can specify a build time target on the bitbake command line, but not a runtime target; you need to find the recipe that provides the package you are trying to build and build that instead (or simply add that package to your image and build the image). In current versions bitbake will at least tell you which recipes have matching or similar-sounding runtime provides (RPROVIDES) so that you'll usually get a hint on which recipe you need to build.

=== I've included a package in my image but files I expect to be there are missing, what's the issue? ===

Check the simple stuff: verify that the package is really in the image - look at the manifest file next to the image to ensure the package is listed. Also if you're flashing the image, double-check that you did indeed flash the right image and if there are multiple partitions / storage devices on your board or device that you're booting the one that you think you are.

Once you're sure of the above, it may be a matter of the package splitting - a lot of recipes split less commonly used components out to separate packages, so it's possible that the files you are looking for are in a different package. You can look at the recipe for this (look for PACKAGES and FILES statements) or assuming the recipe has been built, you can use <code>oe-pkgdata-util list-pkgs -p <recipename></code> and <code>oe-pkgdata-util list-pkg-files</code> to inspect the packages provided by the recipe and the files they contain. Once you find the right package you can add it to your image.

=== I'm required to set LIC_FILES_CHKSUM but the software I'm building doesn't have a license statement, what do I do? ===

Ideally, all software should come with some kind of license statement so that the terms of distribution are clearly stated (especially if its source code is made publicly available); if not a text file describing the license then at the very least a line or two in the accompanying documentation, README file or source header comments. Assuming there is a license statement somewhere but not in a form you can point to with LIC_FILES_CHKSUM as part of the source tree, you can point LIC_FILES_CHKSUM to one of the generic license files in ${COMMON_LICENSE_DIR} (meta/files/common-licenses/), or alternatively you can include a file containing the license statement in a "files" subdirectory next to the recipe (or subdirectory named the same as the recipe - see how such files are handled in other recipes), point to it in SRC_URI using file://, then add it to LIC_FILES_CHKSUM. It is worth noting however that LIC_FILES_CHKSUM is intended to give you a warning if upstream changes its license terms when you do an upgrade of the recipe, and by pointing it to this common license file that is part of the metadata, that mechanism will not function. You may wish to consider encouraging the upstream provider of the software your recipe is building to follow best practices and include a proper license statement, so that you can point to it in a future version. At minimum if you do use such workarounds, you will need to take extra care when upgrading the recipe in future in case the upstream provider changes the license terms.

If there really is no license stated at all anywhere for the software (and this is unfortunately not uncommon on github, for example) then you should really contact upstream - if there's no license, then technically you really shouldn't be distributing it until that's clarified with the original author(s).

=== I am getting a package QA error / warning when building a recipe, how do I solve it? ===

There are some general and specific recommendations in the [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-errors-and-warnings QA Errors and Warnings] section of the Yocto Project Reference Manual.

=== I am getting "taskhash mismatch" errors, what does this mean and how do I fix it? ===

Bitbake parses the metadata (recipes, classes and configuration) repeatedly during its operation, and this error means that the result of parsing changed between one parse and the next. Two situations that can cause this:
# One of the parsed files changed in between e.g. you edited a recipe or performed a git operation (e.g. git checkout) during the build. '''Do not make changes to the metadata while a build is running.''' If you run the build again the error should not recur.
# Alternatively, there is something in the metadata that results in a variable expanding to a different value each time it is parsed. This is often something time-related e.g. a timestamp which is calculated every time an expression is expanded. The solution is to ensure the value is calculated once per build and then the expression expands to the same value for the duration of the build.

=== Building on a system with a GRSec kernel doesn't work well, is that supported? ===

No, grsec isn't really supported. The list of distros that are supported (tested) is in the Yocto mega manual for each release.
You can refer to the work-around given in this defect: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10885

=== Working around Firejail ===
For users of Parrot OS and other secured Linux distros, you will find that your bitbake fetch commands refuse to work, yet you can manually run wget and retrieve the packages with no problem. This is due to Poky creating links to all the tools it requires, in particular 'wget', 'ssh' and 'strings', using the links to these tools in the /usr/local/bin/ directory which all redirect to firejail. To fix the problem you can cd into <your Yocto install directory>/poky/build/tmp/hosttools directory and replace these links with ones redirecting to the actual executables under the /usr/bin directory.

== Dependencies ==

=== How do I find out why something is being built? ===

<code>bitbake -g <recipe></code> will produce some .dot files that allow you to see the dependency relationships - usually pn-depends.dot holds the answers although sometimes you may need to look at task-depends.dot if the dependency is only in the form of a task dependency. Note that these graphs are much too large for most graphviz visualisation tools to process, so you'll probably find it's easiest to view them with "less" or a text editor and search for the item you're looking for.

=== How do I find out why something is in my image? ===

Enable the buildhistory class and build the image again, and it will write out a depends.dot file containing the relationships between packages in the final image. If the package name isn't mentioned it is probably explicitly mentioned in IMAGE_INSTALL or being brought in via IMAGE_FEATURES.

See [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] in the Yocto Project Reference manual which covers how to enable buildhistory and the output it produces.

=== How do I view the .dot files produced by bitbake -g or buildhistory? ===

The size of some of these .dot graphs (particularly those produced by <code>bitbake -g</code>) is a little large for most viewers / processing tools, and unfortunately this isn't something that can be fixed - it's just the nature of the dependency relationships between targets and tasks within OpenEmbedded. Usually if you're just after answering a simple dependency question you can figure it out by viewing it with <code>less</code> and using its built-in search function (or alternatively your favourite text editor).

You can try [http://github.com/jrfonseca/xdot.py xdot] which will work well for some of the graphs, but the task graph produced by <code>bitbake -g</code> for something like an image in particular is likely to be too large to view within it.

=== Why are all of these -native items being built when my host distro has some of these available? ===

It's complicated. In some cases the software in question isn't widely packaged by common Linux distributions. In other cases we need to apply patches to the software, use a more up-to-date version than commonly packaged or build it with a particular configuration. In general it just helps us isolate ourselves from potential problems caused by differences in host Linux distributions. For the most part the time spent building the native tools that are definitely provided by the host distro are dwarfed by the time spent building things that definitely aren't provided, such as the C library for the target and the cross-compiling toolchain.

=== I disabled runtime package management and yet it still seems to be building rpm/opkg, why? ===

The build system always uses a package manager on the host to assemble images, because it is usually the best tool for this job. This is completely independent of whether the package manager is available in the target image - "package-management" being in IMAGE_FEATURES (possibly indirectly via EXTRA_IMAGE_FEATURES) controls whether the package manager is used at runtime i.e. whether it (and its associated package database) will be present in the target image.

=== Why is opkg-native / opkg-utils being built when I don't have ipk packaging enabled? ===

opkg-utils provides update-alternatives which is the default tool used to manage the alternatives system (for selecting between multiple providers of the same file, e.g. busybox and bash both provide /bin/sh).

=== Why is rpm-native being built when I don't have rpm packaging enabled? ===

rpm-native is needed for two things in the generic packaging code implemented in the package class:

# Debug symbol splitting - rpm-native provides the debugedit tool which this code uses
# Per-file dependencies - although this was originally just feeding into rpm when rpm was being used, it also now gets verified by QA checks regardless of which packaging backend is in use.

=== I see a recipe built, but building an image containing the corresponding package fails at do_rootfs because it can't find the package. How does this happen? ===

(For ipk, the error is "Couldn't find anything to satisfy '<package>'"; for rpm it is "<package> not found in the base feeds (<architecture list>)".)

Usually this is because the recipe claimed to provide the specified package (via PACKAGES or PACKAGES_DYNAMIC) but it wasn't actually produced, possibly because it ended up empty (since by default empty packages aren't produced), but the image or some other package still has a dependency that pulls in the specified package. If this is a recipe you are writing yourself the probable cause is your recipe isn't installing any files and thus the main package for the recipe is empty. Fix do_install (or what do_install is already running, e.g. make install) such that files are installed into the correct location such that they can then subsequently be packaged, and then all should be well.

In other situations the reference to the package in question is spurious and either it should be removed entirely or there's another package that should be used instead. For example, the avahi and dhcp recipes both have an empty main package since the client and server are split out into their own packages, and those are the ones you should be using instead (avahi-daemon, avahi-utils, dhcp-server, dhcp-client - there are other packages as well, please see [[#How_do_I_find_out_what_packages_are_produced_by_a_recipe.3F|How do I find out what packages are produced by a recipe?]].) You could argue that these recipes shouldn't claim to provide the main package, or they should have a main package that depends on all the other packages (as some other recipes do).

=== X11 and various other items are being built but I'm only building core-image-minimal that doesn't have X11 in it - why? ===

This is where it helps to understand the difference between build-time dependencies and runtime dependencies - often, a recipe will require things at build time (for example tools that help the build process, or to satisfy optional dependencies) that it doesn't necessarily need at runtime. The default configuration includes "<code>x11</code>" in <code>DISTRO_FEATURES</code>, and thus anything that can optionally support X11 will have its X11 support enabled; however when it comes to actually producing the image there won't be any X11 packages included as long as there are no hard dependencies and there aren't any X11 packages explicitly requested.

If you never intend to use X11, you can set your own <code>DISTRO_FEATURES</code> value that excludes <code>x11</code> (note lower case, as with all feature names) and then X11 support will be disabled at build time and these items won't even be built.

=== How do I avoid the kernel itself being pulled into my image when installing kernel modules? ===

By default, the kernel class sets a dependency on the kernel-base package (which kernel modules always depend on) onto kernel-image, which contains the actual kernel binary. If you don't want this, set the following either in your kernel recipe or at the configuration level:

RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""

Note: for older releases (pre-2.5) do this instead:

RDEPENDS_kernel-base = ""

== Misc ==

=== How do I remove a value from a list variable? ===

For variables that are expected to contain a space-separated list of items, BitBake supports a _remove operator to remove items from it. See [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#removing-override-style-syntax Removal (override style syntax)] in the BitBake user manual.

'''NOTE:''' the _remove operation is final - you cannot "undo" it with other operations elsewhere, thus you should really only make use of it in your distro / local configuration and not in layers that you expect others to re-use for different purposes (and therefore they may need to undo your changes). An alternative way to effectively remove an item is to set the list outright to include all the items minus the one you want to remove.

=== How do I change how my recipe is built depending on what image I'm building? ===

The short answer is you cannot - the reason is that OpenEmbedded builds packages based on the overall configuration, and then the image only selects which of these packages should go into the final image. However, there are some solutions that do allow you to achieve the desired result:

# Have separate packages for the two different versions. This could take the form of different recipes or you could do it within the same recipe. The two packages do have to have different names however; this may create problems if you have other packages that depend on the package.
# Use a postprocessing function within the image(s) - within the image recipe, define a shell or python function that makes the desired changes to the files in the image and add a call to it to ROOTFS_POSTPROCESS_COMMAND within the image recipe. Note that this may not be appropriate if you have runtime package management enabled since the postprocessing will only happen at image creation time and not if the package is installed later on at runtime - you may need to use a postinstall script instead in this case.
# Use a postinstall script (pkg_postinst_<package> function) within the recipe. In order to work, the postinstall script will need to be able to determine what to do when it's run - this may not be practical depending on what you're trying to achieve.

=== Can I use a toolchain built by OE as the external toolchain? ===

In general, this is not recommended and not something that is tested or directly supported out of the box. If you are wanting to do this solely as a means of speeding up the build, it is strongly suggested that you use shared state instead.

There is a [http://layers.openembedded.org/layerindex/branch/master/layer/meta-sourcery/ meta-sourcery layer] available to enable support for the CodeSourcery toolchain, you may be able to use this as a template for bringing in an external toolchain however there are no guarantees.

=== When I run bitbake -c devshell it looks like it's running as root! How is that possible? ===

It's not running as the actual root user, it's just pretending for the benefit of programs that run under it (including your shell) that it is, via pseudo. This is important, because you normally want any owner/group/permission values that you set on files to be reflected in files that the recipe installs and packages and thus reflected in the final image - without this mechanism the actual build would have to run as root which would be very risky. There are no actual elevated privileges through this mechanism however, so you need not be worried.

=== Why does OE use pseudo? Why not use fakeroot / fakechroot instead? ===

Splitting this up into two questions - we use pseudo (not to be confused with sudo!) because we want to be able to create images containing files have the correct permissions and ownership, e.g. files owned by root, without the user running the build system having to have that privilege. By using LD_PRELOAD to intercept function calls, pseudo creates an environment for programs running underneath it where it appears as if the running user has those privileges (and the results of any operations persist within the pseudo environment, i.e. you can write a file as root and it will appear to be owned by root while still running under pseudo). This allows us to run builds entirely as a normal user without needing extra privileges. Without pseudo we would require running the build system under sudo or as root - which would be ill-advised for things such as "make install" in case it happened to be broken and tried to write to / instead of somewhere under the work directory for the recipe; a broken recipe could easily end up destroying your system in that case.

To answer the second part, why we use pseudo instead of fakeroot / fakechroot, see [https://github.com/wrpseudo/pseudo/wiki/WhyNotFakeroot WhyNotFakeroot on the pseudo wiki].

=== How do I find out what packages are produced by a recipe? ===

The Toaster web UI provides easy ways to query this.

In the 1.8 (fido) release and newer you can use the following command, assuming the recipe has already been built:

oe-pkgdata-util list-pkgs -p <recipename>

Alternatively you can look in the "packages-split" subdirectory under the work directory for the recipe - each package produced by the recipe will have a subdirectory under that. If you're not sure how to find the work directory you can run the following command:

bitbake -e <recipename> | grep ^WORKDIR=

Before a recipe gets built it is a bit trickier, since the system often doesn't know exactly which packages will be produced until do_package time; this is particularly true for recipes that package plugins or modules (e.g. kernel modules). You can get a reasonable idea though by looking at the value of PACKAGES (and PACKAGES_DYNAMIC for recipes that produce plugins).

=== How do I find out which package contains a particular file (or python module)? ===

oe-pkgdata-util has a find-path subcommand that will tell you exactly this. For example:

$ oe-pkgdata-util find-path /etc/network/interfaces
init-ifupdown: /etc/network/interfaces

Wildcards are allowed anywhere in the path (but you should enclose such expressions in quotes to avoid the shell itself attempting to expand the wildcard):

$ oe-pkgdata-util find-path "*/fstrim"
util-linux-bash-completion: /usr/share/bash-completion/completions/fstrim
util-linux-ptest: /usr/lib/util-linux/ptest/fstrim
util-linux-dbg: /sbin/.debug/fstrim
util-linux-fstrim: /sbin/fstrim

As a specific example of where this can be useful, our Python packaging is a bit more granular than most typical distributions, allowing you to tune the contents of your image to just what you need. However, that does mean you may have trouble figuring out which package provides a particular module. oe-pkgdata-util find-path can also be used for this. For example, to find the package containing the "shutil" module, run this:

$ oe-pkgdata-util find-path "*/shutil.*"
python3-shell: /usr/lib/python3.5/shutil.py
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-2.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-1.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.pyc

Thus the package you are looking for is python3-shell. (Note that you could use */shutil.py, but if the module you are looking for is written in C as some of them are, that won't match it.)

=== I have a local source tree I want to build instead of the upstream source a recipe normally fetches, how do I do that? ===

If it's for development purposes i.e. you have your own local source tree you want to work on and have built, then run:

devtool modify -n <recipename> path/to/sourcetree/

Once you are done you can use <code>devtool finish</code> or <code>devtool reset</code> (depending on the situation) to return to building the source specified in the recipe.

Alternatively if it's more permanent, use the <code>externalsrc</code> class - you can inherit this in the original recipe or a bbappend:

inherit externalsrc
EXTERNALSRC = "/path/to/sources"

If you're going to use it across a number of recipes you can inherit it globally at the configuration level (perhaps via an inc file that you include/require there):

INHERIT += "externalsrc"
EXTERNALSRC_pn-<recipename> = "/path/to/sources"

=== How do I specify the default shell? (e.g. bash instead of busybox) ===

It depends what you mean. As far as which provides /bin/sh, this is controlled through the alternatives system, and by default bash has a higher priority than busybox, so simply installing bash into your image will automatically have /bin/sh link to bash rather than busybox.

If you mean you want a user's login shell to be a specific shell, you'll need to modify /etc/passwd. One fairly easy way to achieve this is to use the extrausers class in your image recipe:

inherit extrausers
EXTRA_USERS_PARAMS = "usermod -s /bin/bash <username>; "

=== How do I get "full" versions of typical shell commands? ===

Most of the shell commands in our images are provided by busybox by default, and are very much simplified compared to what you would have on a typical Linux system in order to save space. If you need the full versions, most of them are built and packaged by the coreutils recipe (for disk and other typical utilities) and procps (for ps, etc). You may also want to install bash for more typical shell built-in commands. There is also a core-image-full-cmdline image if you want a base image that is already set up to provide a more typical Linux command-line experience. (Note: these will of course use up more disk space and memory.)

=== How do I allow a variable's value through from the external environment? ===

Add the variable's name to the BB_ENV_EXTRAWHITE ''in the external environment'' before running bitbake. Note that the oe-init-build-env script sets a default for this which you will want to preserve, so add to the default value rather than overwriting it.

Alternatively if you just want to get the external value of a variable from python code within the metadata, you can use the BB_ORIGENV variable which itself contains a datastore of the original environment. For example to get the value of the DISPLAY variable from the environment within a python function you would do this:

display = d.getVar("BB_ORIGENV", False).getVar("DISPLAY")

Note that you must specify "false" for the expand parameter when getting the BB_ORIGENV variable, because it's not a string and therefore cannot be expanded in the normal manner.

=== Why is bitbake showing "AUTOINC" in the version for some recipes? ===

Recipes where you see AUTOINC within the version in the console output during a build will be those that set <code>PV</code> to include <code>"${SRCPV}"</code> to get the SCM revision (e.g. the git hash) in the package version. In order to have the version increment properly, there needs to be a number in front of the revision which automatically increments each time the revision changes (assuming you have a PR server enabled), which is where AUTOINC comes in. During the build, AUTOINC is a stand-in for this auto-incrementing number, and later during <code>do_package</code> it gets replaced with the real number so that the packages produced at the end have the full version number.

=== Why are .so files in the -dev package instead of the main package for a recipe? ===

In standard Unix library packaging, non-versioned .so symlinks (e.g. /usr/lib/libgd.so) are intended for development purposes only. At runtime, binaries should be linked to the major-versioned .so file/symlink e.g. /usr/lib/libgd.so.3. This (theoretically) allows multiple major versions of the same library as well as binaries that depend upon each of them to coexist on the same system. If the library is versioned but you have a binary that links to the unversioned .so file, it has almost certainly been linked incorrectly.

Non-symlink .so files on the other hand are sometimes produced and are entirely legal - however these will be picked up in the -dev package in OpenEmbedded simply by virtue of their name, which is almost always not what you want. In this case you can do one of two things:

# Fix the build of the library so it gets versioned. This may not always be appropriate, especially not for things like plugins.
# Set FILES_${PN}-dev within the recipe so that it does not include ${FILES_SOLIBSDEV}. If the software the recipe is building also produces symlink .so files you'll need to set FILES_${PN}-dev such that those do still get packaged in the -dev package though, or you'll get a package QA warning.

=== Can I disable shared state? ===

You cannot, no. Shared state (sstate) is an intrinsic part of staging files into the sysroot. It is possible to construct a recipe that bypasses sstate for some tasks (the kernel does this), however this is quite difficult and if not done properly will lead to many other problems.

Almost always when you are having a problem with shared state the issue is either (a) you're adding/changing files in the sysroot directly (i.e. outside sstate control), or (b) what is being placed into the sysroot isn't relocatable due to hardcoded paths. The solution for (a) is do not do that - files should always be installed under <code>${D}</code> within <code>do_install</code> and then a subset of those are staged into the sysroot automatically. For (b) you need to fix or adapt the hardcoded path(s) - if the program reads (or can be made to read) each path from an environment variable, then you can use the <code>create_wrapper</code> utility function to create a wrapper script that will set the path appropriately. Run <code>git grep create_wrapper</code> in the <code>meta</code> subdirectory to see examples.

=== Files I installed into /opt or some other path never make it into the sysroot but I need them - how do I fix this? ===

OpenEmbedded only stages a subset of files that are installed into <code>${D}</code> by <code>do_install</code> so that the sysroot doesn't fill up with unneeded files. You have two choices in this situation:
# install the files into a more standard location which is part of the subset, or
# adjust the subset to include the paths you are installing to.
Usually option 1 is recommended. If you really do need to adjust the subset, you can append the path (more specifically, the part below <code>${D}</code>) to <code>SYSROOT_DIRS</code> within your recipe. For example:

SYSROOT_DIRS += "/opt"

=== I have some software which needs to build a binary that it then runs as part of its own build process, how do I make this work? ===

Whilst it is possible to do this within a single recipe building for the target, it is tricky to do so because in that context everything is set up for cross-compiling for the target, and you would have to undo all of that to build host tools. The standard and much easier way of handling this is to create a native variant of the recipe using BBCLASSEXTEND and have your host tools built within that, and then have the target variant depend on the native variant. For example, assume your recipe were called xyz (xyz_1.1.bb), then you would include something like this in the recipe:

DEPENDS_append_class-target = " xyz-native"

...

BBCLASSEXTEND += "native"

The host tools will then be built and installed into the sysroot in the native variant ready for when the target variant starts building. If the software you are building didn't intend for those tools to be installed outside of the build tree then you may need to patch the build process (e.g. the makefile) in order to install them and possibly also for the target side to find them in the sysroot. Additionally, for performance since you only need the tools in the native variant, you may also choose to disable building everything except those tools there - e.g. by using _native overrides for variables such as EXTRA_OECONF or functions such as do_configure.

=== How do I fetch from two git repositories in the same recipe? ===

By default, sources fetched from git within a recipe are unpacked into ${WORKDIR}/git, however that only works for a single repository. If you want to fetch from more than one, you need to change the path each repository is unpacked to. This is easy to do, just add <code>;destsuffix=<subdir></code> to the end of each URL in SRC_URI (replacing <code><subdir></code> with the name of the subdirectory). You may then need to change S to match whichever of these you want to be considered the root of the source tree - or alternatively you can specify destsuffix such that repositories beyond the first go into a subdirectory under the default "git" subdirectory. For example, from the gst-libav recipe:

...
SRC_URI = " \
git://anongit.freedesktop.org/gstreamer/gst-libav;branch=1.8;name=base \
git://anongit.freedesktop.org/gstreamer/common;destsuffix=git/common;name=common \
...
"
...
S = "${WORKDIR}/git"
...

(Here we're using the default of "git" for the first repository, so we don't need to specify <code>destsuffix</code> for the first URL.)

=== I'm building a native recipe and I notice that the install path has the full path to the root directory repeated - why? ===

It does look a little odd, but the reason for doing this is that native targets are meant to run on the system they're built on and run in the location they're installed to. This means they install to a destination of "/" and PREFIX is inside the native sysroot directory. We install them to a DESTDIR to allow us to manipulate them before they then get moved to a final DESTDIR of "/".

Most Makefiles handle this correctly by doing:

DESTDIR ?= ""
prefix ?= "/usr"
bindir ?= "$(prefix)/bin"

and then, importantly, install in the form:

install -d $(DESTDIR)$(bindir)

so both prefix and DESTDIR are used. Whilst this is a convention, its a widely adopted and followed one. You can call into a custom makefile and set the variables manually if the makefile doesn't follow the convention.

=== How do I generate static libraries? ===

Its possible you have conf/distro/include/no-static-libs.inc included in your build - poky does this by default. The include list at the top of the bitbake -e output will tell you for certain.

If so, you can remove that or set:

DISABLE_STATIC = ""

as it would currently be set to this if that include file is included:

DISABLE_STATIC = " --disable-static"

Poky disables building static libraries by default as for the most part they're a waste of space/time.

=== Can I conditionally inherit a class in a recipe? ===

Yes, you can. What makes this possible is that the <code>inherit</code> keyword will not complain if what comes after it expands to being empty, so you can use in-line python to do something like this:

<pre><nowiki>
inherit ${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}
</nowiki></pre>

The above example will inherit the <code>perlnative</code> class if "scripting" is in the value of the <code>PACKAGECONFIG</code> variable, otherwise it will do nothing.

You could of course put this into a variable if you prefer:

<pre><nowiki>
SOMEVAR = "${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}"
inherit ${SOMEVAR}
</nowiki></pre>

=== How do I collect the source revisions fetched by each recipe? ===

If you have recipes where <code>SRCREV = "${AUTOREV}"</code> then you won't necessarily know exactly which revisions were built after the fact - it will be whatever was current at the time. You also might alternatively just want to get all of the revisions. Either way, to do this, enable buildhistory by setting the following in your local.conf:

<pre><nowiki>
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
</nowiki></pre>

(The last line is not required with version 2.5 and onwards as it is the default, but will do no harm.)

Once you have enabled buildhistory, you then need to build your image again so that buildhistory has a chance to record history data for it. Following that you can run <code>buildhistory-collect-srcrevs</code> (with <code>-a</code> if you want to see all revisions, not just the ones where AUTOREV was used) and it will output the revisions in a form you can use in a .inc file that you can <code>require</code> from your configuration if you want to fix the build to those revisions.

For more information see the [https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] section of the Yocto Project Development manual, which covers the buildhistory class in detail.

=== How do I do an offline build with recipes that have <code>SRCREV = "${AUTOREV}"</code> set? ===

If you set <code>BB_NO_NETWORK = "1"</code> and you have recipes that have <code>SRCREV = "${AUTOREV}"</code>, you will get an error because the build system will try to check the latest revision on startup and be immediately blocked by <code>BB_NO_NETWORK</code>. There are two ways to handle this:

A) See the previous question "How do I collect the source revisions fetched by each recipe?" and use the output generated by <code>buildhistory-collect-srcrevs</code> as a .inc file in your configuration in order to fix the revisions at the ones which were most recently built.

or

B) Set <code>BB_SRCREV_POLICY = "cache"</code> in your configuration. This will use the last cached revision. (The disadvantage of this method is that it is a little more difficult to preserve or share with others the fixed revisions.)

Note that in either case if you later want to build the latest version again, you will of course need to undo the configuration changes.

=== Is it possible to append a bbclass file (like bbappends do for recipes)? ===

No, see the next question for details.

=== How do I override a bbclass file? ===

This is tricky - bbclass files are found via BBPATH, which is added to by each layer.conf either by prepending or appending. Assuming you are putting your bbclass in a custom layer, you will probably want to have your layer's layer.conf prepend to BBPATH, but then you will also need to make sure that your layer does not appear before any other layer that is also prepending and overriding the same class.

Another alternative is to have an additional class which makes the appropriate changes to the environment, and then you will need to inherit that class after (and in the same manner as) the original class. This is slightly cleaner but can be annoying to enable particularly if the class is inherited by a number of recipes, and won't work if you want to alter the behaviour of a class inherited by recipes you don't control. (If you want a class to be inherited for all images (i.e. all recipes inheriting the <code>image</code> class) you can inject additional classes by setting IMAGE_CLASSES; similarly for the kernel there is KERNEL_CLASSES).

Ultimately, overriding bbclass files is not good practice long term - you are opening yourself up to maintenance issues when the original class changes, and the override is fragile as hinted above. The best solution is to try to get whatever changes you need into the original class; this does of course require additional work and time though.

=== There's a bbappend in a layer I'm using that defines a <code>do_something_append()</code> and I want to append to that function also, how do I do this? ===

Simply create a bbappend in your layer and define your own <code>do_something_append()</code>, and your commands will be executed ''as well as'' those of the other bbappend.

You might assume that defining <code>do_something_append()</code> will overwrite any previously defined <code>do_something_append()</code>, as would be the case with <code>do_something()</code> in the same situation, but that is not the case - the key is that <code>_append</code> (and <code>_prepend</code>, <code>_remove</code>, etc.) are ''operators'' and they will be applied in sequence, where that sequence is the order in which they are parsed (which for bbappends will be in ascending layer priority order).

Technical FAQ

2020-07-01T01:25:54Z

PaulEggleton: /* I'm getting warnings that a recipe is tainted - what does this mean? */

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
| '''NOTE:''' This is currently a draft. Not sure where this should end up but I've been gathering these based on my interactions with people on IRC and email over the years. - [[User:PaulEggleton|PaulEggleton]] ([[User talk:PaulEggleton|talk]]) 21:13, 27 June 2016 (PDT)
|}

== Basics ==

=== How do I figure out which version/codename/bitbake version matches up with which? ===

There is a table in the [http://wiki.yoctoproject.org/wiki/Releases Releases page] on the Yocto Project wiki.

=== How do I control what's in the final image? ===

Each image is defined by its own recipe, and that recipe specifies a list of packages that the image should contain. See [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Customising Images] within the Yocto Project development manual for further details.

Note: if you're doing anything more than basic experimentation / testing then you almost certainly should create your own image recipe rather than using one of the example images e.g. core-image-minimal - though you can certainly start by copying one of the example images. This way you have easier control over what goes into the image.

=== Where do I find build logs? ===

For the overall build, the output of bitbake gets logged to tmp/log/cooker/<machine>.

For each individual recipe, there is a "temp" directory under the work directory for the recipe that contains log.<taskname> and run.<taskname> files - the logs and the runfiles respectively. Within the build system this directory is pointed to by the T variable, so if you need to you can find it by using <code>bitbake -e</code>:

bitbake -e <recipename> | grep ^T=

=== How do I add a patch to a recipe? ===

There are two concerns - how the recipe can fetch the patch and how it can be applied. For fetching, patch files are usually placed in a subdirectory next to the recipe; by default this directory should be named "files" or the the recipe name without any class prefix or suffix (for example for both "xyz" and "xyz-native" the subdirectory would be "xyz"). A pointer to it then needs to be added to <code>SRC_URI</code> within the recipe, which usually takes the form <code>file://<patchname>.patch</code> - i.e. just the filename, no path. If more than one subdirectory needs to be stripped off the paths in the patch (i.e. you need more than the equivalent of the -p1 option to the patch command) then you can add <code>;striplevel=<number></code> to the end of the patch entry in SRC_URI (without any spaces).

As with any modification, if the patch you are applying is a customisation that you do not intend to send to be incorporated in the layer you are modifying, then instead of adding the patch to the recipe directly then you should consider applying it in a bbappend within your own custom layer. This makes things easier if you later want to update the layer in question and the recipe has been modified upstream - you avoid effectively forking the layer.

The <code>devtool</code> utility can help you modify the sources for a recipe and create a patch - basically <code>devtool modify</code>, edit the sources, commit the changes with <code>git commit</code>, then <code>devtool finish</code> (or <code>devtool update-recipe</code> in versions older than 2.2). Since <code>devtool modify</code> gives you a git tree to work with, you can of course use something like <code>git am</code> to apply existing patches this way. For more details see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#devtool-use-devtool-modify-to-enable-work-on-code-associated-with-an-existing-recipe Use devtool modify to Enable Work on Code Associated with an Existing Recipe] within the Yocto Project Development manual.

=== What does "native" mean? ===

The "native" suffix identifies recipes (and variants of recipes) that produce files intended for the build host, as opposed to the target machine. This is usually for tools that are needed during the build process (such as automake).

=== What does "nativesdk" mean? ===

The "nativesdk" prefix identifies recipes (and variants of recipes) that produce files intended for the host portion of the standard SDK, or for things which are constructed like an SDK such as buildtools-tarball. These are built for SDKMACHINE which may or may not be the same architecture as the build host.

=== I have two recipes and one needs to access files provided by another - how can that work? ===

Instead of providing direct access from a recipe to another's build tree (which wouldn't be practical with OpenEmbedded since the build tree (or "workdir") is temporary), we create a "sysroot" where files that are intended to be shared between recipes get copied. The sysroot is managed by the build system and you should not copy files in there directly - instead, you install files under ${D} as normal during do_install and then the build system will copy a subset of those to the sysroot. There is a seperate sysroot for each machine being built for. In a recipe you can get the path of the sysroot and various standard directories under it using the STAGING_* variables.

Often, for commonly-used build systems such as autotools and cmake you don't need to worry about these details - those systems and the environment that OpenEmbedded sets up for them will ensure that files get installed and picked up in the correct locations. However if the software your recipe is building has custom build scripts / makefiles and it takes shortcuts that don't account for cross-compilation or the use of a sysroot, then you will need to make appropriate adjustments.

=== How do I enable package management in the final image? ===

Add <code>package-management</code> to <code>IMAGE_FEATURES</code> (or <code>EXTRA_IMAGE_FEATURES</code>). You should then be able to use dnf/rpm, opkg, or apt-get/dpkg from the running system depending on the packaging format you have selected through PACKAGE_CLASSES. For more information see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-runtime-package-management Using Runtime Package Management] in the Yocto Project Development manual.

=== What do ?=, ??=, := etc. do within a recipe/config file? ===

See the [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#basic-syntax Basic Syntax section of the BitBake manual] for details.

== Layers ==

See http://www.openembedded.org/Layers_FAQ

== Troubleshooting ==

=== I've created a recipe but it's not showing up in my image, what's going on? ===

Creating a recipe (or adding a layer to your configuration with a desired recipe in it) only makes it available to the build system, it doesn't change what goes into the image. For that, see [[#How do I control what's in the final image?|How do I control what's in the final image?]] above.

=== I set a variable but it doesn't seem to be having an effect, how do I fix this? ===

First, double-check that you haven't misspelled the variable name.

The main tool to help troubleshoot any variable-related issue is <code>bitbake -e</code> - this lists all the variables and the complete history of how each one has been set (use <code>bitbake -e recipename</code> if you're dealing with issues in a variable value within a recipe as opposed to the global level). Usually it's best to pipe this through <code>less</code> so you can easily see the history - within less you can press / to search for the variable name. Often you will be dealing with the behaviour of a variable within the context of a specific recipe, so specify that recipe on the <code>bitbake -e</code> command line to get the variables as set within the context of the recipe rather than the global context.

If you're setting a variable in a bbappend, double-check that the bbappend is actually being applied - see the next question.

=== I've created a bbappend for a recipe but what I'm setting there isn't having any effect, how do I fix this? ===

Here are some things to check:

# Check if the layer the bbappend is in is listed in <code>bitbake-layers show-layers</code>. If it isn't, you need to edit your bblayers.conf and ensure the path to the layer is included in the BBLAYERS value
# Check that the bbappend is being picked up by running <code>bitbake-layers show-appends</code> - if your bbappend file isn't listed, it could be named incorrectly (such that it doesn't match the recipe name) or it may be that the BBFILES value in the conf/layer.conf for the layer containing the bbappend file doesn't include an expression that will match the bbappend files.
# If there are multiple versions of the recipe you have bbappended, it could be that the actual recipe being built is a different version than the one you have bbappended. <code>bitbake-layers show-recipes <recipename></code> will list all the versions, with the first one listed being the one that will be built. If this is the case there are several different solutions to this - (a) Rename your bbappend to match the version being built, (b) use a % wildcard in your bbappend so it will apply to any version, (c) set <code>PREFERRED_VERSION_<recipename></code> in the configuration to select a the version you want to be built.
# Finally, as with any other issue with setting variables, use <code>bitbake -e recipename | less</code> and search with <code>/</code> to see the history of how the variable has been set - you may find that the value you're trying set is being overridden.

=== I'm getting warnings that a recipe is tainted - what does this mean? ===

Usually this happens because you have used I used bitbake's <code>-f</code> or <code>-C</code> option to force a task to re-execute. The assumption is that if you forced a task, it is possible that a rebuild from scratch would not include whatever changes you made that necessitated forcing (e.g. if you modified the source in the work directory for the recipe and then ran <code>bitbake -c compile -f</code>). Generally, forcing a task should be reserved for situations where the build system has failed to detect a change you made rather than for everyday usage - if you're finding yourself needing to do it regularly then either there's a bug, you're doing something wrong, or perhaps you're using <code>-f</code> or <code>-C</code> when it's not really needed. Running <code>bitbake -c clean</code> on the recipe will get rid of the taint flag.

There is one other situation where we apply a taint, and that is <code>bitbake -c menuconfig</code> on the kernel (or some other kconfig-using recipe). In this case, the configuration has been saved into the work directory for the kernel, but that is temporary - any rebuild from scratch will use the default configuration, so it is a reminder that you need to take the configuration and apply it back to the metadata and then run <code>bitbake -c clean</code> on the kernel recipe.

=== I'm fetching from a git repository over ssh / http / https but it's not fetching properly, how do I fix this? ===

Bitbake expects the prefix of entries in SRC_URI to specify the fetcher to be used, not the actual protocol. Thus, instead of:

# This will NOT work
SRC_URI = "<nowiki>https://git.example.com/repository</nowiki>"

You should specify:

# This is better
SRC_URI = "<nowiki>git://git.example.com/repository;protocol=https</nowiki>"

The same applies for ssh and of course http.

=== I tried bitbake <some target package name> that I know exists and it told me that nothing PROVIDES this...? ===

There are two namespaces that bitbake concerns itself with - recipe names (a.k.a. build time targets) and package names (a.k.a. runtime targets). You can specify a build time target on the bitbake command line, but not a runtime target; you need to find the recipe that provides the package you are trying to build and build that instead (or simply add that package to your image and build the image). In current versions bitbake will at least tell you which recipes have matching or similar-sounding runtime provides (RPROVIDES) so that you'll usually get a hint on which recipe you need to build.

=== I've included a package in my image but files I expect to be there are missing, what's the issue? ===

Check the simple stuff: verify that the package is really in the image - look at the manifest file next to the image to ensure the package is listed. Also if you're flashing the image, double-check that you did indeed flash the right image and if there are multiple partitions / storage devices on your board or device that you're booting the one that you think you are.

Once you're sure of the above, it may be a matter of the package splitting - a lot of recipes split less commonly used components out to separate packages, so it's possible that the files you are looking for are in a different package. You can look at the recipe for this (look for PACKAGES and FILES statements) or assuming the recipe has been built, you can use <code>oe-pkgdata-util list-pkgs -p recipename</code> and <code>oe-pkgdata-util list-pkg-files</code> to inspect the packages provided by the recipe and the files they contain. Once you find the right package you can add it to your image.

=== I'm required to set LIC_FILES_CHKSUM but the software I'm building doesn't have a license statement, what do I do? ===

Ideally, all software should come with some kind of license statement so that the terms of distribution are clearly stated (especially if its source code is made publicly available); if not a text file describing the license then at the very least a line or two in the accompanying documentation, README file or source header comments. Assuming there is a license statement somewhere but not in a form you can point to with LIC_FILES_CHKSUM as part of the source tree, you can point LIC_FILES_CHKSUM to one of the generic license files in ${COMMON_LICENSE_DIR} (meta/files/common-licenses/), or alternatively you can include a file containing the license statement in a "files" subdirectory next to the recipe (or subdirectory named the same as the recipe - see how such files are handled in other recipes), point to it in SRC_URI using file://, then add it to LIC_FILES_CHKSUM. It is worth noting however that LIC_FILES_CHKSUM is intended to give you a warning if upstream changes its license terms when you do an upgrade of the recipe, and by pointing it to this common license file that is part of the metadata, that mechanism will not function. You may wish to consider encouraging the upstream provider of the software your recipe is building to follow best practices and include a proper license statement, so that you can point to it in a future version. At minimum if you do use such workarounds, you will need to take extra care when upgrading the recipe in future in case the upstream provider changes the license terms.

If there really is no license stated at all anywhere for the software (and this is unfortunately not uncommon on github, for example) then you should really contact upstream - if there's no license, then technically you really shouldn't be distributing it until that's clarified with the original author(s).

=== I am getting a package QA error / warning when building a recipe, how do I solve it? ===

There are some general and specific recommendations in the [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-errors-and-warnings QA Errors and Warnings] section of the Yocto Project Reference Manual.

=== I am getting "taskhash mismatch" errors, what does this mean and how do I fix it? ===

Bitbake parses the metadata (recipes, classes and configuration) repeatedly during its operation, and this error means that the result of parsing changed between one parse and the next. Two situations that can cause this:
# One of the parsed files changed in between e.g. you edited a recipe or performed a git operation (e.g. git checkout) during the build. '''Do not make changes to the metadata while a build is running.''' If you run the build again the error should not recur.
# Alternatively, there is something in the metadata that results in a variable expanding to a different value each time it is parsed. This is often something time-related e.g. a timestamp which is calculated every time an expression is expanded. The solution is to ensure the value is calculated once per build and then the expression expands to the same value for the duration of the build.

=== Building on a system with a GRSec kernel doesn't work well, is that supported? ===

No, grsec isn't really supported. The list of distros that are supported (tested) is in the Yocto mega manual for each release.
You can refer to the work-around given in this defect: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10885

=== Working around Firejail ===
For users of Parrot OS and other secured Linux distros, you will find that your bitbake fetch commands refuse to work, yet you can manually run wget and retrieve the packages with no problem. This is due to Poky creating links to all the tools it requires, in particular 'wget', 'ssh' and 'strings', using the links to these tools in the /usr/local/bin/ directory which all redirect to firejail. To fix the problem you can cd into <your Yocto install directory>/poky/build/tmp/hosttools directory and replace these links with ones redirecting to the actual executables under the /usr/bin directory.

== Dependencies ==

=== How do I find out why something is being built? ===

<code>bitbake -g <recipe></code> will produce some .dot files that allow you to see the dependency relationships - usually pn-depends.dot holds the answers although sometimes you may need to look at task-depends.dot if the dependency is only in the form of a task dependency. Note that these graphs are much too large for most graphviz visualisation tools to process, so you'll probably find it's easiest to view them with "less" or a text editor and search for the item you're looking for.

=== How do I find out why something is in my image? ===

Enable the buildhistory class and build the image again, and it will write out a depends.dot file containing the relationships between packages in the final image. If the package name isn't mentioned it is probably explicitly mentioned in IMAGE_INSTALL or being brought in via IMAGE_FEATURES.

See [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] in the Yocto Project Reference manual which covers how to enable buildhistory and the output it produces.

=== How do I view the .dot files produced by bitbake -g or buildhistory? ===

The size of some of these .dot graphs (particularly those produced by <code>bitbake -g</code>) is a little large for most viewers / processing tools, and unfortunately this isn't something that can be fixed - it's just the nature of the dependency relationships between targets and tasks within OpenEmbedded. Usually if you're just after answering a simple dependency question you can figure it out by viewing it with <code>less</code> and using its built-in search function (or alternatively your favourite text editor).

You can try [http://github.com/jrfonseca/xdot.py xdot] which will work well for some of the graphs, but the task graph produced by <code>bitbake -g</code> for something like an image in particular is likely to be too large to view within it.

=== Why are all of these -native items being built when my host distro has some of these available? ===

It's complicated. In some cases the software in question isn't widely packaged by common Linux distributions. In other cases we need to apply patches to the software, use a more up-to-date version than commonly packaged or build it with a particular configuration. In general it just helps us isolate ourselves from potential problems caused by differences in host Linux distributions. For the most part the time spent building the native tools that are definitely provided by the host distro are dwarfed by the time spent building things that definitely aren't provided, such as the C library for the target and the cross-compiling toolchain.

=== I disabled runtime package management and yet it still seems to be building rpm/opkg, why? ===

The build system always uses a package manager on the host to assemble images, because it is usually the best tool for this job. This is completely independent of whether the package manager is available in the target image - "package-management" being in IMAGE_FEATURES (possibly indirectly via EXTRA_IMAGE_FEATURES) controls whether the package manager is used at runtime i.e. whether it (and its associated package database) will be present in the target image.

=== Why is opkg-native / opkg-utils being built when I don't have ipk packaging enabled? ===

opkg-utils provides update-alternatives which is the default tool used to manage the alternatives system (for selecting between multiple providers of the same file, e.g. busybox and bash both provide /bin/sh).

=== Why is rpm-native being built when I don't have rpm packaging enabled? ===

rpm-native is needed for two things in the generic packaging code implemented in the package class:

# Debug symbol splitting - rpm-native provides the debugedit tool which this code uses
# Per-file dependencies - although this was originally just feeding into rpm when rpm was being used, it also now gets verified by QA checks regardless of which packaging backend is in use.

=== I see a recipe built, but building an image containing the corresponding package fails at do_rootfs because it can't find the package. How does this happen? ===

(For ipk, the error is "Couldn't find anything to satisfy '<package>'"; for rpm it is "<package> not found in the base feeds (<architecture list>)".)

Usually this is because the recipe claimed to provide the specified package (via PACKAGES or PACKAGES_DYNAMIC) but it wasn't actually produced, possibly because it ended up empty (since by default empty packages aren't produced), but the image or some other package still has a dependency that pulls in the specified package. If this is a recipe you are writing yourself the probable cause is your recipe isn't installing any files and thus the main package for the recipe is empty. Fix do_install (or what do_install is already running, e.g. make install) such that files are installed into the correct location such that they can then subsequently be packaged, and then all should be well.

In other situations the reference to the package in question is spurious and either it should be removed entirely or there's another package that should be used instead. For example, the avahi and dhcp recipes both have an empty main package since the client and server are split out into their own packages, and those are the ones you should be using instead (avahi-daemon, avahi-utils, dhcp-server, dhcp-client - there are other packages as well, please see [[#How_do_I_find_out_what_packages_are_produced_by_a_recipe.3F|How do I find out what packages are produced by a recipe?]].) You could argue that these recipes shouldn't claim to provide the main package, or they should have a main package that depends on all the other packages (as some other recipes do).

=== X11 and various other items are being built but I'm only building core-image-minimal that doesn't have X11 in it - why? ===

This is where it helps to understand the difference between build-time dependencies and runtime dependencies - often, a recipe will require things at build time (for example tools that help the build process, or to satisfy optional dependencies) that it doesn't necessarily need at runtime. The default configuration includes "<code>x11</code>" in <code>DISTRO_FEATURES</code>, and thus anything that can optionally support X11 will have its X11 support enabled; however when it comes to actually producing the image there won't be any X11 packages included as long as there are no hard dependencies and there aren't any X11 packages explicitly requested.

If you never intend to use X11, you can set your own <code>DISTRO_FEATURES</code> value that excludes <code>x11</code> (note lower case, as with all feature names) and then X11 support will be disabled at build time and these items won't even be built.

=== How do I avoid the kernel itself being pulled into my image when installing kernel modules? ===

By default, the kernel class sets a dependency on the kernel-base package (which kernel modules always depend on) onto kernel-image, which contains the actual kernel binary. If you don't want this, set the following either in your kernel recipe or at the configuration level:

RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""

Note: for older releases (pre-2.5) do this instead:

RDEPENDS_kernel-base = ""

== Misc ==

=== How do I remove a value from a list variable? ===

For variables that are expected to contain a space-separated list of items, BitBake supports a _remove operator to remove items from it. See [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#removing-override-style-syntax Removal (override style syntax)] in the BitBake user manual.

'''NOTE:''' the _remove operation is final - you cannot "undo" it with other operations elsewhere, thus you should really only make use of it in your distro / local configuration and not in layers that you expect others to re-use for different purposes (and therefore they may need to undo your changes). An alternative way to effectively remove an item is to set the list outright to include all the items minus the one you want to remove.

=== How do I change how my recipe is built depending on what image I'm building? ===

The short answer is you cannot - the reason is that OpenEmbedded builds packages based on the overall configuration, and then the image only selects which of these packages should go into the final image. However, there are some solutions that do allow you to achieve the desired result:

# Have separate packages for the two different versions. This could take the form of different recipes or you could do it within the same recipe. The two packages do have to have different names however; this may create problems if you have other packages that depend on the package.
# Use a postprocessing function within the image(s) - within the image recipe, define a shell or python function that makes the desired changes to the files in the image and add a call to it to ROOTFS_POSTPROCESS_COMMAND within the image recipe. Note that this may not be appropriate if you have runtime package management enabled since the postprocessing will only happen at image creation time and not if the package is installed later on at runtime - you may need to use a postinstall script instead in this case.
# Use a postinstall script (pkg_postinst_<package> function) within the recipe. In order to work, the postinstall script will need to be able to determine what to do when it's run - this may not be practical depending on what you're trying to achieve.

=== Can I use a toolchain built by OE as the external toolchain? ===

In general, this is not recommended and not something that is tested or directly supported out of the box. If you are wanting to do this solely as a means of speeding up the build, it is strongly suggested that you use shared state instead.

There is a [http://layers.openembedded.org/layerindex/branch/master/layer/meta-sourcery/ meta-sourcery layer] available to enable support for the CodeSourcery toolchain, you may be able to use this as a template for bringing in an external toolchain however there are no guarantees.

=== When I run bitbake -c devshell it looks like it's running as root! How is that possible? ===

It's not running as the actual root user, it's just pretending for the benefit of programs that run under it (including your shell) that it is, via pseudo. This is important, because you normally want any owner/group/permission values that you set on files to be reflected in files that the recipe installs and packages and thus reflected in the final image - without this mechanism the actual build would have to run as root which would be very risky. There are no actual elevated privileges through this mechanism however, so you need not be worried.

=== Why does OE use pseudo? Why not use fakeroot / fakechroot instead? ===

Splitting this up into two questions - we use pseudo (not to be confused with sudo!) because we want to be able to create images containing files have the correct permissions and ownership, e.g. files owned by root, without the user running the build system having to have that privilege. By using LD_PRELOAD to intercept function calls, pseudo creates an environment for programs running underneath it where it appears as if the running user has those privileges (and the results of any operations persist within the pseudo environment, i.e. you can write a file as root and it will appear to be owned by root while still running under pseudo). This allows us to run builds entirely as a normal user without needing extra privileges. Without pseudo we would require running the build system under sudo or as root - which would be ill-advised for things such as "make install" in case it happened to be broken and tried to write to / instead of somewhere under the work directory for the recipe; a broken recipe could easily end up destroying your system in that case.

To answer the second part, why we use pseudo instead of fakeroot / fakechroot, see [https://github.com/wrpseudo/pseudo/wiki/WhyNotFakeroot WhyNotFakeroot on the pseudo wiki].

=== How do I find out what packages are produced by a recipe? ===

The Toaster web UI provides easy ways to query this.

In the 1.8 (fido) release and newer you can use the following command, assuming the recipe has already been built:

oe-pkgdata-util list-pkgs -p recipename

Alternatively you can look in the "packages-split" subdirectory under the work directory for the recipe - each package produced by the recipe will have a subdirectory under that. If you're not sure how to find the work directory you can run the following command:

bitbake -e recipename | grep ^WORKDIR=

Before a recipe gets built it is a bit trickier, since the system often doesn't know exactly which packages will be produced until do_package time; this is particularly true for recipes that package plugins or modules (e.g. kernel modules). You can get a reasonable idea though by looking at the value of PACKAGES (and PACKAGES_DYNAMIC for recipes that produce plugins).

=== How do I find out which package contains a particular file (or python module)? ===

oe-pkgdata-util has a find-path subcommand that will tell you exactly this. For example:

$ oe-pkgdata-util find-path /etc/network/interfaces
init-ifupdown: /etc/network/interfaces

Wildcards are allowed anywhere in the path (but you should enclose such expressions in quotes to avoid the shell itself attempting to expand the wildcard):

$ oe-pkgdata-util find-path "*/fstrim"
util-linux-bash-completion: /usr/share/bash-completion/completions/fstrim
util-linux-ptest: /usr/lib/util-linux/ptest/fstrim
util-linux-dbg: /sbin/.debug/fstrim
util-linux-fstrim: /sbin/fstrim

As a specific example of where this can be useful, our Python packaging is a bit more granular than most typical distributions, allowing you to tune the contents of your image to just what you need. However, that does mean you may have trouble figuring out which package provides a particular module. oe-pkgdata-util find-path can also be used for this. For example, to find the package containing the "shutil" module, run this:

$ oe-pkgdata-util find-path "*/shutil.*"
python3-shell: /usr/lib/python3.5/shutil.py
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-2.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-1.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.pyc

Thus the package you are looking for is python3-shell. (Note that you could use */shutil.py, but if the module you are looking for is written in C as some of them are, that won't match it.)

=== I have a local source tree I want to build instead of the upstream source a recipe normally fetches, how do I do that? ===

If it's for development purposes i.e. you have your own local source tree you want to work on and have built, then run:

devtool modify -n <recipename> path/to/sourcetree/

Once you are done you can use <code>devtool finish</code> or <code>devtool reset</code> (depending on the situation) to return to building the source specified in the recipe.

Alternatively if it's more permanent, use the <code>externalsrc</code> class - you can inherit this in the original recipe or a bbappend:

inherit externalsrc
EXTERNALSRC = "/path/to/sources"

If you're going to use it across a number of recipes you can inherit it globally at the configuration level (perhaps via an inc file that you include/require there):

INHERIT += "externalsrc"
EXTERNALSRC_pn-<recipename> = "/path/to/sources"

=== How do I specify the default shell? (e.g. bash instead of busybox) ===

It depends what you mean. As far as which provides /bin/sh, this is controlled through the alternatives system, and by default bash has a higher priority than busybox, so simply installing bash into your image will automatically have /bin/sh link to bash rather than busybox.

If you mean you want a user's login shell to be a specific shell, you'll need to modify /etc/passwd. One fairly easy way to achieve this is to use the extrausers class in your image recipe:

inherit extrausers
EXTRA_USERS_PARAMS = "usermod -s /bin/bash <username>; "

=== How do I get "full" versions of typical shell commands? ===

Most of the shell commands in our images are provided by busybox by default, and are very much simplified compared to what you would have on a typical Linux system in order to save space. If you need the full versions, most of them are built and packaged by the coreutils recipe (for disk and other typical utilities) and procps (for ps, etc). You may also want to install bash for more typical shell built-in commands. There is also a core-image-full-cmdline image if you want a base image that is already set up to provide a more typical Linux command-line experience. (Note: these will of course use up more disk space and memory.)

=== How do I allow a variable's value through from the external environment? ===

Add the variable's name to the BB_ENV_EXTRAWHITE ''in the external environment'' before running bitbake. Note that the oe-init-build-env script sets a default for this which you will want to preserve, so add to the default value rather than overwriting it.

Alternatively if you just want to get the external value of a variable from python code within the metadata, you can use the BB_ORIGENV variable which itself contains a datastore of the original environment. For example to get the value of the DISPLAY variable from the environment within a python function you would do this:

display = d.getVar("BB_ORIGENV", False).getVar("DISPLAY")

Note that you must specify "false" for the expand parameter when getting the BB_ORIGENV variable, because it's not a string and therefore cannot be expanded in the normal manner.

=== Why is bitbake showing "AUTOINC" in the version for some recipes? ===

Recipes where you see AUTOINC within the version in the console output during a build will be those that set <code>PV</code> to include <code>"${SRCPV}"</code> to get the SCM revision (e.g. the git hash) in the package version. In order to have the version increment properly, there needs to be a number in front of the revision which automatically increments each time the revision changes (assuming you have a PR server enabled), which is where AUTOINC comes in. During the build, AUTOINC is a stand-in for this auto-incrementing number, and later during <code>do_package</code> it gets replaced with the real number so that the packages produced at the end have the full version number.

=== Why are .so files in the -dev package instead of the main package for a recipe? ===

In standard Unix library packaging, non-versioned .so symlinks (e.g. /usr/lib/libgd.so) are intended for development purposes only. At runtime, binaries should be linked to the major-versioned .so file/symlink e.g. /usr/lib/libgd.so.3. This (theoretically) allows multiple major versions of the same library as well as binaries that depend upon each of them to coexist on the same system. If the library is versioned but you have a binary that links to the unversioned .so file, it has almost certainly been linked incorrectly.

Non-symlink .so files on the other hand are sometimes produced and are entirely legal - however these will be picked up in the -dev package in OpenEmbedded simply by virtue of their name, which is almost always not what you want. In this case you can do one of two things:

# Fix the build of the library so it gets versioned. This may not always be appropriate, especially not for things like plugins.
# Set FILES_${PN}-dev within the recipe so that it does not include ${FILES_SOLIBSDEV}. If the software the recipe is building also produces symlink .so files you'll need to set FILES_${PN}-dev such that those do still get packaged in the -dev package though, or you'll get a package QA warning.

=== Can I disable shared state? ===

You cannot, no. Shared state (sstate) is an intrinsic part of staging files into the sysroot. It is possible to construct a recipe that bypasses sstate for some tasks (the kernel does this), however this is quite difficult and if not done properly will lead to many other problems.

Almost always when you are having a problem with shared state the issue is either (a) you're adding/changing files in the sysroot directly (i.e. outside sstate control), or (b) what is being placed into the sysroot isn't relocatable due to hardcoded paths. The solution for (a) is do not do that - files should always be installed under <code>${D}</code> within <code>do_install</code> and then a subset of those are staged into the sysroot automatically. For (b) you need to fix or adapt the hardcoded path(s) - if the program reads (or can be made to read) each path from an environment variable, then you can use the <code>create_wrapper</code> utility function to create a wrapper script that will set the path appropriately. Run <code>git grep create_wrapper</code> in the <code>meta</code> subdirectory to see examples.

=== Files I installed into /opt or some other path never make it into the sysroot but I need them - how do I fix this? ===

OpenEmbedded only stages a subset of files that are installed into <code>${D}</code> by <code>do_install</code> so that the sysroot doesn't fill up with unneeded files. You have two choices in this situation:
# install the files into a more standard location which is part of the subset, or
# adjust the subset to include the paths you are installing to.
Usually option 1 is recommended. If you really do need to adjust the subset, you can append the path (more specifically, the part below <code>${D}</code>) to <code>SYSROOT_DIRS</code> within your recipe. For example:

SYSROOT_DIRS += "/opt"

=== I have some software which needs to build a binary that it then runs as part of its own build process, how do I make this work? ===

Whilst it is possible to do this within a single recipe building for the target, it is tricky to do so because in that context everything is set up for cross-compiling for the target, and you would have to undo all of that to build host tools. The standard and much easier way of handling this is to create a native variant of the recipe using BBCLASSEXTEND and have your host tools built within that, and then have the target variant depend on the native variant. For example, assume your recipe were called xyz (xyz_1.1.bb), then you would include something like this in the recipe:

DEPENDS_append_class-target = " xyz-native"

...

BBCLASSEXTEND += "native"

The host tools will then be built and installed into the sysroot in the native variant ready for when the target variant starts building. If the software you are building didn't intend for those tools to be installed outside of the build tree then you may need to patch the build process (e.g. the makefile) in order to install them and possibly also for the target side to find them in the sysroot. Additionally, for performance since you only need the tools in the native variant, you may also choose to disable building everything except those tools there - e.g. by using _native overrides for variables such as EXTRA_OECONF or functions such as do_configure.

=== How do I fetch from two git repositories in the same recipe? ===

By default, sources fetched from git within a recipe are unpacked into ${WORKDIR}/git, however that only works for a single repository. If you want to fetch from more than one, you need to change the path each repository is unpacked to. This is easy to do, just add <code>;destsuffix=<subdir></code> to the end of each URL in SRC_URI (replacing <code><subdir></code> with the name of the subdirectory). You may then need to change S to match whichever of these you want to be considered the root of the source tree - or alternatively you can specify destsuffix such that repositories beyond the first go into a subdirectory under the default "git" subdirectory. For example, from the gst-libav recipe:

...
SRC_URI = " \
git://anongit.freedesktop.org/gstreamer/gst-libav;branch=1.8;name=base \
git://anongit.freedesktop.org/gstreamer/common;destsuffix=git/common;name=common \
...
"
...
S = "${WORKDIR}/git"
...

(Here we're using the default of "git" for the first repository, so we don't need to specify <code>destsuffix</code> for the first URL.)

=== I'm building a native recipe and I notice that the install path has the full path to the root directory repeated - why? ===

It does look a little odd, but the reason for doing this is that native targets are meant to run on the system they're built on and run in the location they're installed to. This means they install to a destination of "/" and PREFIX is inside the native sysroot directory. We install them to a DESTDIR to allow us to manipulate them before they then get moved to a final DESTDIR of "/".

Most Makefiles handle this correctly by doing:

DESTDIR ?= ""
prefix ?= "/usr"
bindir ?= "$(prefix)/bin"

and then, importantly, install in the form:

install -d $(DESTDIR)$(bindir)

so both prefix and DESTDIR are used. Whilst this is a convention, its a widely adopted and followed one. You can call into a custom makefile and set the variables manually if the makefile doesn't follow the convention.

=== How do I generate static libraries? ===

Its possible you have conf/distro/include/no-static-libs.inc included in your build - poky does this by default. The include list at the top of the bitbake -e output will tell you for certain.

If so, you can remove that or set:

DISABLE_STATIC = ""

as it would currently be set to this if that include file is included:

DISABLE_STATIC = " --disable-static"

Poky disables building static libraries by default as for the most part they're a waste of space/time.

=== Can I conditionally inherit a class in a recipe? ===

Yes, you can. What makes this possible is that the <code>inherit</code> keyword will not complain if what comes after it expands to being empty, so you can use in-line python to do something like this:

<pre><nowiki>
inherit ${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}
</nowiki></pre>

The above example will inherit the <code>perlnative</code> class if "scripting" is in the value of the <code>PACKAGECONFIG</code> variable, otherwise it will do nothing.

You could of course put this into a variable if you prefer:

<pre><nowiki>
SOMEVAR = "${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}"
inherit ${SOMEVAR}
</nowiki></pre>

=== How do I collect the source revisions fetched by each recipe? ===

If you have recipes where <code>SRCREV = "${AUTOREV}"</code> then you won't necessarily know exactly which revisions were built after the fact - it will be whatever was current at the time. You also might alternatively just want to get all of the revisions. Either way, to do this, enable buildhistory by setting the following in your local.conf:

<pre><nowiki>
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
</nowiki></pre>

(The last line is not required with version 2.5 and onwards as it is the default, but will do no harm.)

Once you have enabled buildhistory, you then need to build your image again so that buildhistory has a chance to record history data for it. Following that you can run <code>buildhistory-collect-srcrevs</code> (with <code>-a</code> if you want to see all revisions, not just the ones where AUTOREV was used) and it will output the revisions in a form you can use in a .inc file that you can <code>require</code> from your configuration if you want to fix the build to those revisions.

For more information see the [https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] section of the Yocto Project Development manual, which covers the buildhistory class in detail.

=== How do I do an offline build with recipes that have <code>SRCREV = "${AUTOREV}"</code> set? ===

If you set <code>BB_NO_NETWORK = "1"</code> and you have recipes that have <code>SRCREV = "${AUTOREV}"</code>, you will get an error because the build system will try to check the latest revision on startup and be immediately blocked by <code>BB_NO_NETWORK</code>. There are two ways to handle this:

A) See the previous question "How do I collect the source revisions fetched by each recipe?" and use the output generated by <code>buildhistory-collect-srcrevs</code> as a .inc file in your configuration in order to fix the revisions at the ones which were most recently built.

or

B) Set <code>BB_SRCREV_POLICY = "cache"</code> in your configuration. This will use the last cached revision. (The disadvantage of this method is that it is a little more difficult to preserve or share with others the fixed revisions.)

Note that in either case if you later want to build the latest version again, you will of course need to undo the configuration changes.

=== Is it possible to append a bbclass file (like bbappends do for recipes)? ===

No, see the next question for details.

=== How do I override a bbclass file? ===

This is tricky - bbclass files are found via BBPATH, which is added to by each layer.conf either by prepending or appending. Assuming you are putting your bbclass in a custom layer, you will probably want to have your layer's layer.conf prepend to BBPATH, but then you will also need to make sure that your layer does not appear before any other layer that is also prepending and overriding the same class.

Another alternative is to have an additional class which makes the appropriate changes to the environment, and then you will need to inherit that class after (and in the same manner as) the original class. This is slightly cleaner but can be annoying to enable particularly if the class is inherited by a number of recipes, and won't work if you want to alter the behaviour of a class inherited by recipes you don't control. (If you want a class to be inherited for all images (i.e. all recipes inheriting the <code>image</code> class) you can inject additional classes by setting IMAGE_CLASSES; similarly for the kernel there is KERNEL_CLASSES).

Ultimately, overriding bbclass files is not good practice long term - you are opening yourself up to maintenance issues when the original class changes, and the override is fragile as hinted above. The best solution is to try to get whatever changes you need into the original class; this does of course require additional work and time though.

=== There's a bbappend in a layer I'm using that defines a <code>do_something_append()</code> and I want to append to that function also, how do I do this? ===

Simply create a bbappend in your layer and define your own <code>do_something_append()</code>, and your commands will be executed ''as well as'' those of the other bbappend.

You might assume that defining <code>do_something_append()</code> will overwrite any previously defined <code>do_something_append()</code>, as would be the case with <code>do_something()</code> in the same situation, but that is not the case - the key is that <code>_append</code> (and <code>_prepend</code>, <code>_remove</code>, etc.) are ''operators'' and they will be applied in sequence, where that sequence is the order in which they are parsed (which for bbappends will be in ascending layer priority order).

Technical FAQ

2020-07-01T01:24:56Z

PaulEggleton: /* I'm fetching from a git repository over ssh / http / https but it's not fetching properly, how do I fix this? */

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
| '''NOTE:''' This is currently a draft. Not sure where this should end up but I've been gathering these based on my interactions with people on IRC and email over the years. - [[User:PaulEggleton|PaulEggleton]] ([[User talk:PaulEggleton|talk]]) 21:13, 27 June 2016 (PDT)
|}

== Basics ==

=== How do I figure out which version/codename/bitbake version matches up with which? ===

There is a table in the [http://wiki.yoctoproject.org/wiki/Releases Releases page] on the Yocto Project wiki.

=== How do I control what's in the final image? ===

Each image is defined by its own recipe, and that recipe specifies a list of packages that the image should contain. See [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Customising Images] within the Yocto Project development manual for further details.

Note: if you're doing anything more than basic experimentation / testing then you almost certainly should create your own image recipe rather than using one of the example images e.g. core-image-minimal - though you can certainly start by copying one of the example images. This way you have easier control over what goes into the image.

=== Where do I find build logs? ===

For the overall build, the output of bitbake gets logged to tmp/log/cooker/<machine>.

For each individual recipe, there is a "temp" directory under the work directory for the recipe that contains log.<taskname> and run.<taskname> files - the logs and the runfiles respectively. Within the build system this directory is pointed to by the T variable, so if you need to you can find it by using <code>bitbake -e</code>:

bitbake -e <recipename> | grep ^T=

=== How do I add a patch to a recipe? ===

There are two concerns - how the recipe can fetch the patch and how it can be applied. For fetching, patch files are usually placed in a subdirectory next to the recipe; by default this directory should be named "files" or the the recipe name without any class prefix or suffix (for example for both "xyz" and "xyz-native" the subdirectory would be "xyz"). A pointer to it then needs to be added to <code>SRC_URI</code> within the recipe, which usually takes the form <code>file://<patchname>.patch</code> - i.e. just the filename, no path. If more than one subdirectory needs to be stripped off the paths in the patch (i.e. you need more than the equivalent of the -p1 option to the patch command) then you can add <code>;striplevel=<number></code> to the end of the patch entry in SRC_URI (without any spaces).

As with any modification, if the patch you are applying is a customisation that you do not intend to send to be incorporated in the layer you are modifying, then instead of adding the patch to the recipe directly then you should consider applying it in a bbappend within your own custom layer. This makes things easier if you later want to update the layer in question and the recipe has been modified upstream - you avoid effectively forking the layer.

The <code>devtool</code> utility can help you modify the sources for a recipe and create a patch - basically <code>devtool modify</code>, edit the sources, commit the changes with <code>git commit</code>, then <code>devtool finish</code> (or <code>devtool update-recipe</code> in versions older than 2.2). Since <code>devtool modify</code> gives you a git tree to work with, you can of course use something like <code>git am</code> to apply existing patches this way. For more details see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#devtool-use-devtool-modify-to-enable-work-on-code-associated-with-an-existing-recipe Use devtool modify to Enable Work on Code Associated with an Existing Recipe] within the Yocto Project Development manual.

=== What does "native" mean? ===

The "native" suffix identifies recipes (and variants of recipes) that produce files intended for the build host, as opposed to the target machine. This is usually for tools that are needed during the build process (such as automake).

=== What does "nativesdk" mean? ===

The "nativesdk" prefix identifies recipes (and variants of recipes) that produce files intended for the host portion of the standard SDK, or for things which are constructed like an SDK such as buildtools-tarball. These are built for SDKMACHINE which may or may not be the same architecture as the build host.

=== I have two recipes and one needs to access files provided by another - how can that work? ===

Instead of providing direct access from a recipe to another's build tree (which wouldn't be practical with OpenEmbedded since the build tree (or "workdir") is temporary), we create a "sysroot" where files that are intended to be shared between recipes get copied. The sysroot is managed by the build system and you should not copy files in there directly - instead, you install files under ${D} as normal during do_install and then the build system will copy a subset of those to the sysroot. There is a seperate sysroot for each machine being built for. In a recipe you can get the path of the sysroot and various standard directories under it using the STAGING_* variables.

Often, for commonly-used build systems such as autotools and cmake you don't need to worry about these details - those systems and the environment that OpenEmbedded sets up for them will ensure that files get installed and picked up in the correct locations. However if the software your recipe is building has custom build scripts / makefiles and it takes shortcuts that don't account for cross-compilation or the use of a sysroot, then you will need to make appropriate adjustments.

=== How do I enable package management in the final image? ===

Add <code>package-management</code> to <code>IMAGE_FEATURES</code> (or <code>EXTRA_IMAGE_FEATURES</code>). You should then be able to use dnf/rpm, opkg, or apt-get/dpkg from the running system depending on the packaging format you have selected through PACKAGE_CLASSES. For more information see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-runtime-package-management Using Runtime Package Management] in the Yocto Project Development manual.

=== What do ?=, ??=, := etc. do within a recipe/config file? ===

See the [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#basic-syntax Basic Syntax section of the BitBake manual] for details.

== Layers ==

See http://www.openembedded.org/Layers_FAQ

== Troubleshooting ==

=== I've created a recipe but it's not showing up in my image, what's going on? ===

Creating a recipe (or adding a layer to your configuration with a desired recipe in it) only makes it available to the build system, it doesn't change what goes into the image. For that, see [[#How do I control what's in the final image?|How do I control what's in the final image?]] above.

=== I set a variable but it doesn't seem to be having an effect, how do I fix this? ===

First, double-check that you haven't misspelled the variable name.

The main tool to help troubleshoot any variable-related issue is <code>bitbake -e</code> - this lists all the variables and the complete history of how each one has been set (use <code>bitbake -e recipename</code> if you're dealing with issues in a variable value within a recipe as opposed to the global level). Usually it's best to pipe this through <code>less</code> so you can easily see the history - within less you can press / to search for the variable name. Often you will be dealing with the behaviour of a variable within the context of a specific recipe, so specify that recipe on the <code>bitbake -e</code> command line to get the variables as set within the context of the recipe rather than the global context.

If you're setting a variable in a bbappend, double-check that the bbappend is actually being applied - see the next question.

=== I've created a bbappend for a recipe but what I'm setting there isn't having any effect, how do I fix this? ===

Here are some things to check:

# Check if the layer the bbappend is in is listed in <code>bitbake-layers show-layers</code>. If it isn't, you need to edit your bblayers.conf and ensure the path to the layer is included in the BBLAYERS value
# Check that the bbappend is being picked up by running <code>bitbake-layers show-appends</code> - if your bbappend file isn't listed, it could be named incorrectly (such that it doesn't match the recipe name) or it may be that the BBFILES value in the conf/layer.conf for the layer containing the bbappend file doesn't include an expression that will match the bbappend files.
# If there are multiple versions of the recipe you have bbappended, it could be that the actual recipe being built is a different version than the one you have bbappended. <code>bitbake-layers show-recipes <recipename></code> will list all the versions, with the first one listed being the one that will be built. If this is the case there are several different solutions to this - (a) Rename your bbappend to match the version being built, (b) use a % wildcard in your bbappend so it will apply to any version, (c) set <code>PREFERRED_VERSION_<recipename></code> in the configuration to select a the version you want to be built.
# Finally, as with any other issue with setting variables, use <code>bitbake -e recipename | less</code> and search with <code>/</code> to see the history of how the variable has been set - you may find that the value you're trying set is being overridden.

=== I'm getting warnings that a recipe is tainted - what does this mean? ===

Usually this happens because you have used I used bitbake's <code>-f</code> or <code>-C</code> option to force a task to re-execute. The assumption is that if you forced a task, it is possible that a rebuild from scratch would not include whatever changes you made that necessitated forcing (e.g. if you modified the source in the work directory for the recipe and then ran <code>bitbake -c compile -f</code>). Generally, forcing a task should be reserved for situations where the build system has failed to detect a change you made rather than for everyday usage - if you're finding yourself needing to do it regularly then either there's a bug, you're doing something wrong, or perhaps you're using <code>-f</code> or <code>-C</code> when it's not really needed. Running <code>bitbake -c clean</code> on the recipe will get rid of the taint flag.

There is one other situation where we apply a taint, and that is <code>bitbake -c menuconfig</code> on the kernel. In this case, the configuration has been saved into the work directory for the kernel, but that is temporary - any rebuild from scratch will use the default configuration, so it is a reminder that you need to take the configuration and apply it back to the metadata and then run <code>bitbake -c clean</code> on the kernel recipe.

=== I'm fetching from a git repository over ssh / http / https but it's not fetching properly, how do I fix this? ===

Bitbake expects the prefix of entries in SRC_URI to specify the fetcher to be used, not the actual protocol. Thus, instead of:

# This will NOT work
SRC_URI = "<nowiki>https://git.example.com/repository</nowiki>"

You should specify:

# This is better
SRC_URI = "<nowiki>git://git.example.com/repository;protocol=https</nowiki>"

The same applies for ssh and of course http.

=== I tried bitbake <some target package name> that I know exists and it told me that nothing PROVIDES this...? ===

There are two namespaces that bitbake concerns itself with - recipe names (a.k.a. build time targets) and package names (a.k.a. runtime targets). You can specify a build time target on the bitbake command line, but not a runtime target; you need to find the recipe that provides the package you are trying to build and build that instead (or simply add that package to your image and build the image). In current versions bitbake will at least tell you which recipes have matching or similar-sounding runtime provides (RPROVIDES) so that you'll usually get a hint on which recipe you need to build.

=== I've included a package in my image but files I expect to be there are missing, what's the issue? ===

Check the simple stuff: verify that the package is really in the image - look at the manifest file next to the image to ensure the package is listed. Also if you're flashing the image, double-check that you did indeed flash the right image and if there are multiple partitions / storage devices on your board or device that you're booting the one that you think you are.

Once you're sure of the above, it may be a matter of the package splitting - a lot of recipes split less commonly used components out to separate packages, so it's possible that the files you are looking for are in a different package. You can look at the recipe for this (look for PACKAGES and FILES statements) or assuming the recipe has been built, you can use <code>oe-pkgdata-util list-pkgs -p recipename</code> and <code>oe-pkgdata-util list-pkg-files</code> to inspect the packages provided by the recipe and the files they contain. Once you find the right package you can add it to your image.

=== I'm required to set LIC_FILES_CHKSUM but the software I'm building doesn't have a license statement, what do I do? ===

Ideally, all software should come with some kind of license statement so that the terms of distribution are clearly stated (especially if its source code is made publicly available); if not a text file describing the license then at the very least a line or two in the accompanying documentation, README file or source header comments. Assuming there is a license statement somewhere but not in a form you can point to with LIC_FILES_CHKSUM as part of the source tree, you can point LIC_FILES_CHKSUM to one of the generic license files in ${COMMON_LICENSE_DIR} (meta/files/common-licenses/), or alternatively you can include a file containing the license statement in a "files" subdirectory next to the recipe (or subdirectory named the same as the recipe - see how such files are handled in other recipes), point to it in SRC_URI using file://, then add it to LIC_FILES_CHKSUM. It is worth noting however that LIC_FILES_CHKSUM is intended to give you a warning if upstream changes its license terms when you do an upgrade of the recipe, and by pointing it to this common license file that is part of the metadata, that mechanism will not function. You may wish to consider encouraging the upstream provider of the software your recipe is building to follow best practices and include a proper license statement, so that you can point to it in a future version. At minimum if you do use such workarounds, you will need to take extra care when upgrading the recipe in future in case the upstream provider changes the license terms.

If there really is no license stated at all anywhere for the software (and this is unfortunately not uncommon on github, for example) then you should really contact upstream - if there's no license, then technically you really shouldn't be distributing it until that's clarified with the original author(s).

=== I am getting a package QA error / warning when building a recipe, how do I solve it? ===

There are some general and specific recommendations in the [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-errors-and-warnings QA Errors and Warnings] section of the Yocto Project Reference Manual.

=== I am getting "taskhash mismatch" errors, what does this mean and how do I fix it? ===

Bitbake parses the metadata (recipes, classes and configuration) repeatedly during its operation, and this error means that the result of parsing changed between one parse and the next. Two situations that can cause this:
# One of the parsed files changed in between e.g. you edited a recipe or performed a git operation (e.g. git checkout) during the build. '''Do not make changes to the metadata while a build is running.''' If you run the build again the error should not recur.
# Alternatively, there is something in the metadata that results in a variable expanding to a different value each time it is parsed. This is often something time-related e.g. a timestamp which is calculated every time an expression is expanded. The solution is to ensure the value is calculated once per build and then the expression expands to the same value for the duration of the build.

=== Building on a system with a GRSec kernel doesn't work well, is that supported? ===

No, grsec isn't really supported. The list of distros that are supported (tested) is in the Yocto mega manual for each release.
You can refer to the work-around given in this defect: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10885

=== Working around Firejail ===
For users of Parrot OS and other secured Linux distros, you will find that your bitbake fetch commands refuse to work, yet you can manually run wget and retrieve the packages with no problem. This is due to Poky creating links to all the tools it requires, in particular 'wget', 'ssh' and 'strings', using the links to these tools in the /usr/local/bin/ directory which all redirect to firejail. To fix the problem you can cd into <your Yocto install directory>/poky/build/tmp/hosttools directory and replace these links with ones redirecting to the actual executables under the /usr/bin directory.

== Dependencies ==

=== How do I find out why something is being built? ===

<code>bitbake -g <recipe></code> will produce some .dot files that allow you to see the dependency relationships - usually pn-depends.dot holds the answers although sometimes you may need to look at task-depends.dot if the dependency is only in the form of a task dependency. Note that these graphs are much too large for most graphviz visualisation tools to process, so you'll probably find it's easiest to view them with "less" or a text editor and search for the item you're looking for.

=== How do I find out why something is in my image? ===

Enable the buildhistory class and build the image again, and it will write out a depends.dot file containing the relationships between packages in the final image. If the package name isn't mentioned it is probably explicitly mentioned in IMAGE_INSTALL or being brought in via IMAGE_FEATURES.

See [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] in the Yocto Project Reference manual which covers how to enable buildhistory and the output it produces.

=== How do I view the .dot files produced by bitbake -g or buildhistory? ===

The size of some of these .dot graphs (particularly those produced by <code>bitbake -g</code>) is a little large for most viewers / processing tools, and unfortunately this isn't something that can be fixed - it's just the nature of the dependency relationships between targets and tasks within OpenEmbedded. Usually if you're just after answering a simple dependency question you can figure it out by viewing it with <code>less</code> and using its built-in search function (or alternatively your favourite text editor).

You can try [http://github.com/jrfonseca/xdot.py xdot] which will work well for some of the graphs, but the task graph produced by <code>bitbake -g</code> for something like an image in particular is likely to be too large to view within it.

=== Why are all of these -native items being built when my host distro has some of these available? ===

It's complicated. In some cases the software in question isn't widely packaged by common Linux distributions. In other cases we need to apply patches to the software, use a more up-to-date version than commonly packaged or build it with a particular configuration. In general it just helps us isolate ourselves from potential problems caused by differences in host Linux distributions. For the most part the time spent building the native tools that are definitely provided by the host distro are dwarfed by the time spent building things that definitely aren't provided, such as the C library for the target and the cross-compiling toolchain.

=== I disabled runtime package management and yet it still seems to be building rpm/opkg, why? ===

The build system always uses a package manager on the host to assemble images, because it is usually the best tool for this job. This is completely independent of whether the package manager is available in the target image - "package-management" being in IMAGE_FEATURES (possibly indirectly via EXTRA_IMAGE_FEATURES) controls whether the package manager is used at runtime i.e. whether it (and its associated package database) will be present in the target image.

=== Why is opkg-native / opkg-utils being built when I don't have ipk packaging enabled? ===

opkg-utils provides update-alternatives which is the default tool used to manage the alternatives system (for selecting between multiple providers of the same file, e.g. busybox and bash both provide /bin/sh).

=== Why is rpm-native being built when I don't have rpm packaging enabled? ===

rpm-native is needed for two things in the generic packaging code implemented in the package class:

# Debug symbol splitting - rpm-native provides the debugedit tool which this code uses
# Per-file dependencies - although this was originally just feeding into rpm when rpm was being used, it also now gets verified by QA checks regardless of which packaging backend is in use.

=== I see a recipe built, but building an image containing the corresponding package fails at do_rootfs because it can't find the package. How does this happen? ===

(For ipk, the error is "Couldn't find anything to satisfy '<package>'"; for rpm it is "<package> not found in the base feeds (<architecture list>)".)

Usually this is because the recipe claimed to provide the specified package (via PACKAGES or PACKAGES_DYNAMIC) but it wasn't actually produced, possibly because it ended up empty (since by default empty packages aren't produced), but the image or some other package still has a dependency that pulls in the specified package. If this is a recipe you are writing yourself the probable cause is your recipe isn't installing any files and thus the main package for the recipe is empty. Fix do_install (or what do_install is already running, e.g. make install) such that files are installed into the correct location such that they can then subsequently be packaged, and then all should be well.

In other situations the reference to the package in question is spurious and either it should be removed entirely or there's another package that should be used instead. For example, the avahi and dhcp recipes both have an empty main package since the client and server are split out into their own packages, and those are the ones you should be using instead (avahi-daemon, avahi-utils, dhcp-server, dhcp-client - there are other packages as well, please see [[#How_do_I_find_out_what_packages_are_produced_by_a_recipe.3F|How do I find out what packages are produced by a recipe?]].) You could argue that these recipes shouldn't claim to provide the main package, or they should have a main package that depends on all the other packages (as some other recipes do).

=== X11 and various other items are being built but I'm only building core-image-minimal that doesn't have X11 in it - why? ===

This is where it helps to understand the difference between build-time dependencies and runtime dependencies - often, a recipe will require things at build time (for example tools that help the build process, or to satisfy optional dependencies) that it doesn't necessarily need at runtime. The default configuration includes "<code>x11</code>" in <code>DISTRO_FEATURES</code>, and thus anything that can optionally support X11 will have its X11 support enabled; however when it comes to actually producing the image there won't be any X11 packages included as long as there are no hard dependencies and there aren't any X11 packages explicitly requested.

If you never intend to use X11, you can set your own <code>DISTRO_FEATURES</code> value that excludes <code>x11</code> (note lower case, as with all feature names) and then X11 support will be disabled at build time and these items won't even be built.

=== How do I avoid the kernel itself being pulled into my image when installing kernel modules? ===

By default, the kernel class sets a dependency on the kernel-base package (which kernel modules always depend on) onto kernel-image, which contains the actual kernel binary. If you don't want this, set the following either in your kernel recipe or at the configuration level:

RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""

Note: for older releases (pre-2.5) do this instead:

RDEPENDS_kernel-base = ""

== Misc ==

=== How do I remove a value from a list variable? ===

For variables that are expected to contain a space-separated list of items, BitBake supports a _remove operator to remove items from it. See [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#removing-override-style-syntax Removal (override style syntax)] in the BitBake user manual.

'''NOTE:''' the _remove operation is final - you cannot "undo" it with other operations elsewhere, thus you should really only make use of it in your distro / local configuration and not in layers that you expect others to re-use for different purposes (and therefore they may need to undo your changes). An alternative way to effectively remove an item is to set the list outright to include all the items minus the one you want to remove.

=== How do I change how my recipe is built depending on what image I'm building? ===

The short answer is you cannot - the reason is that OpenEmbedded builds packages based on the overall configuration, and then the image only selects which of these packages should go into the final image. However, there are some solutions that do allow you to achieve the desired result:

# Have separate packages for the two different versions. This could take the form of different recipes or you could do it within the same recipe. The two packages do have to have different names however; this may create problems if you have other packages that depend on the package.
# Use a postprocessing function within the image(s) - within the image recipe, define a shell or python function that makes the desired changes to the files in the image and add a call to it to ROOTFS_POSTPROCESS_COMMAND within the image recipe. Note that this may not be appropriate if you have runtime package management enabled since the postprocessing will only happen at image creation time and not if the package is installed later on at runtime - you may need to use a postinstall script instead in this case.
# Use a postinstall script (pkg_postinst_<package> function) within the recipe. In order to work, the postinstall script will need to be able to determine what to do when it's run - this may not be practical depending on what you're trying to achieve.

=== Can I use a toolchain built by OE as the external toolchain? ===

In general, this is not recommended and not something that is tested or directly supported out of the box. If you are wanting to do this solely as a means of speeding up the build, it is strongly suggested that you use shared state instead.

There is a [http://layers.openembedded.org/layerindex/branch/master/layer/meta-sourcery/ meta-sourcery layer] available to enable support for the CodeSourcery toolchain, you may be able to use this as a template for bringing in an external toolchain however there are no guarantees.

=== When I run bitbake -c devshell it looks like it's running as root! How is that possible? ===

It's not running as the actual root user, it's just pretending for the benefit of programs that run under it (including your shell) that it is, via pseudo. This is important, because you normally want any owner/group/permission values that you set on files to be reflected in files that the recipe installs and packages and thus reflected in the final image - without this mechanism the actual build would have to run as root which would be very risky. There are no actual elevated privileges through this mechanism however, so you need not be worried.

=== Why does OE use pseudo? Why not use fakeroot / fakechroot instead? ===

Splitting this up into two questions - we use pseudo (not to be confused with sudo!) because we want to be able to create images containing files have the correct permissions and ownership, e.g. files owned by root, without the user running the build system having to have that privilege. By using LD_PRELOAD to intercept function calls, pseudo creates an environment for programs running underneath it where it appears as if the running user has those privileges (and the results of any operations persist within the pseudo environment, i.e. you can write a file as root and it will appear to be owned by root while still running under pseudo). This allows us to run builds entirely as a normal user without needing extra privileges. Without pseudo we would require running the build system under sudo or as root - which would be ill-advised for things such as "make install" in case it happened to be broken and tried to write to / instead of somewhere under the work directory for the recipe; a broken recipe could easily end up destroying your system in that case.

To answer the second part, why we use pseudo instead of fakeroot / fakechroot, see [https://github.com/wrpseudo/pseudo/wiki/WhyNotFakeroot WhyNotFakeroot on the pseudo wiki].

=== How do I find out what packages are produced by a recipe? ===

The Toaster web UI provides easy ways to query this.

In the 1.8 (fido) release and newer you can use the following command, assuming the recipe has already been built:

oe-pkgdata-util list-pkgs -p recipename

Alternatively you can look in the "packages-split" subdirectory under the work directory for the recipe - each package produced by the recipe will have a subdirectory under that. If you're not sure how to find the work directory you can run the following command:

bitbake -e recipename | grep ^WORKDIR=

Before a recipe gets built it is a bit trickier, since the system often doesn't know exactly which packages will be produced until do_package time; this is particularly true for recipes that package plugins or modules (e.g. kernel modules). You can get a reasonable idea though by looking at the value of PACKAGES (and PACKAGES_DYNAMIC for recipes that produce plugins).

=== How do I find out which package contains a particular file (or python module)? ===

oe-pkgdata-util has a find-path subcommand that will tell you exactly this. For example:

$ oe-pkgdata-util find-path /etc/network/interfaces
init-ifupdown: /etc/network/interfaces

Wildcards are allowed anywhere in the path (but you should enclose such expressions in quotes to avoid the shell itself attempting to expand the wildcard):

$ oe-pkgdata-util find-path "*/fstrim"
util-linux-bash-completion: /usr/share/bash-completion/completions/fstrim
util-linux-ptest: /usr/lib/util-linux/ptest/fstrim
util-linux-dbg: /sbin/.debug/fstrim
util-linux-fstrim: /sbin/fstrim

As a specific example of where this can be useful, our Python packaging is a bit more granular than most typical distributions, allowing you to tune the contents of your image to just what you need. However, that does mean you may have trouble figuring out which package provides a particular module. oe-pkgdata-util find-path can also be used for this. For example, to find the package containing the "shutil" module, run this:

$ oe-pkgdata-util find-path "*/shutil.*"
python3-shell: /usr/lib/python3.5/shutil.py
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-2.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-1.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.pyc

Thus the package you are looking for is python3-shell. (Note that you could use */shutil.py, but if the module you are looking for is written in C as some of them are, that won't match it.)

=== I have a local source tree I want to build instead of the upstream source a recipe normally fetches, how do I do that? ===

If it's for development purposes i.e. you have your own local source tree you want to work on and have built, then run:

devtool modify -n <recipename> path/to/sourcetree/

Once you are done you can use <code>devtool finish</code> or <code>devtool reset</code> (depending on the situation) to return to building the source specified in the recipe.

Alternatively if it's more permanent, use the <code>externalsrc</code> class - you can inherit this in the original recipe or a bbappend:

inherit externalsrc
EXTERNALSRC = "/path/to/sources"

If you're going to use it across a number of recipes you can inherit it globally at the configuration level (perhaps via an inc file that you include/require there):

INHERIT += "externalsrc"
EXTERNALSRC_pn-<recipename> = "/path/to/sources"

=== How do I specify the default shell? (e.g. bash instead of busybox) ===

It depends what you mean. As far as which provides /bin/sh, this is controlled through the alternatives system, and by default bash has a higher priority than busybox, so simply installing bash into your image will automatically have /bin/sh link to bash rather than busybox.

If you mean you want a user's login shell to be a specific shell, you'll need to modify /etc/passwd. One fairly easy way to achieve this is to use the extrausers class in your image recipe:

inherit extrausers
EXTRA_USERS_PARAMS = "usermod -s /bin/bash <username>; "

=== How do I get "full" versions of typical shell commands? ===

Most of the shell commands in our images are provided by busybox by default, and are very much simplified compared to what you would have on a typical Linux system in order to save space. If you need the full versions, most of them are built and packaged by the coreutils recipe (for disk and other typical utilities) and procps (for ps, etc). You may also want to install bash for more typical shell built-in commands. There is also a core-image-full-cmdline image if you want a base image that is already set up to provide a more typical Linux command-line experience. (Note: these will of course use up more disk space and memory.)

=== How do I allow a variable's value through from the external environment? ===

Add the variable's name to the BB_ENV_EXTRAWHITE ''in the external environment'' before running bitbake. Note that the oe-init-build-env script sets a default for this which you will want to preserve, so add to the default value rather than overwriting it.

Alternatively if you just want to get the external value of a variable from python code within the metadata, you can use the BB_ORIGENV variable which itself contains a datastore of the original environment. For example to get the value of the DISPLAY variable from the environment within a python function you would do this:

display = d.getVar("BB_ORIGENV", False).getVar("DISPLAY")

Note that you must specify "false" for the expand parameter when getting the BB_ORIGENV variable, because it's not a string and therefore cannot be expanded in the normal manner.

=== Why is bitbake showing "AUTOINC" in the version for some recipes? ===

Recipes where you see AUTOINC within the version in the console output during a build will be those that set <code>PV</code> to include <code>"${SRCPV}"</code> to get the SCM revision (e.g. the git hash) in the package version. In order to have the version increment properly, there needs to be a number in front of the revision which automatically increments each time the revision changes (assuming you have a PR server enabled), which is where AUTOINC comes in. During the build, AUTOINC is a stand-in for this auto-incrementing number, and later during <code>do_package</code> it gets replaced with the real number so that the packages produced at the end have the full version number.

=== Why are .so files in the -dev package instead of the main package for a recipe? ===

In standard Unix library packaging, non-versioned .so symlinks (e.g. /usr/lib/libgd.so) are intended for development purposes only. At runtime, binaries should be linked to the major-versioned .so file/symlink e.g. /usr/lib/libgd.so.3. This (theoretically) allows multiple major versions of the same library as well as binaries that depend upon each of them to coexist on the same system. If the library is versioned but you have a binary that links to the unversioned .so file, it has almost certainly been linked incorrectly.

Non-symlink .so files on the other hand are sometimes produced and are entirely legal - however these will be picked up in the -dev package in OpenEmbedded simply by virtue of their name, which is almost always not what you want. In this case you can do one of two things:

# Fix the build of the library so it gets versioned. This may not always be appropriate, especially not for things like plugins.
# Set FILES_${PN}-dev within the recipe so that it does not include ${FILES_SOLIBSDEV}. If the software the recipe is building also produces symlink .so files you'll need to set FILES_${PN}-dev such that those do still get packaged in the -dev package though, or you'll get a package QA warning.

=== Can I disable shared state? ===

You cannot, no. Shared state (sstate) is an intrinsic part of staging files into the sysroot. It is possible to construct a recipe that bypasses sstate for some tasks (the kernel does this), however this is quite difficult and if not done properly will lead to many other problems.

Almost always when you are having a problem with shared state the issue is either (a) you're adding/changing files in the sysroot directly (i.e. outside sstate control), or (b) what is being placed into the sysroot isn't relocatable due to hardcoded paths. The solution for (a) is do not do that - files should always be installed under <code>${D}</code> within <code>do_install</code> and then a subset of those are staged into the sysroot automatically. For (b) you need to fix or adapt the hardcoded path(s) - if the program reads (or can be made to read) each path from an environment variable, then you can use the <code>create_wrapper</code> utility function to create a wrapper script that will set the path appropriately. Run <code>git grep create_wrapper</code> in the <code>meta</code> subdirectory to see examples.

=== Files I installed into /opt or some other path never make it into the sysroot but I need them - how do I fix this? ===

OpenEmbedded only stages a subset of files that are installed into <code>${D}</code> by <code>do_install</code> so that the sysroot doesn't fill up with unneeded files. You have two choices in this situation:
# install the files into a more standard location which is part of the subset, or
# adjust the subset to include the paths you are installing to.
Usually option 1 is recommended. If you really do need to adjust the subset, you can append the path (more specifically, the part below <code>${D}</code>) to <code>SYSROOT_DIRS</code> within your recipe. For example:

SYSROOT_DIRS += "/opt"

=== I have some software which needs to build a binary that it then runs as part of its own build process, how do I make this work? ===

Whilst it is possible to do this within a single recipe building for the target, it is tricky to do so because in that context everything is set up for cross-compiling for the target, and you would have to undo all of that to build host tools. The standard and much easier way of handling this is to create a native variant of the recipe using BBCLASSEXTEND and have your host tools built within that, and then have the target variant depend on the native variant. For example, assume your recipe were called xyz (xyz_1.1.bb), then you would include something like this in the recipe:

DEPENDS_append_class-target = " xyz-native"

...

BBCLASSEXTEND += "native"

The host tools will then be built and installed into the sysroot in the native variant ready for when the target variant starts building. If the software you are building didn't intend for those tools to be installed outside of the build tree then you may need to patch the build process (e.g. the makefile) in order to install them and possibly also for the target side to find them in the sysroot. Additionally, for performance since you only need the tools in the native variant, you may also choose to disable building everything except those tools there - e.g. by using _native overrides for variables such as EXTRA_OECONF or functions such as do_configure.

=== How do I fetch from two git repositories in the same recipe? ===

By default, sources fetched from git within a recipe are unpacked into ${WORKDIR}/git, however that only works for a single repository. If you want to fetch from more than one, you need to change the path each repository is unpacked to. This is easy to do, just add <code>;destsuffix=<subdir></code> to the end of each URL in SRC_URI (replacing <code><subdir></code> with the name of the subdirectory). You may then need to change S to match whichever of these you want to be considered the root of the source tree - or alternatively you can specify destsuffix such that repositories beyond the first go into a subdirectory under the default "git" subdirectory. For example, from the gst-libav recipe:

...
SRC_URI = " \
git://anongit.freedesktop.org/gstreamer/gst-libav;branch=1.8;name=base \
git://anongit.freedesktop.org/gstreamer/common;destsuffix=git/common;name=common \
...
"
...
S = "${WORKDIR}/git"
...

(Here we're using the default of "git" for the first repository, so we don't need to specify <code>destsuffix</code> for the first URL.)

=== I'm building a native recipe and I notice that the install path has the full path to the root directory repeated - why? ===

It does look a little odd, but the reason for doing this is that native targets are meant to run on the system they're built on and run in the location they're installed to. This means they install to a destination of "/" and PREFIX is inside the native sysroot directory. We install them to a DESTDIR to allow us to manipulate them before they then get moved to a final DESTDIR of "/".

Most Makefiles handle this correctly by doing:

DESTDIR ?= ""
prefix ?= "/usr"
bindir ?= "$(prefix)/bin"

and then, importantly, install in the form:

install -d $(DESTDIR)$(bindir)

so both prefix and DESTDIR are used. Whilst this is a convention, its a widely adopted and followed one. You can call into a custom makefile and set the variables manually if the makefile doesn't follow the convention.

=== How do I generate static libraries? ===

Its possible you have conf/distro/include/no-static-libs.inc included in your build - poky does this by default. The include list at the top of the bitbake -e output will tell you for certain.

If so, you can remove that or set:

DISABLE_STATIC = ""

as it would currently be set to this if that include file is included:

DISABLE_STATIC = " --disable-static"

Poky disables building static libraries by default as for the most part they're a waste of space/time.

=== Can I conditionally inherit a class in a recipe? ===

Yes, you can. What makes this possible is that the <code>inherit</code> keyword will not complain if what comes after it expands to being empty, so you can use in-line python to do something like this:

<pre><nowiki>
inherit ${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}
</nowiki></pre>

The above example will inherit the <code>perlnative</code> class if "scripting" is in the value of the <code>PACKAGECONFIG</code> variable, otherwise it will do nothing.

You could of course put this into a variable if you prefer:

<pre><nowiki>
SOMEVAR = "${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}"
inherit ${SOMEVAR}
</nowiki></pre>

=== How do I collect the source revisions fetched by each recipe? ===

If you have recipes where <code>SRCREV = "${AUTOREV}"</code> then you won't necessarily know exactly which revisions were built after the fact - it will be whatever was current at the time. You also might alternatively just want to get all of the revisions. Either way, to do this, enable buildhistory by setting the following in your local.conf:

<pre><nowiki>
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
</nowiki></pre>

(The last line is not required with version 2.5 and onwards as it is the default, but will do no harm.)

Once you have enabled buildhistory, you then need to build your image again so that buildhistory has a chance to record history data for it. Following that you can run <code>buildhistory-collect-srcrevs</code> (with <code>-a</code> if you want to see all revisions, not just the ones where AUTOREV was used) and it will output the revisions in a form you can use in a .inc file that you can <code>require</code> from your configuration if you want to fix the build to those revisions.

For more information see the [https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] section of the Yocto Project Development manual, which covers the buildhistory class in detail.

=== How do I do an offline build with recipes that have <code>SRCREV = "${AUTOREV}"</code> set? ===

If you set <code>BB_NO_NETWORK = "1"</code> and you have recipes that have <code>SRCREV = "${AUTOREV}"</code>, you will get an error because the build system will try to check the latest revision on startup and be immediately blocked by <code>BB_NO_NETWORK</code>. There are two ways to handle this:

A) See the previous question "How do I collect the source revisions fetched by each recipe?" and use the output generated by <code>buildhistory-collect-srcrevs</code> as a .inc file in your configuration in order to fix the revisions at the ones which were most recently built.

or

B) Set <code>BB_SRCREV_POLICY = "cache"</code> in your configuration. This will use the last cached revision. (The disadvantage of this method is that it is a little more difficult to preserve or share with others the fixed revisions.)

Note that in either case if you later want to build the latest version again, you will of course need to undo the configuration changes.

=== Is it possible to append a bbclass file (like bbappends do for recipes)? ===

No, see the next question for details.

=== How do I override a bbclass file? ===

This is tricky - bbclass files are found via BBPATH, which is added to by each layer.conf either by prepending or appending. Assuming you are putting your bbclass in a custom layer, you will probably want to have your layer's layer.conf prepend to BBPATH, but then you will also need to make sure that your layer does not appear before any other layer that is also prepending and overriding the same class.

Another alternative is to have an additional class which makes the appropriate changes to the environment, and then you will need to inherit that class after (and in the same manner as) the original class. This is slightly cleaner but can be annoying to enable particularly if the class is inherited by a number of recipes, and won't work if you want to alter the behaviour of a class inherited by recipes you don't control. (If you want a class to be inherited for all images (i.e. all recipes inheriting the <code>image</code> class) you can inject additional classes by setting IMAGE_CLASSES; similarly for the kernel there is KERNEL_CLASSES).

Ultimately, overriding bbclass files is not good practice long term - you are opening yourself up to maintenance issues when the original class changes, and the override is fragile as hinted above. The best solution is to try to get whatever changes you need into the original class; this does of course require additional work and time though.

=== There's a bbappend in a layer I'm using that defines a <code>do_something_append()</code> and I want to append to that function also, how do I do this? ===

Simply create a bbappend in your layer and define your own <code>do_something_append()</code>, and your commands will be executed ''as well as'' those of the other bbappend.

You might assume that defining <code>do_something_append()</code> will overwrite any previously defined <code>do_something_append()</code>, as would be the case with <code>do_something()</code> in the same situation, but that is not the case - the key is that <code>_append</code> (and <code>_prepend</code>, <code>_remove</code>, etc.) are ''operators'' and they will be applied in sequence, where that sequence is the order in which they are parsed (which for bbappends will be in ascending layer priority order).

Technical FAQ

2020-07-01T01:22:39Z

PaulEggleton: /* X11 and various other items are being built but I'm only building core-image-minimal - why? */

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
| '''NOTE:''' This is currently a draft. Not sure where this should end up but I've been gathering these based on my interactions with people on IRC and email over the years. - [[User:PaulEggleton|PaulEggleton]] ([[User talk:PaulEggleton|talk]]) 21:13, 27 June 2016 (PDT)
|}

== Basics ==

=== How do I figure out which version/codename/bitbake version matches up with which? ===

There is a table in the [http://wiki.yoctoproject.org/wiki/Releases Releases page] on the Yocto Project wiki.

=== How do I control what's in the final image? ===

Each image is defined by its own recipe, and that recipe specifies a list of packages that the image should contain. See [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Customising Images] within the Yocto Project development manual for further details.

Note: if you're doing anything more than basic experimentation / testing then you almost certainly should create your own image recipe rather than using one of the example images e.g. core-image-minimal - though you can certainly start by copying one of the example images. This way you have easier control over what goes into the image.

=== Where do I find build logs? ===

For the overall build, the output of bitbake gets logged to tmp/log/cooker/<machine>.

For each individual recipe, there is a "temp" directory under the work directory for the recipe that contains log.<taskname> and run.<taskname> files - the logs and the runfiles respectively. Within the build system this directory is pointed to by the T variable, so if you need to you can find it by using <code>bitbake -e</code>:

bitbake -e <recipename> | grep ^T=

=== How do I add a patch to a recipe? ===

There are two concerns - how the recipe can fetch the patch and how it can be applied. For fetching, patch files are usually placed in a subdirectory next to the recipe; by default this directory should be named "files" or the the recipe name without any class prefix or suffix (for example for both "xyz" and "xyz-native" the subdirectory would be "xyz"). A pointer to it then needs to be added to <code>SRC_URI</code> within the recipe, which usually takes the form <code>file://<patchname>.patch</code> - i.e. just the filename, no path. If more than one subdirectory needs to be stripped off the paths in the patch (i.e. you need more than the equivalent of the -p1 option to the patch command) then you can add <code>;striplevel=<number></code> to the end of the patch entry in SRC_URI (without any spaces).

As with any modification, if the patch you are applying is a customisation that you do not intend to send to be incorporated in the layer you are modifying, then instead of adding the patch to the recipe directly then you should consider applying it in a bbappend within your own custom layer. This makes things easier if you later want to update the layer in question and the recipe has been modified upstream - you avoid effectively forking the layer.

The <code>devtool</code> utility can help you modify the sources for a recipe and create a patch - basically <code>devtool modify</code>, edit the sources, commit the changes with <code>git commit</code>, then <code>devtool finish</code> (or <code>devtool update-recipe</code> in versions older than 2.2). Since <code>devtool modify</code> gives you a git tree to work with, you can of course use something like <code>git am</code> to apply existing patches this way. For more details see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#devtool-use-devtool-modify-to-enable-work-on-code-associated-with-an-existing-recipe Use devtool modify to Enable Work on Code Associated with an Existing Recipe] within the Yocto Project Development manual.

=== What does "native" mean? ===

The "native" suffix identifies recipes (and variants of recipes) that produce files intended for the build host, as opposed to the target machine. This is usually for tools that are needed during the build process (such as automake).

=== What does "nativesdk" mean? ===

The "nativesdk" prefix identifies recipes (and variants of recipes) that produce files intended for the host portion of the standard SDK, or for things which are constructed like an SDK such as buildtools-tarball. These are built for SDKMACHINE which may or may not be the same architecture as the build host.

=== I have two recipes and one needs to access files provided by another - how can that work? ===

Instead of providing direct access from a recipe to another's build tree (which wouldn't be practical with OpenEmbedded since the build tree (or "workdir") is temporary), we create a "sysroot" where files that are intended to be shared between recipes get copied. The sysroot is managed by the build system and you should not copy files in there directly - instead, you install files under ${D} as normal during do_install and then the build system will copy a subset of those to the sysroot. There is a seperate sysroot for each machine being built for. In a recipe you can get the path of the sysroot and various standard directories under it using the STAGING_* variables.

Often, for commonly-used build systems such as autotools and cmake you don't need to worry about these details - those systems and the environment that OpenEmbedded sets up for them will ensure that files get installed and picked up in the correct locations. However if the software your recipe is building has custom build scripts / makefiles and it takes shortcuts that don't account for cross-compilation or the use of a sysroot, then you will need to make appropriate adjustments.

=== How do I enable package management in the final image? ===

Add <code>package-management</code> to <code>IMAGE_FEATURES</code> (or <code>EXTRA_IMAGE_FEATURES</code>). You should then be able to use dnf/rpm, opkg, or apt-get/dpkg from the running system depending on the packaging format you have selected through PACKAGE_CLASSES. For more information see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-runtime-package-management Using Runtime Package Management] in the Yocto Project Development manual.

=== What do ?=, ??=, := etc. do within a recipe/config file? ===

See the [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#basic-syntax Basic Syntax section of the BitBake manual] for details.

== Layers ==

See http://www.openembedded.org/Layers_FAQ

== Troubleshooting ==

=== I've created a recipe but it's not showing up in my image, what's going on? ===

Creating a recipe (or adding a layer to your configuration with a desired recipe in it) only makes it available to the build system, it doesn't change what goes into the image. For that, see [[#How do I control what's in the final image?|How do I control what's in the final image?]] above.

=== I set a variable but it doesn't seem to be having an effect, how do I fix this? ===

First, double-check that you haven't misspelled the variable name.

The main tool to help troubleshoot any variable-related issue is <code>bitbake -e</code> - this lists all the variables and the complete history of how each one has been set (use <code>bitbake -e recipename</code> if you're dealing with issues in a variable value within a recipe as opposed to the global level). Usually it's best to pipe this through <code>less</code> so you can easily see the history - within less you can press / to search for the variable name. Often you will be dealing with the behaviour of a variable within the context of a specific recipe, so specify that recipe on the <code>bitbake -e</code> command line to get the variables as set within the context of the recipe rather than the global context.

If you're setting a variable in a bbappend, double-check that the bbappend is actually being applied - see the next question.

=== I've created a bbappend for a recipe but what I'm setting there isn't having any effect, how do I fix this? ===

Here are some things to check:

# Check if the layer the bbappend is in is listed in <code>bitbake-layers show-layers</code>. If it isn't, you need to edit your bblayers.conf and ensure the path to the layer is included in the BBLAYERS value
# Check that the bbappend is being picked up by running <code>bitbake-layers show-appends</code> - if your bbappend file isn't listed, it could be named incorrectly (such that it doesn't match the recipe name) or it may be that the BBFILES value in the conf/layer.conf for the layer containing the bbappend file doesn't include an expression that will match the bbappend files.
# If there are multiple versions of the recipe you have bbappended, it could be that the actual recipe being built is a different version than the one you have bbappended. <code>bitbake-layers show-recipes <recipename></code> will list all the versions, with the first one listed being the one that will be built. If this is the case there are several different solutions to this - (a) Rename your bbappend to match the version being built, (b) use a % wildcard in your bbappend so it will apply to any version, (c) set <code>PREFERRED_VERSION_<recipename></code> in the configuration to select a the version you want to be built.
# Finally, as with any other issue with setting variables, use <code>bitbake -e recipename | less</code> and search with <code>/</code> to see the history of how the variable has been set - you may find that the value you're trying set is being overridden.

=== I'm getting warnings that a recipe is tainted - what does this mean? ===

Usually this happens because you have used I used bitbake's <code>-f</code> or <code>-C</code> option to force a task to re-execute. The assumption is that if you forced a task, it is possible that a rebuild from scratch would not include whatever changes you made that necessitated forcing (e.g. if you modified the source in the work directory for the recipe and then ran <code>bitbake -c compile -f</code>). Generally, forcing a task should be reserved for situations where the build system has failed to detect a change you made rather than for everyday usage - if you're finding yourself needing to do it regularly then either there's a bug, you're doing something wrong, or perhaps you're using <code>-f</code> or <code>-C</code> when it's not really needed. Running <code>bitbake -c clean</code> on the recipe will get rid of the taint flag.

There is one other situation where we apply a taint, and that is <code>bitbake -c menuconfig</code> on the kernel. In this case, the configuration has been saved into the work directory for the kernel, but that is temporary - any rebuild from scratch will use the default configuration, so it is a reminder that you need to take the configuration and apply it back to the metadata and then run <code>bitbake -c clean</code> on the kernel recipe.

=== I'm fetching from a git repository over ssh / http / https but it's not fetching properly, how do I fix this? ===

Bitbake expects the prefix of entries in SRC_URI to specify the fetcher to be used, not the actual protocol. Thus, instead of:

# This will NOT work
SRC_URI = "<nowiki>http://git.example.com/repository</nowiki>"

You should specify:

# This is better
SRC_URI = "<nowiki>git://git.example.com/repository;protocol=http</nowiki>"

The same applies for ssh and https.

=== I tried bitbake <some target package name> that I know exists and it told me that nothing PROVIDES this...? ===

There are two namespaces that bitbake concerns itself with - recipe names (a.k.a. build time targets) and package names (a.k.a. runtime targets). You can specify a build time target on the bitbake command line, but not a runtime target; you need to find the recipe that provides the package you are trying to build and build that instead (or simply add that package to your image and build the image). In current versions bitbake will at least tell you which recipes have matching or similar-sounding runtime provides (RPROVIDES) so that you'll usually get a hint on which recipe you need to build.

=== I've included a package in my image but files I expect to be there are missing, what's the issue? ===

Check the simple stuff: verify that the package is really in the image - look at the manifest file next to the image to ensure the package is listed. Also if you're flashing the image, double-check that you did indeed flash the right image and if there are multiple partitions / storage devices on your board or device that you're booting the one that you think you are.

Once you're sure of the above, it may be a matter of the package splitting - a lot of recipes split less commonly used components out to separate packages, so it's possible that the files you are looking for are in a different package. You can look at the recipe for this (look for PACKAGES and FILES statements) or assuming the recipe has been built, you can use <code>oe-pkgdata-util list-pkgs -p recipename</code> and <code>oe-pkgdata-util list-pkg-files</code> to inspect the packages provided by the recipe and the files they contain. Once you find the right package you can add it to your image.

=== I'm required to set LIC_FILES_CHKSUM but the software I'm building doesn't have a license statement, what do I do? ===

Ideally, all software should come with some kind of license statement so that the terms of distribution are clearly stated (especially if its source code is made publicly available); if not a text file describing the license then at the very least a line or two in the accompanying documentation, README file or source header comments. Assuming there is a license statement somewhere but not in a form you can point to with LIC_FILES_CHKSUM as part of the source tree, you can point LIC_FILES_CHKSUM to one of the generic license files in ${COMMON_LICENSE_DIR} (meta/files/common-licenses/), or alternatively you can include a file containing the license statement in a "files" subdirectory next to the recipe (or subdirectory named the same as the recipe - see how such files are handled in other recipes), point to it in SRC_URI using file://, then add it to LIC_FILES_CHKSUM. It is worth noting however that LIC_FILES_CHKSUM is intended to give you a warning if upstream changes its license terms when you do an upgrade of the recipe, and by pointing it to this common license file that is part of the metadata, that mechanism will not function. You may wish to consider encouraging the upstream provider of the software your recipe is building to follow best practices and include a proper license statement, so that you can point to it in a future version. At minimum if you do use such workarounds, you will need to take extra care when upgrading the recipe in future in case the upstream provider changes the license terms.

If there really is no license stated at all anywhere for the software (and this is unfortunately not uncommon on github, for example) then you should really contact upstream - if there's no license, then technically you really shouldn't be distributing it until that's clarified with the original author(s).

=== I am getting a package QA error / warning when building a recipe, how do I solve it? ===

There are some general and specific recommendations in the [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-errors-and-warnings QA Errors and Warnings] section of the Yocto Project Reference Manual.

=== I am getting "taskhash mismatch" errors, what does this mean and how do I fix it? ===

Bitbake parses the metadata (recipes, classes and configuration) repeatedly during its operation, and this error means that the result of parsing changed between one parse and the next. Two situations that can cause this:
# One of the parsed files changed in between e.g. you edited a recipe or performed a git operation (e.g. git checkout) during the build. '''Do not make changes to the metadata while a build is running.''' If you run the build again the error should not recur.
# Alternatively, there is something in the metadata that results in a variable expanding to a different value each time it is parsed. This is often something time-related e.g. a timestamp which is calculated every time an expression is expanded. The solution is to ensure the value is calculated once per build and then the expression expands to the same value for the duration of the build.

=== Building on a system with a GRSec kernel doesn't work well, is that supported? ===

No, grsec isn't really supported. The list of distros that are supported (tested) is in the Yocto mega manual for each release.
You can refer to the work-around given in this defect: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10885

=== Working around Firejail ===
For users of Parrot OS and other secured Linux distros, you will find that your bitbake fetch commands refuse to work, yet you can manually run wget and retrieve the packages with no problem. This is due to Poky creating links to all the tools it requires, in particular 'wget', 'ssh' and 'strings', using the links to these tools in the /usr/local/bin/ directory which all redirect to firejail. To fix the problem you can cd into <your Yocto install directory>/poky/build/tmp/hosttools directory and replace these links with ones redirecting to the actual executables under the /usr/bin directory.

== Dependencies ==

=== How do I find out why something is being built? ===

<code>bitbake -g <recipe></code> will produce some .dot files that allow you to see the dependency relationships - usually pn-depends.dot holds the answers although sometimes you may need to look at task-depends.dot if the dependency is only in the form of a task dependency. Note that these graphs are much too large for most graphviz visualisation tools to process, so you'll probably find it's easiest to view them with "less" or a text editor and search for the item you're looking for.

=== How do I find out why something is in my image? ===

Enable the buildhistory class and build the image again, and it will write out a depends.dot file containing the relationships between packages in the final image. If the package name isn't mentioned it is probably explicitly mentioned in IMAGE_INSTALL or being brought in via IMAGE_FEATURES.

See [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] in the Yocto Project Reference manual which covers how to enable buildhistory and the output it produces.

=== How do I view the .dot files produced by bitbake -g or buildhistory? ===

The size of some of these .dot graphs (particularly those produced by <code>bitbake -g</code>) is a little large for most viewers / processing tools, and unfortunately this isn't something that can be fixed - it's just the nature of the dependency relationships between targets and tasks within OpenEmbedded. Usually if you're just after answering a simple dependency question you can figure it out by viewing it with <code>less</code> and using its built-in search function (or alternatively your favourite text editor).

You can try [http://github.com/jrfonseca/xdot.py xdot] which will work well for some of the graphs, but the task graph produced by <code>bitbake -g</code> for something like an image in particular is likely to be too large to view within it.

=== Why are all of these -native items being built when my host distro has some of these available? ===

It's complicated. In some cases the software in question isn't widely packaged by common Linux distributions. In other cases we need to apply patches to the software, use a more up-to-date version than commonly packaged or build it with a particular configuration. In general it just helps us isolate ourselves from potential problems caused by differences in host Linux distributions. For the most part the time spent building the native tools that are definitely provided by the host distro are dwarfed by the time spent building things that definitely aren't provided, such as the C library for the target and the cross-compiling toolchain.

=== I disabled runtime package management and yet it still seems to be building rpm/opkg, why? ===

The build system always uses a package manager on the host to assemble images, because it is usually the best tool for this job. This is completely independent of whether the package manager is available in the target image - "package-management" being in IMAGE_FEATURES (possibly indirectly via EXTRA_IMAGE_FEATURES) controls whether the package manager is used at runtime i.e. whether it (and its associated package database) will be present in the target image.

=== Why is opkg-native / opkg-utils being built when I don't have ipk packaging enabled? ===

opkg-utils provides update-alternatives which is the default tool used to manage the alternatives system (for selecting between multiple providers of the same file, e.g. busybox and bash both provide /bin/sh).

=== Why is rpm-native being built when I don't have rpm packaging enabled? ===

rpm-native is needed for two things in the generic packaging code implemented in the package class:

# Debug symbol splitting - rpm-native provides the debugedit tool which this code uses
# Per-file dependencies - although this was originally just feeding into rpm when rpm was being used, it also now gets verified by QA checks regardless of which packaging backend is in use.

=== I see a recipe built, but building an image containing the corresponding package fails at do_rootfs because it can't find the package. How does this happen? ===

(For ipk, the error is "Couldn't find anything to satisfy '<package>'"; for rpm it is "<package> not found in the base feeds (<architecture list>)".)

Usually this is because the recipe claimed to provide the specified package (via PACKAGES or PACKAGES_DYNAMIC) but it wasn't actually produced, possibly because it ended up empty (since by default empty packages aren't produced), but the image or some other package still has a dependency that pulls in the specified package. If this is a recipe you are writing yourself the probable cause is your recipe isn't installing any files and thus the main package for the recipe is empty. Fix do_install (or what do_install is already running, e.g. make install) such that files are installed into the correct location such that they can then subsequently be packaged, and then all should be well.

In other situations the reference to the package in question is spurious and either it should be removed entirely or there's another package that should be used instead. For example, the avahi and dhcp recipes both have an empty main package since the client and server are split out into their own packages, and those are the ones you should be using instead (avahi-daemon, avahi-utils, dhcp-server, dhcp-client - there are other packages as well, please see [[#How_do_I_find_out_what_packages_are_produced_by_a_recipe.3F|How do I find out what packages are produced by a recipe?]].) You could argue that these recipes shouldn't claim to provide the main package, or they should have a main package that depends on all the other packages (as some other recipes do).

=== X11 and various other items are being built but I'm only building core-image-minimal that doesn't have X11 in it - why? ===

This is where it helps to understand the difference between build-time dependencies and runtime dependencies - often, a recipe will require things at build time (for example tools that help the build process, or to satisfy optional dependencies) that it doesn't necessarily need at runtime. The default configuration includes "<code>x11</code>" in <code>DISTRO_FEATURES</code>, and thus anything that can optionally support X11 will have its X11 support enabled; however when it comes to actually producing the image there won't be any X11 packages included as long as there are no hard dependencies and there aren't any X11 packages explicitly requested.

If you never intend to use X11, you can set your own <code>DISTRO_FEATURES</code> value that excludes <code>x11</code> (note lower case, as with all feature names) and then X11 support will be disabled at build time and these items won't even be built.

=== How do I avoid the kernel itself being pulled into my image when installing kernel modules? ===

By default, the kernel class sets a dependency on the kernel-base package (which kernel modules always depend on) onto kernel-image, which contains the actual kernel binary. If you don't want this, set the following either in your kernel recipe or at the configuration level:

RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""

Note: for older releases (pre-2.5) do this instead:

RDEPENDS_kernel-base = ""

== Misc ==

=== How do I remove a value from a list variable? ===

For variables that are expected to contain a space-separated list of items, BitBake supports a _remove operator to remove items from it. See [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#removing-override-style-syntax Removal (override style syntax)] in the BitBake user manual.

'''NOTE:''' the _remove operation is final - you cannot "undo" it with other operations elsewhere, thus you should really only make use of it in your distro / local configuration and not in layers that you expect others to re-use for different purposes (and therefore they may need to undo your changes). An alternative way to effectively remove an item is to set the list outright to include all the items minus the one you want to remove.

=== How do I change how my recipe is built depending on what image I'm building? ===

The short answer is you cannot - the reason is that OpenEmbedded builds packages based on the overall configuration, and then the image only selects which of these packages should go into the final image. However, there are some solutions that do allow you to achieve the desired result:

# Have separate packages for the two different versions. This could take the form of different recipes or you could do it within the same recipe. The two packages do have to have different names however; this may create problems if you have other packages that depend on the package.
# Use a postprocessing function within the image(s) - within the image recipe, define a shell or python function that makes the desired changes to the files in the image and add a call to it to ROOTFS_POSTPROCESS_COMMAND within the image recipe. Note that this may not be appropriate if you have runtime package management enabled since the postprocessing will only happen at image creation time and not if the package is installed later on at runtime - you may need to use a postinstall script instead in this case.
# Use a postinstall script (pkg_postinst_<package> function) within the recipe. In order to work, the postinstall script will need to be able to determine what to do when it's run - this may not be practical depending on what you're trying to achieve.

=== Can I use a toolchain built by OE as the external toolchain? ===

In general, this is not recommended and not something that is tested or directly supported out of the box. If you are wanting to do this solely as a means of speeding up the build, it is strongly suggested that you use shared state instead.

There is a [http://layers.openembedded.org/layerindex/branch/master/layer/meta-sourcery/ meta-sourcery layer] available to enable support for the CodeSourcery toolchain, you may be able to use this as a template for bringing in an external toolchain however there are no guarantees.

=== When I run bitbake -c devshell it looks like it's running as root! How is that possible? ===

It's not running as the actual root user, it's just pretending for the benefit of programs that run under it (including your shell) that it is, via pseudo. This is important, because you normally want any owner/group/permission values that you set on files to be reflected in files that the recipe installs and packages and thus reflected in the final image - without this mechanism the actual build would have to run as root which would be very risky. There are no actual elevated privileges through this mechanism however, so you need not be worried.

=== Why does OE use pseudo? Why not use fakeroot / fakechroot instead? ===

Splitting this up into two questions - we use pseudo (not to be confused with sudo!) because we want to be able to create images containing files have the correct permissions and ownership, e.g. files owned by root, without the user running the build system having to have that privilege. By using LD_PRELOAD to intercept function calls, pseudo creates an environment for programs running underneath it where it appears as if the running user has those privileges (and the results of any operations persist within the pseudo environment, i.e. you can write a file as root and it will appear to be owned by root while still running under pseudo). This allows us to run builds entirely as a normal user without needing extra privileges. Without pseudo we would require running the build system under sudo or as root - which would be ill-advised for things such as "make install" in case it happened to be broken and tried to write to / instead of somewhere under the work directory for the recipe; a broken recipe could easily end up destroying your system in that case.

To answer the second part, why we use pseudo instead of fakeroot / fakechroot, see [https://github.com/wrpseudo/pseudo/wiki/WhyNotFakeroot WhyNotFakeroot on the pseudo wiki].

=== How do I find out what packages are produced by a recipe? ===

The Toaster web UI provides easy ways to query this.

In the 1.8 (fido) release and newer you can use the following command, assuming the recipe has already been built:

oe-pkgdata-util list-pkgs -p recipename

Alternatively you can look in the "packages-split" subdirectory under the work directory for the recipe - each package produced by the recipe will have a subdirectory under that. If you're not sure how to find the work directory you can run the following command:

bitbake -e recipename | grep ^WORKDIR=

Before a recipe gets built it is a bit trickier, since the system often doesn't know exactly which packages will be produced until do_package time; this is particularly true for recipes that package plugins or modules (e.g. kernel modules). You can get a reasonable idea though by looking at the value of PACKAGES (and PACKAGES_DYNAMIC for recipes that produce plugins).

=== How do I find out which package contains a particular file (or python module)? ===

oe-pkgdata-util has a find-path subcommand that will tell you exactly this. For example:

$ oe-pkgdata-util find-path /etc/network/interfaces
init-ifupdown: /etc/network/interfaces

Wildcards are allowed anywhere in the path (but you should enclose such expressions in quotes to avoid the shell itself attempting to expand the wildcard):

$ oe-pkgdata-util find-path "*/fstrim"
util-linux-bash-completion: /usr/share/bash-completion/completions/fstrim
util-linux-ptest: /usr/lib/util-linux/ptest/fstrim
util-linux-dbg: /sbin/.debug/fstrim
util-linux-fstrim: /sbin/fstrim

As a specific example of where this can be useful, our Python packaging is a bit more granular than most typical distributions, allowing you to tune the contents of your image to just what you need. However, that does mean you may have trouble figuring out which package provides a particular module. oe-pkgdata-util find-path can also be used for this. For example, to find the package containing the "shutil" module, run this:

$ oe-pkgdata-util find-path "*/shutil.*"
python3-shell: /usr/lib/python3.5/shutil.py
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-2.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-1.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.pyc

Thus the package you are looking for is python3-shell. (Note that you could use */shutil.py, but if the module you are looking for is written in C as some of them are, that won't match it.)

=== I have a local source tree I want to build instead of the upstream source a recipe normally fetches, how do I do that? ===

If it's for development purposes i.e. you have your own local source tree you want to work on and have built, then run:

devtool modify -n <recipename> path/to/sourcetree/

Once you are done you can use <code>devtool finish</code> or <code>devtool reset</code> (depending on the situation) to return to building the source specified in the recipe.

Alternatively if it's more permanent, use the <code>externalsrc</code> class - you can inherit this in the original recipe or a bbappend:

inherit externalsrc
EXTERNALSRC = "/path/to/sources"

If you're going to use it across a number of recipes you can inherit it globally at the configuration level (perhaps via an inc file that you include/require there):

INHERIT += "externalsrc"
EXTERNALSRC_pn-<recipename> = "/path/to/sources"

=== How do I specify the default shell? (e.g. bash instead of busybox) ===

It depends what you mean. As far as which provides /bin/sh, this is controlled through the alternatives system, and by default bash has a higher priority than busybox, so simply installing bash into your image will automatically have /bin/sh link to bash rather than busybox.

If you mean you want a user's login shell to be a specific shell, you'll need to modify /etc/passwd. One fairly easy way to achieve this is to use the extrausers class in your image recipe:

inherit extrausers
EXTRA_USERS_PARAMS = "usermod -s /bin/bash <username>; "

=== How do I get "full" versions of typical shell commands? ===

Most of the shell commands in our images are provided by busybox by default, and are very much simplified compared to what you would have on a typical Linux system in order to save space. If you need the full versions, most of them are built and packaged by the coreutils recipe (for disk and other typical utilities) and procps (for ps, etc). You may also want to install bash for more typical shell built-in commands. There is also a core-image-full-cmdline image if you want a base image that is already set up to provide a more typical Linux command-line experience. (Note: these will of course use up more disk space and memory.)

=== How do I allow a variable's value through from the external environment? ===

Add the variable's name to the BB_ENV_EXTRAWHITE ''in the external environment'' before running bitbake. Note that the oe-init-build-env script sets a default for this which you will want to preserve, so add to the default value rather than overwriting it.

Alternatively if you just want to get the external value of a variable from python code within the metadata, you can use the BB_ORIGENV variable which itself contains a datastore of the original environment. For example to get the value of the DISPLAY variable from the environment within a python function you would do this:

display = d.getVar("BB_ORIGENV", False).getVar("DISPLAY")

Note that you must specify "false" for the expand parameter when getting the BB_ORIGENV variable, because it's not a string and therefore cannot be expanded in the normal manner.

=== Why is bitbake showing "AUTOINC" in the version for some recipes? ===

Recipes where you see AUTOINC within the version in the console output during a build will be those that set <code>PV</code> to include <code>"${SRCPV}"</code> to get the SCM revision (e.g. the git hash) in the package version. In order to have the version increment properly, there needs to be a number in front of the revision which automatically increments each time the revision changes (assuming you have a PR server enabled), which is where AUTOINC comes in. During the build, AUTOINC is a stand-in for this auto-incrementing number, and later during <code>do_package</code> it gets replaced with the real number so that the packages produced at the end have the full version number.

=== Why are .so files in the -dev package instead of the main package for a recipe? ===

In standard Unix library packaging, non-versioned .so symlinks (e.g. /usr/lib/libgd.so) are intended for development purposes only. At runtime, binaries should be linked to the major-versioned .so file/symlink e.g. /usr/lib/libgd.so.3. This (theoretically) allows multiple major versions of the same library as well as binaries that depend upon each of them to coexist on the same system. If the library is versioned but you have a binary that links to the unversioned .so file, it has almost certainly been linked incorrectly.

Non-symlink .so files on the other hand are sometimes produced and are entirely legal - however these will be picked up in the -dev package in OpenEmbedded simply by virtue of their name, which is almost always not what you want. In this case you can do one of two things:

# Fix the build of the library so it gets versioned. This may not always be appropriate, especially not for things like plugins.
# Set FILES_${PN}-dev within the recipe so that it does not include ${FILES_SOLIBSDEV}. If the software the recipe is building also produces symlink .so files you'll need to set FILES_${PN}-dev such that those do still get packaged in the -dev package though, or you'll get a package QA warning.

=== Can I disable shared state? ===

You cannot, no. Shared state (sstate) is an intrinsic part of staging files into the sysroot. It is possible to construct a recipe that bypasses sstate for some tasks (the kernel does this), however this is quite difficult and if not done properly will lead to many other problems.

Almost always when you are having a problem with shared state the issue is either (a) you're adding/changing files in the sysroot directly (i.e. outside sstate control), or (b) what is being placed into the sysroot isn't relocatable due to hardcoded paths. The solution for (a) is do not do that - files should always be installed under <code>${D}</code> within <code>do_install</code> and then a subset of those are staged into the sysroot automatically. For (b) you need to fix or adapt the hardcoded path(s) - if the program reads (or can be made to read) each path from an environment variable, then you can use the <code>create_wrapper</code> utility function to create a wrapper script that will set the path appropriately. Run <code>git grep create_wrapper</code> in the <code>meta</code> subdirectory to see examples.

=== Files I installed into /opt or some other path never make it into the sysroot but I need them - how do I fix this? ===

OpenEmbedded only stages a subset of files that are installed into <code>${D}</code> by <code>do_install</code> so that the sysroot doesn't fill up with unneeded files. You have two choices in this situation:
# install the files into a more standard location which is part of the subset, or
# adjust the subset to include the paths you are installing to.
Usually option 1 is recommended. If you really do need to adjust the subset, you can append the path (more specifically, the part below <code>${D}</code>) to <code>SYSROOT_DIRS</code> within your recipe. For example:

SYSROOT_DIRS += "/opt"

=== I have some software which needs to build a binary that it then runs as part of its own build process, how do I make this work? ===

Whilst it is possible to do this within a single recipe building for the target, it is tricky to do so because in that context everything is set up for cross-compiling for the target, and you would have to undo all of that to build host tools. The standard and much easier way of handling this is to create a native variant of the recipe using BBCLASSEXTEND and have your host tools built within that, and then have the target variant depend on the native variant. For example, assume your recipe were called xyz (xyz_1.1.bb), then you would include something like this in the recipe:

DEPENDS_append_class-target = " xyz-native"

...

BBCLASSEXTEND += "native"

The host tools will then be built and installed into the sysroot in the native variant ready for when the target variant starts building. If the software you are building didn't intend for those tools to be installed outside of the build tree then you may need to patch the build process (e.g. the makefile) in order to install them and possibly also for the target side to find them in the sysroot. Additionally, for performance since you only need the tools in the native variant, you may also choose to disable building everything except those tools there - e.g. by using _native overrides for variables such as EXTRA_OECONF or functions such as do_configure.

=== How do I fetch from two git repositories in the same recipe? ===

By default, sources fetched from git within a recipe are unpacked into ${WORKDIR}/git, however that only works for a single repository. If you want to fetch from more than one, you need to change the path each repository is unpacked to. This is easy to do, just add <code>;destsuffix=<subdir></code> to the end of each URL in SRC_URI (replacing <code><subdir></code> with the name of the subdirectory). You may then need to change S to match whichever of these you want to be considered the root of the source tree - or alternatively you can specify destsuffix such that repositories beyond the first go into a subdirectory under the default "git" subdirectory. For example, from the gst-libav recipe:

...
SRC_URI = " \
git://anongit.freedesktop.org/gstreamer/gst-libav;branch=1.8;name=base \
git://anongit.freedesktop.org/gstreamer/common;destsuffix=git/common;name=common \
...
"
...
S = "${WORKDIR}/git"
...

(Here we're using the default of "git" for the first repository, so we don't need to specify <code>destsuffix</code> for the first URL.)

=== I'm building a native recipe and I notice that the install path has the full path to the root directory repeated - why? ===

It does look a little odd, but the reason for doing this is that native targets are meant to run on the system they're built on and run in the location they're installed to. This means they install to a destination of "/" and PREFIX is inside the native sysroot directory. We install them to a DESTDIR to allow us to manipulate them before they then get moved to a final DESTDIR of "/".

Most Makefiles handle this correctly by doing:

DESTDIR ?= ""
prefix ?= "/usr"
bindir ?= "$(prefix)/bin"

and then, importantly, install in the form:

install -d $(DESTDIR)$(bindir)

so both prefix and DESTDIR are used. Whilst this is a convention, its a widely adopted and followed one. You can call into a custom makefile and set the variables manually if the makefile doesn't follow the convention.

=== How do I generate static libraries? ===

Its possible you have conf/distro/include/no-static-libs.inc included in your build - poky does this by default. The include list at the top of the bitbake -e output will tell you for certain.

If so, you can remove that or set:

DISABLE_STATIC = ""

as it would currently be set to this if that include file is included:

DISABLE_STATIC = " --disable-static"

Poky disables building static libraries by default as for the most part they're a waste of space/time.

=== Can I conditionally inherit a class in a recipe? ===

Yes, you can. What makes this possible is that the <code>inherit</code> keyword will not complain if what comes after it expands to being empty, so you can use in-line python to do something like this:

<pre><nowiki>
inherit ${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}
</nowiki></pre>

The above example will inherit the <code>perlnative</code> class if "scripting" is in the value of the <code>PACKAGECONFIG</code> variable, otherwise it will do nothing.

You could of course put this into a variable if you prefer:

<pre><nowiki>
SOMEVAR = "${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}"
inherit ${SOMEVAR}
</nowiki></pre>

=== How do I collect the source revisions fetched by each recipe? ===

If you have recipes where <code>SRCREV = "${AUTOREV}"</code> then you won't necessarily know exactly which revisions were built after the fact - it will be whatever was current at the time. You also might alternatively just want to get all of the revisions. Either way, to do this, enable buildhistory by setting the following in your local.conf:

<pre><nowiki>
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
</nowiki></pre>

(The last line is not required with version 2.5 and onwards as it is the default, but will do no harm.)

Once you have enabled buildhistory, you then need to build your image again so that buildhistory has a chance to record history data for it. Following that you can run <code>buildhistory-collect-srcrevs</code> (with <code>-a</code> if you want to see all revisions, not just the ones where AUTOREV was used) and it will output the revisions in a form you can use in a .inc file that you can <code>require</code> from your configuration if you want to fix the build to those revisions.

For more information see the [https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] section of the Yocto Project Development manual, which covers the buildhistory class in detail.

=== How do I do an offline build with recipes that have <code>SRCREV = "${AUTOREV}"</code> set? ===

If you set <code>BB_NO_NETWORK = "1"</code> and you have recipes that have <code>SRCREV = "${AUTOREV}"</code>, you will get an error because the build system will try to check the latest revision on startup and be immediately blocked by <code>BB_NO_NETWORK</code>. There are two ways to handle this:

A) See the previous question "How do I collect the source revisions fetched by each recipe?" and use the output generated by <code>buildhistory-collect-srcrevs</code> as a .inc file in your configuration in order to fix the revisions at the ones which were most recently built.

or

B) Set <code>BB_SRCREV_POLICY = "cache"</code> in your configuration. This will use the last cached revision. (The disadvantage of this method is that it is a little more difficult to preserve or share with others the fixed revisions.)

Note that in either case if you later want to build the latest version again, you will of course need to undo the configuration changes.

=== Is it possible to append a bbclass file (like bbappends do for recipes)? ===

No, see the next question for details.

=== How do I override a bbclass file? ===

This is tricky - bbclass files are found via BBPATH, which is added to by each layer.conf either by prepending or appending. Assuming you are putting your bbclass in a custom layer, you will probably want to have your layer's layer.conf prepend to BBPATH, but then you will also need to make sure that your layer does not appear before any other layer that is also prepending and overriding the same class.

Another alternative is to have an additional class which makes the appropriate changes to the environment, and then you will need to inherit that class after (and in the same manner as) the original class. This is slightly cleaner but can be annoying to enable particularly if the class is inherited by a number of recipes, and won't work if you want to alter the behaviour of a class inherited by recipes you don't control. (If you want a class to be inherited for all images (i.e. all recipes inheriting the <code>image</code> class) you can inject additional classes by setting IMAGE_CLASSES; similarly for the kernel there is KERNEL_CLASSES).

Ultimately, overriding bbclass files is not good practice long term - you are opening yourself up to maintenance issues when the original class changes, and the override is fragile as hinted above. The best solution is to try to get whatever changes you need into the original class; this does of course require additional work and time though.

=== There's a bbappend in a layer I'm using that defines a <code>do_something_append()</code> and I want to append to that function also, how do I do this? ===

Simply create a bbappend in your layer and define your own <code>do_something_append()</code>, and your commands will be executed ''as well as'' those of the other bbappend.

You might assume that defining <code>do_something_append()</code> will overwrite any previously defined <code>do_something_append()</code>, as would be the case with <code>do_something()</code> in the same situation, but that is not the case - the key is that <code>_append</code> (and <code>_prepend</code>, <code>_remove</code>, etc.) are ''operators'' and they will be applied in sequence, where that sequence is the order in which they are parsed (which for bbappends will be in ascending layer priority order).

Technical FAQ

2020-07-01T01:16:40Z

PaulEggleton: /* Can I disable shared state? */

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
| '''NOTE:''' This is currently a draft. Not sure where this should end up but I've been gathering these based on my interactions with people on IRC and email over the years. - [[User:PaulEggleton|PaulEggleton]] ([[User talk:PaulEggleton|talk]]) 21:13, 27 June 2016 (PDT)
|}

== Basics ==

=== How do I figure out which version/codename/bitbake version matches up with which? ===

There is a table in the [http://wiki.yoctoproject.org/wiki/Releases Releases page] on the Yocto Project wiki.

=== How do I control what's in the final image? ===

Each image is defined by its own recipe, and that recipe specifies a list of packages that the image should contain. See [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Customising Images] within the Yocto Project development manual for further details.

Note: if you're doing anything more than basic experimentation / testing then you almost certainly should create your own image recipe rather than using one of the example images e.g. core-image-minimal - though you can certainly start by copying one of the example images. This way you have easier control over what goes into the image.

=== Where do I find build logs? ===

For the overall build, the output of bitbake gets logged to tmp/log/cooker/<machine>.

For each individual recipe, there is a "temp" directory under the work directory for the recipe that contains log.<taskname> and run.<taskname> files - the logs and the runfiles respectively. Within the build system this directory is pointed to by the T variable, so if you need to you can find it by using <code>bitbake -e</code>:

bitbake -e <recipename> | grep ^T=

=== How do I add a patch to a recipe? ===

There are two concerns - how the recipe can fetch the patch and how it can be applied. For fetching, patch files are usually placed in a subdirectory next to the recipe; by default this directory should be named "files" or the the recipe name without any class prefix or suffix (for example for both "xyz" and "xyz-native" the subdirectory would be "xyz"). A pointer to it then needs to be added to <code>SRC_URI</code> within the recipe, which usually takes the form <code>file://<patchname>.patch</code> - i.e. just the filename, no path. If more than one subdirectory needs to be stripped off the paths in the patch (i.e. you need more than the equivalent of the -p1 option to the patch command) then you can add <code>;striplevel=<number></code> to the end of the patch entry in SRC_URI (without any spaces).

As with any modification, if the patch you are applying is a customisation that you do not intend to send to be incorporated in the layer you are modifying, then instead of adding the patch to the recipe directly then you should consider applying it in a bbappend within your own custom layer. This makes things easier if you later want to update the layer in question and the recipe has been modified upstream - you avoid effectively forking the layer.

The <code>devtool</code> utility can help you modify the sources for a recipe and create a patch - basically <code>devtool modify</code>, edit the sources, commit the changes with <code>git commit</code>, then <code>devtool finish</code> (or <code>devtool update-recipe</code> in versions older than 2.2). Since <code>devtool modify</code> gives you a git tree to work with, you can of course use something like <code>git am</code> to apply existing patches this way. For more details see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#devtool-use-devtool-modify-to-enable-work-on-code-associated-with-an-existing-recipe Use devtool modify to Enable Work on Code Associated with an Existing Recipe] within the Yocto Project Development manual.

=== What does "native" mean? ===

The "native" suffix identifies recipes (and variants of recipes) that produce files intended for the build host, as opposed to the target machine. This is usually for tools that are needed during the build process (such as automake).

=== What does "nativesdk" mean? ===

The "nativesdk" prefix identifies recipes (and variants of recipes) that produce files intended for the host portion of the standard SDK, or for things which are constructed like an SDK such as buildtools-tarball. These are built for SDKMACHINE which may or may not be the same architecture as the build host.

=== I have two recipes and one needs to access files provided by another - how can that work? ===

Instead of providing direct access from a recipe to another's build tree (which wouldn't be practical with OpenEmbedded since the build tree (or "workdir") is temporary), we create a "sysroot" where files that are intended to be shared between recipes get copied. The sysroot is managed by the build system and you should not copy files in there directly - instead, you install files under ${D} as normal during do_install and then the build system will copy a subset of those to the sysroot. There is a seperate sysroot for each machine being built for. In a recipe you can get the path of the sysroot and various standard directories under it using the STAGING_* variables.

Often, for commonly-used build systems such as autotools and cmake you don't need to worry about these details - those systems and the environment that OpenEmbedded sets up for them will ensure that files get installed and picked up in the correct locations. However if the software your recipe is building has custom build scripts / makefiles and it takes shortcuts that don't account for cross-compilation or the use of a sysroot, then you will need to make appropriate adjustments.

=== How do I enable package management in the final image? ===

Add <code>package-management</code> to <code>IMAGE_FEATURES</code> (or <code>EXTRA_IMAGE_FEATURES</code>). You should then be able to use dnf/rpm, opkg, or apt-get/dpkg from the running system depending on the packaging format you have selected through PACKAGE_CLASSES. For more information see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-runtime-package-management Using Runtime Package Management] in the Yocto Project Development manual.

=== What do ?=, ??=, := etc. do within a recipe/config file? ===

See the [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#basic-syntax Basic Syntax section of the BitBake manual] for details.

== Layers ==

See http://www.openembedded.org/Layers_FAQ

== Troubleshooting ==

=== I've created a recipe but it's not showing up in my image, what's going on? ===

Creating a recipe (or adding a layer to your configuration with a desired recipe in it) only makes it available to the build system, it doesn't change what goes into the image. For that, see [[#How do I control what's in the final image?|How do I control what's in the final image?]] above.

=== I set a variable but it doesn't seem to be having an effect, how do I fix this? ===

First, double-check that you haven't misspelled the variable name.

The main tool to help troubleshoot any variable-related issue is <code>bitbake -e</code> - this lists all the variables and the complete history of how each one has been set (use <code>bitbake -e recipename</code> if you're dealing with issues in a variable value within a recipe as opposed to the global level). Usually it's best to pipe this through <code>less</code> so you can easily see the history - within less you can press / to search for the variable name. Often you will be dealing with the behaviour of a variable within the context of a specific recipe, so specify that recipe on the <code>bitbake -e</code> command line to get the variables as set within the context of the recipe rather than the global context.

If you're setting a variable in a bbappend, double-check that the bbappend is actually being applied - see the next question.

=== I've created a bbappend for a recipe but what I'm setting there isn't having any effect, how do I fix this? ===

Here are some things to check:

# Check if the layer the bbappend is in is listed in <code>bitbake-layers show-layers</code>. If it isn't, you need to edit your bblayers.conf and ensure the path to the layer is included in the BBLAYERS value
# Check that the bbappend is being picked up by running <code>bitbake-layers show-appends</code> - if your bbappend file isn't listed, it could be named incorrectly (such that it doesn't match the recipe name) or it may be that the BBFILES value in the conf/layer.conf for the layer containing the bbappend file doesn't include an expression that will match the bbappend files.
# If there are multiple versions of the recipe you have bbappended, it could be that the actual recipe being built is a different version than the one you have bbappended. <code>bitbake-layers show-recipes <recipename></code> will list all the versions, with the first one listed being the one that will be built. If this is the case there are several different solutions to this - (a) Rename your bbappend to match the version being built, (b) use a % wildcard in your bbappend so it will apply to any version, (c) set <code>PREFERRED_VERSION_<recipename></code> in the configuration to select a the version you want to be built.
# Finally, as with any other issue with setting variables, use <code>bitbake -e recipename | less</code> and search with <code>/</code> to see the history of how the variable has been set - you may find that the value you're trying set is being overridden.

=== I'm getting warnings that a recipe is tainted - what does this mean? ===

Usually this happens because you have used I used bitbake's <code>-f</code> or <code>-C</code> option to force a task to re-execute. The assumption is that if you forced a task, it is possible that a rebuild from scratch would not include whatever changes you made that necessitated forcing (e.g. if you modified the source in the work directory for the recipe and then ran <code>bitbake -c compile -f</code>). Generally, forcing a task should be reserved for situations where the build system has failed to detect a change you made rather than for everyday usage - if you're finding yourself needing to do it regularly then either there's a bug, you're doing something wrong, or perhaps you're using <code>-f</code> or <code>-C</code> when it's not really needed. Running <code>bitbake -c clean</code> on the recipe will get rid of the taint flag.

There is one other situation where we apply a taint, and that is <code>bitbake -c menuconfig</code> on the kernel. In this case, the configuration has been saved into the work directory for the kernel, but that is temporary - any rebuild from scratch will use the default configuration, so it is a reminder that you need to take the configuration and apply it back to the metadata and then run <code>bitbake -c clean</code> on the kernel recipe.

=== I'm fetching from a git repository over ssh / http / https but it's not fetching properly, how do I fix this? ===

Bitbake expects the prefix of entries in SRC_URI to specify the fetcher to be used, not the actual protocol. Thus, instead of:

# This will NOT work
SRC_URI = "<nowiki>http://git.example.com/repository</nowiki>"

You should specify:

# This is better
SRC_URI = "<nowiki>git://git.example.com/repository;protocol=http</nowiki>"

The same applies for ssh and https.

=== I tried bitbake <some target package name> that I know exists and it told me that nothing PROVIDES this...? ===

There are two namespaces that bitbake concerns itself with - recipe names (a.k.a. build time targets) and package names (a.k.a. runtime targets). You can specify a build time target on the bitbake command line, but not a runtime target; you need to find the recipe that provides the package you are trying to build and build that instead (or simply add that package to your image and build the image). In current versions bitbake will at least tell you which recipes have matching or similar-sounding runtime provides (RPROVIDES) so that you'll usually get a hint on which recipe you need to build.

=== I've included a package in my image but files I expect to be there are missing, what's the issue? ===

Check the simple stuff: verify that the package is really in the image - look at the manifest file next to the image to ensure the package is listed. Also if you're flashing the image, double-check that you did indeed flash the right image and if there are multiple partitions / storage devices on your board or device that you're booting the one that you think you are.

Once you're sure of the above, it may be a matter of the package splitting - a lot of recipes split less commonly used components out to separate packages, so it's possible that the files you are looking for are in a different package. You can look at the recipe for this (look for PACKAGES and FILES statements) or assuming the recipe has been built, you can use <code>oe-pkgdata-util list-pkgs -p recipename</code> and <code>oe-pkgdata-util list-pkg-files</code> to inspect the packages provided by the recipe and the files they contain. Once you find the right package you can add it to your image.

=== I'm required to set LIC_FILES_CHKSUM but the software I'm building doesn't have a license statement, what do I do? ===

Ideally, all software should come with some kind of license statement so that the terms of distribution are clearly stated (especially if its source code is made publicly available); if not a text file describing the license then at the very least a line or two in the accompanying documentation, README file or source header comments. Assuming there is a license statement somewhere but not in a form you can point to with LIC_FILES_CHKSUM as part of the source tree, you can point LIC_FILES_CHKSUM to one of the generic license files in ${COMMON_LICENSE_DIR} (meta/files/common-licenses/), or alternatively you can include a file containing the license statement in a "files" subdirectory next to the recipe (or subdirectory named the same as the recipe - see how such files are handled in other recipes), point to it in SRC_URI using file://, then add it to LIC_FILES_CHKSUM. It is worth noting however that LIC_FILES_CHKSUM is intended to give you a warning if upstream changes its license terms when you do an upgrade of the recipe, and by pointing it to this common license file that is part of the metadata, that mechanism will not function. You may wish to consider encouraging the upstream provider of the software your recipe is building to follow best practices and include a proper license statement, so that you can point to it in a future version. At minimum if you do use such workarounds, you will need to take extra care when upgrading the recipe in future in case the upstream provider changes the license terms.

If there really is no license stated at all anywhere for the software (and this is unfortunately not uncommon on github, for example) then you should really contact upstream - if there's no license, then technically you really shouldn't be distributing it until that's clarified with the original author(s).

=== I am getting a package QA error / warning when building a recipe, how do I solve it? ===

There are some general and specific recommendations in the [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-errors-and-warnings QA Errors and Warnings] section of the Yocto Project Reference Manual.

=== I am getting "taskhash mismatch" errors, what does this mean and how do I fix it? ===

Bitbake parses the metadata (recipes, classes and configuration) repeatedly during its operation, and this error means that the result of parsing changed between one parse and the next. Two situations that can cause this:
# One of the parsed files changed in between e.g. you edited a recipe or performed a git operation (e.g. git checkout) during the build. '''Do not make changes to the metadata while a build is running.''' If you run the build again the error should not recur.
# Alternatively, there is something in the metadata that results in a variable expanding to a different value each time it is parsed. This is often something time-related e.g. a timestamp which is calculated every time an expression is expanded. The solution is to ensure the value is calculated once per build and then the expression expands to the same value for the duration of the build.

=== Building on a system with a GRSec kernel doesn't work well, is that supported? ===

No, grsec isn't really supported. The list of distros that are supported (tested) is in the Yocto mega manual for each release.
You can refer to the work-around given in this defect: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10885

=== Working around Firejail ===
For users of Parrot OS and other secured Linux distros, you will find that your bitbake fetch commands refuse to work, yet you can manually run wget and retrieve the packages with no problem. This is due to Poky creating links to all the tools it requires, in particular 'wget', 'ssh' and 'strings', using the links to these tools in the /usr/local/bin/ directory which all redirect to firejail. To fix the problem you can cd into <your Yocto install directory>/poky/build/tmp/hosttools directory and replace these links with ones redirecting to the actual executables under the /usr/bin directory.

== Dependencies ==

=== How do I find out why something is being built? ===

<code>bitbake -g <recipe></code> will produce some .dot files that allow you to see the dependency relationships - usually pn-depends.dot holds the answers although sometimes you may need to look at task-depends.dot if the dependency is only in the form of a task dependency. Note that these graphs are much too large for most graphviz visualisation tools to process, so you'll probably find it's easiest to view them with "less" or a text editor and search for the item you're looking for.

=== How do I find out why something is in my image? ===

Enable the buildhistory class and build the image again, and it will write out a depends.dot file containing the relationships between packages in the final image. If the package name isn't mentioned it is probably explicitly mentioned in IMAGE_INSTALL or being brought in via IMAGE_FEATURES.

See [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] in the Yocto Project Reference manual which covers how to enable buildhistory and the output it produces.

=== How do I view the .dot files produced by bitbake -g or buildhistory? ===

The size of some of these .dot graphs (particularly those produced by <code>bitbake -g</code>) is a little large for most viewers / processing tools, and unfortunately this isn't something that can be fixed - it's just the nature of the dependency relationships between targets and tasks within OpenEmbedded. Usually if you're just after answering a simple dependency question you can figure it out by viewing it with <code>less</code> and using its built-in search function (or alternatively your favourite text editor).

You can try [http://github.com/jrfonseca/xdot.py xdot] which will work well for some of the graphs, but the task graph produced by <code>bitbake -g</code> for something like an image in particular is likely to be too large to view within it.

=== Why are all of these -native items being built when my host distro has some of these available? ===

It's complicated. In some cases the software in question isn't widely packaged by common Linux distributions. In other cases we need to apply patches to the software, use a more up-to-date version than commonly packaged or build it with a particular configuration. In general it just helps us isolate ourselves from potential problems caused by differences in host Linux distributions. For the most part the time spent building the native tools that are definitely provided by the host distro are dwarfed by the time spent building things that definitely aren't provided, such as the C library for the target and the cross-compiling toolchain.

=== I disabled runtime package management and yet it still seems to be building rpm/opkg, why? ===

The build system always uses a package manager on the host to assemble images, because it is usually the best tool for this job. This is completely independent of whether the package manager is available in the target image - "package-management" being in IMAGE_FEATURES (possibly indirectly via EXTRA_IMAGE_FEATURES) controls whether the package manager is used at runtime i.e. whether it (and its associated package database) will be present in the target image.

=== Why is opkg-native / opkg-utils being built when I don't have ipk packaging enabled? ===

opkg-utils provides update-alternatives which is the default tool used to manage the alternatives system (for selecting between multiple providers of the same file, e.g. busybox and bash both provide /bin/sh).

=== Why is rpm-native being built when I don't have rpm packaging enabled? ===

rpm-native is needed for two things in the generic packaging code implemented in the package class:

# Debug symbol splitting - rpm-native provides the debugedit tool which this code uses
# Per-file dependencies - although this was originally just feeding into rpm when rpm was being used, it also now gets verified by QA checks regardless of which packaging backend is in use.

=== I see a recipe built, but building an image containing the corresponding package fails at do_rootfs because it can't find the package. How does this happen? ===

(For ipk, the error is "Couldn't find anything to satisfy '<package>'"; for rpm it is "<package> not found in the base feeds (<architecture list>)".)

Usually this is because the recipe claimed to provide the specified package (via PACKAGES or PACKAGES_DYNAMIC) but it wasn't actually produced, possibly because it ended up empty (since by default empty packages aren't produced), but the image or some other package still has a dependency that pulls in the specified package. If this is a recipe you are writing yourself the probable cause is your recipe isn't installing any files and thus the main package for the recipe is empty. Fix do_install (or what do_install is already running, e.g. make install) such that files are installed into the correct location such that they can then subsequently be packaged, and then all should be well.

In other situations the reference to the package in question is spurious and either it should be removed entirely or there's another package that should be used instead. For example, the avahi and dhcp recipes both have an empty main package since the client and server are split out into their own packages, and those are the ones you should be using instead (avahi-daemon, avahi-utils, dhcp-server, dhcp-client - there are other packages as well, please see [[#How_do_I_find_out_what_packages_are_produced_by_a_recipe.3F|How do I find out what packages are produced by a recipe?]].) You could argue that these recipes shouldn't claim to provide the main package, or they should have a main package that depends on all the other packages (as some other recipes do).

=== X11 and various other items are being built but I'm only building core-image-minimal - why? ===

This is where it helps to understand the difference between build-time dependencies and runtime dependencies - often, a recipe will require things at build time (for example tools that help the build process, or to satisfy optional dependencies) that it doesn't necessarily need at runtime. The default configuration includes "<code>x11</code>" in <code>DISTRO_FEATURES</code>, and thus anything that can optionally support X11 will have its X11 support enabled; however when it comes to actually producing the image there won't be any X11 packages included as long as there are no hard dependencies and there aren't any X11 packages explicitly requested.

If you never intend to use X11, you can set your own <code>DISTRO_FEATURES</code> value that excludes <code>x11</code> (note lower case, as with all feature names) and then X11 support will be disabled at build time and these items won't even be built.

=== How do I avoid the kernel itself being pulled into my image when installing kernel modules? ===

By default, the kernel class sets a dependency on the kernel-base package (which kernel modules always depend on) onto kernel-image, which contains the actual kernel binary. If you don't want this, set the following either in your kernel recipe or at the configuration level:

RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""

Note: for older releases (pre-2.5) do this instead:

RDEPENDS_kernel-base = ""

== Misc ==

=== How do I remove a value from a list variable? ===

For variables that are expected to contain a space-separated list of items, BitBake supports a _remove operator to remove items from it. See [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#removing-override-style-syntax Removal (override style syntax)] in the BitBake user manual.

'''NOTE:''' the _remove operation is final - you cannot "undo" it with other operations elsewhere, thus you should really only make use of it in your distro / local configuration and not in layers that you expect others to re-use for different purposes (and therefore they may need to undo your changes). An alternative way to effectively remove an item is to set the list outright to include all the items minus the one you want to remove.

=== How do I change how my recipe is built depending on what image I'm building? ===

The short answer is you cannot - the reason is that OpenEmbedded builds packages based on the overall configuration, and then the image only selects which of these packages should go into the final image. However, there are some solutions that do allow you to achieve the desired result:

# Have separate packages for the two different versions. This could take the form of different recipes or you could do it within the same recipe. The two packages do have to have different names however; this may create problems if you have other packages that depend on the package.
# Use a postprocessing function within the image(s) - within the image recipe, define a shell or python function that makes the desired changes to the files in the image and add a call to it to ROOTFS_POSTPROCESS_COMMAND within the image recipe. Note that this may not be appropriate if you have runtime package management enabled since the postprocessing will only happen at image creation time and not if the package is installed later on at runtime - you may need to use a postinstall script instead in this case.
# Use a postinstall script (pkg_postinst_<package> function) within the recipe. In order to work, the postinstall script will need to be able to determine what to do when it's run - this may not be practical depending on what you're trying to achieve.

=== Can I use a toolchain built by OE as the external toolchain? ===

In general, this is not recommended and not something that is tested or directly supported out of the box. If you are wanting to do this solely as a means of speeding up the build, it is strongly suggested that you use shared state instead.

There is a [http://layers.openembedded.org/layerindex/branch/master/layer/meta-sourcery/ meta-sourcery layer] available to enable support for the CodeSourcery toolchain, you may be able to use this as a template for bringing in an external toolchain however there are no guarantees.

=== When I run bitbake -c devshell it looks like it's running as root! How is that possible? ===

It's not running as the actual root user, it's just pretending for the benefit of programs that run under it (including your shell) that it is, via pseudo. This is important, because you normally want any owner/group/permission values that you set on files to be reflected in files that the recipe installs and packages and thus reflected in the final image - without this mechanism the actual build would have to run as root which would be very risky. There are no actual elevated privileges through this mechanism however, so you need not be worried.

=== Why does OE use pseudo? Why not use fakeroot / fakechroot instead? ===

Splitting this up into two questions - we use pseudo (not to be confused with sudo!) because we want to be able to create images containing files have the correct permissions and ownership, e.g. files owned by root, without the user running the build system having to have that privilege. By using LD_PRELOAD to intercept function calls, pseudo creates an environment for programs running underneath it where it appears as if the running user has those privileges (and the results of any operations persist within the pseudo environment, i.e. you can write a file as root and it will appear to be owned by root while still running under pseudo). This allows us to run builds entirely as a normal user without needing extra privileges. Without pseudo we would require running the build system under sudo or as root - which would be ill-advised for things such as "make install" in case it happened to be broken and tried to write to / instead of somewhere under the work directory for the recipe; a broken recipe could easily end up destroying your system in that case.

To answer the second part, why we use pseudo instead of fakeroot / fakechroot, see [https://github.com/wrpseudo/pseudo/wiki/WhyNotFakeroot WhyNotFakeroot on the pseudo wiki].

=== How do I find out what packages are produced by a recipe? ===

The Toaster web UI provides easy ways to query this.

In the 1.8 (fido) release and newer you can use the following command, assuming the recipe has already been built:

oe-pkgdata-util list-pkgs -p recipename

Alternatively you can look in the "packages-split" subdirectory under the work directory for the recipe - each package produced by the recipe will have a subdirectory under that. If you're not sure how to find the work directory you can run the following command:

bitbake -e recipename | grep ^WORKDIR=

Before a recipe gets built it is a bit trickier, since the system often doesn't know exactly which packages will be produced until do_package time; this is particularly true for recipes that package plugins or modules (e.g. kernel modules). You can get a reasonable idea though by looking at the value of PACKAGES (and PACKAGES_DYNAMIC for recipes that produce plugins).

=== How do I find out which package contains a particular file (or python module)? ===

oe-pkgdata-util has a find-path subcommand that will tell you exactly this. For example:

$ oe-pkgdata-util find-path /etc/network/interfaces
init-ifupdown: /etc/network/interfaces

Wildcards are allowed anywhere in the path (but you should enclose such expressions in quotes to avoid the shell itself attempting to expand the wildcard):

$ oe-pkgdata-util find-path "*/fstrim"
util-linux-bash-completion: /usr/share/bash-completion/completions/fstrim
util-linux-ptest: /usr/lib/util-linux/ptest/fstrim
util-linux-dbg: /sbin/.debug/fstrim
util-linux-fstrim: /sbin/fstrim

As a specific example of where this can be useful, our Python packaging is a bit more granular than most typical distributions, allowing you to tune the contents of your image to just what you need. However, that does mean you may have trouble figuring out which package provides a particular module. oe-pkgdata-util find-path can also be used for this. For example, to find the package containing the "shutil" module, run this:

$ oe-pkgdata-util find-path "*/shutil.*"
python3-shell: /usr/lib/python3.5/shutil.py
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-2.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-1.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.pyc

Thus the package you are looking for is python3-shell. (Note that you could use */shutil.py, but if the module you are looking for is written in C as some of them are, that won't match it.)

=== I have a local source tree I want to build instead of the upstream source a recipe normally fetches, how do I do that? ===

If it's for development purposes i.e. you have your own local source tree you want to work on and have built, then run:

devtool modify -n <recipename> path/to/sourcetree/

Once you are done you can use <code>devtool finish</code> or <code>devtool reset</code> (depending on the situation) to return to building the source specified in the recipe.

Alternatively if it's more permanent, use the <code>externalsrc</code> class - you can inherit this in the original recipe or a bbappend:

inherit externalsrc
EXTERNALSRC = "/path/to/sources"

If you're going to use it across a number of recipes you can inherit it globally at the configuration level (perhaps via an inc file that you include/require there):

INHERIT += "externalsrc"
EXTERNALSRC_pn-<recipename> = "/path/to/sources"

=== How do I specify the default shell? (e.g. bash instead of busybox) ===

It depends what you mean. As far as which provides /bin/sh, this is controlled through the alternatives system, and by default bash has a higher priority than busybox, so simply installing bash into your image will automatically have /bin/sh link to bash rather than busybox.

If you mean you want a user's login shell to be a specific shell, you'll need to modify /etc/passwd. One fairly easy way to achieve this is to use the extrausers class in your image recipe:

inherit extrausers
EXTRA_USERS_PARAMS = "usermod -s /bin/bash <username>; "

=== How do I get "full" versions of typical shell commands? ===

Most of the shell commands in our images are provided by busybox by default, and are very much simplified compared to what you would have on a typical Linux system in order to save space. If you need the full versions, most of them are built and packaged by the coreutils recipe (for disk and other typical utilities) and procps (for ps, etc). You may also want to install bash for more typical shell built-in commands. There is also a core-image-full-cmdline image if you want a base image that is already set up to provide a more typical Linux command-line experience. (Note: these will of course use up more disk space and memory.)

=== How do I allow a variable's value through from the external environment? ===

Add the variable's name to the BB_ENV_EXTRAWHITE ''in the external environment'' before running bitbake. Note that the oe-init-build-env script sets a default for this which you will want to preserve, so add to the default value rather than overwriting it.

Alternatively if you just want to get the external value of a variable from python code within the metadata, you can use the BB_ORIGENV variable which itself contains a datastore of the original environment. For example to get the value of the DISPLAY variable from the environment within a python function you would do this:

display = d.getVar("BB_ORIGENV", False).getVar("DISPLAY")

Note that you must specify "false" for the expand parameter when getting the BB_ORIGENV variable, because it's not a string and therefore cannot be expanded in the normal manner.

=== Why is bitbake showing "AUTOINC" in the version for some recipes? ===

Recipes where you see AUTOINC within the version in the console output during a build will be those that set <code>PV</code> to include <code>"${SRCPV}"</code> to get the SCM revision (e.g. the git hash) in the package version. In order to have the version increment properly, there needs to be a number in front of the revision which automatically increments each time the revision changes (assuming you have a PR server enabled), which is where AUTOINC comes in. During the build, AUTOINC is a stand-in for this auto-incrementing number, and later during <code>do_package</code> it gets replaced with the real number so that the packages produced at the end have the full version number.

=== Why are .so files in the -dev package instead of the main package for a recipe? ===

In standard Unix library packaging, non-versioned .so symlinks (e.g. /usr/lib/libgd.so) are intended for development purposes only. At runtime, binaries should be linked to the major-versioned .so file/symlink e.g. /usr/lib/libgd.so.3. This (theoretically) allows multiple major versions of the same library as well as binaries that depend upon each of them to coexist on the same system. If the library is versioned but you have a binary that links to the unversioned .so file, it has almost certainly been linked incorrectly.

Non-symlink .so files on the other hand are sometimes produced and are entirely legal - however these will be picked up in the -dev package in OpenEmbedded simply by virtue of their name, which is almost always not what you want. In this case you can do one of two things:

# Fix the build of the library so it gets versioned. This may not always be appropriate, especially not for things like plugins.
# Set FILES_${PN}-dev within the recipe so that it does not include ${FILES_SOLIBSDEV}. If the software the recipe is building also produces symlink .so files you'll need to set FILES_${PN}-dev such that those do still get packaged in the -dev package though, or you'll get a package QA warning.

=== Can I disable shared state? ===

You cannot, no. Shared state (sstate) is an intrinsic part of staging files into the sysroot. It is possible to construct a recipe that bypasses sstate for some tasks (the kernel does this), however this is quite difficult and if not done properly will lead to many other problems.

Almost always when you are having a problem with shared state the issue is either (a) you're adding/changing files in the sysroot directly (i.e. outside sstate control), or (b) what is being placed into the sysroot isn't relocatable due to hardcoded paths. The solution for (a) is do not do that - files should always be installed under <code>${D}</code> within <code>do_install</code> and then a subset of those are staged into the sysroot automatically. For (b) you need to fix or adapt the hardcoded path(s) - if the program reads (or can be made to read) each path from an environment variable, then you can use the <code>create_wrapper</code> utility function to create a wrapper script that will set the path appropriately. Run <code>git grep create_wrapper</code> in the <code>meta</code> subdirectory to see examples.

=== Files I installed into /opt or some other path never make it into the sysroot but I need them - how do I fix this? ===

OpenEmbedded only stages a subset of files that are installed into <code>${D}</code> by <code>do_install</code> so that the sysroot doesn't fill up with unneeded files. You have two choices in this situation:
# install the files into a more standard location which is part of the subset, or
# adjust the subset to include the paths you are installing to.
Usually option 1 is recommended. If you really do need to adjust the subset, you can append the path (more specifically, the part below <code>${D}</code>) to <code>SYSROOT_DIRS</code> within your recipe. For example:

SYSROOT_DIRS += "/opt"

=== I have some software which needs to build a binary that it then runs as part of its own build process, how do I make this work? ===

Whilst it is possible to do this within a single recipe building for the target, it is tricky to do so because in that context everything is set up for cross-compiling for the target, and you would have to undo all of that to build host tools. The standard and much easier way of handling this is to create a native variant of the recipe using BBCLASSEXTEND and have your host tools built within that, and then have the target variant depend on the native variant. For example, assume your recipe were called xyz (xyz_1.1.bb), then you would include something like this in the recipe:

DEPENDS_append_class-target = " xyz-native"

...

BBCLASSEXTEND += "native"

The host tools will then be built and installed into the sysroot in the native variant ready for when the target variant starts building. If the software you are building didn't intend for those tools to be installed outside of the build tree then you may need to patch the build process (e.g. the makefile) in order to install them and possibly also for the target side to find them in the sysroot. Additionally, for performance since you only need the tools in the native variant, you may also choose to disable building everything except those tools there - e.g. by using _native overrides for variables such as EXTRA_OECONF or functions such as do_configure.

=== How do I fetch from two git repositories in the same recipe? ===

By default, sources fetched from git within a recipe are unpacked into ${WORKDIR}/git, however that only works for a single repository. If you want to fetch from more than one, you need to change the path each repository is unpacked to. This is easy to do, just add <code>;destsuffix=<subdir></code> to the end of each URL in SRC_URI (replacing <code><subdir></code> with the name of the subdirectory). You may then need to change S to match whichever of these you want to be considered the root of the source tree - or alternatively you can specify destsuffix such that repositories beyond the first go into a subdirectory under the default "git" subdirectory. For example, from the gst-libav recipe:

...
SRC_URI = " \
git://anongit.freedesktop.org/gstreamer/gst-libav;branch=1.8;name=base \
git://anongit.freedesktop.org/gstreamer/common;destsuffix=git/common;name=common \
...
"
...
S = "${WORKDIR}/git"
...

(Here we're using the default of "git" for the first repository, so we don't need to specify <code>destsuffix</code> for the first URL.)

=== I'm building a native recipe and I notice that the install path has the full path to the root directory repeated - why? ===

It does look a little odd, but the reason for doing this is that native targets are meant to run on the system they're built on and run in the location they're installed to. This means they install to a destination of "/" and PREFIX is inside the native sysroot directory. We install them to a DESTDIR to allow us to manipulate them before they then get moved to a final DESTDIR of "/".

Most Makefiles handle this correctly by doing:

DESTDIR ?= ""
prefix ?= "/usr"
bindir ?= "$(prefix)/bin"

and then, importantly, install in the form:

install -d $(DESTDIR)$(bindir)

so both prefix and DESTDIR are used. Whilst this is a convention, its a widely adopted and followed one. You can call into a custom makefile and set the variables manually if the makefile doesn't follow the convention.

=== How do I generate static libraries? ===

Its possible you have conf/distro/include/no-static-libs.inc included in your build - poky does this by default. The include list at the top of the bitbake -e output will tell you for certain.

If so, you can remove that or set:

DISABLE_STATIC = ""

as it would currently be set to this if that include file is included:

DISABLE_STATIC = " --disable-static"

Poky disables building static libraries by default as for the most part they're a waste of space/time.

=== Can I conditionally inherit a class in a recipe? ===

Yes, you can. What makes this possible is that the <code>inherit</code> keyword will not complain if what comes after it expands to being empty, so you can use in-line python to do something like this:

<pre><nowiki>
inherit ${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}
</nowiki></pre>

The above example will inherit the <code>perlnative</code> class if "scripting" is in the value of the <code>PACKAGECONFIG</code> variable, otherwise it will do nothing.

You could of course put this into a variable if you prefer:

<pre><nowiki>
SOMEVAR = "${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}"
inherit ${SOMEVAR}
</nowiki></pre>

=== How do I collect the source revisions fetched by each recipe? ===

If you have recipes where <code>SRCREV = "${AUTOREV}"</code> then you won't necessarily know exactly which revisions were built after the fact - it will be whatever was current at the time. You also might alternatively just want to get all of the revisions. Either way, to do this, enable buildhistory by setting the following in your local.conf:

<pre><nowiki>
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
</nowiki></pre>

(The last line is not required with version 2.5 and onwards as it is the default, but will do no harm.)

Once you have enabled buildhistory, you then need to build your image again so that buildhistory has a chance to record history data for it. Following that you can run <code>buildhistory-collect-srcrevs</code> (with <code>-a</code> if you want to see all revisions, not just the ones where AUTOREV was used) and it will output the revisions in a form you can use in a .inc file that you can <code>require</code> from your configuration if you want to fix the build to those revisions.

For more information see the [https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] section of the Yocto Project Development manual, which covers the buildhistory class in detail.

=== How do I do an offline build with recipes that have <code>SRCREV = "${AUTOREV}"</code> set? ===

If you set <code>BB_NO_NETWORK = "1"</code> and you have recipes that have <code>SRCREV = "${AUTOREV}"</code>, you will get an error because the build system will try to check the latest revision on startup and be immediately blocked by <code>BB_NO_NETWORK</code>. There are two ways to handle this:

A) See the previous question "How do I collect the source revisions fetched by each recipe?" and use the output generated by <code>buildhistory-collect-srcrevs</code> as a .inc file in your configuration in order to fix the revisions at the ones which were most recently built.

or

B) Set <code>BB_SRCREV_POLICY = "cache"</code> in your configuration. This will use the last cached revision. (The disadvantage of this method is that it is a little more difficult to preserve or share with others the fixed revisions.)

Note that in either case if you later want to build the latest version again, you will of course need to undo the configuration changes.

=== Is it possible to append a bbclass file (like bbappends do for recipes)? ===

No, see the next question for details.

=== How do I override a bbclass file? ===

This is tricky - bbclass files are found via BBPATH, which is added to by each layer.conf either by prepending or appending. Assuming you are putting your bbclass in a custom layer, you will probably want to have your layer's layer.conf prepend to BBPATH, but then you will also need to make sure that your layer does not appear before any other layer that is also prepending and overriding the same class.

Another alternative is to have an additional class which makes the appropriate changes to the environment, and then you will need to inherit that class after (and in the same manner as) the original class. This is slightly cleaner but can be annoying to enable particularly if the class is inherited by a number of recipes, and won't work if you want to alter the behaviour of a class inherited by recipes you don't control. (If you want a class to be inherited for all images (i.e. all recipes inheriting the <code>image</code> class) you can inject additional classes by setting IMAGE_CLASSES; similarly for the kernel there is KERNEL_CLASSES).

Ultimately, overriding bbclass files is not good practice long term - you are opening yourself up to maintenance issues when the original class changes, and the override is fragile as hinted above. The best solution is to try to get whatever changes you need into the original class; this does of course require additional work and time though.

=== There's a bbappend in a layer I'm using that defines a <code>do_something_append()</code> and I want to append to that function also, how do I do this? ===

Simply create a bbappend in your layer and define your own <code>do_something_append()</code>, and your commands will be executed ''as well as'' those of the other bbappend.

You might assume that defining <code>do_something_append()</code> will overwrite any previously defined <code>do_something_append()</code>, as would be the case with <code>do_something()</code> in the same situation, but that is not the case - the key is that <code>_append</code> (and <code>_prepend</code>, <code>_remove</code>, etc.) are ''operators'' and they will be applied in sequence, where that sequence is the order in which they are parsed (which for bbappends will be in ascending layer priority order).

Technical FAQ

2020-07-01T01:15:59Z

PaulEggleton: /* Can I disable shared state? */

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
| '''NOTE:''' This is currently a draft. Not sure where this should end up but I've been gathering these based on my interactions with people on IRC and email over the years. - [[User:PaulEggleton|PaulEggleton]] ([[User talk:PaulEggleton|talk]]) 21:13, 27 June 2016 (PDT)
|}

== Basics ==

=== How do I figure out which version/codename/bitbake version matches up with which? ===

There is a table in the [http://wiki.yoctoproject.org/wiki/Releases Releases page] on the Yocto Project wiki.

=== How do I control what's in the final image? ===

Each image is defined by its own recipe, and that recipe specifies a list of packages that the image should contain. See [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Customising Images] within the Yocto Project development manual for further details.

Note: if you're doing anything more than basic experimentation / testing then you almost certainly should create your own image recipe rather than using one of the example images e.g. core-image-minimal - though you can certainly start by copying one of the example images. This way you have easier control over what goes into the image.

=== Where do I find build logs? ===

For the overall build, the output of bitbake gets logged to tmp/log/cooker/<machine>.

For each individual recipe, there is a "temp" directory under the work directory for the recipe that contains log.<taskname> and run.<taskname> files - the logs and the runfiles respectively. Within the build system this directory is pointed to by the T variable, so if you need to you can find it by using <code>bitbake -e</code>:

bitbake -e <recipename> | grep ^T=

=== How do I add a patch to a recipe? ===

There are two concerns - how the recipe can fetch the patch and how it can be applied. For fetching, patch files are usually placed in a subdirectory next to the recipe; by default this directory should be named "files" or the the recipe name without any class prefix or suffix (for example for both "xyz" and "xyz-native" the subdirectory would be "xyz"). A pointer to it then needs to be added to <code>SRC_URI</code> within the recipe, which usually takes the form <code>file://<patchname>.patch</code> - i.e. just the filename, no path. If more than one subdirectory needs to be stripped off the paths in the patch (i.e. you need more than the equivalent of the -p1 option to the patch command) then you can add <code>;striplevel=<number></code> to the end of the patch entry in SRC_URI (without any spaces).

As with any modification, if the patch you are applying is a customisation that you do not intend to send to be incorporated in the layer you are modifying, then instead of adding the patch to the recipe directly then you should consider applying it in a bbappend within your own custom layer. This makes things easier if you later want to update the layer in question and the recipe has been modified upstream - you avoid effectively forking the layer.

The <code>devtool</code> utility can help you modify the sources for a recipe and create a patch - basically <code>devtool modify</code>, edit the sources, commit the changes with <code>git commit</code>, then <code>devtool finish</code> (or <code>devtool update-recipe</code> in versions older than 2.2). Since <code>devtool modify</code> gives you a git tree to work with, you can of course use something like <code>git am</code> to apply existing patches this way. For more details see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#devtool-use-devtool-modify-to-enable-work-on-code-associated-with-an-existing-recipe Use devtool modify to Enable Work on Code Associated with an Existing Recipe] within the Yocto Project Development manual.

=== What does "native" mean? ===

The "native" suffix identifies recipes (and variants of recipes) that produce files intended for the build host, as opposed to the target machine. This is usually for tools that are needed during the build process (such as automake).

=== What does "nativesdk" mean? ===

The "nativesdk" prefix identifies recipes (and variants of recipes) that produce files intended for the host portion of the standard SDK, or for things which are constructed like an SDK such as buildtools-tarball. These are built for SDKMACHINE which may or may not be the same architecture as the build host.

=== I have two recipes and one needs to access files provided by another - how can that work? ===

Instead of providing direct access from a recipe to another's build tree (which wouldn't be practical with OpenEmbedded since the build tree (or "workdir") is temporary), we create a "sysroot" where files that are intended to be shared between recipes get copied. The sysroot is managed by the build system and you should not copy files in there directly - instead, you install files under ${D} as normal during do_install and then the build system will copy a subset of those to the sysroot. There is a seperate sysroot for each machine being built for. In a recipe you can get the path of the sysroot and various standard directories under it using the STAGING_* variables.

Often, for commonly-used build systems such as autotools and cmake you don't need to worry about these details - those systems and the environment that OpenEmbedded sets up for them will ensure that files get installed and picked up in the correct locations. However if the software your recipe is building has custom build scripts / makefiles and it takes shortcuts that don't account for cross-compilation or the use of a sysroot, then you will need to make appropriate adjustments.

=== How do I enable package management in the final image? ===

Add <code>package-management</code> to <code>IMAGE_FEATURES</code> (or <code>EXTRA_IMAGE_FEATURES</code>). You should then be able to use dnf/rpm, opkg, or apt-get/dpkg from the running system depending on the packaging format you have selected through PACKAGE_CLASSES. For more information see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-runtime-package-management Using Runtime Package Management] in the Yocto Project Development manual.

=== What do ?=, ??=, := etc. do within a recipe/config file? ===

See the [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#basic-syntax Basic Syntax section of the BitBake manual] for details.

== Layers ==

See http://www.openembedded.org/Layers_FAQ

== Troubleshooting ==

=== I've created a recipe but it's not showing up in my image, what's going on? ===

Creating a recipe (or adding a layer to your configuration with a desired recipe in it) only makes it available to the build system, it doesn't change what goes into the image. For that, see [[#How do I control what's in the final image?|How do I control what's in the final image?]] above.

=== I set a variable but it doesn't seem to be having an effect, how do I fix this? ===

First, double-check that you haven't misspelled the variable name.

The main tool to help troubleshoot any variable-related issue is <code>bitbake -e</code> - this lists all the variables and the complete history of how each one has been set (use <code>bitbake -e recipename</code> if you're dealing with issues in a variable value within a recipe as opposed to the global level). Usually it's best to pipe this through <code>less</code> so you can easily see the history - within less you can press / to search for the variable name. Often you will be dealing with the behaviour of a variable within the context of a specific recipe, so specify that recipe on the <code>bitbake -e</code> command line to get the variables as set within the context of the recipe rather than the global context.

If you're setting a variable in a bbappend, double-check that the bbappend is actually being applied - see the next question.

=== I've created a bbappend for a recipe but what I'm setting there isn't having any effect, how do I fix this? ===

Here are some things to check:

# Check if the layer the bbappend is in is listed in <code>bitbake-layers show-layers</code>. If it isn't, you need to edit your bblayers.conf and ensure the path to the layer is included in the BBLAYERS value
# Check that the bbappend is being picked up by running <code>bitbake-layers show-appends</code> - if your bbappend file isn't listed, it could be named incorrectly (such that it doesn't match the recipe name) or it may be that the BBFILES value in the conf/layer.conf for the layer containing the bbappend file doesn't include an expression that will match the bbappend files.
# If there are multiple versions of the recipe you have bbappended, it could be that the actual recipe being built is a different version than the one you have bbappended. <code>bitbake-layers show-recipes <recipename></code> will list all the versions, with the first one listed being the one that will be built. If this is the case there are several different solutions to this - (a) Rename your bbappend to match the version being built, (b) use a % wildcard in your bbappend so it will apply to any version, (c) set <code>PREFERRED_VERSION_<recipename></code> in the configuration to select a the version you want to be built.
# Finally, as with any other issue with setting variables, use <code>bitbake -e recipename | less</code> and search with <code>/</code> to see the history of how the variable has been set - you may find that the value you're trying set is being overridden.

=== I'm getting warnings that a recipe is tainted - what does this mean? ===

Usually this happens because you have used I used bitbake's <code>-f</code> or <code>-C</code> option to force a task to re-execute. The assumption is that if you forced a task, it is possible that a rebuild from scratch would not include whatever changes you made that necessitated forcing (e.g. if you modified the source in the work directory for the recipe and then ran <code>bitbake -c compile -f</code>). Generally, forcing a task should be reserved for situations where the build system has failed to detect a change you made rather than for everyday usage - if you're finding yourself needing to do it regularly then either there's a bug, you're doing something wrong, or perhaps you're using <code>-f</code> or <code>-C</code> when it's not really needed. Running <code>bitbake -c clean</code> on the recipe will get rid of the taint flag.

There is one other situation where we apply a taint, and that is <code>bitbake -c menuconfig</code> on the kernel. In this case, the configuration has been saved into the work directory for the kernel, but that is temporary - any rebuild from scratch will use the default configuration, so it is a reminder that you need to take the configuration and apply it back to the metadata and then run <code>bitbake -c clean</code> on the kernel recipe.

=== I'm fetching from a git repository over ssh / http / https but it's not fetching properly, how do I fix this? ===

Bitbake expects the prefix of entries in SRC_URI to specify the fetcher to be used, not the actual protocol. Thus, instead of:

# This will NOT work
SRC_URI = "<nowiki>http://git.example.com/repository</nowiki>"

You should specify:

# This is better
SRC_URI = "<nowiki>git://git.example.com/repository;protocol=http</nowiki>"

The same applies for ssh and https.

=== I tried bitbake <some target package name> that I know exists and it told me that nothing PROVIDES this...? ===

There are two namespaces that bitbake concerns itself with - recipe names (a.k.a. build time targets) and package names (a.k.a. runtime targets). You can specify a build time target on the bitbake command line, but not a runtime target; you need to find the recipe that provides the package you are trying to build and build that instead (or simply add that package to your image and build the image). In current versions bitbake will at least tell you which recipes have matching or similar-sounding runtime provides (RPROVIDES) so that you'll usually get a hint on which recipe you need to build.

=== I've included a package in my image but files I expect to be there are missing, what's the issue? ===

Check the simple stuff: verify that the package is really in the image - look at the manifest file next to the image to ensure the package is listed. Also if you're flashing the image, double-check that you did indeed flash the right image and if there are multiple partitions / storage devices on your board or device that you're booting the one that you think you are.

Once you're sure of the above, it may be a matter of the package splitting - a lot of recipes split less commonly used components out to separate packages, so it's possible that the files you are looking for are in a different package. You can look at the recipe for this (look for PACKAGES and FILES statements) or assuming the recipe has been built, you can use <code>oe-pkgdata-util list-pkgs -p recipename</code> and <code>oe-pkgdata-util list-pkg-files</code> to inspect the packages provided by the recipe and the files they contain. Once you find the right package you can add it to your image.

=== I'm required to set LIC_FILES_CHKSUM but the software I'm building doesn't have a license statement, what do I do? ===

Ideally, all software should come with some kind of license statement so that the terms of distribution are clearly stated (especially if its source code is made publicly available); if not a text file describing the license then at the very least a line or two in the accompanying documentation, README file or source header comments. Assuming there is a license statement somewhere but not in a form you can point to with LIC_FILES_CHKSUM as part of the source tree, you can point LIC_FILES_CHKSUM to one of the generic license files in ${COMMON_LICENSE_DIR} (meta/files/common-licenses/), or alternatively you can include a file containing the license statement in a "files" subdirectory next to the recipe (or subdirectory named the same as the recipe - see how such files are handled in other recipes), point to it in SRC_URI using file://, then add it to LIC_FILES_CHKSUM. It is worth noting however that LIC_FILES_CHKSUM is intended to give you a warning if upstream changes its license terms when you do an upgrade of the recipe, and by pointing it to this common license file that is part of the metadata, that mechanism will not function. You may wish to consider encouraging the upstream provider of the software your recipe is building to follow best practices and include a proper license statement, so that you can point to it in a future version. At minimum if you do use such workarounds, you will need to take extra care when upgrading the recipe in future in case the upstream provider changes the license terms.

If there really is no license stated at all anywhere for the software (and this is unfortunately not uncommon on github, for example) then you should really contact upstream - if there's no license, then technically you really shouldn't be distributing it until that's clarified with the original author(s).

=== I am getting a package QA error / warning when building a recipe, how do I solve it? ===

There are some general and specific recommendations in the [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-errors-and-warnings QA Errors and Warnings] section of the Yocto Project Reference Manual.

=== I am getting "taskhash mismatch" errors, what does this mean and how do I fix it? ===

Bitbake parses the metadata (recipes, classes and configuration) repeatedly during its operation, and this error means that the result of parsing changed between one parse and the next. Two situations that can cause this:
# One of the parsed files changed in between e.g. you edited a recipe or performed a git operation (e.g. git checkout) during the build. '''Do not make changes to the metadata while a build is running.''' If you run the build again the error should not recur.
# Alternatively, there is something in the metadata that results in a variable expanding to a different value each time it is parsed. This is often something time-related e.g. a timestamp which is calculated every time an expression is expanded. The solution is to ensure the value is calculated once per build and then the expression expands to the same value for the duration of the build.

=== Building on a system with a GRSec kernel doesn't work well, is that supported? ===

No, grsec isn't really supported. The list of distros that are supported (tested) is in the Yocto mega manual for each release.
You can refer to the work-around given in this defect: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10885

=== Working around Firejail ===
For users of Parrot OS and other secured Linux distros, you will find that your bitbake fetch commands refuse to work, yet you can manually run wget and retrieve the packages with no problem. This is due to Poky creating links to all the tools it requires, in particular 'wget', 'ssh' and 'strings', using the links to these tools in the /usr/local/bin/ directory which all redirect to firejail. To fix the problem you can cd into <your Yocto install directory>/poky/build/tmp/hosttools directory and replace these links with ones redirecting to the actual executables under the /usr/bin directory.

== Dependencies ==

=== How do I find out why something is being built? ===

<code>bitbake -g <recipe></code> will produce some .dot files that allow you to see the dependency relationships - usually pn-depends.dot holds the answers although sometimes you may need to look at task-depends.dot if the dependency is only in the form of a task dependency. Note that these graphs are much too large for most graphviz visualisation tools to process, so you'll probably find it's easiest to view them with "less" or a text editor and search for the item you're looking for.

=== How do I find out why something is in my image? ===

Enable the buildhistory class and build the image again, and it will write out a depends.dot file containing the relationships between packages in the final image. If the package name isn't mentioned it is probably explicitly mentioned in IMAGE_INSTALL or being brought in via IMAGE_FEATURES.

See [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] in the Yocto Project Reference manual which covers how to enable buildhistory and the output it produces.

=== How do I view the .dot files produced by bitbake -g or buildhistory? ===

The size of some of these .dot graphs (particularly those produced by <code>bitbake -g</code>) is a little large for most viewers / processing tools, and unfortunately this isn't something that can be fixed - it's just the nature of the dependency relationships between targets and tasks within OpenEmbedded. Usually if you're just after answering a simple dependency question you can figure it out by viewing it with <code>less</code> and using its built-in search function (or alternatively your favourite text editor).

You can try [http://github.com/jrfonseca/xdot.py xdot] which will work well for some of the graphs, but the task graph produced by <code>bitbake -g</code> for something like an image in particular is likely to be too large to view within it.

=== Why are all of these -native items being built when my host distro has some of these available? ===

It's complicated. In some cases the software in question isn't widely packaged by common Linux distributions. In other cases we need to apply patches to the software, use a more up-to-date version than commonly packaged or build it with a particular configuration. In general it just helps us isolate ourselves from potential problems caused by differences in host Linux distributions. For the most part the time spent building the native tools that are definitely provided by the host distro are dwarfed by the time spent building things that definitely aren't provided, such as the C library for the target and the cross-compiling toolchain.

=== I disabled runtime package management and yet it still seems to be building rpm/opkg, why? ===

The build system always uses a package manager on the host to assemble images, because it is usually the best tool for this job. This is completely independent of whether the package manager is available in the target image - "package-management" being in IMAGE_FEATURES (possibly indirectly via EXTRA_IMAGE_FEATURES) controls whether the package manager is used at runtime i.e. whether it (and its associated package database) will be present in the target image.

=== Why is opkg-native / opkg-utils being built when I don't have ipk packaging enabled? ===

opkg-utils provides update-alternatives which is the default tool used to manage the alternatives system (for selecting between multiple providers of the same file, e.g. busybox and bash both provide /bin/sh).

=== Why is rpm-native being built when I don't have rpm packaging enabled? ===

rpm-native is needed for two things in the generic packaging code implemented in the package class:

# Debug symbol splitting - rpm-native provides the debugedit tool which this code uses
# Per-file dependencies - although this was originally just feeding into rpm when rpm was being used, it also now gets verified by QA checks regardless of which packaging backend is in use.

=== I see a recipe built, but building an image containing the corresponding package fails at do_rootfs because it can't find the package. How does this happen? ===

(For ipk, the error is "Couldn't find anything to satisfy '<package>'"; for rpm it is "<package> not found in the base feeds (<architecture list>)".)

Usually this is because the recipe claimed to provide the specified package (via PACKAGES or PACKAGES_DYNAMIC) but it wasn't actually produced, possibly because it ended up empty (since by default empty packages aren't produced), but the image or some other package still has a dependency that pulls in the specified package. If this is a recipe you are writing yourself the probable cause is your recipe isn't installing any files and thus the main package for the recipe is empty. Fix do_install (or what do_install is already running, e.g. make install) such that files are installed into the correct location such that they can then subsequently be packaged, and then all should be well.

In other situations the reference to the package in question is spurious and either it should be removed entirely or there's another package that should be used instead. For example, the avahi and dhcp recipes both have an empty main package since the client and server are split out into their own packages, and those are the ones you should be using instead (avahi-daemon, avahi-utils, dhcp-server, dhcp-client - there are other packages as well, please see [[#How_do_I_find_out_what_packages_are_produced_by_a_recipe.3F|How do I find out what packages are produced by a recipe?]].) You could argue that these recipes shouldn't claim to provide the main package, or they should have a main package that depends on all the other packages (as some other recipes do).

=== X11 and various other items are being built but I'm only building core-image-minimal - why? ===

This is where it helps to understand the difference between build-time dependencies and runtime dependencies - often, a recipe will require things at build time (for example tools that help the build process, or to satisfy optional dependencies) that it doesn't necessarily need at runtime. The default configuration includes "<code>x11</code>" in <code>DISTRO_FEATURES</code>, and thus anything that can optionally support X11 will have its X11 support enabled; however when it comes to actually producing the image there won't be any X11 packages included as long as there are no hard dependencies and there aren't any X11 packages explicitly requested.

If you never intend to use X11, you can set your own <code>DISTRO_FEATURES</code> value that excludes <code>x11</code> (note lower case, as with all feature names) and then X11 support will be disabled at build time and these items won't even be built.

=== How do I avoid the kernel itself being pulled into my image when installing kernel modules? ===

By default, the kernel class sets a dependency on the kernel-base package (which kernel modules always depend on) onto kernel-image, which contains the actual kernel binary. If you don't want this, set the following either in your kernel recipe or at the configuration level:

RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""

Note: for older releases (pre-2.5) do this instead:

RDEPENDS_kernel-base = ""

== Misc ==

=== How do I remove a value from a list variable? ===

For variables that are expected to contain a space-separated list of items, BitBake supports a _remove operator to remove items from it. See [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#removing-override-style-syntax Removal (override style syntax)] in the BitBake user manual.

'''NOTE:''' the _remove operation is final - you cannot "undo" it with other operations elsewhere, thus you should really only make use of it in your distro / local configuration and not in layers that you expect others to re-use for different purposes (and therefore they may need to undo your changes). An alternative way to effectively remove an item is to set the list outright to include all the items minus the one you want to remove.

=== How do I change how my recipe is built depending on what image I'm building? ===

The short answer is you cannot - the reason is that OpenEmbedded builds packages based on the overall configuration, and then the image only selects which of these packages should go into the final image. However, there are some solutions that do allow you to achieve the desired result:

# Have separate packages for the two different versions. This could take the form of different recipes or you could do it within the same recipe. The two packages do have to have different names however; this may create problems if you have other packages that depend on the package.
# Use a postprocessing function within the image(s) - within the image recipe, define a shell or python function that makes the desired changes to the files in the image and add a call to it to ROOTFS_POSTPROCESS_COMMAND within the image recipe. Note that this may not be appropriate if you have runtime package management enabled since the postprocessing will only happen at image creation time and not if the package is installed later on at runtime - you may need to use a postinstall script instead in this case.
# Use a postinstall script (pkg_postinst_<package> function) within the recipe. In order to work, the postinstall script will need to be able to determine what to do when it's run - this may not be practical depending on what you're trying to achieve.

=== Can I use a toolchain built by OE as the external toolchain? ===

In general, this is not recommended and not something that is tested or directly supported out of the box. If you are wanting to do this solely as a means of speeding up the build, it is strongly suggested that you use shared state instead.

There is a [http://layers.openembedded.org/layerindex/branch/master/layer/meta-sourcery/ meta-sourcery layer] available to enable support for the CodeSourcery toolchain, you may be able to use this as a template for bringing in an external toolchain however there are no guarantees.

=== When I run bitbake -c devshell it looks like it's running as root! How is that possible? ===

It's not running as the actual root user, it's just pretending for the benefit of programs that run under it (including your shell) that it is, via pseudo. This is important, because you normally want any owner/group/permission values that you set on files to be reflected in files that the recipe installs and packages and thus reflected in the final image - without this mechanism the actual build would have to run as root which would be very risky. There are no actual elevated privileges through this mechanism however, so you need not be worried.

=== Why does OE use pseudo? Why not use fakeroot / fakechroot instead? ===

Splitting this up into two questions - we use pseudo (not to be confused with sudo!) because we want to be able to create images containing files have the correct permissions and ownership, e.g. files owned by root, without the user running the build system having to have that privilege. By using LD_PRELOAD to intercept function calls, pseudo creates an environment for programs running underneath it where it appears as if the running user has those privileges (and the results of any operations persist within the pseudo environment, i.e. you can write a file as root and it will appear to be owned by root while still running under pseudo). This allows us to run builds entirely as a normal user without needing extra privileges. Without pseudo we would require running the build system under sudo or as root - which would be ill-advised for things such as "make install" in case it happened to be broken and tried to write to / instead of somewhere under the work directory for the recipe; a broken recipe could easily end up destroying your system in that case.

To answer the second part, why we use pseudo instead of fakeroot / fakechroot, see [https://github.com/wrpseudo/pseudo/wiki/WhyNotFakeroot WhyNotFakeroot on the pseudo wiki].

=== How do I find out what packages are produced by a recipe? ===

The Toaster web UI provides easy ways to query this.

In the 1.8 (fido) release and newer you can use the following command, assuming the recipe has already been built:

oe-pkgdata-util list-pkgs -p recipename

Alternatively you can look in the "packages-split" subdirectory under the work directory for the recipe - each package produced by the recipe will have a subdirectory under that. If you're not sure how to find the work directory you can run the following command:

bitbake -e recipename | grep ^WORKDIR=

Before a recipe gets built it is a bit trickier, since the system often doesn't know exactly which packages will be produced until do_package time; this is particularly true for recipes that package plugins or modules (e.g. kernel modules). You can get a reasonable idea though by looking at the value of PACKAGES (and PACKAGES_DYNAMIC for recipes that produce plugins).

=== How do I find out which package contains a particular file (or python module)? ===

oe-pkgdata-util has a find-path subcommand that will tell you exactly this. For example:

$ oe-pkgdata-util find-path /etc/network/interfaces
init-ifupdown: /etc/network/interfaces

Wildcards are allowed anywhere in the path (but you should enclose such expressions in quotes to avoid the shell itself attempting to expand the wildcard):

$ oe-pkgdata-util find-path "*/fstrim"
util-linux-bash-completion: /usr/share/bash-completion/completions/fstrim
util-linux-ptest: /usr/lib/util-linux/ptest/fstrim
util-linux-dbg: /sbin/.debug/fstrim
util-linux-fstrim: /sbin/fstrim

As a specific example of where this can be useful, our Python packaging is a bit more granular than most typical distributions, allowing you to tune the contents of your image to just what you need. However, that does mean you may have trouble figuring out which package provides a particular module. oe-pkgdata-util find-path can also be used for this. For example, to find the package containing the "shutil" module, run this:

$ oe-pkgdata-util find-path "*/shutil.*"
python3-shell: /usr/lib/python3.5/shutil.py
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-2.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-1.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.pyc

Thus the package you are looking for is python3-shell. (Note that you could use */shutil.py, but if the module you are looking for is written in C as some of them are, that won't match it.)

=== I have a local source tree I want to build instead of the upstream source a recipe normally fetches, how do I do that? ===

If it's for development purposes i.e. you have your own local source tree you want to work on and have built, then run:

devtool modify -n <recipename> path/to/sourcetree/

Once you are done you can use <code>devtool finish</code> or <code>devtool reset</code> (depending on the situation) to return to building the source specified in the recipe.

Alternatively if it's more permanent, use the <code>externalsrc</code> class - you can inherit this in the original recipe or a bbappend:

inherit externalsrc
EXTERNALSRC = "/path/to/sources"

If you're going to use it across a number of recipes you can inherit it globally at the configuration level (perhaps via an inc file that you include/require there):

INHERIT += "externalsrc"
EXTERNALSRC_pn-<recipename> = "/path/to/sources"

=== How do I specify the default shell? (e.g. bash instead of busybox) ===

It depends what you mean. As far as which provides /bin/sh, this is controlled through the alternatives system, and by default bash has a higher priority than busybox, so simply installing bash into your image will automatically have /bin/sh link to bash rather than busybox.

If you mean you want a user's login shell to be a specific shell, you'll need to modify /etc/passwd. One fairly easy way to achieve this is to use the extrausers class in your image recipe:

inherit extrausers
EXTRA_USERS_PARAMS = "usermod -s /bin/bash <username>; "

=== How do I get "full" versions of typical shell commands? ===

Most of the shell commands in our images are provided by busybox by default, and are very much simplified compared to what you would have on a typical Linux system in order to save space. If you need the full versions, most of them are built and packaged by the coreutils recipe (for disk and other typical utilities) and procps (for ps, etc). You may also want to install bash for more typical shell built-in commands. There is also a core-image-full-cmdline image if you want a base image that is already set up to provide a more typical Linux command-line experience. (Note: these will of course use up more disk space and memory.)

=== How do I allow a variable's value through from the external environment? ===

Add the variable's name to the BB_ENV_EXTRAWHITE ''in the external environment'' before running bitbake. Note that the oe-init-build-env script sets a default for this which you will want to preserve, so add to the default value rather than overwriting it.

Alternatively if you just want to get the external value of a variable from python code within the metadata, you can use the BB_ORIGENV variable which itself contains a datastore of the original environment. For example to get the value of the DISPLAY variable from the environment within a python function you would do this:

display = d.getVar("BB_ORIGENV", False).getVar("DISPLAY")

Note that you must specify "false" for the expand parameter when getting the BB_ORIGENV variable, because it's not a string and therefore cannot be expanded in the normal manner.

=== Why is bitbake showing "AUTOINC" in the version for some recipes? ===

Recipes where you see AUTOINC within the version in the console output during a build will be those that set <code>PV</code> to include <code>"${SRCPV}"</code> to get the SCM revision (e.g. the git hash) in the package version. In order to have the version increment properly, there needs to be a number in front of the revision which automatically increments each time the revision changes (assuming you have a PR server enabled), which is where AUTOINC comes in. During the build, AUTOINC is a stand-in for this auto-incrementing number, and later during <code>do_package</code> it gets replaced with the real number so that the packages produced at the end have the full version number.

=== Why are .so files in the -dev package instead of the main package for a recipe? ===

In standard Unix library packaging, non-versioned .so symlinks (e.g. /usr/lib/libgd.so) are intended for development purposes only. At runtime, binaries should be linked to the major-versioned .so file/symlink e.g. /usr/lib/libgd.so.3. This (theoretically) allows multiple major versions of the same library as well as binaries that depend upon each of them to coexist on the same system. If the library is versioned but you have a binary that links to the unversioned .so file, it has almost certainly been linked incorrectly.

Non-symlink .so files on the other hand are sometimes produced and are entirely legal - however these will be picked up in the -dev package in OpenEmbedded simply by virtue of their name, which is almost always not what you want. In this case you can do one of two things:

# Fix the build of the library so it gets versioned. This may not always be appropriate, especially not for things like plugins.
# Set FILES_${PN}-dev within the recipe so that it does not include ${FILES_SOLIBSDEV}. If the software the recipe is building also produces symlink .so files you'll need to set FILES_${PN}-dev such that those do still get packaged in the -dev package though, or you'll get a package QA warning.

=== Can I disable shared state? ===

You cannot, no. Shared state (sstate) is an intrinsic part of staging files into the sysroot. It is possible to construct a recipe that bypasses sstate for some tasks (the kernel does this), however this is quite difficult and if not done properly will lead to many other problems.

Almost always when you are having a problem with shared state the issue is either (a) you're adding/changing files in the sysroot directly (i.e. outside sstate control), or (b) what is being placed into the sysroot isn't relocatable. The solution for (a) is do not do that - files should always be installed under <code>${D}</code> within <code>do_install</code> and then a subset of those are staged into the sysroot automatically. For (b) you need to fix or adapt the hardcoded path(s) - if the program reads (or can be made to read) each path from an environment variable, then you can use the <code>create_wrapper</code> utility function to create a wrapper script that will set the path appropriately. Run <code>git grep create_wrapper</code> in the <code>meta</code> subdirectory to see examples.

=== Files I installed into /opt or some other path never make it into the sysroot but I need them - how do I fix this? ===

OpenEmbedded only stages a subset of files that are installed into <code>${D}</code> by <code>do_install</code> so that the sysroot doesn't fill up with unneeded files. You have two choices in this situation:
# install the files into a more standard location which is part of the subset, or
# adjust the subset to include the paths you are installing to.
Usually option 1 is recommended. If you really do need to adjust the subset, you can append the path (more specifically, the part below <code>${D}</code>) to <code>SYSROOT_DIRS</code> within your recipe. For example:

SYSROOT_DIRS += "/opt"

=== I have some software which needs to build a binary that it then runs as part of its own build process, how do I make this work? ===

Whilst it is possible to do this within a single recipe building for the target, it is tricky to do so because in that context everything is set up for cross-compiling for the target, and you would have to undo all of that to build host tools. The standard and much easier way of handling this is to create a native variant of the recipe using BBCLASSEXTEND and have your host tools built within that, and then have the target variant depend on the native variant. For example, assume your recipe were called xyz (xyz_1.1.bb), then you would include something like this in the recipe:

DEPENDS_append_class-target = " xyz-native"

...

BBCLASSEXTEND += "native"

The host tools will then be built and installed into the sysroot in the native variant ready for when the target variant starts building. If the software you are building didn't intend for those tools to be installed outside of the build tree then you may need to patch the build process (e.g. the makefile) in order to install them and possibly also for the target side to find them in the sysroot. Additionally, for performance since you only need the tools in the native variant, you may also choose to disable building everything except those tools there - e.g. by using _native overrides for variables such as EXTRA_OECONF or functions such as do_configure.

=== How do I fetch from two git repositories in the same recipe? ===

By default, sources fetched from git within a recipe are unpacked into ${WORKDIR}/git, however that only works for a single repository. If you want to fetch from more than one, you need to change the path each repository is unpacked to. This is easy to do, just add <code>;destsuffix=<subdir></code> to the end of each URL in SRC_URI (replacing <code><subdir></code> with the name of the subdirectory). You may then need to change S to match whichever of these you want to be considered the root of the source tree - or alternatively you can specify destsuffix such that repositories beyond the first go into a subdirectory under the default "git" subdirectory. For example, from the gst-libav recipe:

...
SRC_URI = " \
git://anongit.freedesktop.org/gstreamer/gst-libav;branch=1.8;name=base \
git://anongit.freedesktop.org/gstreamer/common;destsuffix=git/common;name=common \
...
"
...
S = "${WORKDIR}/git"
...

(Here we're using the default of "git" for the first repository, so we don't need to specify <code>destsuffix</code> for the first URL.)

=== I'm building a native recipe and I notice that the install path has the full path to the root directory repeated - why? ===

It does look a little odd, but the reason for doing this is that native targets are meant to run on the system they're built on and run in the location they're installed to. This means they install to a destination of "/" and PREFIX is inside the native sysroot directory. We install them to a DESTDIR to allow us to manipulate them before they then get moved to a final DESTDIR of "/".

Most Makefiles handle this correctly by doing:

DESTDIR ?= ""
prefix ?= "/usr"
bindir ?= "$(prefix)/bin"

and then, importantly, install in the form:

install -d $(DESTDIR)$(bindir)

so both prefix and DESTDIR are used. Whilst this is a convention, its a widely adopted and followed one. You can call into a custom makefile and set the variables manually if the makefile doesn't follow the convention.

=== How do I generate static libraries? ===

Its possible you have conf/distro/include/no-static-libs.inc included in your build - poky does this by default. The include list at the top of the bitbake -e output will tell you for certain.

If so, you can remove that or set:

DISABLE_STATIC = ""

as it would currently be set to this if that include file is included:

DISABLE_STATIC = " --disable-static"

Poky disables building static libraries by default as for the most part they're a waste of space/time.

=== Can I conditionally inherit a class in a recipe? ===

Yes, you can. What makes this possible is that the <code>inherit</code> keyword will not complain if what comes after it expands to being empty, so you can use in-line python to do something like this:

<pre><nowiki>
inherit ${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}
</nowiki></pre>

The above example will inherit the <code>perlnative</code> class if "scripting" is in the value of the <code>PACKAGECONFIG</code> variable, otherwise it will do nothing.

You could of course put this into a variable if you prefer:

<pre><nowiki>
SOMEVAR = "${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}"
inherit ${SOMEVAR}
</nowiki></pre>

=== How do I collect the source revisions fetched by each recipe? ===

If you have recipes where <code>SRCREV = "${AUTOREV}"</code> then you won't necessarily know exactly which revisions were built after the fact - it will be whatever was current at the time. You also might alternatively just want to get all of the revisions. Either way, to do this, enable buildhistory by setting the following in your local.conf:

<pre><nowiki>
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
</nowiki></pre>

(The last line is not required with version 2.5 and onwards as it is the default, but will do no harm.)

Once you have enabled buildhistory, you then need to build your image again so that buildhistory has a chance to record history data for it. Following that you can run <code>buildhistory-collect-srcrevs</code> (with <code>-a</code> if you want to see all revisions, not just the ones where AUTOREV was used) and it will output the revisions in a form you can use in a .inc file that you can <code>require</code> from your configuration if you want to fix the build to those revisions.

For more information see the [https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] section of the Yocto Project Development manual, which covers the buildhistory class in detail.

=== How do I do an offline build with recipes that have <code>SRCREV = "${AUTOREV}"</code> set? ===

If you set <code>BB_NO_NETWORK = "1"</code> and you have recipes that have <code>SRCREV = "${AUTOREV}"</code>, you will get an error because the build system will try to check the latest revision on startup and be immediately blocked by <code>BB_NO_NETWORK</code>. There are two ways to handle this:

A) See the previous question "How do I collect the source revisions fetched by each recipe?" and use the output generated by <code>buildhistory-collect-srcrevs</code> as a .inc file in your configuration in order to fix the revisions at the ones which were most recently built.

or

B) Set <code>BB_SRCREV_POLICY = "cache"</code> in your configuration. This will use the last cached revision. (The disadvantage of this method is that it is a little more difficult to preserve or share with others the fixed revisions.)

Note that in either case if you later want to build the latest version again, you will of course need to undo the configuration changes.

=== Is it possible to append a bbclass file (like bbappends do for recipes)? ===

No, see the next question for details.

=== How do I override a bbclass file? ===

This is tricky - bbclass files are found via BBPATH, which is added to by each layer.conf either by prepending or appending. Assuming you are putting your bbclass in a custom layer, you will probably want to have your layer's layer.conf prepend to BBPATH, but then you will also need to make sure that your layer does not appear before any other layer that is also prepending and overriding the same class.

Another alternative is to have an additional class which makes the appropriate changes to the environment, and then you will need to inherit that class after (and in the same manner as) the original class. This is slightly cleaner but can be annoying to enable particularly if the class is inherited by a number of recipes, and won't work if you want to alter the behaviour of a class inherited by recipes you don't control. (If you want a class to be inherited for all images (i.e. all recipes inheriting the <code>image</code> class) you can inject additional classes by setting IMAGE_CLASSES; similarly for the kernel there is KERNEL_CLASSES).

Ultimately, overriding bbclass files is not good practice long term - you are opening yourself up to maintenance issues when the original class changes, and the override is fragile as hinted above. The best solution is to try to get whatever changes you need into the original class; this does of course require additional work and time though.

=== There's a bbappend in a layer I'm using that defines a <code>do_something_append()</code> and I want to append to that function also, how do I do this? ===

Simply create a bbappend in your layer and define your own <code>do_something_append()</code>, and your commands will be executed ''as well as'' those of the other bbappend.

You might assume that defining <code>do_something_append()</code> will overwrite any previously defined <code>do_something_append()</code>, as would be the case with <code>do_something()</code> in the same situation, but that is not the case - the key is that <code>_append</code> (and <code>_prepend</code>, <code>_remove</code>, etc.) are ''operators'' and they will be applied in sequence, where that sequence is the order in which they are parsed (which for bbappends will be in ascending layer priority order).

Technical FAQ

2020-07-01T01:11:19Z

PaulEggleton: /* How do I allow a variable's value through from the external environment? */

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
| '''NOTE:''' This is currently a draft. Not sure where this should end up but I've been gathering these based on my interactions with people on IRC and email over the years. - [[User:PaulEggleton|PaulEggleton]] ([[User talk:PaulEggleton|talk]]) 21:13, 27 June 2016 (PDT)
|}

== Basics ==

=== How do I figure out which version/codename/bitbake version matches up with which? ===

There is a table in the [http://wiki.yoctoproject.org/wiki/Releases Releases page] on the Yocto Project wiki.

=== How do I control what's in the final image? ===

Each image is defined by its own recipe, and that recipe specifies a list of packages that the image should contain. See [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Customising Images] within the Yocto Project development manual for further details.

Note: if you're doing anything more than basic experimentation / testing then you almost certainly should create your own image recipe rather than using one of the example images e.g. core-image-minimal - though you can certainly start by copying one of the example images. This way you have easier control over what goes into the image.

=== Where do I find build logs? ===

For the overall build, the output of bitbake gets logged to tmp/log/cooker/<machine>.

For each individual recipe, there is a "temp" directory under the work directory for the recipe that contains log.<taskname> and run.<taskname> files - the logs and the runfiles respectively. Within the build system this directory is pointed to by the T variable, so if you need to you can find it by using <code>bitbake -e</code>:

bitbake -e <recipename> | grep ^T=

=== How do I add a patch to a recipe? ===

There are two concerns - how the recipe can fetch the patch and how it can be applied. For fetching, patch files are usually placed in a subdirectory next to the recipe; by default this directory should be named "files" or the the recipe name without any class prefix or suffix (for example for both "xyz" and "xyz-native" the subdirectory would be "xyz"). A pointer to it then needs to be added to <code>SRC_URI</code> within the recipe, which usually takes the form <code>file://<patchname>.patch</code> - i.e. just the filename, no path. If more than one subdirectory needs to be stripped off the paths in the patch (i.e. you need more than the equivalent of the -p1 option to the patch command) then you can add <code>;striplevel=<number></code> to the end of the patch entry in SRC_URI (without any spaces).

As with any modification, if the patch you are applying is a customisation that you do not intend to send to be incorporated in the layer you are modifying, then instead of adding the patch to the recipe directly then you should consider applying it in a bbappend within your own custom layer. This makes things easier if you later want to update the layer in question and the recipe has been modified upstream - you avoid effectively forking the layer.

The <code>devtool</code> utility can help you modify the sources for a recipe and create a patch - basically <code>devtool modify</code>, edit the sources, commit the changes with <code>git commit</code>, then <code>devtool finish</code> (or <code>devtool update-recipe</code> in versions older than 2.2). Since <code>devtool modify</code> gives you a git tree to work with, you can of course use something like <code>git am</code> to apply existing patches this way. For more details see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#devtool-use-devtool-modify-to-enable-work-on-code-associated-with-an-existing-recipe Use devtool modify to Enable Work on Code Associated with an Existing Recipe] within the Yocto Project Development manual.

=== What does "native" mean? ===

The "native" suffix identifies recipes (and variants of recipes) that produce files intended for the build host, as opposed to the target machine. This is usually for tools that are needed during the build process (such as automake).

=== What does "nativesdk" mean? ===

The "nativesdk" prefix identifies recipes (and variants of recipes) that produce files intended for the host portion of the standard SDK, or for things which are constructed like an SDK such as buildtools-tarball. These are built for SDKMACHINE which may or may not be the same architecture as the build host.

=== I have two recipes and one needs to access files provided by another - how can that work? ===

Instead of providing direct access from a recipe to another's build tree (which wouldn't be practical with OpenEmbedded since the build tree (or "workdir") is temporary), we create a "sysroot" where files that are intended to be shared between recipes get copied. The sysroot is managed by the build system and you should not copy files in there directly - instead, you install files under ${D} as normal during do_install and then the build system will copy a subset of those to the sysroot. There is a seperate sysroot for each machine being built for. In a recipe you can get the path of the sysroot and various standard directories under it using the STAGING_* variables.

Often, for commonly-used build systems such as autotools and cmake you don't need to worry about these details - those systems and the environment that OpenEmbedded sets up for them will ensure that files get installed and picked up in the correct locations. However if the software your recipe is building has custom build scripts / makefiles and it takes shortcuts that don't account for cross-compilation or the use of a sysroot, then you will need to make appropriate adjustments.

=== How do I enable package management in the final image? ===

Add <code>package-management</code> to <code>IMAGE_FEATURES</code> (or <code>EXTRA_IMAGE_FEATURES</code>). You should then be able to use dnf/rpm, opkg, or apt-get/dpkg from the running system depending on the packaging format you have selected through PACKAGE_CLASSES. For more information see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-runtime-package-management Using Runtime Package Management] in the Yocto Project Development manual.

=== What do ?=, ??=, := etc. do within a recipe/config file? ===

See the [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#basic-syntax Basic Syntax section of the BitBake manual] for details.

== Layers ==

See http://www.openembedded.org/Layers_FAQ

== Troubleshooting ==

=== I've created a recipe but it's not showing up in my image, what's going on? ===

Creating a recipe (or adding a layer to your configuration with a desired recipe in it) only makes it available to the build system, it doesn't change what goes into the image. For that, see [[#How do I control what's in the final image?|How do I control what's in the final image?]] above.

=== I set a variable but it doesn't seem to be having an effect, how do I fix this? ===

First, double-check that you haven't misspelled the variable name.

The main tool to help troubleshoot any variable-related issue is <code>bitbake -e</code> - this lists all the variables and the complete history of how each one has been set (use <code>bitbake -e recipename</code> if you're dealing with issues in a variable value within a recipe as opposed to the global level). Usually it's best to pipe this through <code>less</code> so you can easily see the history - within less you can press / to search for the variable name. Often you will be dealing with the behaviour of a variable within the context of a specific recipe, so specify that recipe on the <code>bitbake -e</code> command line to get the variables as set within the context of the recipe rather than the global context.

If you're setting a variable in a bbappend, double-check that the bbappend is actually being applied - see the next question.

=== I've created a bbappend for a recipe but what I'm setting there isn't having any effect, how do I fix this? ===

Here are some things to check:

# Check if the layer the bbappend is in is listed in <code>bitbake-layers show-layers</code>. If it isn't, you need to edit your bblayers.conf and ensure the path to the layer is included in the BBLAYERS value
# Check that the bbappend is being picked up by running <code>bitbake-layers show-appends</code> - if your bbappend file isn't listed, it could be named incorrectly (such that it doesn't match the recipe name) or it may be that the BBFILES value in the conf/layer.conf for the layer containing the bbappend file doesn't include an expression that will match the bbappend files.
# If there are multiple versions of the recipe you have bbappended, it could be that the actual recipe being built is a different version than the one you have bbappended. <code>bitbake-layers show-recipes <recipename></code> will list all the versions, with the first one listed being the one that will be built. If this is the case there are several different solutions to this - (a) Rename your bbappend to match the version being built, (b) use a % wildcard in your bbappend so it will apply to any version, (c) set <code>PREFERRED_VERSION_<recipename></code> in the configuration to select a the version you want to be built.
# Finally, as with any other issue with setting variables, use <code>bitbake -e recipename | less</code> and search with <code>/</code> to see the history of how the variable has been set - you may find that the value you're trying set is being overridden.

=== I'm getting warnings that a recipe is tainted - what does this mean? ===

Usually this happens because you have used I used bitbake's <code>-f</code> or <code>-C</code> option to force a task to re-execute. The assumption is that if you forced a task, it is possible that a rebuild from scratch would not include whatever changes you made that necessitated forcing (e.g. if you modified the source in the work directory for the recipe and then ran <code>bitbake -c compile -f</code>). Generally, forcing a task should be reserved for situations where the build system has failed to detect a change you made rather than for everyday usage - if you're finding yourself needing to do it regularly then either there's a bug, you're doing something wrong, or perhaps you're using <code>-f</code> or <code>-C</code> when it's not really needed. Running <code>bitbake -c clean</code> on the recipe will get rid of the taint flag.

There is one other situation where we apply a taint, and that is <code>bitbake -c menuconfig</code> on the kernel. In this case, the configuration has been saved into the work directory for the kernel, but that is temporary - any rebuild from scratch will use the default configuration, so it is a reminder that you need to take the configuration and apply it back to the metadata and then run <code>bitbake -c clean</code> on the kernel recipe.

=== I'm fetching from a git repository over ssh / http / https but it's not fetching properly, how do I fix this? ===

Bitbake expects the prefix of entries in SRC_URI to specify the fetcher to be used, not the actual protocol. Thus, instead of:

# This will NOT work
SRC_URI = "<nowiki>http://git.example.com/repository</nowiki>"

You should specify:

# This is better
SRC_URI = "<nowiki>git://git.example.com/repository;protocol=http</nowiki>"

The same applies for ssh and https.

=== I tried bitbake <some target package name> that I know exists and it told me that nothing PROVIDES this...? ===

There are two namespaces that bitbake concerns itself with - recipe names (a.k.a. build time targets) and package names (a.k.a. runtime targets). You can specify a build time target on the bitbake command line, but not a runtime target; you need to find the recipe that provides the package you are trying to build and build that instead (or simply add that package to your image and build the image). In current versions bitbake will at least tell you which recipes have matching or similar-sounding runtime provides (RPROVIDES) so that you'll usually get a hint on which recipe you need to build.

=== I've included a package in my image but files I expect to be there are missing, what's the issue? ===

Check the simple stuff: verify that the package is really in the image - look at the manifest file next to the image to ensure the package is listed. Also if you're flashing the image, double-check that you did indeed flash the right image and if there are multiple partitions / storage devices on your board or device that you're booting the one that you think you are.

Once you're sure of the above, it may be a matter of the package splitting - a lot of recipes split less commonly used components out to separate packages, so it's possible that the files you are looking for are in a different package. You can look at the recipe for this (look for PACKAGES and FILES statements) or assuming the recipe has been built, you can use <code>oe-pkgdata-util list-pkgs -p recipename</code> and <code>oe-pkgdata-util list-pkg-files</code> to inspect the packages provided by the recipe and the files they contain. Once you find the right package you can add it to your image.

=== I'm required to set LIC_FILES_CHKSUM but the software I'm building doesn't have a license statement, what do I do? ===

Ideally, all software should come with some kind of license statement so that the terms of distribution are clearly stated (especially if its source code is made publicly available); if not a text file describing the license then at the very least a line or two in the accompanying documentation, README file or source header comments. Assuming there is a license statement somewhere but not in a form you can point to with LIC_FILES_CHKSUM as part of the source tree, you can point LIC_FILES_CHKSUM to one of the generic license files in ${COMMON_LICENSE_DIR} (meta/files/common-licenses/), or alternatively you can include a file containing the license statement in a "files" subdirectory next to the recipe (or subdirectory named the same as the recipe - see how such files are handled in other recipes), point to it in SRC_URI using file://, then add it to LIC_FILES_CHKSUM. It is worth noting however that LIC_FILES_CHKSUM is intended to give you a warning if upstream changes its license terms when you do an upgrade of the recipe, and by pointing it to this common license file that is part of the metadata, that mechanism will not function. You may wish to consider encouraging the upstream provider of the software your recipe is building to follow best practices and include a proper license statement, so that you can point to it in a future version. At minimum if you do use such workarounds, you will need to take extra care when upgrading the recipe in future in case the upstream provider changes the license terms.

If there really is no license stated at all anywhere for the software (and this is unfortunately not uncommon on github, for example) then you should really contact upstream - if there's no license, then technically you really shouldn't be distributing it until that's clarified with the original author(s).

=== I am getting a package QA error / warning when building a recipe, how do I solve it? ===

There are some general and specific recommendations in the [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-errors-and-warnings QA Errors and Warnings] section of the Yocto Project Reference Manual.

=== I am getting "taskhash mismatch" errors, what does this mean and how do I fix it? ===

Bitbake parses the metadata (recipes, classes and configuration) repeatedly during its operation, and this error means that the result of parsing changed between one parse and the next. Two situations that can cause this:
# One of the parsed files changed in between e.g. you edited a recipe or performed a git operation (e.g. git checkout) during the build. '''Do not make changes to the metadata while a build is running.''' If you run the build again the error should not recur.
# Alternatively, there is something in the metadata that results in a variable expanding to a different value each time it is parsed. This is often something time-related e.g. a timestamp which is calculated every time an expression is expanded. The solution is to ensure the value is calculated once per build and then the expression expands to the same value for the duration of the build.

=== Building on a system with a GRSec kernel doesn't work well, is that supported? ===

No, grsec isn't really supported. The list of distros that are supported (tested) is in the Yocto mega manual for each release.
You can refer to the work-around given in this defect: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10885

=== Working around Firejail ===
For users of Parrot OS and other secured Linux distros, you will find that your bitbake fetch commands refuse to work, yet you can manually run wget and retrieve the packages with no problem. This is due to Poky creating links to all the tools it requires, in particular 'wget', 'ssh' and 'strings', using the links to these tools in the /usr/local/bin/ directory which all redirect to firejail. To fix the problem you can cd into <your Yocto install directory>/poky/build/tmp/hosttools directory and replace these links with ones redirecting to the actual executables under the /usr/bin directory.

== Dependencies ==

=== How do I find out why something is being built? ===

<code>bitbake -g <recipe></code> will produce some .dot files that allow you to see the dependency relationships - usually pn-depends.dot holds the answers although sometimes you may need to look at task-depends.dot if the dependency is only in the form of a task dependency. Note that these graphs are much too large for most graphviz visualisation tools to process, so you'll probably find it's easiest to view them with "less" or a text editor and search for the item you're looking for.

=== How do I find out why something is in my image? ===

Enable the buildhistory class and build the image again, and it will write out a depends.dot file containing the relationships between packages in the final image. If the package name isn't mentioned it is probably explicitly mentioned in IMAGE_INSTALL or being brought in via IMAGE_FEATURES.

See [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] in the Yocto Project Reference manual which covers how to enable buildhistory and the output it produces.

=== How do I view the .dot files produced by bitbake -g or buildhistory? ===

The size of some of these .dot graphs (particularly those produced by <code>bitbake -g</code>) is a little large for most viewers / processing tools, and unfortunately this isn't something that can be fixed - it's just the nature of the dependency relationships between targets and tasks within OpenEmbedded. Usually if you're just after answering a simple dependency question you can figure it out by viewing it with <code>less</code> and using its built-in search function (or alternatively your favourite text editor).

You can try [http://github.com/jrfonseca/xdot.py xdot] which will work well for some of the graphs, but the task graph produced by <code>bitbake -g</code> for something like an image in particular is likely to be too large to view within it.

=== Why are all of these -native items being built when my host distro has some of these available? ===

It's complicated. In some cases the software in question isn't widely packaged by common Linux distributions. In other cases we need to apply patches to the software, use a more up-to-date version than commonly packaged or build it with a particular configuration. In general it just helps us isolate ourselves from potential problems caused by differences in host Linux distributions. For the most part the time spent building the native tools that are definitely provided by the host distro are dwarfed by the time spent building things that definitely aren't provided, such as the C library for the target and the cross-compiling toolchain.

=== I disabled runtime package management and yet it still seems to be building rpm/opkg, why? ===

The build system always uses a package manager on the host to assemble images, because it is usually the best tool for this job. This is completely independent of whether the package manager is available in the target image - "package-management" being in IMAGE_FEATURES (possibly indirectly via EXTRA_IMAGE_FEATURES) controls whether the package manager is used at runtime i.e. whether it (and its associated package database) will be present in the target image.

=== Why is opkg-native / opkg-utils being built when I don't have ipk packaging enabled? ===

opkg-utils provides update-alternatives which is the default tool used to manage the alternatives system (for selecting between multiple providers of the same file, e.g. busybox and bash both provide /bin/sh).

=== Why is rpm-native being built when I don't have rpm packaging enabled? ===

rpm-native is needed for two things in the generic packaging code implemented in the package class:

# Debug symbol splitting - rpm-native provides the debugedit tool which this code uses
# Per-file dependencies - although this was originally just feeding into rpm when rpm was being used, it also now gets verified by QA checks regardless of which packaging backend is in use.

=== I see a recipe built, but building an image containing the corresponding package fails at do_rootfs because it can't find the package. How does this happen? ===

(For ipk, the error is "Couldn't find anything to satisfy '<package>'"; for rpm it is "<package> not found in the base feeds (<architecture list>)".)

Usually this is because the recipe claimed to provide the specified package (via PACKAGES or PACKAGES_DYNAMIC) but it wasn't actually produced, possibly because it ended up empty (since by default empty packages aren't produced), but the image or some other package still has a dependency that pulls in the specified package. If this is a recipe you are writing yourself the probable cause is your recipe isn't installing any files and thus the main package for the recipe is empty. Fix do_install (or what do_install is already running, e.g. make install) such that files are installed into the correct location such that they can then subsequently be packaged, and then all should be well.

In other situations the reference to the package in question is spurious and either it should be removed entirely or there's another package that should be used instead. For example, the avahi and dhcp recipes both have an empty main package since the client and server are split out into their own packages, and those are the ones you should be using instead (avahi-daemon, avahi-utils, dhcp-server, dhcp-client - there are other packages as well, please see [[#How_do_I_find_out_what_packages_are_produced_by_a_recipe.3F|How do I find out what packages are produced by a recipe?]].) You could argue that these recipes shouldn't claim to provide the main package, or they should have a main package that depends on all the other packages (as some other recipes do).

=== X11 and various other items are being built but I'm only building core-image-minimal - why? ===

This is where it helps to understand the difference between build-time dependencies and runtime dependencies - often, a recipe will require things at build time (for example tools that help the build process, or to satisfy optional dependencies) that it doesn't necessarily need at runtime. The default configuration includes "<code>x11</code>" in <code>DISTRO_FEATURES</code>, and thus anything that can optionally support X11 will have its X11 support enabled; however when it comes to actually producing the image there won't be any X11 packages included as long as there are no hard dependencies and there aren't any X11 packages explicitly requested.

If you never intend to use X11, you can set your own <code>DISTRO_FEATURES</code> value that excludes <code>x11</code> (note lower case, as with all feature names) and then X11 support will be disabled at build time and these items won't even be built.

=== How do I avoid the kernel itself being pulled into my image when installing kernel modules? ===

By default, the kernel class sets a dependency on the kernel-base package (which kernel modules always depend on) onto kernel-image, which contains the actual kernel binary. If you don't want this, set the following either in your kernel recipe or at the configuration level:

RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""

Note: for older releases (pre-2.5) do this instead:

RDEPENDS_kernel-base = ""

== Misc ==

=== How do I remove a value from a list variable? ===

For variables that are expected to contain a space-separated list of items, BitBake supports a _remove operator to remove items from it. See [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#removing-override-style-syntax Removal (override style syntax)] in the BitBake user manual.

'''NOTE:''' the _remove operation is final - you cannot "undo" it with other operations elsewhere, thus you should really only make use of it in your distro / local configuration and not in layers that you expect others to re-use for different purposes (and therefore they may need to undo your changes). An alternative way to effectively remove an item is to set the list outright to include all the items minus the one you want to remove.

=== How do I change how my recipe is built depending on what image I'm building? ===

The short answer is you cannot - the reason is that OpenEmbedded builds packages based on the overall configuration, and then the image only selects which of these packages should go into the final image. However, there are some solutions that do allow you to achieve the desired result:

# Have separate packages for the two different versions. This could take the form of different recipes or you could do it within the same recipe. The two packages do have to have different names however; this may create problems if you have other packages that depend on the package.
# Use a postprocessing function within the image(s) - within the image recipe, define a shell or python function that makes the desired changes to the files in the image and add a call to it to ROOTFS_POSTPROCESS_COMMAND within the image recipe. Note that this may not be appropriate if you have runtime package management enabled since the postprocessing will only happen at image creation time and not if the package is installed later on at runtime - you may need to use a postinstall script instead in this case.
# Use a postinstall script (pkg_postinst_<package> function) within the recipe. In order to work, the postinstall script will need to be able to determine what to do when it's run - this may not be practical depending on what you're trying to achieve.

=== Can I use a toolchain built by OE as the external toolchain? ===

In general, this is not recommended and not something that is tested or directly supported out of the box. If you are wanting to do this solely as a means of speeding up the build, it is strongly suggested that you use shared state instead.

There is a [http://layers.openembedded.org/layerindex/branch/master/layer/meta-sourcery/ meta-sourcery layer] available to enable support for the CodeSourcery toolchain, you may be able to use this as a template for bringing in an external toolchain however there are no guarantees.

=== When I run bitbake -c devshell it looks like it's running as root! How is that possible? ===

It's not running as the actual root user, it's just pretending for the benefit of programs that run under it (including your shell) that it is, via pseudo. This is important, because you normally want any owner/group/permission values that you set on files to be reflected in files that the recipe installs and packages and thus reflected in the final image - without this mechanism the actual build would have to run as root which would be very risky. There are no actual elevated privileges through this mechanism however, so you need not be worried.

=== Why does OE use pseudo? Why not use fakeroot / fakechroot instead? ===

Splitting this up into two questions - we use pseudo (not to be confused with sudo!) because we want to be able to create images containing files have the correct permissions and ownership, e.g. files owned by root, without the user running the build system having to have that privilege. By using LD_PRELOAD to intercept function calls, pseudo creates an environment for programs running underneath it where it appears as if the running user has those privileges (and the results of any operations persist within the pseudo environment, i.e. you can write a file as root and it will appear to be owned by root while still running under pseudo). This allows us to run builds entirely as a normal user without needing extra privileges. Without pseudo we would require running the build system under sudo or as root - which would be ill-advised for things such as "make install" in case it happened to be broken and tried to write to / instead of somewhere under the work directory for the recipe; a broken recipe could easily end up destroying your system in that case.

To answer the second part, why we use pseudo instead of fakeroot / fakechroot, see [https://github.com/wrpseudo/pseudo/wiki/WhyNotFakeroot WhyNotFakeroot on the pseudo wiki].

=== How do I find out what packages are produced by a recipe? ===

The Toaster web UI provides easy ways to query this.

In the 1.8 (fido) release and newer you can use the following command, assuming the recipe has already been built:

oe-pkgdata-util list-pkgs -p recipename

Alternatively you can look in the "packages-split" subdirectory under the work directory for the recipe - each package produced by the recipe will have a subdirectory under that. If you're not sure how to find the work directory you can run the following command:

bitbake -e recipename | grep ^WORKDIR=

Before a recipe gets built it is a bit trickier, since the system often doesn't know exactly which packages will be produced until do_package time; this is particularly true for recipes that package plugins or modules (e.g. kernel modules). You can get a reasonable idea though by looking at the value of PACKAGES (and PACKAGES_DYNAMIC for recipes that produce plugins).

=== How do I find out which package contains a particular file (or python module)? ===

oe-pkgdata-util has a find-path subcommand that will tell you exactly this. For example:

$ oe-pkgdata-util find-path /etc/network/interfaces
init-ifupdown: /etc/network/interfaces

Wildcards are allowed anywhere in the path (but you should enclose such expressions in quotes to avoid the shell itself attempting to expand the wildcard):

$ oe-pkgdata-util find-path "*/fstrim"
util-linux-bash-completion: /usr/share/bash-completion/completions/fstrim
util-linux-ptest: /usr/lib/util-linux/ptest/fstrim
util-linux-dbg: /sbin/.debug/fstrim
util-linux-fstrim: /sbin/fstrim

As a specific example of where this can be useful, our Python packaging is a bit more granular than most typical distributions, allowing you to tune the contents of your image to just what you need. However, that does mean you may have trouble figuring out which package provides a particular module. oe-pkgdata-util find-path can also be used for this. For example, to find the package containing the "shutil" module, run this:

$ oe-pkgdata-util find-path "*/shutil.*"
python3-shell: /usr/lib/python3.5/shutil.py
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-2.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-1.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.pyc

Thus the package you are looking for is python3-shell. (Note that you could use */shutil.py, but if the module you are looking for is written in C as some of them are, that won't match it.)

=== I have a local source tree I want to build instead of the upstream source a recipe normally fetches, how do I do that? ===

If it's for development purposes i.e. you have your own local source tree you want to work on and have built, then run:

devtool modify -n <recipename> path/to/sourcetree/

Once you are done you can use <code>devtool finish</code> or <code>devtool reset</code> (depending on the situation) to return to building the source specified in the recipe.

Alternatively if it's more permanent, use the <code>externalsrc</code> class - you can inherit this in the original recipe or a bbappend:

inherit externalsrc
EXTERNALSRC = "/path/to/sources"

If you're going to use it across a number of recipes you can inherit it globally at the configuration level (perhaps via an inc file that you include/require there):

INHERIT += "externalsrc"
EXTERNALSRC_pn-<recipename> = "/path/to/sources"

=== How do I specify the default shell? (e.g. bash instead of busybox) ===

It depends what you mean. As far as which provides /bin/sh, this is controlled through the alternatives system, and by default bash has a higher priority than busybox, so simply installing bash into your image will automatically have /bin/sh link to bash rather than busybox.

If you mean you want a user's login shell to be a specific shell, you'll need to modify /etc/passwd. One fairly easy way to achieve this is to use the extrausers class in your image recipe:

inherit extrausers
EXTRA_USERS_PARAMS = "usermod -s /bin/bash <username>; "

=== How do I get "full" versions of typical shell commands? ===

Most of the shell commands in our images are provided by busybox by default, and are very much simplified compared to what you would have on a typical Linux system in order to save space. If you need the full versions, most of them are built and packaged by the coreutils recipe (for disk and other typical utilities) and procps (for ps, etc). You may also want to install bash for more typical shell built-in commands. There is also a core-image-full-cmdline image if you want a base image that is already set up to provide a more typical Linux command-line experience. (Note: these will of course use up more disk space and memory.)

=== How do I allow a variable's value through from the external environment? ===

Add the variable's name to the BB_ENV_EXTRAWHITE ''in the external environment'' before running bitbake. Note that the oe-init-build-env script sets a default for this which you will want to preserve, so add to the default value rather than overwriting it.

Alternatively if you just want to get the external value of a variable from python code within the metadata, you can use the BB_ORIGENV variable which itself contains a datastore of the original environment. For example to get the value of the DISPLAY variable from the environment within a python function you would do this:

display = d.getVar("BB_ORIGENV", False).getVar("DISPLAY")

Note that you must specify "false" for the expand parameter when getting the BB_ORIGENV variable, because it's not a string and therefore cannot be expanded in the normal manner.

=== Why is bitbake showing "AUTOINC" in the version for some recipes? ===

Recipes where you see AUTOINC within the version in the console output during a build will be those that set <code>PV</code> to include <code>"${SRCPV}"</code> to get the SCM revision (e.g. the git hash) in the package version. In order to have the version increment properly, there needs to be a number in front of the revision which automatically increments each time the revision changes (assuming you have a PR server enabled), which is where AUTOINC comes in. During the build, AUTOINC is a stand-in for this auto-incrementing number, and later during <code>do_package</code> it gets replaced with the real number so that the packages produced at the end have the full version number.

=== Why are .so files in the -dev package instead of the main package for a recipe? ===

In standard Unix library packaging, non-versioned .so symlinks (e.g. /usr/lib/libgd.so) are intended for development purposes only. At runtime, binaries should be linked to the major-versioned .so file/symlink e.g. /usr/lib/libgd.so.3. This (theoretically) allows multiple major versions of the same library as well as binaries that depend upon each of them to coexist on the same system. If the library is versioned but you have a binary that links to the unversioned .so file, it has almost certainly been linked incorrectly.

Non-symlink .so files on the other hand are sometimes produced and are entirely legal - however these will be picked up in the -dev package in OpenEmbedded simply by virtue of their name, which is almost always not what you want. In this case you can do one of two things:

# Fix the build of the library so it gets versioned. This may not always be appropriate, especially not for things like plugins.
# Set FILES_${PN}-dev within the recipe so that it does not include ${FILES_SOLIBSDEV}. If the software the recipe is building also produces symlink .so files you'll need to set FILES_${PN}-dev such that those do still get packaged in the -dev package though, or you'll get a package QA warning.

=== Can I disable shared state? ===

You cannot, no. Shared state is an intrinsic part of staging files into the sysroot. It is possible to construct a recipe that bypasses sstate for some tasks (the kernel does this), however this is quite difficult and if not done properly will lead to many other problems.

Almost always when you are having a problem with shared state the issue is either (a) you're adding/changing files in the sysroot directly (i.e. outside sstate control), or (b) what is being placed into the sysroot isn't relocatable. The solution for (a) is do not do that - files should always be installed under ${D} within do_install and then a subset of those are staged into the sysroot automatically. For (b) you need to fix or adapt the hardcoded path(s) - if the program reads (or can be made to read) each path from an environment variable, then you can use the create_wrapper utility function to create a wrapper script that will set the path appropriately. Run "git grep create_wrapper" in the meta subdirectory to see examples.

=== Files I installed into /opt or some other path never make it into the sysroot but I need them - how do I fix this? ===

OpenEmbedded only stages a subset of files that are installed into <code>${D}</code> by <code>do_install</code> so that the sysroot doesn't fill up with unneeded files. You have two choices in this situation:
# install the files into a more standard location which is part of the subset, or
# adjust the subset to include the paths you are installing to.
Usually option 1 is recommended. If you really do need to adjust the subset, you can append the path (more specifically, the part below <code>${D}</code>) to <code>SYSROOT_DIRS</code> within your recipe. For example:

SYSROOT_DIRS += "/opt"

=== I have some software which needs to build a binary that it then runs as part of its own build process, how do I make this work? ===

Whilst it is possible to do this within a single recipe building for the target, it is tricky to do so because in that context everything is set up for cross-compiling for the target, and you would have to undo all of that to build host tools. The standard and much easier way of handling this is to create a native variant of the recipe using BBCLASSEXTEND and have your host tools built within that, and then have the target variant depend on the native variant. For example, assume your recipe were called xyz (xyz_1.1.bb), then you would include something like this in the recipe:

DEPENDS_append_class-target = " xyz-native"

...

BBCLASSEXTEND += "native"

The host tools will then be built and installed into the sysroot in the native variant ready for when the target variant starts building. If the software you are building didn't intend for those tools to be installed outside of the build tree then you may need to patch the build process (e.g. the makefile) in order to install them and possibly also for the target side to find them in the sysroot. Additionally, for performance since you only need the tools in the native variant, you may also choose to disable building everything except those tools there - e.g. by using _native overrides for variables such as EXTRA_OECONF or functions such as do_configure.

=== How do I fetch from two git repositories in the same recipe? ===

By default, sources fetched from git within a recipe are unpacked into ${WORKDIR}/git, however that only works for a single repository. If you want to fetch from more than one, you need to change the path each repository is unpacked to. This is easy to do, just add <code>;destsuffix=<subdir></code> to the end of each URL in SRC_URI (replacing <code><subdir></code> with the name of the subdirectory). You may then need to change S to match whichever of these you want to be considered the root of the source tree - or alternatively you can specify destsuffix such that repositories beyond the first go into a subdirectory under the default "git" subdirectory. For example, from the gst-libav recipe:

...
SRC_URI = " \
git://anongit.freedesktop.org/gstreamer/gst-libav;branch=1.8;name=base \
git://anongit.freedesktop.org/gstreamer/common;destsuffix=git/common;name=common \
...
"
...
S = "${WORKDIR}/git"
...

(Here we're using the default of "git" for the first repository, so we don't need to specify <code>destsuffix</code> for the first URL.)

=== I'm building a native recipe and I notice that the install path has the full path to the root directory repeated - why? ===

It does look a little odd, but the reason for doing this is that native targets are meant to run on the system they're built on and run in the location they're installed to. This means they install to a destination of "/" and PREFIX is inside the native sysroot directory. We install them to a DESTDIR to allow us to manipulate them before they then get moved to a final DESTDIR of "/".

Most Makefiles handle this correctly by doing:

DESTDIR ?= ""
prefix ?= "/usr"
bindir ?= "$(prefix)/bin"

and then, importantly, install in the form:

install -d $(DESTDIR)$(bindir)

so both prefix and DESTDIR are used. Whilst this is a convention, its a widely adopted and followed one. You can call into a custom makefile and set the variables manually if the makefile doesn't follow the convention.

=== How do I generate static libraries? ===

Its possible you have conf/distro/include/no-static-libs.inc included in your build - poky does this by default. The include list at the top of the bitbake -e output will tell you for certain.

If so, you can remove that or set:

DISABLE_STATIC = ""

as it would currently be set to this if that include file is included:

DISABLE_STATIC = " --disable-static"

Poky disables building static libraries by default as for the most part they're a waste of space/time.

=== Can I conditionally inherit a class in a recipe? ===

Yes, you can. What makes this possible is that the <code>inherit</code> keyword will not complain if what comes after it expands to being empty, so you can use in-line python to do something like this:

<pre><nowiki>
inherit ${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}
</nowiki></pre>

The above example will inherit the <code>perlnative</code> class if "scripting" is in the value of the <code>PACKAGECONFIG</code> variable, otherwise it will do nothing.

You could of course put this into a variable if you prefer:

<pre><nowiki>
SOMEVAR = "${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}"
inherit ${SOMEVAR}
</nowiki></pre>

=== How do I collect the source revisions fetched by each recipe? ===

If you have recipes where <code>SRCREV = "${AUTOREV}"</code> then you won't necessarily know exactly which revisions were built after the fact - it will be whatever was current at the time. You also might alternatively just want to get all of the revisions. Either way, to do this, enable buildhistory by setting the following in your local.conf:

<pre><nowiki>
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
</nowiki></pre>

(The last line is not required with version 2.5 and onwards as it is the default, but will do no harm.)

Once you have enabled buildhistory, you then need to build your image again so that buildhistory has a chance to record history data for it. Following that you can run <code>buildhistory-collect-srcrevs</code> (with <code>-a</code> if you want to see all revisions, not just the ones where AUTOREV was used) and it will output the revisions in a form you can use in a .inc file that you can <code>require</code> from your configuration if you want to fix the build to those revisions.

For more information see the [https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] section of the Yocto Project Development manual, which covers the buildhistory class in detail.

=== How do I do an offline build with recipes that have <code>SRCREV = "${AUTOREV}"</code> set? ===

If you set <code>BB_NO_NETWORK = "1"</code> and you have recipes that have <code>SRCREV = "${AUTOREV}"</code>, you will get an error because the build system will try to check the latest revision on startup and be immediately blocked by <code>BB_NO_NETWORK</code>. There are two ways to handle this:

A) See the previous question "How do I collect the source revisions fetched by each recipe?" and use the output generated by <code>buildhistory-collect-srcrevs</code> as a .inc file in your configuration in order to fix the revisions at the ones which were most recently built.

or

B) Set <code>BB_SRCREV_POLICY = "cache"</code> in your configuration. This will use the last cached revision. (The disadvantage of this method is that it is a little more difficult to preserve or share with others the fixed revisions.)

Note that in either case if you later want to build the latest version again, you will of course need to undo the configuration changes.

=== Is it possible to append a bbclass file (like bbappends do for recipes)? ===

No, see the next question for details.

=== How do I override a bbclass file? ===

This is tricky - bbclass files are found via BBPATH, which is added to by each layer.conf either by prepending or appending. Assuming you are putting your bbclass in a custom layer, you will probably want to have your layer's layer.conf prepend to BBPATH, but then you will also need to make sure that your layer does not appear before any other layer that is also prepending and overriding the same class.

Another alternative is to have an additional class which makes the appropriate changes to the environment, and then you will need to inherit that class after (and in the same manner as) the original class. This is slightly cleaner but can be annoying to enable particularly if the class is inherited by a number of recipes, and won't work if you want to alter the behaviour of a class inherited by recipes you don't control. (If you want a class to be inherited for all images (i.e. all recipes inheriting the <code>image</code> class) you can inject additional classes by setting IMAGE_CLASSES; similarly for the kernel there is KERNEL_CLASSES).

Ultimately, overriding bbclass files is not good practice long term - you are opening yourself up to maintenance issues when the original class changes, and the override is fragile as hinted above. The best solution is to try to get whatever changes you need into the original class; this does of course require additional work and time though.

=== There's a bbappend in a layer I'm using that defines a <code>do_something_append()</code> and I want to append to that function also, how do I do this? ===

Simply create a bbappend in your layer and define your own <code>do_something_append()</code>, and your commands will be executed ''as well as'' those of the other bbappend.

You might assume that defining <code>do_something_append()</code> will overwrite any previously defined <code>do_something_append()</code>, as would be the case with <code>do_something()</code> in the same situation, but that is not the case - the key is that <code>_append</code> (and <code>_prepend</code>, <code>_remove</code>, etc.) are ''operators'' and they will be applied in sequence, where that sequence is the order in which they are parsed (which for bbappends will be in ascending layer priority order).

Main Page

2020-06-04T22:34:30Z

PaulEggleton:

== Welcome to the Yocto Project Wiki! ==
The [http://yoctoproject.org Yocto Project] is an open-source project that delivers a set of tools that create operating system images for embedded Linux systems. The Yocto Project tools are based on the [http://www.openembedded.org/wiki/Main_Page OpenEmbedded] (OE) project, which uses the BitBake build tool, to construct complete Linux images. BitBake and OE are combined to form a reference build host known as Poky which includes the following [[Core Components|core components]]. This [https://www.youtube.com/watch?v=utZpKM7i5Z4 video] will help explain what it's all about.

===Where to Start?===
If you're new to Yocto take a look at the '''[[Glossary]]''' so you're familiar with the terms used in this wiki and the project documentation. Then take a look at the [http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html '''Quick Start Guide''']. You can follow the steps in this document to clone the poky repository, quickly configure your build environment, and then try a build. Corporate firewalls can be problematic so network proxy configurations are detailed on the '''[[Working Behind a Network Proxy]]''' page. We advise you go straight for the [[Working_Behind_a_Network_Proxy#Option_2:_Chameleonsocks| Chameleonsocks option]].

===Where to Next?===
Thanks to the quick start guide, it's pretty easy to get your first Linux image and and running. Here are some places to look for help when improving your Yocto skills.
* The [https://linuxfoundation.org Linux Foundation] have some great [https://docs.google.com/presentation/d/1LmI3mHoD_Dzl8wplIYcUBrFF8BzDb_EadTvfbnpSK7Q/edit training slides]. There is also an [https://docs.google.com/presentation/d/1HoDtyN5SzlmuTN47ab4Y7w_i6c_VEW6EBUD944ntf38/edit#slide advanced slide deck] for more more experienced users.
* The first tool you'll need to get familiar with is '''bitbake''', so reading through the [https://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html user manual] is recommended. You don't need to understand it all right now, but bookmark this page for reference. Implementation of bitake is covered in the [[Bitbake Internals Primer]]
* Once you start adding packages and configuring your image to create your own distribution, things can go wrong and it can hard to track down the root cause. There is no shortage of Yocto documentation resource, but if you're not exactly sure what you're looking for this '''[[Documentation Decoder]]''' will help you out. Also take a look at the [https://wiki.yoctoproject.org/wiki/Cookbook '''Cookbook'''] and [https://wiki.yoctoproject.org/wiki/Technical_FAQ troubleshooting guide]. Also [https://www.yoctoproject.org/blogs/jefro/2016/yocto-project-books these books] are helpful.
* Some new tools such as [http://www.yoctoproject.org/docs/current/toaster-manual/toaster-manual.html Toaster], [[Extensible SDK]] and [https://github.com/crops CROPS] are making it easier to get the best out of Yocto on Windows and Mac OS X. Take a look at the new workflow in [[Developer Workflow Improvements]].
* There is also a [https://wiki.yoctoproject.org/wiki/TipsAndTricks '''Tips and Tricks'''] section where more experienced developers contribute to articles that will help those new to Yocto Project.
* You can also read and participate on the [https://lists.yoctoproject.org mailing lists] - start with the [https://lists.yoctoproject.org/g/yocto main list] first - and the [https://www.yoctoproject.org/tools-resources/community/irc IRC channels].

== Project planning ==

=== Features ===
* [[Yocto Feature Summary]] (Current and Next)

=== Project Planning for current release ===

* [[Planning]]

=== Project Status and Schedule ===
* [[Weekly_Status]]
* [[Yocto Project v2.8 Status]]
* [[Yocto 2.8 Schedule]]
* Testresults - https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults

== Release Engineering ==

* [[Yocto Release Engineering | Yocto Project Release Engineering]]
* [[Yocto Release Engineering | Release Activity (with status, version info, QA links, etc)]]

== QA & Automation ==

* [[The_Yocto_Autobuilder| The Yocto Project Autobuilder]]
* [[QA| Yocto Project QA Main Page]]
* [[QA/Archive| Yocto Project QA Test Report Archive ]]

== Quick guide for newcomers ==

If you are new to the project and are willing to contribute, please refer to our [[Newcomers|guide for newcomers]].

== TSC ==
* Yocto Project Technical Steering Committee [[TSC]]

== Wiki reference sitemap ==
* [[Glossary]]
* [[Documentation Decoder]]
* [[Working Behind a Network Proxy]]
* [[FAQ]] and [[Technical FAQ]]. These need to be unified.
* [[Cookbook]] and [[TipsAndTricks | Tips and Tricks]]. Need clear messaging on how these should be differentiated.
* [[Developer Workflow Improvements]], including [[Nodejs Workflow Improvements]]
* [[Planning and Governance]]
* [[Community Guidelines]]
* [[Yocto Release Engineering | Yocto Project Release Engineering]]
* [[License Infrastructure Interest Group | License Infrastructure]]
* [[Processes and Activities]]
* [[Technical Contributors]]
* [[Projects]]
* [[Security]] - find out what we do about CVEs and security
* [[Yocto Interest Groups]]
* [[Testopia]] - The Yocto Project's community-opened test case management platform
* [[Toaster]] - the web interface
* [[Archive]] - Graveyard for out of date articles.

== Other resources ==
* [http://yoctoproject.org Yocto Project Front Page]
* [http://git.yoctoproject.org/ Yocto Project Git Source Repos]
* [https://bugzilla.yoctoproject.org/ Yocto Project Bugzilla]
* [https://www.yoctoproject.org/tools-resources/community/mailing-lists Yocto Project Mailing Lists]
* [http://recipes.yoctoproject.org/rrs Yocto Project Recipe Reporting System]
* [https://autobuilder.yoctoproject.org/typhoon Yocto Project Autobuilder]
* [http://downloads.yoctoproject.org/releases/yocto/ Yocto Project Releases Downloads]
* [http://autobuilder.yoctoproject.org/pub/nightly/ Yocto Project Nightly Build Images]
* [http://downloads.yoctoproject.org/mirror/sources/ Upstream Sources Mirror]
* [http://www.openembedded.org/wiki/Main_Page OpenEmbedded Wiki]
* [http://cgit.openembedded.org/ OpenEmbedded Git Repos]
* [http://layers.openembedded.org/ OpenEmbedded Community Layers]
* [http://patchwork.openembedded.org/ OpenEmbedded Patch Tracking System]
* '''IRC''': irc.freenode.net
:* #yocto - Public discussions on the Yocto Project.
:* #oe - Public discussions on OpenEmbedded Core.

Technical FAQ

2020-03-27T04:14:45Z

PaulEggleton: Add taskhash mismatch

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
| '''NOTE:''' This is currently a draft. Not sure where this should end up but I've been gathering these based on my interactions with people on IRC and email over the years. - [[User:PaulEggleton|PaulEggleton]] ([[User talk:PaulEggleton|talk]]) 21:13, 27 June 2016 (PDT)
|}

== Basics ==

=== How do I figure out which version/codename/bitbake version matches up with which? ===

There is a table in the [http://wiki.yoctoproject.org/wiki/Releases Releases page] on the Yocto Project wiki.

=== How do I control what's in the final image? ===

Each image is defined by its own recipe, and that recipe specifies a list of packages that the image should contain. See [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Customising Images] within the Yocto Project development manual for further details.

Note: if you're doing anything more than basic experimentation / testing then you almost certainly should create your own image recipe rather than using one of the example images e.g. core-image-minimal - though you can certainly start by copying one of the example images. This way you have easier control over what goes into the image.

=== Where do I find build logs? ===

For the overall build, the output of bitbake gets logged to tmp/log/cooker/<machine>.

For each individual recipe, there is a "temp" directory under the work directory for the recipe that contains log.<taskname> and run.<taskname> files - the logs and the runfiles respectively. Within the build system this directory is pointed to by the T variable, so if you need to you can find it by using <code>bitbake -e</code>:

bitbake -e <recipename> | grep ^T=

=== How do I add a patch to a recipe? ===

There are two concerns - how the recipe can fetch the patch and how it can be applied. For fetching, patch files are usually placed in a subdirectory next to the recipe; by default this directory should be named "files" or the the recipe name without any class prefix or suffix (for example for both "xyz" and "xyz-native" the subdirectory would be "xyz"). A pointer to it then needs to be added to <code>SRC_URI</code> within the recipe, which usually takes the form <code>file://<patchname>.patch</code> - i.e. just the filename, no path. If more than one subdirectory needs to be stripped off the paths in the patch (i.e. you need more than the equivalent of the -p1 option to the patch command) then you can add <code>;striplevel=<number></code> to the end of the patch entry in SRC_URI (without any spaces).

As with any modification, if the patch you are applying is a customisation that you do not intend to send to be incorporated in the layer you are modifying, then instead of adding the patch to the recipe directly then you should consider applying it in a bbappend within your own custom layer. This makes things easier if you later want to update the layer in question and the recipe has been modified upstream - you avoid effectively forking the layer.

The <code>devtool</code> utility can help you modify the sources for a recipe and create a patch - basically <code>devtool modify</code>, edit the sources, commit the changes with <code>git commit</code>, then <code>devtool finish</code> (or <code>devtool update-recipe</code> in versions older than 2.2). Since <code>devtool modify</code> gives you a git tree to work with, you can of course use something like <code>git am</code> to apply existing patches this way. For more details see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#devtool-use-devtool-modify-to-enable-work-on-code-associated-with-an-existing-recipe Use devtool modify to Enable Work on Code Associated with an Existing Recipe] within the Yocto Project Development manual.

=== What does "native" mean? ===

The "native" suffix identifies recipes (and variants of recipes) that produce files intended for the build host, as opposed to the target machine. This is usually for tools that are needed during the build process (such as automake).

=== What does "nativesdk" mean? ===

The "nativesdk" prefix identifies recipes (and variants of recipes) that produce files intended for the host portion of the standard SDK, or for things which are constructed like an SDK such as buildtools-tarball. These are built for SDKMACHINE which may or may not be the same architecture as the build host.

=== I have two recipes and one needs to access files provided by another - how can that work? ===

Instead of providing direct access from a recipe to another's build tree (which wouldn't be practical with OpenEmbedded since the build tree (or "workdir") is temporary), we create a "sysroot" where files that are intended to be shared between recipes get copied. The sysroot is managed by the build system and you should not copy files in there directly - instead, you install files under ${D} as normal during do_install and then the build system will copy a subset of those to the sysroot. There is a seperate sysroot for each machine being built for. In a recipe you can get the path of the sysroot and various standard directories under it using the STAGING_* variables.

Often, for commonly-used build systems such as autotools and cmake you don't need to worry about these details - those systems and the environment that OpenEmbedded sets up for them will ensure that files get installed and picked up in the correct locations. However if the software your recipe is building has custom build scripts / makefiles and it takes shortcuts that don't account for cross-compilation or the use of a sysroot, then you will need to make appropriate adjustments.

=== How do I enable package management in the final image? ===

Add <code>package-management</code> to <code>IMAGE_FEATURES</code> (or <code>EXTRA_IMAGE_FEATURES</code>). You should then be able to use dnf/rpm, opkg, or apt-get/dpkg from the running system depending on the packaging format you have selected through PACKAGE_CLASSES. For more information see [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-runtime-package-management Using Runtime Package Management] in the Yocto Project Development manual.

=== What do ?=, ??=, := etc. do within a recipe/config file? ===

See the [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#basic-syntax Basic Syntax section of the BitBake manual] for details.

== Layers ==

See http://www.openembedded.org/Layers_FAQ

== Troubleshooting ==

=== I've created a recipe but it's not showing up in my image, what's going on? ===

Creating a recipe (or adding a layer to your configuration with a desired recipe in it) only makes it available to the build system, it doesn't change what goes into the image. For that, see [[#How do I control what's in the final image?|How do I control what's in the final image?]] above.

=== I set a variable but it doesn't seem to be having an effect, how do I fix this? ===

First, double-check that you haven't misspelled the variable name.

The main tool to help troubleshoot any variable-related issue is <code>bitbake -e</code> - this lists all the variables and the complete history of how each one has been set (use <code>bitbake -e recipename</code> if you're dealing with issues in a variable value within a recipe as opposed to the global level). Usually it's best to pipe this through <code>less</code> so you can easily see the history - within less you can press / to search for the variable name. Often you will be dealing with the behaviour of a variable within the context of a specific recipe, so specify that recipe on the <code>bitbake -e</code> command line to get the variables as set within the context of the recipe rather than the global context.

If you're setting a variable in a bbappend, double-check that the bbappend is actually being applied - see the next question.

=== I've created a bbappend for a recipe but what I'm setting there isn't having any effect, how do I fix this? ===

Here are some things to check:

# Check if the layer the bbappend is in is listed in <code>bitbake-layers show-layers</code>. If it isn't, you need to edit your bblayers.conf and ensure the path to the layer is included in the BBLAYERS value
# Check that the bbappend is being picked up by running <code>bitbake-layers show-appends</code> - if your bbappend file isn't listed, it could be named incorrectly (such that it doesn't match the recipe name) or it may be that the BBFILES value in the conf/layer.conf for the layer containing the bbappend file doesn't include an expression that will match the bbappend files.
# If there are multiple versions of the recipe you have bbappended, it could be that the actual recipe being built is a different version than the one you have bbappended. <code>bitbake-layers show-recipes <recipename></code> will list all the versions, with the first one listed being the one that will be built. If this is the case there are several different solutions to this - (a) Rename your bbappend to match the version being built, (b) use a % wildcard in your bbappend so it will apply to any version, (c) set <code>PREFERRED_VERSION_<recipename></code> in the configuration to select a the version you want to be built.
# Finally, as with any other issue with setting variables, use <code>bitbake -e recipename | less</code> and search with <code>/</code> to see the history of how the variable has been set - you may find that the value you're trying set is being overridden.

=== I'm getting warnings that a recipe is tainted - what does this mean? ===

Usually this happens because you have used I used bitbake's <code>-f</code> or <code>-C</code> option to force a task to re-execute. The assumption is that if you forced a task, it is possible that a rebuild from scratch would not include whatever changes you made that necessitated forcing (e.g. if you modified the source in the work directory for the recipe and then ran <code>bitbake -c compile -f</code>). Generally, forcing a task should be reserved for situations where the build system has failed to detect a change you made rather than for everyday usage - if you're finding yourself needing to do it regularly then either there's a bug, you're doing something wrong, or perhaps you're using <code>-f</code> or <code>-C</code> when it's not really needed. Running <code>bitbake -c clean</code> on the recipe will get rid of the taint flag.

There is one other situation where we apply a taint, and that is <code>bitbake -c menuconfig</code> on the kernel. In this case, the configuration has been saved into the work directory for the kernel, but that is temporary - any rebuild from scratch will use the default configuration, so it is a reminder that you need to take the configuration and apply it back to the metadata and then run <code>bitbake -c clean</code> on the kernel recipe.

=== I'm fetching from a git repository over ssh / http / https but it's not fetching properly, how do I fix this? ===

Bitbake expects the prefix of entries in SRC_URI to specify the fetcher to be used, not the actual protocol. Thus, instead of:

# This will NOT work
SRC_URI = "<nowiki>http://git.example.com/repository</nowiki>"

You should specify:

# This is better
SRC_URI = "<nowiki>git://git.example.com/repository;protocol=http</nowiki>"

The same applies for ssh and https.

=== I tried bitbake <some target package name> that I know exists and it told me that nothing PROVIDES this...? ===

There are two namespaces that bitbake concerns itself with - recipe names (a.k.a. build time targets) and package names (a.k.a. runtime targets). You can specify a build time target on the bitbake command line, but not a runtime target; you need to find the recipe that provides the package you are trying to build and build that instead (or simply add that package to your image and build the image). In current versions bitbake will at least tell you which recipes have matching or similar-sounding runtime provides (RPROVIDES) so that you'll usually get a hint on which recipe you need to build.

=== I've included a package in my image but files I expect to be there are missing, what's the issue? ===

Check the simple stuff: verify that the package is really in the image - look at the manifest file next to the image to ensure the package is listed. Also if you're flashing the image, double-check that you did indeed flash the right image and if there are multiple partitions / storage devices on your board or device that you're booting the one that you think you are.

Once you're sure of the above, it may be a matter of the package splitting - a lot of recipes split less commonly used components out to separate packages, so it's possible that the files you are looking for are in a different package. You can look at the recipe for this (look for PACKAGES and FILES statements) or assuming the recipe has been built, you can use <code>oe-pkgdata-util list-pkgs -p recipename</code> and <code>oe-pkgdata-util list-pkg-files</code> to inspect the packages provided by the recipe and the files they contain. Once you find the right package you can add it to your image.

=== I'm required to set LIC_FILES_CHKSUM but the software I'm building doesn't have a license statement, what do I do? ===

Ideally, all software should come with some kind of license statement so that the terms of distribution are clearly stated (especially if its source code is made publicly available); if not a text file describing the license then at the very least a line or two in the accompanying documentation, README file or source header comments. Assuming there is a license statement somewhere but not in a form you can point to with LIC_FILES_CHKSUM as part of the source tree, you can point LIC_FILES_CHKSUM to one of the generic license files in ${COMMON_LICENSE_DIR} (meta/files/common-licenses/), or alternatively you can include a file containing the license statement in a "files" subdirectory next to the recipe (or subdirectory named the same as the recipe - see how such files are handled in other recipes), point to it in SRC_URI using file://, then add it to LIC_FILES_CHKSUM. It is worth noting however that LIC_FILES_CHKSUM is intended to give you a warning if upstream changes its license terms when you do an upgrade of the recipe, and by pointing it to this common license file that is part of the metadata, that mechanism will not function. You may wish to consider encouraging the upstream provider of the software your recipe is building to follow best practices and include a proper license statement, so that you can point to it in a future version. At minimum if you do use such workarounds, you will need to take extra care when upgrading the recipe in future in case the upstream provider changes the license terms.

If there really is no license stated at all anywhere for the software (and this is unfortunately not uncommon on github, for example) then you should really contact upstream - if there's no license, then technically you really shouldn't be distributing it until that's clarified with the original author(s).

=== I am getting a package QA error / warning when building a recipe, how do I solve it? ===

There are some general and specific recommendations in the [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-errors-and-warnings QA Errors and Warnings] section of the Yocto Project Reference Manual.

=== I am getting "taskhash mismatch" errors, what does this mean and how do I fix it? ===

Bitbake parses the metadata (recipes, classes and configuration) repeatedly during its operation, and this error means that the result of parsing changed between one parse and the next. Two situations that can cause this:
# One of the parsed files changed in between e.g. you edited a recipe or performed a git operation (e.g. git checkout) during the build. '''Do not make changes to the metadata while a build is running.''' If you run the build again the error should not recur.
# Alternatively, there is something in the metadata that results in a variable expanding to a different value each time it is parsed. This is often something time-related e.g. a timestamp which is calculated every time an expression is expanded. The solution is to ensure the value is calculated once per build and then the expression expands to the same value for the duration of the build.

=== Building on a system with a GRSec kernel doesn't work well, is that supported? ===

No, grsec isn't really supported. The list of distros that are supported (tested) is in the Yocto mega manual for each release.
You can refer to the work-around given in this defect: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10885

=== Working around Firejail ===
For users of Parrot OS and other secured Linux distros, you will find that your bitbake fetch commands refuse to work, yet you can manually run wget and retrieve the packages with no problem. This is due to Poky creating links to all the tools it requires, in particular 'wget', 'ssh' and 'strings', using the links to these tools in the /usr/local/bin/ directory which all redirect to firejail. To fix the problem you can cd into <your Yocto install directory>/poky/build/tmp/hosttools directory and replace these links with ones redirecting to the actual executables under the /usr/bin directory.

== Dependencies ==

=== How do I find out why something is being built? ===

<code>bitbake -g <recipe></code> will produce some .dot files that allow you to see the dependency relationships - usually pn-depends.dot holds the answers although sometimes you may need to look at task-depends.dot if the dependency is only in the form of a task dependency. Note that these graphs are much too large for most graphviz visualisation tools to process, so you'll probably find it's easiest to view them with "less" or a text editor and search for the item you're looking for.

=== How do I find out why something is in my image? ===

Enable the buildhistory class and build the image again, and it will write out a depends.dot file containing the relationships between packages in the final image. If the package name isn't mentioned it is probably explicitly mentioned in IMAGE_INSTALL or being brought in via IMAGE_FEATURES.

See [http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] in the Yocto Project Reference manual which covers how to enable buildhistory and the output it produces.

=== How do I view the .dot files produced by bitbake -g or buildhistory? ===

The size of some of these .dot graphs (particularly those produced by <code>bitbake -g</code>) is a little large for most viewers / processing tools, and unfortunately this isn't something that can be fixed - it's just the nature of the dependency relationships between targets and tasks within OpenEmbedded. Usually if you're just after answering a simple dependency question you can figure it out by viewing it with <code>less</code> and using its built-in search function (or alternatively your favourite text editor).

You can try [http://github.com/jrfonseca/xdot.py xdot] which will work well for some of the graphs, but the task graph produced by <code>bitbake -g</code> for something like an image in particular is likely to be too large to view within it.

=== Why are all of these -native items being built when my host distro has some of these available? ===

It's complicated. In some cases the software in question isn't widely packaged by common Linux distributions. In other cases we need to apply patches to the software, use a more up-to-date version than commonly packaged or build it with a particular configuration. In general it just helps us isolate ourselves from potential problems caused by differences in host Linux distributions. For the most part the time spent building the native tools that are definitely provided by the host distro are dwarfed by the time spent building things that definitely aren't provided, such as the C library for the target and the cross-compiling toolchain.

=== I disabled runtime package management and yet it still seems to be building rpm/opkg, why? ===

The build system always uses a package manager on the host to assemble images, because it is usually the best tool for this job. This is completely independent of whether the package manager is available in the target image - "package-management" being in IMAGE_FEATURES (possibly indirectly via EXTRA_IMAGE_FEATURES) controls whether the package manager is used at runtime i.e. whether it (and its associated package database) will be present in the target image.

=== Why is opkg-native / opkg-utils being built when I don't have ipk packaging enabled? ===

opkg-utils provides update-alternatives which is the default tool used to manage the alternatives system (for selecting between multiple providers of the same file, e.g. busybox and bash both provide /bin/sh).

=== Why is rpm-native being built when I don't have rpm packaging enabled? ===

rpm-native is needed for two things in the generic packaging code implemented in the package class:

# Debug symbol splitting - rpm-native provides the debugedit tool which this code uses
# Per-file dependencies - although this was originally just feeding into rpm when rpm was being used, it also now gets verified by QA checks regardless of which packaging backend is in use.

=== I see a recipe built, but building an image containing the corresponding package fails at do_rootfs because it can't find the package. How does this happen? ===

(For ipk, the error is "Couldn't find anything to satisfy '<package>'"; for rpm it is "<package> not found in the base feeds (<architecture list>)".)

Usually this is because the recipe claimed to provide the specified package (via PACKAGES or PACKAGES_DYNAMIC) but it wasn't actually produced, possibly because it ended up empty (since by default empty packages aren't produced), but the image or some other package still has a dependency that pulls in the specified package. If this is a recipe you are writing yourself the probable cause is your recipe isn't installing any files and thus the main package for the recipe is empty. Fix do_install (or what do_install is already running, e.g. make install) such that files are installed into the correct location such that they can then subsequently be packaged, and then all should be well.

In other situations the reference to the package in question is spurious and either it should be removed entirely or there's another package that should be used instead. For example, the avahi and dhcp recipes both have an empty main package since the client and server are split out into their own packages, and those are the ones you should be using instead (avahi-daemon, avahi-utils, dhcp-server, dhcp-client - there are other packages as well, please see [[#How_do_I_find_out_what_packages_are_produced_by_a_recipe.3F|How do I find out what packages are produced by a recipe?]].) You could argue that these recipes shouldn't claim to provide the main package, or they should have a main package that depends on all the other packages (as some other recipes do).

=== X11 and various other items are being built but I'm only building core-image-minimal - why? ===

This is where it helps to understand the difference between build-time dependencies and runtime dependencies - often, a recipe will require things at build time (for example tools that help the build process, or to satisfy optional dependencies) that it doesn't necessarily need at runtime. The default configuration includes "<code>x11</code>" in <code>DISTRO_FEATURES</code>, and thus anything that can optionally support X11 will have its X11 support enabled; however when it comes to actually producing the image there won't be any X11 packages included as long as there are no hard dependencies and there aren't any X11 packages explicitly requested.

If you never intend to use X11, you can set your own <code>DISTRO_FEATURES</code> value that excludes <code>x11</code> (note lower case, as with all feature names) and then X11 support will be disabled at build time and these items won't even be built.

=== How do I avoid the kernel itself being pulled into my image when installing kernel modules? ===

By default, the kernel class sets a dependency on the kernel-base package (which kernel modules always depend on) onto kernel-image, which contains the actual kernel binary. If you don't want this, set the following either in your kernel recipe or at the configuration level:

RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""

Note: for older releases (pre-2.5) do this instead:

RDEPENDS_kernel-base = ""

== Misc ==

=== How do I remove a value from a list variable? ===

For variables that are expected to contain a space-separated list of items, BitBake supports a _remove operator to remove items from it. See [http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#removing-override-style-syntax Removal (override style syntax)] in the BitBake user manual.

'''NOTE:''' the _remove operation is final - you cannot "undo" it with other operations elsewhere, thus you should really only make use of it in your distro / local configuration and not in layers that you expect others to re-use for different purposes (and therefore they may need to undo your changes). An alternative way to effectively remove an item is to set the list outright to include all the items minus the one you want to remove.

=== How do I change how my recipe is built depending on what image I'm building? ===

The short answer is you cannot - the reason is that OpenEmbedded builds packages based on the overall configuration, and then the image only selects which of these packages should go into the final image. However, there are some solutions that do allow you to achieve the desired result:

# Have separate packages for the two different versions. This could take the form of different recipes or you could do it within the same recipe. The two packages do have to have different names however; this may create problems if you have other packages that depend on the package.
# Use a postprocessing function within the image(s) - within the image recipe, define a shell or python function that makes the desired changes to the files in the image and add a call to it to ROOTFS_POSTPROCESS_COMMAND within the image recipe. Note that this may not be appropriate if you have runtime package management enabled since the postprocessing will only happen at image creation time and not if the package is installed later on at runtime - you may need to use a postinstall script instead in this case.
# Use a postinstall script (pkg_postinst_<package> function) within the recipe. In order to work, the postinstall script will need to be able to determine what to do when it's run - this may not be practical depending on what you're trying to achieve.

=== Can I use a toolchain built by OE as the external toolchain? ===

In general, this is not recommended and not something that is tested or directly supported out of the box. If you are wanting to do this solely as a means of speeding up the build, it is strongly suggested that you use shared state instead.

There is a [http://layers.openembedded.org/layerindex/branch/master/layer/meta-sourcery/ meta-sourcery layer] available to enable support for the CodeSourcery toolchain, you may be able to use this as a template for bringing in an external toolchain however there are no guarantees.

=== When I run bitbake -c devshell it looks like it's running as root! How is that possible? ===

It's not running as the actual root user, it's just pretending for the benefit of programs that run under it (including your shell) that it is, via pseudo. This is important, because you normally want any owner/group/permission values that you set on files to be reflected in files that the recipe installs and packages and thus reflected in the final image - without this mechanism the actual build would have to run as root which would be very risky. There are no actual elevated privileges through this mechanism however, so you need not be worried.

=== Why does OE use pseudo? Why not use fakeroot / fakechroot instead? ===

Splitting this up into two questions - we use pseudo (not to be confused with sudo!) because we want to be able to create images containing files have the correct permissions and ownership, e.g. files owned by root, without the user running the build system having to have that privilege. By using LD_PRELOAD to intercept function calls, pseudo creates an environment for programs running underneath it where it appears as if the running user has those privileges (and the results of any operations persist within the pseudo environment, i.e. you can write a file as root and it will appear to be owned by root while still running under pseudo). This allows us to run builds entirely as a normal user without needing extra privileges. Without pseudo we would require running the build system under sudo or as root - which would be ill-advised for things such as "make install" in case it happened to be broken and tried to write to / instead of somewhere under the work directory for the recipe; a broken recipe could easily end up destroying your system in that case.

To answer the second part, why we use pseudo instead of fakeroot / fakechroot, see [https://github.com/wrpseudo/pseudo/wiki/WhyNotFakeroot WhyNotFakeroot on the pseudo wiki].

=== How do I find out what packages are produced by a recipe? ===

The Toaster web UI provides easy ways to query this.

In the 1.8 (fido) release and newer you can use the following command, assuming the recipe has already been built:

oe-pkgdata-util list-pkgs -p recipename

Alternatively you can look in the "packages-split" subdirectory under the work directory for the recipe - each package produced by the recipe will have a subdirectory under that. If you're not sure how to find the work directory you can run the following command:

bitbake -e recipename | grep ^WORKDIR=

Before a recipe gets built it is a bit trickier, since the system often doesn't know exactly which packages will be produced until do_package time; this is particularly true for recipes that package plugins or modules (e.g. kernel modules). You can get a reasonable idea though by looking at the value of PACKAGES (and PACKAGES_DYNAMIC for recipes that produce plugins).

=== How do I find out which package contains a particular file (or python module)? ===

oe-pkgdata-util has a find-path subcommand that will tell you exactly this. For example:

$ oe-pkgdata-util find-path /etc/network/interfaces
init-ifupdown: /etc/network/interfaces

Wildcards are allowed anywhere in the path (but you should enclose such expressions in quotes to avoid the shell itself attempting to expand the wildcard):

$ oe-pkgdata-util find-path "*/fstrim"
util-linux-bash-completion: /usr/share/bash-completion/completions/fstrim
util-linux-ptest: /usr/lib/util-linux/ptest/fstrim
util-linux-dbg: /sbin/.debug/fstrim
util-linux-fstrim: /sbin/fstrim

As a specific example of where this can be useful, our Python packaging is a bit more granular than most typical distributions, allowing you to tune the contents of your image to just what you need. However, that does mean you may have trouble figuring out which package provides a particular module. oe-pkgdata-util find-path can also be used for this. For example, to find the package containing the "shutil" module, run this:

$ oe-pkgdata-util find-path "*/shutil.*"
python3-shell: /usr/lib/python3.5/shutil.py
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-2.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.opt-1.pyc
python3-shell: /usr/lib/python3.5/__pycache__/shutil.cpython-35.pyc

Thus the package you are looking for is python3-shell. (Note that you could use */shutil.py, but if the module you are looking for is written in C as some of them are, that won't match it.)

=== I have a local source tree I want to build instead of the upstream source a recipe normally fetches, how do I do that? ===

If it's for development purposes i.e. you have your own local source tree you want to work on and have built, then run:

devtool modify -n <recipename> path/to/sourcetree/

Once you are done you can use <code>devtool finish</code> or <code>devtool reset</code> (depending on the situation) to return to building the source specified in the recipe.

Alternatively if it's more permanent, use the <code>externalsrc</code> class - you can inherit this in the original recipe or a bbappend:

inherit externalsrc
EXTERNALSRC = "/path/to/sources"

If you're going to use it across a number of recipes you can inherit it globally at the configuration level (perhaps via an inc file that you include/require there):

INHERIT += "externalsrc"
EXTERNALSRC_pn-<recipename> = "/path/to/sources"

=== How do I specify the default shell? (e.g. bash instead of busybox) ===

It depends what you mean. As far as which provides /bin/sh, this is controlled through the alternatives system, and by default bash has a higher priority than busybox, so simply installing bash into your image will automatically have /bin/sh link to bash rather than busybox.

If you mean you want a user's login shell to be a specific shell, you'll need to modify /etc/passwd. One fairly easy way to achieve this is to use the extrausers class in your image recipe:

inherit extrausers
EXTRA_USERS_PARAMS = "usermod -s /bin/bash <username>; "

=== How do I get "full" versions of typical shell commands? ===

Most of the shell commands in our images are provided by busybox by default, and are very much simplified compared to what you would have on a typical Linux system in order to save space. If you need the full versions, most of them are built and packaged by the coreutils recipe (for disk and other typical utilities) and procps (for ps, etc). You may also want to install bash for more typical shell built-in commands. There is also a core-image-full-cmdline image if you want a base image that is already set up to provide a more typical Linux command-line experience. (Note: these will of course use up more disk space and memory.)

=== How do I allow a variable's value through from the external environment? ===

Add the variable's name to the BB_ENV_EXTRAWHITE ''in the external environment'' before running bitbake. Note that the oe-init-build-env script sets a default for this which you will want to preserve, so add to the default value rather than overwriting it.

Alternatively if you just want to get the external value of a variable from python code within the metadata, you can use the BB_ORIGENV variable which itself contains a datastore of the original environment. For example to get the value of the DISPLAY variable from the environment within a python function you would do this:

display = d.getVar("BB_ORIGENV", False).getVar("DISPLAY", True)

Note that you must specify "false" for the expand parameter when getting the BB_ORIGENV variable, because it's not a string and therefore cannot be expanded in the normal manner.

=== Why is bitbake showing "AUTOINC" in the version for some recipes? ===

Recipes where you see AUTOINC within the version in the console output during a build will be those that set <code>PV</code> to include <code>"${SRCPV}"</code> to get the SCM revision (e.g. the git hash) in the package version. In order to have the version increment properly, there needs to be a number in front of the revision which automatically increments each time the revision changes (assuming you have a PR server enabled), which is where AUTOINC comes in. During the build, AUTOINC is a stand-in for this auto-incrementing number, and later during <code>do_package</code> it gets replaced with the real number so that the packages produced at the end have the full version number.

=== Why are .so files in the -dev package instead of the main package for a recipe? ===

In standard Unix library packaging, non-versioned .so symlinks (e.g. /usr/lib/libgd.so) are intended for development purposes only. At runtime, binaries should be linked to the major-versioned .so file/symlink e.g. /usr/lib/libgd.so.3. This (theoretically) allows multiple major versions of the same library as well as binaries that depend upon each of them to coexist on the same system. If the library is versioned but you have a binary that links to the unversioned .so file, it has almost certainly been linked incorrectly.

Non-symlink .so files on the other hand are sometimes produced and are entirely legal - however these will be picked up in the -dev package in OpenEmbedded simply by virtue of their name, which is almost always not what you want. In this case you can do one of two things:

# Fix the build of the library so it gets versioned. This may not always be appropriate, especially not for things like plugins.
# Set FILES_${PN}-dev within the recipe so that it does not include ${FILES_SOLIBSDEV}. If the software the recipe is building also produces symlink .so files you'll need to set FILES_${PN}-dev such that those do still get packaged in the -dev package though, or you'll get a package QA warning.

=== Can I disable shared state? ===

You cannot, no. Shared state is an intrinsic part of staging files into the sysroot. It is possible to construct a recipe that bypasses sstate for some tasks (the kernel does this), however this is quite difficult and if not done properly will lead to many other problems.

Almost always when you are having a problem with shared state the issue is either (a) you're adding/changing files in the sysroot directly (i.e. outside sstate control), or (b) what is being placed into the sysroot isn't relocatable. The solution for (a) is do not do that - files should always be installed under ${D} within do_install and then a subset of those are staged into the sysroot automatically. For (b) you need to fix or adapt the hardcoded path(s) - if the program reads (or can be made to read) each path from an environment variable, then you can use the create_wrapper utility function to create a wrapper script that will set the path appropriately. Run "git grep create_wrapper" in the meta subdirectory to see examples.

=== Files I installed into /opt or some other path never make it into the sysroot but I need them - how do I fix this? ===

OpenEmbedded only stages a subset of files that are installed into <code>${D}</code> by <code>do_install</code> so that the sysroot doesn't fill up with unneeded files. You have two choices in this situation:
# install the files into a more standard location which is part of the subset, or
# adjust the subset to include the paths you are installing to.
Usually option 1 is recommended. If you really do need to adjust the subset, you can append the path (more specifically, the part below <code>${D}</code>) to <code>SYSROOT_DIRS</code> within your recipe. For example:

SYSROOT_DIRS += "/opt"

=== I have some software which needs to build a binary that it then runs as part of its own build process, how do I make this work? ===

Whilst it is possible to do this within a single recipe building for the target, it is tricky to do so because in that context everything is set up for cross-compiling for the target, and you would have to undo all of that to build host tools. The standard and much easier way of handling this is to create a native variant of the recipe using BBCLASSEXTEND and have your host tools built within that, and then have the target variant depend on the native variant. For example, assume your recipe were called xyz (xyz_1.1.bb), then you would include something like this in the recipe:

DEPENDS_append_class-target = " xyz-native"

...

BBCLASSEXTEND += "native"

The host tools will then be built and installed into the sysroot in the native variant ready for when the target variant starts building. If the software you are building didn't intend for those tools to be installed outside of the build tree then you may need to patch the build process (e.g. the makefile) in order to install them and possibly also for the target side to find them in the sysroot. Additionally, for performance since you only need the tools in the native variant, you may also choose to disable building everything except those tools there - e.g. by using _native overrides for variables such as EXTRA_OECONF or functions such as do_configure.

=== How do I fetch from two git repositories in the same recipe? ===

By default, sources fetched from git within a recipe are unpacked into ${WORKDIR}/git, however that only works for a single repository. If you want to fetch from more than one, you need to change the path each repository is unpacked to. This is easy to do, just add <code>;destsuffix=<subdir></code> to the end of each URL in SRC_URI (replacing <code><subdir></code> with the name of the subdirectory). You may then need to change S to match whichever of these you want to be considered the root of the source tree - or alternatively you can specify destsuffix such that repositories beyond the first go into a subdirectory under the default "git" subdirectory. For example, from the gst-libav recipe:

...
SRC_URI = " \
git://anongit.freedesktop.org/gstreamer/gst-libav;branch=1.8;name=base \
git://anongit.freedesktop.org/gstreamer/common;destsuffix=git/common;name=common \
...
"
...
S = "${WORKDIR}/git"
...

(Here we're using the default of "git" for the first repository, so we don't need to specify <code>destsuffix</code> for the first URL.)

=== I'm building a native recipe and I notice that the install path has the full path to the root directory repeated - why? ===

It does look a little odd, but the reason for doing this is that native targets are meant to run on the system they're built on and run in the location they're installed to. This means they install to a destination of "/" and PREFIX is inside the native sysroot directory. We install them to a DESTDIR to allow us to manipulate them before they then get moved to a final DESTDIR of "/".

Most Makefiles handle this correctly by doing:

DESTDIR ?= ""
prefix ?= "/usr"
bindir ?= "$(prefix)/bin"

and then, importantly, install in the form:

install -d $(DESTDIR)$(bindir)

so both prefix and DESTDIR are used. Whilst this is a convention, its a widely adopted and followed one. You can call into a custom makefile and set the variables manually if the makefile doesn't follow the convention.

=== How do I generate static libraries? ===

Its possible you have conf/distro/include/no-static-libs.inc included in your build - poky does this by default. The include list at the top of the bitbake -e output will tell you for certain.

If so, you can remove that or set:

DISABLE_STATIC = ""

as it would currently be set to this if that include file is included:

DISABLE_STATIC = " --disable-static"

Poky disables building static libraries by default as for the most part they're a waste of space/time.

=== Can I conditionally inherit a class in a recipe? ===

Yes, you can. What makes this possible is that the <code>inherit</code> keyword will not complain if what comes after it expands to being empty, so you can use in-line python to do something like this:

<pre><nowiki>
inherit ${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}
</nowiki></pre>

The above example will inherit the <code>perlnative</code> class if "scripting" is in the value of the <code>PACKAGECONFIG</code> variable, otherwise it will do nothing.

You could of course put this into a variable if you prefer:

<pre><nowiki>
SOMEVAR = "${@bb.utils.contains('PACKAGECONFIG', 'scripting', 'perlnative', '', d)}"
inherit ${SOMEVAR}
</nowiki></pre>

=== How do I collect the source revisions fetched by each recipe? ===

If you have recipes where <code>SRCREV = "${AUTOREV}"</code> then you won't necessarily know exactly which revisions were built after the fact - it will be whatever was current at the time. You also might alternatively just want to get all of the revisions. Either way, to do this, enable buildhistory by setting the following in your local.conf:

<pre><nowiki>
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
</nowiki></pre>

(The last line is not required with version 2.5 and onwards as it is the default, but will do no harm.)

Once you have enabled buildhistory, you then need to build your image again so that buildhistory has a chance to record history data for it. Following that you can run <code>buildhistory-collect-srcrevs</code> (with <code>-a</code> if you want to see all revisions, not just the ones where AUTOREV was used) and it will output the revisions in a form you can use in a .inc file that you can <code>require</code> from your configuration if you want to fix the build to those revisions.

For more information see the [https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#maintaining-build-output-quality Maintaining Build Output Quality] section of the Yocto Project Development manual, which covers the buildhistory class in detail.

=== How do I do an offline build with recipes that have <code>SRCREV = "${AUTOREV}"</code> set? ===

If you set <code>BB_NO_NETWORK = "1"</code> and you have recipes that have <code>SRCREV = "${AUTOREV}"</code>, you will get an error because the build system will try to check the latest revision on startup and be immediately blocked by <code>BB_NO_NETWORK</code>. There are two ways to handle this:

A) See the previous question "How do I collect the source revisions fetched by each recipe?" and use the output generated by <code>buildhistory-collect-srcrevs</code> as a .inc file in your configuration in order to fix the revisions at the ones which were most recently built.

or

B) Set <code>BB_SRCREV_POLICY = "cache"</code> in your configuration. This will use the last cached revision. (The disadvantage of this method is that it is a little more difficult to preserve or share with others the fixed revisions.)

Note that in either case if you later want to build the latest version again, you will of course need to undo the configuration changes.

=== Is it possible to append a bbclass file (like bbappends do for recipes)? ===

No, see the next question for details.

=== How do I override a bbclass file? ===

This is tricky - bbclass files are found via BBPATH, which is added to by each layer.conf either by prepending or appending. Assuming you are putting your bbclass in a custom layer, you will probably want to have your layer's layer.conf prepend to BBPATH, but then you will also need to make sure that your layer does not appear before any other layer that is also prepending and overriding the same class.

Another alternative is to have an additional class which makes the appropriate changes to the environment, and then you will need to inherit that class after (and in the same manner as) the original class. This is slightly cleaner but can be annoying to enable particularly if the class is inherited by a number of recipes, and won't work if you want to alter the behaviour of a class inherited by recipes you don't control. (If you want a class to be inherited for all images (i.e. all recipes inheriting the <code>image</code> class) you can inject additional classes by setting IMAGE_CLASSES; similarly for the kernel there is KERNEL_CLASSES).

Ultimately, overriding bbclass files is not good practice long term - you are opening yourself up to maintenance issues when the original class changes, and the override is fragile as hinted above. The best solution is to try to get whatever changes you need into the original class; this does of course require additional work and time though.

=== There's a bbappend in a layer I'm using that defines a <code>do_something_append()</code> and I want to append to that function also, how do I do this? ===

Simply create a bbappend in your layer and define your own <code>do_something_append()</code>, and your commands will be executed ''as well as'' those of the other bbappend.

You might assume that defining <code>do_something_append()</code> will overwrite any previously defined <code>do_something_append()</code>, as would be the case with <code>do_something()</code> in the same situation, but that is not the case - the key is that <code>_append</code> (and <code>_prepend</code>, <code>_remove</code>, etc.) are ''operators'' and they will be applied in sequence, where that sequence is the order in which they are parsed (which for bbappends will be in ascending layer priority order).

Stable branch maintenance

2020-03-11T03:29:59Z

PaulEggleton: Fix internal linking

The Yocto Project maintains stable branches of Poky (OE-Core and BitBake). Typically, alongside the latest release the previous two releases are also maintained.

== Stable branch maintainers ==

{| class="wikitable"
! Major version
! Current Version
! Branch name
! BitBake version
! Maintainer
|-
| 3.2
| Dreaming
| Gatesgarth
| 1.48
| Richard Purdie <richard.purdie@linuxfoundation.org>
|-
| 3.1
| Dev
| Dunfell
| 1.46
| Richard Purdie <richard.purdie@linuxfoundation.org>
|-
| 3.0
| 3.0.2
| Zeus
| 1.44
| Anuj/Armin
|-
| 2.7
| 2.7.3
| Warrior
| 1.42
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
| 2.6
| 2.6.4
| Thud
| 1.40
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
| 2.5
| 2.5.3
| sumo
| 1.38
| Armin Kuster <akuster808@gmail.com>
|- style="color: slategray;"
| 2.4
| 2.4.4
| rocko
| 1.36
| Armin Kuster <akuster808@gmail.com>
|- style="color: slategray;"
|2.3
|2.3.4
|pyro
|1.34
|Armin Kuster <akuster808@gmail.com>
|- style="color: slategray;"
|2.2
|2.2.4
|morty
|1.32
|Armin Kuster <akuster808@gmail.com>
|- style="color: slategray;"
|2.1
|2.1.3
|krogoth
|1.30
|Armin Kuster <akuster808@gmail.com>
|- style="color: slategray;"
|2.0
|2.0.3
|jethro
|1.28
|Robert Yang <liezhi.yang@windriver.com>
|- style="color: slategray;"
|1.8
|1.8.2
|fido
|1.26
|Joshua Lock <joshua.g.lock@intel.com>
|- style="color: slategray;"
|1.7
|1.7.3
|dizzy
|1.24
|Armin Kuster <akuster808@gmail.com>
|- style="color: slategray;"
|1.6
|1.6.3
|daisy
|1.22
|Saul Wold <sgw@linux.intel.com>
|- style="color: slategray;"
|1.5
|1.5.4
|dora
|1.20
|Robert Yang <liezhi.yang@windriver.com>
|- style="color: slategray;"
|1.4
|1.4.3[http://lists.yoctoproject.org/pipermail/yocto/2014-July/020699.html *]
|dylan
|1.18
|Paul Eggleton <paul.eggleton@linux.intel.com>
|- style="color: slategray;"
|1.3
|1.3.2
|danny
|1.16
|Ross Burton <ross.burton@intel.com>
|- style="color: slategray;"
|}

(Versions in <font color="slategray">grey</font> above are no longer actively maintained, but well-tested patches may still be accepted for them.)

== Policies ==
See [[Stable Release and LTS]].

Stable Release and LTS

2020-03-11T03:27:38Z

PaulEggleton: Fix internal linking

= Yocto Project Stable Branch Maintenance and Long Term Support (LTS) =

Background on how the project's LTS plans came about can be found [[LTS_Background | here]]. The document below details the current project release lifecycle and LTS plans. The aim is to have a stable series maintenance policy which allows for different stages of maintenance including standard "stable" series, LTS series and community support.

'''[[Stable branch maintenance|Current Maintainers list]]'''

== Release Lifecycle ==
The project releases every six months in April and October (spring and fall). This is necessary to bring development together to a focus point and provide points of increased testing and focus on stability. There are two possible lifecycles a release may follow:

Initial Release -> Stable -> Community -> EOL
:: or
Initial Release -> LTS -> Community -> EOL

The change in status of a given release series should be announced in the weekly status report and reflected on the “Releases” wiki page.

The stages have the following properties:

'''Stable/LTS common properties:'''
* Has point release tarballs created
* Has release artefacts
* Patches merged to the main repository branch
* Requires autobuilder testing
* The project will appoint someone to act as the maintainer to coordinate and handle patch testing and merging
* Strict “backport only”, master first policy

'''Stable/LTS differences:'''
* Stable releases are maintained for seven months
* LTS releases are maintained initially for two years
* LTS releases are preannounced and known to be LTS in advance (usually every two years)
* LTS tested only on a subset of supported native build platforms (announced at time of LTS)

'''Community status properties:'''
* Branches only have community support status if there is an active community member willing to step into the maintainer role for that series
* Patches merge to the main repository but in a community/XXX namespace
* Automated testing is on a best effort basis, some autobuilder cycles may be available but not guaranteed.
* The maintainer is required to publish a testing plan to show what testing will be made for patches to merge to the community branch.
* No point releases version and no release artefacts
* Master first policy recommended

'''EOL (End of life):'''
* When there is no longer any active community maintainer, branches become EOL

== LTS “Mixin” repositories ==
We realise that a given LTS may need other versions of some components within its lifetime as no “one size” fits everyone’s needs. Rather than adding potentially invasive changes to older releases (such as new gcc versions), the project proposes the use of “mixin” layers. These would be thin specific purpose layers which can be stacked with an LTS release to mix a specific feature into that build. These are to be created on an as needed basis and maintained by the people who need them. The structure would be to create them in the repository oecore-backport-mixin with the branch naming scheme <releaseseries>/<mixin name>. We expect this may be used for gcc and possibly for rapidly changing languages like go/nodejs/rust. Policies on testing these layers will depend on how widespread their usage is and determined on a case by case basis. There may be other 'mixin' layers within the wider community too.

The layers should have a single purpose and be Yocto Project Compatible (passing the test script) allowing them to be selected by users as needed. The maintainer should be listed in the README and note when the layer is no longer maintained.

== Stable/LTS Patch Acceptance Policies ==
All changes must have already been accepted into the current master release and any other release still within its “stable” seven month support window.

Patches must pass testing on the project’s automated test infrastructure.

'''Acceptable:'''
* Security and CVE fixes
* Fixes for bugs
* Changes to follow an upstream stable series or LTS that aligns with the original release (based on compatibility)

'''Potentially Acceptable:'''
* Fixes so codebase works with newly released distros (only in the first six months after a given release series first releases)
* Bug fix only version upgrades for upstreams with a good stable process

'''Unacceptable:'''
* General version upgrades
* New features
* ABI/API breakage

== Components (layers) to be covered ==

The project LTS covers:
* Bitbake
* OE-Core
* Meta-yocto
* yocto-docs

The project LTS does not cover:
* meta-mingw
* meta-gplv2
* vendor layers

Other layers can and will have their own LTS processes.

== Testing ==
The project releases are only tested using the automated testing based on virtual environments. The build host OSes used to run these tests are determined at the initial release time. For LTS releases only some subset of native OSes maybe supported, particularly where the lifetime of the OS would be shorter than the LTS.

Further testing of releases, e.g. on real hardware platforms is encouraged and there is a process to allow these results to be merged into the release test results but the process for making the release no longer depends upon this happening.

== Process ( TOC)==
* Need to document the following processes:
** How maintainer is selected
** How are patches proposed - Done
** How are patches queued/tested/reviewed/merged - Done
** When are point releases made? - Done
** How to trigger and run a point release - Done
** Release process itself
** Transferring stable/LTS release to community/EOL status - YP TSC
** New maintainer training - TBD

== Requesting a fix in a stable branch ==

With reference to the above policies, if you would like to request a backport of a commit in a newer release, you can either (a) do the backport yourself and send the patch marked with <tt>[branchname]</tt> to the appropriate mailing list; or alternatively (b) you can send a simple request giving commit hashes / URLs that you would like to be backported. In both cases it helps to CC the maintainer - refer to the [[Stable branch maintenance|stable release table]].

For information on which mailing list you should send these to see the [http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/README README file] in the Poky repository.

== '''Maintainer Procedures''' ==

=== Normal process ===

When there are enough changes (or a few critical ones), the stable/LTS maintainer should follow this procedure:

# Look out for patches on the mailing list marked with the appropriate branch name in the subject
# Look through recently merged patches in master that are suitable for backporting
# Collect patches together on a branch
#* If a submitted patch is a backport from master, rather than taking the patch as submitted, it is preferable to backport the patch from master so that the original commit message is preserved.
#* If you do the backporting from poky you will get the original commit ID in the commit message which is useful for reference.
#* It is beneficial to change the original commit ID line to say "OE-Core master rev" instead of "OE-Core rev" to distinguish it from the OE-Core branch revision that will be added when the commit is merged
# Run a local build or two to pick up any obvious problems
# Bitbake change should be in the bitbake-contrib repo
## https://git.openembedded.org/bitbake-contrib stable/{branch}-nut
# Openembedded-core changes should be be in the openembedded-core-contrib stable/{branch}-nut
## https://git.openembedded.org/openembedded-core-contrib
# Meta-yocto changes should be in poky-contrib meta-yocto/stable/{branch}-nut
## git://git.yoctoproject.org/poky-contrib
# yocto-docs changes should be in poky-contrib yocto-docs/stable/{branch}-nut
## git://git.yoctoproject.org/poky-contrib
#Now create your Poky distro for testing.
## The Autobuilder requires changes to reside in poky, bitbake and openembedded-core
## Combine bitabke, core, meta-yocto and yocto-docs changes into one repo.
## Push the changes to poky-contrib stable/{branch}-nut
## git://git.yoctoproject.org/poky-contrib
# Test the changes on the autobuilder (see [[How to start a build on the Autobuilder]])
#* Make sure you check directly for the results of the build as these won't be reported to the yocto-builds mailing list.
## For any build failure, Defects should be opened
## Address any build failures, update repo's accordingly and rebuild

There will very likely be a number of these cycles during the lifetime of the stable branch.

=== Patch review ===
# When collating patches for review, Make sure of the following:
## Subject indicates "Patch review"
## Provide a deadline for any comments included in the body of the email
## Standard to date is 2 days.
###Exception is if the changes are patches sent to the appropriate mailing list.
## Use the appropriate branch reference.
## Use create-pull-request -p "{branch}" ...{etc}
# Send any bitbake changes bitbake-devel mailing list
# Send any OE-Core changes openembedded-core mailing list.
# Send any meta-yocto changes to the poky@lists.yoctoproject.org mailing list.
# Send any yocto-docs changes the docs@lists.yoctoproject.org mailing list.
# Wait for any feedback
## If there are changes make any necessary adjustments
### rebuild if necessary
# Push any changes to the appropriate repos and branches.

=== Merge request===
# Push affected repos and branches to stable/{branch}-next branch
# When preparing patches for merge, Make sure of the following:
## Subject indicates "Merge Request"
## Use the appropriate branch reference.
## Use create-pull-requests -p"{branch}"
# Send any bitbake changes bitbake-devel mailing list
# Send any OE-Core changes openembedded-core mailing list.
# Send any meta-yocto changes to the poky@lists.yoctoproject.org mailing list.
# Send any yocto-docs changes the docs@lists.yoctoproject.org mailing list.
# When the patches are merged, mark any bugs specific to the stable branch as resolved as appropriate

=== Point release ===

Normally point releases are scheduled in advance as appropriate - contact Stephen Jolley <sjolley.yp.pm@gmail.com> and CC: Ricard Purdie <richard.purdie@linuxfoundation.org> about scheduling point releases.

# Update yocto-docs with release information.
## Send a patch to docs@lists.yoctoproject.org
# Once all dot release changes are merged, ask Richard to run the release candidate build
#* The stable branch or LTS maintainer should monitor the build and follow up on any failures
# When the release candidate build completes successfully, The stable branch or LTS maintainer should notify the QA team to start the release QA process.
# Gather together changes in the form needed for a release notes and send them Yocto Project TSC, Branch or LTS maintainer for review and approval.
## If acceptable the changes will be incorporated into the final release notes and to Stephen Jolley <sjolley.yp.pm@gmail.com> so he can have them in preparation for the release meeting.
# Send a patch to update the stable version in meta-yocto/conf/distro/poky.conf for the release

=== Other ===

* It is useful to provide status updates on the Yocto Project technical call, particularly coming up to a stable release. If you're not able to be on the call, send the status update information to Stephen Jolley <sjolley.yp.pm@gmail.com> and he will present it.

=== Releases ===
[[Releases|Yocto Project releases]]

=== Kernel LTS ===
[[Linux Yocto#Release_Cadence|Kernel cadence]]

=== New Releases process ===
[[Yocto Project Release Process|Standard release process]]

== Decision Makers==
Decisions are expected to be handled by the maintainers. The TSC holds the ultimate decision making authority in case of disagreement. The TSC makes the final release go/nogo decisions.

Project Users

2020-01-17T01:07:44Z

PaulEggleton:

It's hard to know which companies or projects use the Yocto Project since there is no requirement to tell us. This list is here to informally collate the companies, projects and products that use the Yocto Project in some way.

= Companies using the Yocto Project =

Semiconductor Vendors:
* AMD (Silver Member)
* ARM (Platinum Member)
* Intel (Platinum Member)
* NXP (Silver Member)
* Qualcomm
* Renesas (Gold Member)
* STMicroelectronics (Silver Member)
* Texas Instruments (Platinum Member)
* Xilinx (Platinum Member)

OSVs:
* ENEA (Silver Member)
* Linaro (Silver Member)
* Lineo (Silver Member)
* Mentor Graphics (Gold Member)
* Montavista (Silver Member)
* Wind River (Gold Member)

Others:
* Cisco (Platinum Member)
* Comcast (Platinum Member)
* Dell (Silver Member)
* Facebook (Platinum Member)
* Juniper (Gold Member)
* LG (Silver Member)
* Microsoft

= Products that use the Yocto Project =

* Comcast set top boxes
* LG TVs

= Projects that use the Yocto Project =

* Automotive Grade Linux (AGL)
* Comcast RDK
* OpenBMC
* Windows Subsystem Linux (v1+v2)

FutureMigrationGuide

2019-10-22T21:32:32Z

PaulEggleton:

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|This page should be used to keep track of items which should be added to the [http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration migration guide] in the YP Reference Manual. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.

Once the migration guide for a release has been completed the contents of this page should be cleared out.
|}

=3.0 Migration Guide items=

== Init system selection ==

Changing the init system manager previously required setting a number of different variables; this can now be accomplished by setting the INIT_MANAGER variable and corresponding include files (conf/distro/include/init-manager-*.conf); include files are provided for four values - "none", "sysvinit", "systemd" and "mdev-busybox". The default value "none" for INIT_MANAGER should allow your current settings to continue working, but it is advisable to set INIT_MANAGER explicitly.

== LSB support removed ==

LSB as a standard isn't current, and isn't well suited to embedded applications. Support may be continued in a separate layer if needed but at present it has been removed from the core.

Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

== Removed recipes ==

* core-image-lsb-dev: part of removed LSB support
* core-image-lsb: part of removed LSB support
* core-image-lsb-sdk: part of removed LSB support
* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
* gcc-8.3: version 8.3 removed (replaced by 9.2)
* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
* irda-utils: obsolete - IrDA support has been removed from the Linux kernel in version 4.17 and later.
* libnewt-python: libnewt Python support merged into main libnewt recipe
* libsdl: replaced by newer libsdl2
* libx11-diet: obsolete
* libxx86dga: remove obsolete client libary
* libxx86misc: remove this now redundant library
* linux-yocto: version 5.0 removed (5.2 / 4.19 present)
* lsbinitscripts: part of removed LSB support
* lsb: part of removed LSB support
* lsbtest: part of removed LSB support
* openssl10: replaced by newer openssl 1.1
* packagegroup-core-lsb: part of removed LSB support
* python-nose: remove the python 2.x version of the recipe
* python-numpy: remove the python 2.x version of the recipe
* python-scons: remove the python 2.x version of the recipe
* source-highlight: no longer needed
* stress: replaced by stress-ng
* vulkan: split into vulkan-loader, vulkan-headers and vulkan-tools
* weston-conf: functionality moved to weston-init

== Packaging changes ==

* The epiphany browser has been dropped from packagegroup-self-hosted as it has not been needed inside build-appliance-image for a long time and was causing resource problems.
* libcap-ng python support has been moved to a separate libcap-ng-python recipe to streamline the build process when the python bindings aren't needed
* libdrm now packages the amdgpu.ids file into a separate libdrm-amdgpu package
* python3: the runpy module is now in the python3-core package as it is required to support the common "python3 -m" command usage.
* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

== CVE checking ==

cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 scoring and makes other improvements.

Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

== Bitbake changes ==

* addtask statements now properly validate dependent tasks - previously an invalid task here would be silently ignored, now it will generate a warning.
* Other invalid addtask and deltask usages will now trigger warnings (multiple target tasks arguments with addtask / deltask, multiple before/after clauses)
* The "multiconfig" prefix is now shortened to "mc"; "multiconfig" will continue to work, however it may be removed in a future release.
* bitbake -g no longer generates a recipe-depends.dot file as the contents (a reprocessed version of task-depends.dot) were confusing.
* The bb.build.FuncFailed exception, previously raised by bb.build.exec_func() when certain other exceptions have occurred, has been removed. The real underlying exceptions will be raised instead. If you have calls to bb.build.exec_func() in custom classes or tinfoil-using scripts, any references to bb.build.FuncFailed should be cleaned up.
* Additionally, the bb.build.exec_func() no longer accepts the "pythonexception" parameter - it now always raises exceptions. Remove this argument in any calls to bb.build.exec_func() in custom classes or scripts.
* The BB_SETSCENE_VERIFY_FUNCTION2 is no longer used - in the unlikely event that you have any references to it, they should be removed.
* The RunQueueExecuteScenequeue and RunQueueExecuteTasks events have been removed since setscene tasks are now executed as part of the normal runqueue. Any event handling code in custom classes or scripts that handles these two events will need to be updated.
* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

== Sanity checks ==

* SRC_URI is now checked for usage of two problematic items:
*# "${PN}" - instead "${BPN}" should be used to avoid problems when PN is prefixed or suffixed e.g. with multiconfig.
*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
* The file-rdeps runtime dependency check no longer expands RDEPENDS recursively as there is no mechanism to ensure they can be fully computed, and thus races sometimes resulted in errors showing up and sometimes not. Thus you may now see errors for missing runtime dependencies that were previously satisfied recursively e.g. package A contains a shell script starting with #!/bin/bash but has no dependency on bash, but depends on package B that does depend on bash. Add the missing dependency / dependencies to resolve the warning.
* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

== Miscellaneous ==

* The gnome class has been removed, as it did not do very much anymore. Recipes that previously inherited this class should be updated to do the following:
inherit gnomebase gtk-icon-cache gconf mime
* The meta/recipes-kernel/linux/linux-dtb.inc file has been removed. It was previously deprecated (in favour of setting KERNEL_DEVICETREE in any kernel recipe) and only produced a warning. Remove any include/require statements pointing to this file.
* TARGET_CFLAGS, TARGET_CPPFLAGS, TARGET_CXXFLAGS, and TARGET_LDFLAGS are no longer exported to the external environment. This has not required changes to any recipes, but if for some reason the software being built by one of your recipes is expecting these variables to be set then it will now fail, and you will need to either export the variable(s) in the recipe or change the scripts so that that isn't necessary.
* The host distro identifier as used in NATIVELSBSTRING (when not using uninative) and SANITY_TESTED_DISTROS is now always lowercased even if it does not contain a version number.
* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. However, this should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.
* conf/distro/include/world-broken.inc has been removed - where we need to disable certain recipes when using the musl C library, individual recipes now have COMPATIBLE_HOST_libc-musl set with a comment explaining why.

3.0 Migration Guide

2019-10-22T21:32:14Z

PaulEggleton:

=Moving to the Yocto Project 3.0 Release=

This section provides migration information for moving to the Yocto Project 3.0 Release from the prior release.

== Init system selection ==

Changing the init system manager previously required setting a number of different variables; this can now be accomplished by setting the INIT_MANAGER variable and corresponding include files (conf/distro/include/init-manager-*.conf); include files are provided for four values - "none", "sysvinit", "systemd" and "mdev-busybox". The default value "none" for INIT_MANAGER should allow your current settings to continue working, but it is advisable to set INIT_MANAGER explicitly.

== LSB support removed ==

[http://en.wikipedia.org/wiki/Linux_Standard_Base LSB] as a standard isn't current, and isn't well suited to embedded applications. Support may be continued in a separate layer if needed but at present it has been removed from the core.

Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

== Removed recipes ==

* core-image-lsb-dev: part of removed LSB support
* core-image-lsb: part of removed LSB support
* core-image-lsb-sdk: part of removed LSB support
* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
* gcc-8.3: version 8.3 removed (replaced by 9.2)
* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
* irda-utils: obsolete - IrDA support has been removed from the Linux kernel in version 4.17 and later.
* libnewt-python: libnewt Python support merged into main libnewt recipe
* libsdl: replaced by newer libsdl2
* libx11-diet: obsolete
* libxx86dga: remove obsolete client libary
* libxx86misc: remove this now redundant library
* linux-yocto: version 5.0 removed (5.2 / 4.19 present)
* lsbinitscripts: part of removed LSB support
* lsb: part of removed LSB support
* lsbtest: part of removed LSB support
* openssl10: replaced by newer openssl 1.1
* packagegroup-core-lsb: part of removed LSB support
* python-nose: remove the python 2.x version of the recipe
* python-numpy: remove the python 2.x version of the recipe
* python-scons: remove the python 2.x version of the recipe
* source-highlight: no longer needed
* stress: replaced by stress-ng
* vulkan: split into vulkan-loader, vulkan-headers and vulkan-tools
* weston-conf: functionality moved to weston-init

== Packaging changes ==

* The epiphany browser has been dropped from packagegroup-self-hosted as it has not been needed inside build-appliance-image for a long time and was causing resource problems.
* libcap-ng python support has been moved to a separate libcap-ng-python recipe to streamline the build process when the python bindings aren't needed
* libdrm now packages the amdgpu.ids file into a separate libdrm-amdgpu package
* python3: the runpy module is now in the python3-core package as it is required to support the common "python3 -m" command usage.
* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

== CVE checking ==

cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 scoring and makes other improvements.

Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

== Bitbake changes ==

* addtask statements now properly validate dependent tasks - previously an invalid task here would be silently ignored, now it will generate a warning.
* Other invalid addtask and deltask usages will now trigger warnings (multiple target tasks arguments with addtask / deltask, multiple before/after clauses)
* The "multiconfig" prefix is now shortened to "mc"; "multiconfig" will continue to work, however it may be removed in a future release.
* bitbake -g no longer generates a recipe-depends.dot file as the contents (a reprocessed version of task-depends.dot) were confusing.
* The bb.build.FuncFailed exception, previously raised by bb.build.exec_func() when certain other exceptions have occurred, has been removed. The real underlying exceptions will be raised instead. If you have calls to bb.build.exec_func() in custom classes or tinfoil-using scripts, any references to bb.build.FuncFailed should be cleaned up.
* Additionally, the bb.build.exec_func() no longer accepts the "pythonexception" parameter - it now always raises exceptions. Remove this argument in any calls to bb.build.exec_func() in custom classes or scripts.
* The BB_SETSCENE_VERIFY_FUNCTION2 is no longer used - in the unlikely event that you have any references to it, they should be removed.
* The RunQueueExecuteScenequeue and RunQueueExecuteTasks events have been removed since setscene tasks are now executed as part of the normal runqueue. Any event handling code in custom classes or scripts that handles these two events will need to be updated.
* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

== Sanity checks ==

* SRC_URI is now checked for usage of two problematic items:
*# "${PN}" - instead "${BPN}" should be used to avoid problems when PN is prefixed or suffixed e.g. with multiconfig.
*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
* The file-rdeps runtime dependency check no longer expands RDEPENDS recursively as there is no mechanism to ensure they can be fully computed, and thus races sometimes resulted in errors showing up and sometimes not. Thus you may now see errors for missing runtime dependencies that were previously satisfied recursively e.g. package A contains a shell script starting with #!/bin/bash but has no dependency on bash, but depends on package B that does depend on bash. Add the missing dependency / dependencies to resolve the warning.
* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

== Miscellaneous ==

* The gnome class has been removed, as it did not do very much anymore. Recipes that previously inherited this class should be updated to do the following:
inherit gnomebase gtk-icon-cache gconf mime
* The meta/recipes-kernel/linux/linux-dtb.inc file has been removed. It was previously deprecated (in favour of setting KERNEL_DEVICETREE in any kernel recipe) and only produced a warning. Remove any include/require statements pointing to this file.
* TARGET_CFLAGS, TARGET_CPPFLAGS, TARGET_CXXFLAGS, and TARGET_LDFLAGS are no longer exported to the external environment. This has not required changes to any recipes, but if for some reason the software being built by one of your recipes is expecting these variables to be set then it will now fail, and you will need to either export the variable(s) in the recipe or change the scripts so that that isn't necessary.
* The host distro identifier as used in NATIVELSBSTRING (when not using uninative) and SANITY_TESTED_DISTROS is now always lowercased even if it does not contain a version number.
* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. However, this should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.
* conf/distro/include/world-broken.inc has been removed - where we need to disable certain recipes when using the musl C library, individual recipes now have COMPATIBLE_HOST_libc-musl set with a comment explaining why.

3.0 Migration Guide

2019-10-22T21:26:45Z

PaulEggleton:

=Moving to the Yocto Project 3.0 Release=

This section provides migration information for moving to the Yocto Project 3.0 Release from the prior release.

== Init system selection ==

Changing the init system manager previously required setting a number of different variables; this can now be accomplished by setting the INIT_MANAGER variable and corresponding include files (conf/distro/include/init-manager-*.conf); include files are provided for four values - "none", "sysvinit", "systemd" and "mdev-busybox". The default value "none" for INIT_MANAGER should allow your current settings to continue working, but it is advisable to set INIT_MANAGER explicitly.

== LSB support removed ==

[http://en.wikipedia.org/wiki/Linux_Standard_Base LSB] as a standard isn't current, and isn't well suited to embedded applications. Support may be continued in a separate layer if needed but at present it has been removed from the core.

Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

== Removed recipes ==

* core-image-lsb-dev: part of removed LSB support
* core-image-lsb: part of removed LSB support
* core-image-lsb-sdk: part of removed LSB support
* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
* gcc-8.3: remove 8.3 from zeus
* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
* irda-utils: obsolete - IrDA support has been removed from the Linux kernel in version 4.17 and later.
* libnewt-python: libnewt Python support merged into main libnewt recipe
* libsdl: replaced by newer libsdl2
* libx11-diet: obsolete
* libxx86dga: remove obsolete client libary
* libxx86misc: remove this now redundant library
* linux-yocto: version 5.0 removed
* lsbinitscripts: part of removed LSB support
* lsb: part of removed LSB support
* lsbtest: part of removed LSB support
* openssl10: replaced by newer openssl 1.1
* packagegroup-core-lsb: part of removed LSB support
* python-nose: remove the python 2.x version of the recipe
* python-numpy: remove the python 2.x version of the recipe
* python-scons: remove the python 2.x version of the recipe
* source-highlight: no longer needed
* stress: replaced by stress-ng
* vulkan: split into vulkan-loader, vulkan-headers and vulkan-tools
* weston-conf: functionality moved to weston-init

== Packaging changes ==

* The epiphany browser has been dropped from packagegroup-self-hosted as it has not been needed inside build-appliance-image for a long time and was causing resource problems.
* libcap-ng python support has been moved to a separate libcap-ng-python recipe to streamline the build process when the python bindings aren't needed
* libdrm now packages the amdgpu.ids file into a separate libdrm-amdgpu package
* python3: the runpy module is now in the python3-core package as it is required to support the common "python3 -m" command usage.
* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

== CVE checking ==

cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 scoring and makes other improvements.

Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

== Bitbake changes ==

* addtask statements now properly validate dependent tasks - previously an invalid task here would be silently ignored, now it will generate a warning.
* Other invalid addtask and deltask usages will now trigger warnings (multiple target tasks arguments with addtask / deltask, multiple before/after clauses)
* The "multiconfig" prefix is now shortened to "mc"; "multiconfig" will continue to work, however it may be removed in a future release.
* bitbake -g no longer generates a recipe-depends.dot file as the contents (a reprocessed version of task-depends.dot) were confusing.
* The bb.build.FuncFailed exception, previously raised by bb.build.exec_func() when certain other exceptions have occurred, has been removed. The real underlying exceptions will be raised instead. If you have calls to bb.build.exec_func() in custom classes or tinfoil-using scripts, any references to bb.build.FuncFailed should be cleaned up.
* Additionally, the bb.build.exec_func() no longer accepts the "pythonexception" parameter - it now always raises exceptions. Remove this argument in any calls to bb.build.exec_func() in custom classes or scripts.
* The BB_SETSCENE_VERIFY_FUNCTION2 is no longer used - in the unlikely event that you have any references to it, they should be removed.
* The RunQueueExecuteScenequeue and RunQueueExecuteTasks events have been removed since setscene tasks are now executed as part of the normal runqueue. Any event handling code in custom classes or scripts that handles these two events will need to be updated.
* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

== Sanity checks ==

* SRC_URI is now checked for usage of two problematic items:
*# "${PN}" - instead "${BPN}" should be used to avoid problems when PN is prefixed or suffixed e.g. with multiconfig.
*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
* The file-rdeps runtime dependency check no longer expands RDEPENDS recursively as there is no mechanism to ensure they can be fully computed, and thus races sometimes resulted in errors showing up and sometimes not. Thus you may now see errors for missing runtime dependencies that were previously satisfied recursively e.g. package A contains a shell script starting with #!/bin/bash but has no dependency on bash, but depends on package B that does depend on bash. Add the missing dependency / dependencies to resolve the warning.
* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

== Miscellaneous ==

* The gnome class has been removed, as it did not do very much anymore. Recipes that previously inherited this class should be updated to do the following:
inherit gnomebase gtk-icon-cache gconf mime
* The meta/recipes-kernel/linux/linux-dtb.inc file has been removed. It was previously deprecated (in favour of setting KERNEL_DEVICETREE in any kernel recipe) and only produced a warning. Remove any include/require statements pointing to this file.
* TARGET_CFLAGS, TARGET_CPPFLAGS, TARGET_CXXFLAGS, and TARGET_LDFLAGS are no longer exported to the external environment. This has not required changes to any recipes, but if for some reason the software being built by one of your recipes is expecting these variables to be set then it will now fail, and you will need to either export the variable(s) in the recipe or change the scripts so that that isn't necessary.
* The host distro identifier as used in NATIVELSBSTRING (when not using uninative) and SANITY_TESTED_DISTROS is now always lowercased even if it does not contain a version number.
* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. However, this should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.
* conf/distro/include/world-broken.inc has been removed - where we need to disable certain recipes when using the musl C library, individual recipes now have COMPATIBLE_HOST_libc-musl set with a comment explaining why.

3.0 Migration Guide

2019-10-22T21:24:19Z

PaulEggleton: Created page with "=Moving to the Yocto Project 3.0 Release= This section provides migration information for moving to the Yocto Project 3.0 Release from the prior release. == Init system sel..."

=Moving to the Yocto Project 3.0 Release=

This section provides migration information for moving to the Yocto Project 3.0 Release from the prior release.

== Init system selection ==

Changing the init system manager previously required setting a number of different variables; this can now be accomplished by setting the INIT_MANAGER variable and corresponding include files (conf/distro/include/init-manager-*.conf); include files are provided for four values - "none", "sysvinit", "systemd" and "mdev-busybox". The default value "none" for INIT_MANAGER should allow your current settings to continue working, but it is advisable to set INIT_MANAGER explicitly.

== LSB support removed ==

LSB as a standard isn't current, and isn't well suited to embedded applications. Support may be continued in a separate layer if needed but at present it has been removed from the core.

Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

== Removed recipes ==

* core-image-lsb-dev: part of removed LSB support
* core-image-lsb: part of removed LSB support
* core-image-lsb-sdk: part of removed LSB support
* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
* gcc-8.3: remove 8.3 from zeus
* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
* irda-utils: obsolete - IrDA support has been removed from the Linux kernel in version 4.17 and later.
* libnewt-python: libnewt Python support merged into main libnewt recipe
* libsdl: replaced by newer libsdl2
* libx11-diet: obsolete
* libxx86dga: remove obsolete client libary
* libxx86misc: remove this now redundant library
* linux-yocto: version 5.0 removed
* lsbinitscripts: part of removed LSB support
* lsb: part of removed LSB support
* lsbtest: part of removed LSB support
* openssl10: replaced by newer openssl 1.1
* packagegroup-core-lsb: part of removed LSB support
* python-nose: remove the python 2.x version of the recipe
* python-numpy: remove the python 2.x version of the recipe
* python-scons: remove the python 2.x version of the recipe
* source-highlight: no longer needed
* stress: replaced by stress-ng
* vulkan: split into vulkan-loader, vulkan-headers and vulkan-tools
* weston-conf: functionality moved to weston-init

== Packaging changes ==

* The epiphany browser has been dropped from packagegroup-self-hosted as it has not been needed inside build-appliance-image for a long time and was causing resource problems.
* libcap-ng python support has been moved to a separate libcap-ng-python recipe to streamline the build process when the python bindings aren't needed
* libdrm now packages the amdgpu.ids file into a separate libdrm-amdgpu package
* python3: the runpy module is now in the python3-core package as it is required to support the common "python3 -m" command usage.
* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

== CVE checking ==

cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 scoring and makes other improvements.

Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

== Bitbake changes ==

* addtask statements now properly validate dependent tasks - previously an invalid task here would be silently ignored, now it will generate a warning.
* Other invalid addtask and deltask usages will now trigger warnings (multiple target tasks arguments with addtask / deltask, multiple before/after clauses)
* The "multiconfig" prefix is now shortened to "mc"; "multiconfig" will continue to work, however it may be removed in a future release.
* bitbake -g no longer generates a recipe-depends.dot file as the contents (a reprocessed version of task-depends.dot) were confusing.
* The bb.build.FuncFailed exception, previously raised by bb.build.exec_func() when certain other exceptions have occurred, has been removed. The real underlying exceptions will be raised instead. If you have calls to bb.build.exec_func() in custom classes or tinfoil-using scripts, any references to bb.build.FuncFailed should be cleaned up.
* Additionally, the bb.build.exec_func() no longer accepts the "pythonexception" parameter - it now always raises exceptions. Remove this argument in any calls to bb.build.exec_func() in custom classes or scripts.
* The BB_SETSCENE_VERIFY_FUNCTION2 is no longer used - in the unlikely event that you have any references to it, they should be removed.
* The RunQueueExecuteScenequeue and RunQueueExecuteTasks events have been removed since setscene tasks are now executed as part of the normal runqueue. Any event handling code in custom classes or scripts that handles these two events will need to be updated.
* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

== Sanity checks ==

* SRC_URI is now checked for usage of two problematic items:
*# "${PN}" - instead "${BPN}" should be used to avoid problems when PN is prefixed or suffixed e.g. with multiconfig.
*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
* The file-rdeps runtime dependency check no longer expands RDEPENDS recursively as there is no mechanism to ensure they can be fully computed, and thus races sometimes resulted in errors showing up and sometimes not. Thus you may now see errors for missing runtime dependencies that were previously satisfied recursively e.g. package A contains a shell script starting with #!/bin/bash but has no dependency on bash, but depends on package B that does depend on bash. Add the missing dependency / dependencies to resolve the warning.
* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

== Miscellaneous ==

* The gnome class has been removed, as it did not do very much anymore. Recipes that previously inherited this class should be updated to do the following:
inherit gnomebase gtk-icon-cache gconf mime
* The meta/recipes-kernel/linux/linux-dtb.inc file has been removed. It was previously deprecated (in favour of setting KERNEL_DEVICETREE in any kernel recipe) and only produced a warning. Remove any include/require statements pointing to this file.
* TARGET_CFLAGS, TARGET_CPPFLAGS, TARGET_CXXFLAGS, and TARGET_LDFLAGS are no longer exported to the external environment. This has not required changes to any recipes, but if for some reason the software being built by one of your recipes is expecting these variables to be set then it will now fail, and you will need to either export the variable(s) in the recipe or change the scripts so that that isn't necessary.
* The host distro identifier as used in NATIVELSBSTRING (when not using uninative) and SANITY_TESTED_DISTROS is now always lowercased even if it does not contain a version number.
* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. However, this should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.
* conf/distro/include/world-broken.inc has been removed - where we need to disable certain recipes when using the musl C library, individual recipes now have COMPATIBLE_HOST_libc-musl set with a comment explaining why.

3.0 Release Notes WIP

2019-10-18T13:15:33Z

PaulEggleton: Reorder and add bits to be closer to final release notes

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|NOTE: The formatting in this page is not meant to look good in the wiki - it's just a convenient place to collaborate. We need to stick to the text formatting that will end up in the actual release notes.
|}

-----------------------
yocto-3.0 Release Notes
-----------------------

----------
Downloads
----------

---------------------------
New Features / Enhancements
---------------------------
* Linux kernel 5.2/4.19, gcc 9.2, glibc 2.30 and ~260 other recipe upgrades
* Build change equivalence is detected and used to avoid rebuilding unchanged components (BETA)
* Architecture / machine-specific enhancements:
- New "qemuriscv64" emulated RISC-V 64-bit machine
- qemu: Add ppc64 to QEMU_TARGETS
- qemuarm64: Add QB_CPU_KVM to allow kvm acceleration
- New tune file for ARM Cortex-A53-Cortex-A57
- New tune file for arm1176jz-s CPU
- meson.bbclass: Handle microblaze* mapping to cpu family
- meson.bbclass: Make meson support aarch64_be.
- libffi: added RISC-V support
- icu: added armeb support
- runqemu: added support for kvm on aarch64
- beaglebone-yocto machine now set up to support booting images with runqemu
- qemux86: make it possible to use higher tunes using DEFAULTTUNE
* Kernel improvements:
- kernel-fitimage: introduce FIT_HASH_ALG
- kernel-module-split.bbclass: support CONFIG_MODULE_COMPRESS=y
- kernel-yocto: import security fragments from meta-security
- linux-yocto: add drm-bochs support
- linux-yocto: bsp/beaglebone: support qemu -machine virt
* multiconfig builds now reach their full potential:
- Many bugfixes and improvements
- sstate cache is now shared between configurations being built concurrently
- multiconfig configurations can be contained in layers
* Significant removal of old/obsolete software/patches ensuring we have a modern and up to date core Linux software stack:
- LSB support removed
- GTK+ 2 moved out to meta-oe
- Python 2 dependencies minimised
- Many obsolete patches dropped
* CVE checking enhancements:
- New cve-update-db recipe that reads from NVD JSON data feeds and supports network proxies
- Support for CVSSv3 scoring
- CVE_PRODUCT entries can now contain strings to match the vendor as well as product (vendor:product syntax)
* New INIT_MANAGER variable to make it easy to select the init manager (sysvinit, systemd, mdev-busybox)
* New recipes: binutils-cross-testsuite, core-image-sato-ptest-fast, dejagnu, efibootmgr, efivar, ell, glibc-testsuite, libcap-ng-python, libedit, libmodule-build-perl, libx11-compose-data, libxcrypt-compat, lsb-release, musl-obstack, opensbi, python3-pygments, python3-scons, python3-scons-native, stress-ng, vulkan-headers, vulkan-loader, vulkan-tools, wireless-regdb
* Added native variant to: glib-networking, grub, libsoup, python3-dbus
* BitBake improvements:
- Merged setscene tasks into the main runqueue so they can run in parallel
- fetch2/git: added sanity checking for git-lfs
- fetch2/svn: prevent from directly pulling from an externals w/o fetcher
- fetch2/npm: use npm pack to download node modules instead of wget
- Added --skip-setscene option
- Respect -f/--force option in conjunction with --runall or --runonly
- bitbake -e now supports showing base multiconfig configuration (using mc: prefix)
- "mc:" prefix now supported as a shorter version of multiconfig:
- Print more information when basehashes are mismatched
- Show task elapsed time in hours, minutes, and seconds
- Report all nonexistent directories in BBLAYERS in error message instead of just the first
- Improve validation of addtask and deltask arguments
- Added support for custom progress handlers injected via OE_EXTRA_IMPORTS
- Enable console keepalive to help usage with remote sessions
- Symlink the current cache file
* systemd-related improvements:
- serial-getty@.service: Allow device to fast fail if it does not exist
- Rewrote systemctl-native in Python supporting preset-all and mask
- Added partial support of drop-in configuration files to systemd-systemctl-native
- systemd-conf: added default configuration for wired network with DHCP
- systemd-conf: simplified creation of machine-specific configuration
- Create preset files and allow systemd to populate /etc/systemd/system instead of populating explicitly
- Added systemd helper unit to load/restore iptables rules
* runqemu improvements:
- Added support to pass multiple ports to tcpserial parameter
- Added support for a BIOS command-line variable (consistent with KERNEL)
- New QB_FSINFO variable supporting "wic:no-kernel-in-fs" and "wic:kernel-in-fs" for wic images
- Added support to handle EnrollDefaultKeys PK/KEK1 certificate
- Decoupled gtk and gl options
* wic improvements:
- New partition type for msdos partition tables
- New "bootimg-biosplusefi" source type that supports both BIOS and EFI
- Support for kernel with initramfs bundled
- bootimg-efi: add label source parameter
- bootimg-efi: allow multiple initrd
- bootimg-efi: replace hardcoded volume name with label
- Include .wks.in in wic search and list
- Use KERNEL_IMAGETYPE instead of hardcoding bzImage
- Added global debug option
* Other image-related improvements:
- Centralised default UEFI image configuration in conf/distro/image-uefi.conf
- Make gzipped images rsyncable
- initramfs-framework: support PARTLABEL option
- New bash-completion IMAGE_FEATURES item to add bash-completion support for all installed packages
* devtool/recipetool improvements:
- New "devtool menuconfig" subcommand
- devtool build now also runs do_deploy if applicable
- devtool finish now supports a --no-clean option
- devtool finish now warns if multiple layers have the same base name
- recipetool now supports creating recipes for Python 3
* Other script improvements:
- buildstats-diff: added option to filter tasks
- bitbake-layers: added several options to to make it easier to get plain output (for scripting)
- ddimage: replaced target device blacklist with mount check
- yocto-check-layer: Allow any case for README file detection
* SDK-related changes:
- New SDK_ARCHIVE_TYPE variable to control SDK archive format
- Introduce mechanism to keep nativesdk* sstate in eSDK
- Added nativesdk variant to: dnf, gzip, libtasn1, python3-dbus
- Use the best xz compression for the SDK
* buildhistory improvements:
- Record sysroot changes in addition to runtime content
- Show time spent writing buildhistory
* Recipe sanity checking improvements:
- Added check to ensure perllocal.pod is not installed by non-CPAN perl recipes
- Added sanity checks for ${PN} vs ${BPN} and github archives in SRC_URI
- Check if a recipe incorrectly uses DEPENDS_${PN}
- Improved buildpath warning messages
- Simplified paths in host contamination warnings
* Automated testing improvements:
- Enabled test suites for gcc, glibc, binutils
- Add ptest ptest support to elfutils, m4, gettext
- Fixes for many ptest test failures
- testimage: consider QB_DEFAULT_FSTYPE
- oe-selftest: implement console keepalive output
- Support for LTP / LTP compliance
- Added core-image-sato-ptest-fast image to execute 'fast' subset of ptests
- resulttool: Add log subcommand
- resulttool: enable loading results directly from an http/https URL
- resulttool: add manual test case configuration option
- resulttool: Add option to dump all ptest logs
* poky-lsb replaced by poky-altcfg for alternate configurations to be tested on the autobuilder (as well as an example of subclassing a distro config)
* Added minver and maxver parameters for patches in SRC_URI for more flexibility in bbappends and common inc files
* PRIVATE_LIBS variable now supports shell-style wildcards for matching libraries
* Adoption of SPDX license identifiers throughout Yocto Project's components
* Added bbverbnote shell log command (consistent with bbwarn, bberror etc.)
* New OE_EXTRA_IMPORTS variable to make it easier to import custom modules into BitBake python environment
* busybox: enabled unicode support by default
* cmake: Use compiler launcher variable when ccache is enabled so that it can be disabled by build scripts if needed
* db: add new "verify" PACKAGECONFIG option for enabling database verification with db_verify command (default disabled)
* distcc: split into client and server packages
* dropbear: new "disable-weak-ciphers" PACKAGECONFIG option to disable older weak ciphers
* grub-efi-native: install grub-editenv
* lttng-modules: added git based recipe
* opkg: allow overriding OPKGLIBDIR
* ovmf: Generate test Platform key and first Key Exchange Key
* New PKGDATA_VARS variable to specify variables written out to pkgdata
* Obsolete stress recipe replaced by stress-ng
* uboot-sign: add support for different u-boot configurations
* update-rc.d: support enable/disable options
* waffle: support building without x11
* weston-init: Add possibility to run weston as non-root user
* python3: support recommends in manifest
* package_deb: add DPKG_BUILDCMD variable to allow customising dpkg command
* chrpath.bbclass: Add break_hardlinks parameter to allow breaking hardlinks when processing rpaths
* New "Apache-2.0-with-LLVM-exception" common license file
* screen: add /etc/screenrc as global config file
* utils/multiprocess_launch: Improve failing subprocess output
* Added local.conf/auto.conf into error report submitted by report-error.bbclass
* Added OpenEmbedded logo .svg file to repository (from OE-Classic)

------------
Known Issues
------------
*Bug 13594: mpc8315e-rdb: the stap oeqa test causes OOM.
This issue is on a platform with minimal support and works outside the framework.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13594

*Bug 13595: strace ptest failed .
strace issue is two individual test regressions which is an improvement on the test timeouts we had previously.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13595

---------------
Recipe Licenses
---------------
The following corrections have been made to the LICENSE values set by recipes:

* cairo: MPL-1 -> MPL-1.1
* dbus / dbus-glib / dbus-test: AFL-2 -> AFL-2.1
* iw: BSD -> BSD-2-Clause
* libical: MPL-1 -> MPL-1.0
* openssh: some files are licensed under ISC or MIT license, so add these to LICENSE
* taglib: MPL-1 -> MPL-1.1
* vte: several files in libvte source are LGPLv3+, so add to LICENSE and set LGPLv3+ as the libvte package LICENSE

----------------------
Migration instructions
----------------------

For details on changes that you might need to make when migrating to the Yocto Project 3.0
release from previous releases, please see the following manual section:

http://www.yoctoproject.org/docs/3.0/ref-manual/ref-manual.html#moving-to-the-yocto-project-3.0-release

--------------
Security Fixes
--------------
* binutils: CVE-2019-12972, CVE-2019-14250, CVE-2019-14444, CVE-2019-9070, CVE-2019-9071, CVE-2019-9074, CVE-2019-9075, CVE-2019-9076, CVE-2019-9077
* dbus: CVE-2019-12749
* gcc: CVE-2019-14250, CVE-2018-12886, CVE-2018-18484, CVE-2019-15847
* gdb: CVE-2017-9778
* ghostscript: CVE-2019-14811, CVE-2019-14817
* glib-2.0: CVE-2019-12450
* glibc: CVE-2018-20796 (same as CVE-2019-9169)
* gnupg: CVE-2019-13050
* gnutls: GNUTLS-SA-2019-03-27
* iptables: CVE-2019-11360
* libid3tag: CVE-2017-11550, CVE-2017-11551 (same as CVE-2004-2779)
* libxslt: CVE-2019-11068, CVE-2019-13117, CVE-2019-13118
* linux-yocto/4.19: CVE-2019-3887
* linux-yocto/5.0: CVE-2019-3887
* ltp: CVE-2017-17052
* nasm: CVE-2018-19755
* openssh: CVE-2018-20685, CVE-2019-6109, CVE-2019-6111
* patch: CVE-2018-1000156 (improved fix), CVE-2019-13636, CVE-2019-13638
* python3: CVE-2019-9740, CVE-2019-9948
* python: CVE-2018-20852, CVE-2019-9740, CVE-2019-9947 (same as CVE-2019-9740), CVE-2019-9948, CVE-2019-9636
* qemu: CVE-2019-12155, CVE-2019-15890
* rsync: CVE-2016-9840, CVE-2016-9841, CVE-2016-9842, CVE-2016-9843
* squashfs-tools: CVE-2015-4645, CVE-2015-4646
* tiff: CVE-2019-6128, CVE-2019-7663, CVE-2019-14973
* u-boot: CVE-2019-13103, CVE-2019-13104, CVE-2019-13105, CVE-2019-13106, CVE-2019-14192, CVE-2019-14193, CVE-2019-14194, CVE-2019-14195, CVE-2019-14196, CVE-2019-14197, CVE-2019-14198, CVE-2019-14199, CVE-2019-14200, CVE-2019-14201, CVE-2019-14202, CVE-2019-14203, CVE-2019-14204
* unzip: CVE-2019-13232
* vim: CVE-2019-12735

---------------
Recipe Upgrades
---------------
* acpica: update to 20190816
* acpid: upgrade 2.0.31 -> 2.0.32
* adwaita-icon-theme: upgrade 3.30.1 -> 3.32.0
* alsa-lib: upgrade 1.1.8 -> 1.1.9
* alsa-plugins: upgrade 1.1.8 -> 1.1.9
* alsa-utils: upgrade 1.1.8 -> 1.1.9
* apr: upgrade 1.6.5 -> 1.7.0
* apt: update to 1.2.31
* aspell: update to 0.60.7
* atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-core: upgrade 2.30.0 -> 2.32.1
* autoconf-archive: update to 2019.01.06
* babeltrace: update to 1.5.7
* bash-completion: upgrade 2.8 -> 2.9
* bash: upgrade 4.4.18 -> 5.0
* bison: upgrade 3.0.4 -> 3.4.1
* boost: update to 1.71.0
* btrfs-tools: upgrade 4.20.1 -> 5.2.2
* build-compare: 2015.02.10 -> 2019.08.14
* busybox: 1.30.1 -> 1.31.0
* bzip2: update to 1.0.8
* ccache: upgrade 3.6 -> 3.7.3
* cmake: 3.14.1 -> 3.15.3
* cogl: upgrade 1.22.2 -> 1.22.4
* connman: update to 1.37
* coreutils: update to 8.31
* createrepo-c: update to 0.15.0
* cronie: update to 1.5.4
* cups: update to 2.2.12
* curl: update to 7.66.0
* dbus-test: Upgrade 1.12.12 -> 1.12.16
* dbus: Upgrade 1.12.12 -> 1.12.16
* debianutils: upgrade 4.8.6.1 -> 4.8.6.3
* desktop-file-utils: upgrade 0.23 -> 0.24
* distcc: upgrade 3.3.2 -> 3.3.3
* dnf: upgrade 4.1.0 -> 4.2.2
* dpkg: update to 1.19.7
* dropbear: update to 2019.78
* dtc: upgrade 1.4.7 -> 1.5.1
* e2fsprogs: 1.44.5 -> 1.45.3
* elfutils: 0.176 -> 0.177
* ell: update to 0.22
* encodings: update to 1.0.5
* epiphany: update to 3.32.4
* ethtool: update to 5.2
* eudev: update to 3.2.8
* expat: update to 2.2.8
* ffmpeg: update to 4.2.1
* file: update to 5.37
* flac: Upgrade 1.3.2 -> 1.3.3
* fontconfig: update to 2.13.1
* font-util: update to 1.3.2
* freetype: upgrade 2.9.1 -> 2.10.1
* gawk: upgrade 4.2.1 -> 5.0.1
* gcc-9: Upgrade to 9.2
* gdb: Upgrade from 8.2.1 to 8.3.1
* gdk-pixbuf: update 2.38.0 -> 2.38.2
* ghostscript: 9.26 -> 9.27
* git: update to 2.23.0
* glib-2.0: udpate 2.58.3 -> 2.60.7
* glibc: Update to glibc 2.30
* glib-networking: upgrade 2.60.1 -> 2.60.3
* gnu-config: Update to latest SHA
* gnupg: update to 2.2.17
* gnutls: upgrade 3.6.5 -> 3.6.8
* go-1.12: update to 1.12.9 minor release
* gobject-introspection: update to 1.60.2
* go-dep: update to 0.5.4
* go: update 1.12.1->1.12.6
* gpgme: upgrade 1.12.0 -> 1.13.1
* groff: upgrade 1.22.3 -> 1.22.4
* grub: upgrade 2.02 -> 2.04
* gsettings-desktop-schemas: upgrade 3.28.1 -> 3.32.0
* gst-examples: upgrade to 1.16.0
* gstreamer1.0-libav: upgrade to version 1.16.0
* gstreamer1.0-omx: upgrade to version 1.16.0
* gstreamer1.0-plugins-bad: upgrade to version 1.16.0
* gstreamer1.0-plugins-base: upgrade to version 1.16.0
* gstreamer1.0-plugins-good: upgrade to version 1.16.0
* gstreamer1.0-plugins-ugly: upgrade to version 1.16.0
* gstreamer1.0-python: upgrade to version 1.16.0
* gstreamer1.0-rtsp-server: upgrade to version 1.16.0
* gstreamer1.0: upgrade to version 1.16.0
* gstreamer1.0-vaapi: upgrade to version 1.16.0
* gst-validate: upgrade to version 1.16.0
* gtk+3: update 3.24.5 -> 3.24.8
* gtk-doc: upgrade 1.29 -> 1.31
* harfbuzz: upgrade 2.3.1 -> 2.6.1
* help2man-native: update to 1.47.11
* icu: update to 64.2
* ifupdown: update to 0.8.22
* iproute2: update to 5.2.0
* iptables: upgrade 1.6.2 -> 1.8.3
* iputils: upgrade to s20190709
* iso-codes: upgrade 4.2 -> 4.3
* iw: upgrade 4.14 -> 5.3
* kmscube: Bump revision to f632b23
* less: upgrade 550 -> 551
* libarchive: upgrade 3.3.3 -> 3.4.0
* libatomic-ops: upgrade 7.6.8 -> 7.6.10
* libbsd: upgrade 0.9.1 -> 0.10.0
* libcap: update to 2.27
* libcomps: upgrade 0.1.10 -> 0.1.11
* libcroco: update to 0.6.13
* libdazzle: update to 3.32.3
* libdnf: update to 0.28.1
* libdrm: update to 2.4.99
* libevdev: upgrade 1.6.0 -> 1.8.0
* libevent: upgrade 2.1.8 -> 2.1.11
* libffi: Upgrade to 3.3-rc0
* libglu: upgrade 9.0.0 -> 9.0.1
* libgpg-error: upgrade 1.35 -> 1.36
* libgudev: upgrade 232 -> 233
* libical: upgrade to 3.0.6
* libice: upgrade 1.0.9 -> 1.0.10
* libidn2: upgrade to 2.2.0
* libinput: update to 1.14.1
* libjpeg-turbo: upgrade 2.0.2 -> 2.0.3
* libmodule-build-perl: upgrade 0.4224 -> 0.4229
* libmodulemd: update to 2.6.0
* libnewt: upgrade 0.52.20 -> 0.52.21
* libnl: upgrade to 3.5.0
* libnotify: update to 0.7.8
* libnss-nis: upgrade 3.0 -> 3.1
* libogg: upgrade 1.3.3 -> 1.3.4
* libpam: Upgrade 1.3.0 -> 1.3.1
* libpcap: upgrade 1.9.0 -> 1.9.1
* libpciaccess: upgrade 0.14 -> 0.16
* libpcre2: upgrade 10.32 -> 10.33
* libpng: update to 1.6.37
* libpsl: update to 0.21.0
* librepo: update to 1.10.5
* libsdl2: upgrade 2.0.9 -> 2.0.10
* libsecret: 0.19.0
* libsolf: update to 0.7.5
* libsolv: update to 0.7.6
* libsoup-2.4: upgrade 2.66.1 -> 2.66.2
* libsoup: Upgrade from 2.64.2 to 2.66.1
* libtasn1: upgrade 4.13 -> 4.14
* libtest-needs-perl: upgrade 0.002005 -> 0.002006
* libtirpc: upgrade 1.0.3 -> 1.1.4
* liburcu: update to 0.11.1
* libva: upgrade 2.4.0 -> 2.5.0
* libva-utils: upgrade 2.4.0 -> 2.5.0
* libwebp: upgrade 1.0.2 -> 1.0.3
* libx11-compose-data: upgrade 1.6.7 -> 1.6.8
* libx11: update to 1.6.8
* libxcrypt: update to 4.4.8
* libxdmcp: update to 1.1.3
* libxext: update to 1.3.4
* libxft: upgrade 2.3.2 -> 2.3.3
* libxi: update to 1.7.10
* libxkbfile: update 1.1.0
* libxml2: upgrade 2.9.8 -> 2.9.9
* libxml-sax-perl: upgrade 1.00 -> 1.02
* libxmu: update to 1.1.3
* libxrandr: update to 1.5.2
* libxt: update to 1.2.0
* libxvmc: update to 1.0.11
* libyaml: update to 0.2.2
* lighttpd: Upgrade 1.4.53 -> 1.4.54
* linux-firmware: Upgrade to 20190815
* linux-libc-headers: update to v5.2 headers
* linux-yocto/4.19: update to 4.19.72 and -rt22
* linux-yocto-dev: bump to 5.3-rcX
* linux-yocto: introduce 5.2.17 recipes
* linux-yocto-rt: update to 5.0.5-rt9
* llvm: Update to 8.0.1
* logrotate: upgrade 3.15.0 -> 3.15.1
* ltp: upgrade 20190115 -> 20190517
* lttng-modules: upgrade 2.10.8 -> 2.10.11
* lttng-tools: update to 2.10.7
* lttng-ust: upgrade 2.10.3 -> 2.10.5
* lz4: update to 1.9.2
* makedepend: update to 1.0.6
* man-db: upgrade 2.8.4 -> 2.8.7
* man-pages: upgrade 4.16 -> 5.01
* mc: update to 4.8.23
* mesa-demos: update to 8.4.0
* mesa: Update 19.0.1 -> 19.1.6
* meson: update to 0.51.2
* mmc-utils: update to the latest upstream code
* mobile-broadband-provider-info: upgrade 20190116 -> 20190618
* mpg123: upgrade 1.25.10 -> 1.25.11
* msmtp: 1.6.6 -> 1.8.5
* mtd-utils: Upgrade to 2.1.1
* mtools: update to 4.0.23
* musl: Update to latest master
* ncurses: upgrade 6.1+20181013 -> 6.1+20190803
* nettle: upgrade 3.4.1 -> 3.5.1
* newlib: Upgrade to 3.1.0
* nfs-utils: 2.3.3 -> 2.4.1
* nss: upgrade 3.42.1 -> 3.45
* ofono: upgrade 1.25 -> 1.30
* opensbi: Update from 0.3 to 0.4
* openssh: Upgrade 7.9p1 -> 8.0p1
* openssl: Upgrade 1.1.1b -> 1.1.1d
* opkg: upgrade to version 0.4.1
* opkg-utils: upgrade to version 0.4.1
* orc: update to 0.4.29
* ovmf: Update to version edk2-stable201905
* p11-kit: update to 0.23.16.1
* pango: upgrade 1.42.4 -> 1.44.6
* patchelf: Upgrade 0.9 -> 0.10
* perl: Move perl-sanity -> perl
* perl: update to 5.30.0
* piglit: upgrade to latest revision
* pixman: update to 0.38.4
* pkgconf: upgrade 1.6.0 -> 1.6.3
* ptest-runner: update from 2.3.1 to 2.3.2
* python3-dbus: upgrade 1.2.8 -> 1.2.12
* python3-docutils: update to 0.15
* python3-git: update to 3.0.2
* python3-mako: update to 1.1.0
* python3-numpy: update to 1.17.0
* python3-pbr: update to 5.4.3
* python3-pip: update to 19.2.3
* python3-pycairo: update to 1.18.1
* python3-pygobject: update to 3.34.0
* python3-scons: update to 3.1.1
* python3: upgrade 3.7.3 -> 3.7.4
* python-numpy: update to 1.16.3
* python-scons: update to 3.1.0
* python-setuptools: update to 41.2.0
* python: update to 3.7.3
* qemu: Upgrade from 3.1.0 to 4.1
* quilt: update to 0.66
* quota: update to 4.05
* rng-tools: 6.6 -> 6.7
* ruby: update to 2.5.5
* socat: upgrade 1.7.3.2 -> 1.7.3.3
* sqlite3: update to 3.29.0
* squashfs-tools: upgrade to commit f95864afe883
* strace: Upgrade to 5.3
* subversion: upgrade 1.11.1 -> 1.12.2
* sysprof: upgrade 3.30.2 -> 3.32.0
* sysstat: 12.1.3 -> 12.1.6
* systemd: upgrade to 243
* systemtap: update to 57c9aca9f1ff32a6add10e02ecd33b7314fad499
* tar: update to 1.32
* timezone: update to 2019c
* u-boot: Upgrade from 2019.01 to 2019.07
* uninative: Update to 2.7 release
* usbutils: upgrade 010->012
* util-linux: upgrade to 2.34
* vala: update to 0.44.7
* valgrind: update from 3.14.0 to 3.15.0
* vim: Update to 8.1.1240
* virglrenderer: update 0.7.0 -> 0.8.0
* vte: upgrade 0.52.2 -> 0.56.3
* waffle: upgrade 1.5.2 -> 1.6.0
* wayland-protocols: upgrade 1.17 -> 1.18
* webkitgtk: update to 2.24.4
* weston: upgrade 5.0.0 -> 7.0.0
* wget: update to 1.20.3
* wpa-supplicant: update to 2.9
* x11perf: update to 1.6.1
* x264: upgrade to latest revision
* xauth: upgrade 1.0.10 -> 1.1
* xf86-input-libinput: update to 0.29.0
* xinput: update to 1.6.3
* xkeyboard: upgrade 2.26 -> 2.27
* xorgproto: update to 2019.1
* xrandr: update to 1.5.1
* xserver-xorg: update to 1.20.5
* xtrans: upgrade 1.3.5 -> 1.4.0
* xwininfo: upgrade 1.1.4 -> 1.1.5

3.0 Release Notes WIP

2019-10-18T13:06:36Z

PaulEggleton: Populate license section

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|NOTE: The formatting in this page is not meant to look good in the wiki - it's just a convenient place to collaborate. We need to stick to the text formatting that will end up in the actual release notes.
|}

Security Fixes
--------------
* binutils: CVE-2019-12972, CVE-2019-14250, CVE-2019-14444, CVE-2019-9070, CVE-2019-9071, CVE-2019-9074, CVE-2019-9075, CVE-2019-9076, CVE-2019-9077
* dbus: CVE-2019-12749
* gcc: CVE-2019-14250, CVE-2018-12886, CVE-2018-18484, CVE-2019-15847
* gdb: CVE-2017-9778
* ghostscript: CVE-2019-14811, CVE-2019-14817
* glib-2.0: CVE-2019-12450
* glibc: CVE-2018-20796 (same as CVE-2019-9169)
* gnupg: CVE-2019-13050
* gnutls: GNUTLS-SA-2019-03-27
* iptables: CVE-2019-11360
* libid3tag: CVE-2017-11550, CVE-2017-11551 (same as CVE-2004-2779)
* libxslt: CVE-2019-11068, CVE-2019-13117, CVE-2019-13118
* linux-yocto/4.19: CVE-2019-3887
* linux-yocto/5.0: CVE-2019-3887
* ltp: CVE-2017-17052
* nasm: CVE-2018-19755
* openssh: CVE-2018-20685, CVE-2019-6109, CVE-2019-6111
* patch: CVE-2018-1000156 (improved fix), CVE-2019-13636, CVE-2019-13638
* python3: CVE-2019-9740, CVE-2019-9948
* python: CVE-2018-20852, CVE-2019-9740, CVE-2019-9947 (same as CVE-2019-9740), CVE-2019-9948, CVE-2019-9636
* qemu: CVE-2019-12155, CVE-2019-15890
* rsync: CVE-2016-9840, CVE-2016-9841, CVE-2016-9842, CVE-2016-9843
* squashfs-tools: CVE-2015-4645, CVE-2015-4646
* tiff: CVE-2019-6128, CVE-2019-7663, CVE-2019-14973
* u-boot: CVE-2019-13103, CVE-2019-13104, CVE-2019-13105, CVE-2019-13106, CVE-2019-14192, CVE-2019-14193, CVE-2019-14194, CVE-2019-14195, CVE-2019-14196, CVE-2019-14197, CVE-2019-14198, CVE-2019-14199, CVE-2019-14200, CVE-2019-14201, CVE-2019-14202, CVE-2019-14203, CVE-2019-14204
* unzip: CVE-2019-13232
* vim: CVE-2019-12735

New Features / Enhancements
---------------------------
* Linux kernel 5.2/4.19, gcc 9.2, glibc 2.30 and ~260 other recipe upgrades
* Build change equivalence is detected and used to avoid rebuilding unchanged components (BETA)
* Architecture / machine-specific enhancements:
- New "qemuriscv64" emulated RISC-V 64-bit machine
- qemu: Add ppc64 to QEMU_TARGETS
- qemuarm64: Add QB_CPU_KVM to allow kvm acceleration
- New tune file for ARM Cortex-A53-Cortex-A57
- New tune file for arm1176jz-s CPU
- meson.bbclass: Handle microblaze* mapping to cpu family
- meson.bbclass: Make meson support aarch64_be.
- libffi: added RISC-V support
- icu: added armeb support
- runqemu: added support for kvm on aarch64
- beaglebone-yocto machine now set up to support booting images with runqemu
- qemux86: make it possible to use higher tunes using DEFAULTTUNE
* Kernel improvements:
- kernel-fitimage: introduce FIT_HASH_ALG
- kernel-module-split.bbclass: support CONFIG_MODULE_COMPRESS=y
- kernel-yocto: import security fragments from meta-security
- linux-yocto: add drm-bochs support
- linux-yocto: bsp/beaglebone: support qemu -machine virt
* multiconfig builds now reach their full potential:
- Many bugfixes and improvements
- sstate cache is now shared between configurations being built concurrently
- multiconfig configurations can be contained in layers
* Significant removal of old/obsolete software/patches ensuring we have a modern and up to date core Linux software stack:
- LSB support removed
- GTK+ 2 moved out to meta-oe
- Python 2 dependencies minimised
- Many obsolete patches dropped
* CVE checking enhancements:
- New cve-update-db recipe that reads from NVD JSON data feeds and supports network proxies
- Support for CVSSv3 scoring
- CVE_PRODUCT entries can now contain strings to match the vendor as well as product (vendor:product syntax)
* New INIT_MANAGER variable to make it easy to select the init manager (sysvinit, systemd, mdev-busybox)
* New recipes: binutils-cross-testsuite, core-image-sato-ptest-fast, dejagnu, efibootmgr, efivar, ell, glibc-testsuite, libcap-ng-python, libedit, libmodule-build-perl, libx11-compose-data, libxcrypt-compat, lsb-release, musl-obstack, opensbi, python3-pygments, python3-scons, python3-scons-native, stress-ng, vulkan-headers, vulkan-loader, vulkan-tools, wireless-regdb
* Added native variant to: glib-networking, grub, libsoup, python3-dbus
* BitBake improvements:
- Merged setscene tasks into the main runqueue so they can run in parallel
- fetch2/git: added sanity checking for git-lfs
- fetch2/svn: prevent from directly pulling from an externals w/o fetcher
- fetch2/npm: use npm pack to download node modules instead of wget
- Added --skip-setscene option
- Respect -f/--force option in conjunction with --runall or --runonly
- bitbake -e now supports showing base multiconfig configuration (using mc: prefix)
- "mc:" prefix now supported as a shorter version of multiconfig:
- Print more information when basehashes are mismatched
- Show task elapsed time in hours, minutes, and seconds
- Report all nonexistent directories in BBLAYERS in error message instead of just the first
- Improve validation of addtask and deltask arguments
- Added support for custom progress handlers injected via OE_EXTRA_IMPORTS
- Enable console keepalive to help usage with remote sessions
- Symlink the current cache file
* systemd-related improvements:
- serial-getty@.service: Allow device to fast fail if it does not exist
- Rewrote systemctl-native in Python supporting preset-all and mask
- Added partial support of drop-in configuration files to systemd-systemctl-native
- systemd-conf: added default configuration for wired network with DHCP
- systemd-conf: simplified creation of machine-specific configuration
- Create preset files and allow systemd to populate /etc/systemd/system instead of populating explicitly
- Added systemd helper unit to load/restore iptables rules
* runqemu improvements:
- Added support to pass multiple ports to tcpserial parameter
- Added support for a BIOS command-line variable (consistent with KERNEL)
- New QB_FSINFO variable supporting "wic:no-kernel-in-fs" and "wic:kernel-in-fs" for wic images
- Added support to handle EnrollDefaultKeys PK/KEK1 certificate
- Decoupled gtk and gl options
* wic improvements:
- New partition type for msdos partition tables
- New "bootimg-biosplusefi" source type that supports both BIOS and EFI
- Support for kernel with initramfs bundled
- bootimg-efi: add label source parameter
- bootimg-efi: allow multiple initrd
- bootimg-efi: replace hardcoded volume name with label
- Include .wks.in in wic search and list
- Use KERNEL_IMAGETYPE instead of hardcoding bzImage
- Added global debug option
* Other image-related improvements:
- Centralised default UEFI image configuration in conf/distro/image-uefi.conf
- Make gzipped images rsyncable
- initramfs-framework: support PARTLABEL option
- New bash-completion IMAGE_FEATURES item to add bash-completion support for all installed packages
* devtool/recipetool improvements:
- New "devtool menuconfig" subcommand
- devtool build now also runs do_deploy if applicable
- devtool finish now supports a --no-clean option
- devtool finish now warns if multiple layers have the same base name
- recipetool now supports creating recipes for Python 3
* Other script improvements:
- buildstats-diff: added option to filter tasks
- bitbake-layers: added several options to to make it easier to get plain output (for scripting)
- ddimage: replaced target device blacklist with mount check
- yocto-check-layer: Allow any case for README file detection
* SDK-related changes:
- New SDK_ARCHIVE_TYPE variable to control SDK archive format
- Introduce mechanism to keep nativesdk* sstate in eSDK
- Added nativesdk variant to: dnf, gzip, libtasn1, python3-dbus
- Use the best xz compression for the SDK
* buildhistory improvements:
- Record sysroot changes in addition to runtime content
- Show time spent writing buildhistory
* Recipe sanity checking improvements:
- Added check to ensure perllocal.pod is not installed by non-CPAN perl recipes
- Added sanity checks for ${PN} vs ${BPN} and github archives in SRC_URI
- Check if a recipe incorrectly uses DEPENDS_${PN}
- Improved buildpath warning messages
- Simplified paths in host contamination warnings
* Automated testing improvements:
- Enabled test suites for gcc, glibc, binutils
- Add ptest ptest support to elfutils, m4, gettext
- Fixes for many ptest test failures
- testimage: consider QB_DEFAULT_FSTYPE
- oe-selftest: implement console keepalive output
- Support for LTP / LTP compliance
- Added core-image-sato-ptest-fast image to execute 'fast' subset of ptests
- resulttool: Add log subcommand
- resulttool: enable loading results directly from an http/https URL
- resulttool: add manual test case configuration option
- resulttool: Add option to dump all ptest logs
* poky-lsb replaced by poky-altcfg for alternate configurations to be tested on the autobuilder (as well as an example of subclassing a distro config)
* Added minver and maxver parameters for patches in SRC_URI for more flexibility in bbappends and common inc files
* PRIVATE_LIBS variable now supports shell-style wildcards for matching libraries
* Adoption of SPDX license identifiers throughout Yocto Project's components
* Added bbverbnote shell log command (consistent with bbwarn, bberror etc.)
* New OE_EXTRA_IMPORTS variable to make it easier to import custom modules into BitBake python environment
* busybox: enabled unicode support by default
* cmake: Use compiler launcher variable when ccache is enabled so that it can be disabled by build scripts if needed
* db: add new "verify" PACKAGECONFIG option for enabling database verification with db_verify command (default disabled)
* distcc: split into client and server packages
* dropbear: new "disable-weak-ciphers" PACKAGECONFIG option to disable older weak ciphers
* grub-efi-native: install grub-editenv
* lttng-modules: added git based recipe
* opkg: allow overriding OPKGLIBDIR
* ovmf: Generate test Platform key and first Key Exchange Key
* New PKGDATA_VARS variable to specify variables written out to pkgdata
* Obsolete stress recipe replaced by stress-ng
* uboot-sign: add support for different u-boot configurations
* update-rc.d: support enable/disable options
* waffle: support building without x11
* weston-init: Add possibility to run weston as non-root user
* python3: support recommends in manifest
* package_deb: add DPKG_BUILDCMD variable to allow customising dpkg command
* chrpath.bbclass: Add break_hardlinks parameter to allow breaking hardlinks when processing rpaths
* New "Apache-2.0-with-LLVM-exception" common license file
* screen: add /etc/screenrc as global config file
* utils/multiprocess_launch: Improve failing subprocess output
* Added local.conf/auto.conf into error report submitted by report-error.bbclass
* Added OpenEmbedded logo .svg file to repository (from OE-Classic)

Recipe Upgrades
---------------
* acpica: update to 20190816
* acpid: upgrade 2.0.31 -> 2.0.32
* adwaita-icon-theme: upgrade 3.30.1 -> 3.32.0
* alsa-lib: upgrade 1.1.8 -> 1.1.9
* alsa-plugins: upgrade 1.1.8 -> 1.1.9
* alsa-utils: upgrade 1.1.8 -> 1.1.9
* apr: upgrade 1.6.5 -> 1.7.0
* apt: update to 1.2.31
* aspell: update to 0.60.7
* atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-core: upgrade 2.30.0 -> 2.32.1
* autoconf-archive: update to 2019.01.06
* babeltrace: update to 1.5.7
* bash-completion: upgrade 2.8 -> 2.9
* bash: upgrade 4.4.18 -> 5.0
* bison: upgrade 3.0.4 -> 3.4.1
* boost: update to 1.71.0
* btrfs-tools: upgrade 4.20.1 -> 5.2.2
* build-compare: 2015.02.10 -> 2019.08.14
* busybox: 1.30.1 -> 1.31.0
* bzip2: update to 1.0.8
* ccache: upgrade 3.6 -> 3.7.3
* cmake: 3.14.1 -> 3.15.3
* cogl: upgrade 1.22.2 -> 1.22.4
* connman: update to 1.37
* coreutils: update to 8.31
* createrepo-c: update to 0.15.0
* cronie: update to 1.5.4
* cups: update to 2.2.12
* curl: update to 7.66.0
* dbus-test: Upgrade 1.12.12 -> 1.12.16
* dbus: Upgrade 1.12.12 -> 1.12.16
* debianutils: upgrade 4.8.6.1 -> 4.8.6.3
* desktop-file-utils: upgrade 0.23 -> 0.24
* distcc: upgrade 3.3.2 -> 3.3.3
* dnf: upgrade 4.1.0 -> 4.2.2
* dpkg: update to 1.19.7
* dropbear: update to 2019.78
* dtc: upgrade 1.4.7 -> 1.5.1
* e2fsprogs: 1.44.5 -> 1.45.3
* elfutils: 0.176 -> 0.177
* ell: update to 0.22
* encodings: update to 1.0.5
* epiphany: update to 3.32.4
* ethtool: update to 5.2
* eudev: update to 3.2.8
* expat: update to 2.2.8
* ffmpeg: update to 4.2.1
* file: update to 5.37
* flac: Upgrade 1.3.2 -> 1.3.3
* fontconfig: update to 2.13.1
* font-util: update to 1.3.2
* freetype: upgrade 2.9.1 -> 2.10.1
* gawk: upgrade 4.2.1 -> 5.0.1
* gcc-9: Upgrade to 9.2
* gdb: Upgrade from 8.2.1 to 8.3.1
* gdk-pixbuf: update 2.38.0 -> 2.38.2
* ghostscript: 9.26 -> 9.27
* git: update to 2.23.0
* glib-2.0: udpate 2.58.3 -> 2.60.7
* glibc: Update to glibc 2.30
* glib-networking: upgrade 2.60.1 -> 2.60.3
* gnu-config: Update to latest SHA
* gnupg: update to 2.2.17
* gnutls: upgrade 3.6.5 -> 3.6.8
* go-1.12: update to 1.12.9 minor release
* gobject-introspection: update to 1.60.2
* go-dep: update to 0.5.4
* go: update 1.12.1->1.12.6
* gpgme: upgrade 1.12.0 -> 1.13.1
* groff: upgrade 1.22.3 -> 1.22.4
* grub: upgrade 2.02 -> 2.04
* gsettings-desktop-schemas: upgrade 3.28.1 -> 3.32.0
* gst-examples: upgrade to 1.16.0
* gstreamer1.0-libav: upgrade to version 1.16.0
* gstreamer1.0-omx: upgrade to version 1.16.0
* gstreamer1.0-plugins-bad: upgrade to version 1.16.0
* gstreamer1.0-plugins-base: upgrade to version 1.16.0
* gstreamer1.0-plugins-good: upgrade to version 1.16.0
* gstreamer1.0-plugins-ugly: upgrade to version 1.16.0
* gstreamer1.0-python: upgrade to version 1.16.0
* gstreamer1.0-rtsp-server: upgrade to version 1.16.0
* gstreamer1.0: upgrade to version 1.16.0
* gstreamer1.0-vaapi: upgrade to version 1.16.0
* gst-validate: upgrade to version 1.16.0
* gtk+3: update 3.24.5 -> 3.24.8
* gtk-doc: upgrade 1.29 -> 1.31
* harfbuzz: upgrade 2.3.1 -> 2.6.1
* help2man-native: update to 1.47.11
* icu: update to 64.2
* ifupdown: update to 0.8.22
* iproute2: update to 5.2.0
* iptables: upgrade 1.6.2 -> 1.8.3
* iputils: upgrade to s20190709
* iso-codes: upgrade 4.2 -> 4.3
* iw: upgrade 4.14 -> 5.3
* kmscube: Bump revision to f632b23
* less: upgrade 550 -> 551
* libarchive: upgrade 3.3.3 -> 3.4.0
* libatomic-ops: upgrade 7.6.8 -> 7.6.10
* libbsd: upgrade 0.9.1 -> 0.10.0
* libcap: update to 2.27
* libcomps: upgrade 0.1.10 -> 0.1.11
* libcroco: update to 0.6.13
* libdazzle: update to 3.32.3
* libdnf: update to 0.28.1
* libdrm: update to 2.4.99
* libevdev: upgrade 1.6.0 -> 1.8.0
* libevent: upgrade 2.1.8 -> 2.1.11
* libffi: Upgrade to 3.3-rc0
* libglu: upgrade 9.0.0 -> 9.0.1
* libgpg-error: upgrade 1.35 -> 1.36
* libgudev: upgrade 232 -> 233
* libical: upgrade to 3.0.6
* libice: upgrade 1.0.9 -> 1.0.10
* libidn2: upgrade to 2.2.0
* libinput: update to 1.14.1
* libjpeg-turbo: upgrade 2.0.2 -> 2.0.3
* libmodule-build-perl: upgrade 0.4224 -> 0.4229
* libmodulemd: update to 2.6.0
* libnewt: upgrade 0.52.20 -> 0.52.21
* libnl: upgrade to 3.5.0
* libnotify: update to 0.7.8
* libnss-nis: upgrade 3.0 -> 3.1
* libogg: upgrade 1.3.3 -> 1.3.4
* libpam: Upgrade 1.3.0 -> 1.3.1
* libpcap: upgrade 1.9.0 -> 1.9.1
* libpciaccess: upgrade 0.14 -> 0.16
* libpcre2: upgrade 10.32 -> 10.33
* libpng: update to 1.6.37
* libpsl: update to 0.21.0
* librepo: update to 1.10.5
* libsdl2: upgrade 2.0.9 -> 2.0.10
* libsecret: 0.19.0
* libsolf: update to 0.7.5
* libsolv: update to 0.7.6
* libsoup-2.4: upgrade 2.66.1 -> 2.66.2
* libsoup: Upgrade from 2.64.2 to 2.66.1
* libtasn1: upgrade 4.13 -> 4.14
* libtest-needs-perl: upgrade 0.002005 -> 0.002006
* libtirpc: upgrade 1.0.3 -> 1.1.4
* liburcu: update to 0.11.1
* libva: upgrade 2.4.0 -> 2.5.0
* libva-utils: upgrade 2.4.0 -> 2.5.0
* libwebp: upgrade 1.0.2 -> 1.0.3
* libx11-compose-data: upgrade 1.6.7 -> 1.6.8
* libx11: update to 1.6.8
* libxcrypt: update to 4.4.8
* libxdmcp: update to 1.1.3
* libxext: update to 1.3.4
* libxft: upgrade 2.3.2 -> 2.3.3
* libxi: update to 1.7.10
* libxkbfile: update 1.1.0
* libxml2: upgrade 2.9.8 -> 2.9.9
* libxml-sax-perl: upgrade 1.00 -> 1.02
* libxmu: update to 1.1.3
* libxrandr: update to 1.5.2
* libxt: update to 1.2.0
* libxvmc: update to 1.0.11
* libyaml: update to 0.2.2
* lighttpd: Upgrade 1.4.53 -> 1.4.54
* linux-firmware: Upgrade to 20190815
* linux-libc-headers: update to v5.2 headers
* linux-yocto/4.19: update to 4.19.72 and -rt22
* linux-yocto-dev: bump to 5.3-rcX
* linux-yocto: introduce 5.2.17 recipes
* linux-yocto-rt: update to 5.0.5-rt9
* llvm: Update to 8.0.1
* logrotate: upgrade 3.15.0 -> 3.15.1
* ltp: upgrade 20190115 -> 20190517
* lttng-modules: upgrade 2.10.8 -> 2.10.11
* lttng-tools: update to 2.10.7
* lttng-ust: upgrade 2.10.3 -> 2.10.5
* lz4: update to 1.9.2
* makedepend: update to 1.0.6
* man-db: upgrade 2.8.4 -> 2.8.7
* man-pages: upgrade 4.16 -> 5.01
* mc: update to 4.8.23
* mesa-demos: update to 8.4.0
* mesa: Update 19.0.1 -> 19.1.6
* meson: update to 0.51.2
* mmc-utils: update to the latest upstream code
* mobile-broadband-provider-info: upgrade 20190116 -> 20190618
* mpg123: upgrade 1.25.10 -> 1.25.11
* msmtp: 1.6.6 -> 1.8.5
* mtd-utils: Upgrade to 2.1.1
* mtools: update to 4.0.23
* musl: Update to latest master
* ncurses: upgrade 6.1+20181013 -> 6.1+20190803
* nettle: upgrade 3.4.1 -> 3.5.1
* newlib: Upgrade to 3.1.0
* nfs-utils: 2.3.3 -> 2.4.1
* nss: upgrade 3.42.1 -> 3.45
* ofono: upgrade 1.25 -> 1.30
* opensbi: Update from 0.3 to 0.4
* openssh: Upgrade 7.9p1 -> 8.0p1
* openssl: Upgrade 1.1.1b -> 1.1.1d
* opkg: upgrade to version 0.4.1
* opkg-utils: upgrade to version 0.4.1
* orc: update to 0.4.29
* ovmf: Update to version edk2-stable201905
* p11-kit: update to 0.23.16.1
* pango: upgrade 1.42.4 -> 1.44.6
* patchelf: Upgrade 0.9 -> 0.10
* perl: Move perl-sanity -> perl
* perl: update to 5.30.0
* piglit: upgrade to latest revision
* pixman: update to 0.38.4
* pkgconf: upgrade 1.6.0 -> 1.6.3
* ptest-runner: update from 2.3.1 to 2.3.2
* python3-dbus: upgrade 1.2.8 -> 1.2.12
* python3-docutils: update to 0.15
* python3-git: update to 3.0.2
* python3-mako: update to 1.1.0
* python3-numpy: update to 1.17.0
* python3-pbr: update to 5.4.3
* python3-pip: update to 19.2.3
* python3-pycairo: update to 1.18.1
* python3-pygobject: update to 3.34.0
* python3-scons: update to 3.1.1
* python3: upgrade 3.7.3 -> 3.7.4
* python-numpy: update to 1.16.3
* python-scons: update to 3.1.0
* python-setuptools: update to 41.2.0
* python: update to 3.7.3
* qemu: Upgrade from 3.1.0 to 4.1
* quilt: update to 0.66
* quota: update to 4.05
* rng-tools: 6.6 -> 6.7
* ruby: update to 2.5.5
* socat: upgrade 1.7.3.2 -> 1.7.3.3
* sqlite3: update to 3.29.0
* squashfs-tools: upgrade to commit f95864afe883
* strace: Upgrade to 5.3
* subversion: upgrade 1.11.1 -> 1.12.2
* sysprof: upgrade 3.30.2 -> 3.32.0
* sysstat: 12.1.3 -> 12.1.6
* systemd: upgrade to 243
* systemtap: update to 57c9aca9f1ff32a6add10e02ecd33b7314fad499
* tar: update to 1.32
* timezone: update to 2019c
* u-boot: Upgrade from 2019.01 to 2019.07
* uninative: Update to 2.7 release
* usbutils: upgrade 010->012
* util-linux: upgrade to 2.34
* vala: update to 0.44.7
* valgrind: update from 3.14.0 to 3.15.0
* vim: Update to 8.1.1240
* virglrenderer: update 0.7.0 -> 0.8.0
* vte: upgrade 0.52.2 -> 0.56.3
* waffle: upgrade 1.5.2 -> 1.6.0
* wayland-protocols: upgrade 1.17 -> 1.18
* webkitgtk: update to 2.24.4
* weston: upgrade 5.0.0 -> 7.0.0
* wget: update to 1.20.3
* wpa-supplicant: update to 2.9
* x11perf: update to 1.6.1
* x264: upgrade to latest revision
* xauth: upgrade 1.0.10 -> 1.1
* xf86-input-libinput: update to 0.29.0
* xinput: update to 1.6.3
* xkeyboard: upgrade 2.26 -> 2.27
* xorgproto: update to 2019.1
* xrandr: update to 1.5.1
* xserver-xorg: update to 1.20.5
* xtrans: upgrade 1.3.5 -> 1.4.0
* xwininfo: upgrade 1.1.4 -> 1.1.5

license
-------
The following corrections have been made to the LICENSE values set by recipes:

* cairo: MPL-1 -> MPL-1.1
* dbus / dbus-glib / dbus-test: AFL-2 -> AFL-2.1
* iw: BSD -> BSD-2-Clause
* libical: MPL-1 -> MPL-1.0
* openssh: some files are licensed under ISC or MIT license, so add these to LICENSE
* taglib: MPL-1 -> MPL-1.1
* vte: several files in libvte source are LGPLv3+, so add to LICENSE and set LGPLv3+ as the libvte package LICENSE

Known Issues
------------
*Bug 13594: mpc8315e-rdb: the stap oeqa test causes OOM.
This issue is on a platform with minimal support and works outside the framework.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13594

*Bug 13595: strace ptest failed .
strace issue is two individual test regressions which is an improvement on the test timeouts we had previously.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13595

3.0 Release Notes WIP

2019-10-18T12:51:45Z

PaulEggleton: Tweaks

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|NOTE: The formatting in this page is not meant to look good in the wiki - it's just a convenient place to collaborate. We need to stick to the text formatting that will end up in the actual release notes.
|}

Security Fixes
--------------
* binutils: CVE-2019-12972, CVE-2019-14250, CVE-2019-14444, CVE-2019-9070, CVE-2019-9071, CVE-2019-9074, CVE-2019-9075, CVE-2019-9076, CVE-2019-9077
* dbus: CVE-2019-12749
* gcc: CVE-2019-14250, CVE-2018-12886, CVE-2018-18484, CVE-2019-15847
* gdb: CVE-2017-9778
* ghostscript: CVE-2019-14811, CVE-2019-14817
* glib-2.0: CVE-2019-12450
* glibc: CVE-2018-20796 (same as CVE-2019-9169)
* gnupg: CVE-2019-13050
* gnutls: GNUTLS-SA-2019-03-27
* iptables: CVE-2019-11360
* libid3tag: CVE-2017-11550, CVE-2017-11551 (same as CVE-2004-2779)
* libxslt: CVE-2019-11068, CVE-2019-13117, CVE-2019-13118
* linux-yocto/4.19: CVE-2019-3887
* linux-yocto/5.0: CVE-2019-3887
* ltp: CVE-2017-17052
* nasm: CVE-2018-19755
* openssh: CVE-2018-20685, CVE-2019-6109, CVE-2019-6111
* patch: CVE-2018-1000156 (improved fix), CVE-2019-13636, CVE-2019-13638
* python3: CVE-2019-9740, CVE-2019-9948
* python: CVE-2018-20852, CVE-2019-9740, CVE-2019-9947 (same as CVE-2019-9740), CVE-2019-9948, CVE-2019-9636
* qemu: CVE-2019-12155, CVE-2019-15890
* rsync: CVE-2016-9840, CVE-2016-9841, CVE-2016-9842, CVE-2016-9843
* squashfs-tools: CVE-2015-4645, CVE-2015-4646
* tiff: CVE-2019-6128, CVE-2019-7663, CVE-2019-14973
* u-boot: CVE-2019-13103, CVE-2019-13104, CVE-2019-13105, CVE-2019-13106, CVE-2019-14192, CVE-2019-14193, CVE-2019-14194, CVE-2019-14195, CVE-2019-14196, CVE-2019-14197, CVE-2019-14198, CVE-2019-14199, CVE-2019-14200, CVE-2019-14201, CVE-2019-14202, CVE-2019-14203, CVE-2019-14204
* unzip: CVE-2019-13232
* vim: CVE-2019-12735

New Features / Enhancements
---------------------------
* Linux kernel 5.2/4.19, gcc 9.2, glibc 2.30 and ~260 other recipe upgrades
* Build change equivalence is detected and used to avoid rebuilding unchanged components (BETA)
* Architecture / machine-specific enhancements:
- New "qemuriscv64" emulated RISC-V 64-bit machine
- qemu: Add ppc64 to QEMU_TARGETS
- qemuarm64: Add QB_CPU_KVM to allow kvm acceleration
- New tune file for ARM Cortex-A53-Cortex-A57
- New tune file for arm1176jz-s CPU
- meson.bbclass: Handle microblaze* mapping to cpu family
- meson.bbclass: Make meson support aarch64_be.
- libffi: added RISC-V support
- icu: added armeb support
- runqemu: added support for kvm on aarch64
- beaglebone-yocto machine now set up to support booting images with runqemu
- qemux86: make it possible to use higher tunes using DEFAULTTUNE
* Kernel improvements:
- kernel-fitimage: introduce FIT_HASH_ALG
- kernel-module-split.bbclass: support CONFIG_MODULE_COMPRESS=y
- kernel-yocto: import security fragments from meta-security
- linux-yocto: add drm-bochs support
- linux-yocto: bsp/beaglebone: support qemu -machine virt
* multiconfig builds now reach their full potential:
- Many bugfixes and improvements
- sstate cache is now shared between configurations being built concurrently
- multiconfig configurations can be contained in layers
* Significant removal of old/obsolete software/patches ensuring we have a modern and up to date core Linux software stack:
- LSB support removed
- GTK+ 2 moved out to meta-oe
- Python 2 dependencies minimised
- Many obsolete patches dropped
* CVE checking enhancements:
- New cve-update-db recipe that reads from NVD JSON data feeds and supports network proxies
- Support for CVSSv3 scoring
- CVE_PRODUCT entries can now contain strings to match the vendor as well as product (vendor:product syntax)
* New INIT_MANAGER variable to make it easy to select the init manager (sysvinit, systemd, mdev-busybox)
* New recipes: binutils-cross-testsuite, core-image-sato-ptest-fast, dejagnu, efibootmgr, efivar, ell, glibc-testsuite, libcap-ng-python, libedit, libmodule-build-perl, libx11-compose-data, libxcrypt-compat, lsb-release, musl-obstack, opensbi, python3-pygments, python3-scons, python3-scons-native, stress-ng, vulkan-headers, vulkan-loader, vulkan-tools, wireless-regdb
* Added native variant to: glib-networking, grub, libsoup, python3-dbus
* BitBake improvements:
- Merged setscene tasks into the main runqueue so they can run in parallel
- fetch2/git: added sanity checking for git-lfs
- fetch2/svn: prevent from directly pulling from an externals w/o fetcher
- fetch2/npm: use npm pack to download node modules instead of wget
- Added --skip-setscene option
- Respect -f/--force option in conjunction with --runall or --runonly
- bitbake -e now supports showing base multiconfig configuration (using mc: prefix)
- "mc:" prefix now supported as a shorter version of multiconfig:
- Print more information when basehashes are mismatched
- Show task elapsed time in hours, minutes, and seconds
- Report all nonexistent directories in BBLAYERS in error message instead of just the first
- Improve validation of addtask and deltask arguments
- Added support for custom progress handlers injected via OE_EXTRA_IMPORTS
- Enable console keepalive to help usage with remote sessions
- Symlink the current cache file
* systemd-related improvements:
- serial-getty@.service: Allow device to fast fail if it does not exist
- Rewrote systemctl-native in Python supporting preset-all and mask
- Added partial support of drop-in configuration files to systemd-systemctl-native
- systemd-conf: added default configuration for wired network with DHCP
- systemd-conf: simplified creation of machine-specific configuration
- Create preset files and allow systemd to populate /etc/systemd/system instead of populating explicitly
- Added systemd helper unit to load/restore iptables rules
* runqemu improvements:
- Added support to pass multiple ports to tcpserial parameter
- Added support for a BIOS command-line variable (consistent with KERNEL)
- New QB_FSINFO variable supporting "wic:no-kernel-in-fs" and "wic:kernel-in-fs" for wic images
- Added support to handle EnrollDefaultKeys PK/KEK1 certificate
- Decoupled gtk and gl options
* wic improvements:
- New partition type for msdos partition tables
- New "bootimg-biosplusefi" source type that supports both BIOS and EFI
- Support for kernel with initramfs bundled
- bootimg-efi: add label source parameter
- bootimg-efi: allow multiple initrd
- bootimg-efi: replace hardcoded volume name with label
- Include .wks.in in wic search and list
- Use KERNEL_IMAGETYPE instead of hardcoding bzImage
- Added global debug option
* Other image-related improvements:
- Centralised default UEFI image configuration in conf/distro/image-uefi.conf
- Make gzipped images rsyncable
- initramfs-framework: support PARTLABEL option
- New bash-completion IMAGE_FEATURES item to add bash-completion support for all installed packages
* devtool/recipetool improvements:
- New "devtool menuconfig" subcommand
- devtool build now also runs do_deploy if applicable
- devtool finish now supports a --no-clean option
- devtool finish now warns if multiple layers have the same base name
- recipetool now supports creating recipes for Python 3
* Other script improvements:
- buildstats-diff: added option to filter tasks
- bitbake-layers: added several options to to make it easier to get plain output (for scripting)
- ddimage: replaced target device blacklist with mount check
- yocto-check-layer: Allow any case for README file detection
* SDK-related changes:
- New SDK_ARCHIVE_TYPE variable to control SDK archive format
- Introduce mechanism to keep nativesdk* sstate in eSDK
- Added nativesdk variant to: dnf, gzip, libtasn1, python3-dbus
- Use the best xz compression for the SDK
* buildhistory improvements:
- Record sysroot changes in addition to runtime content
- Show time spent writing buildhistory
* Recipe sanity checking improvements:
- Added check to ensure perllocal.pod is not installed by non-CPAN perl recipes
- Added sanity checks for ${PN} vs ${BPN} and github archives in SRC_URI
- Check if a recipe incorrectly uses DEPENDS_${PN}
- Improved buildpath warning messages
- Simplified paths in host contamination warnings
* Automated testing improvements:
- Enabled test suites for gcc, glibc, binutils
- Add ptest ptest support to elfutils, m4, gettext
- Fixes for many ptest test failures
- testimage: consider QB_DEFAULT_FSTYPE
- oe-selftest: implement console keepalive output
- Support for LTP / LTP compliance
- Added core-image-sato-ptest-fast image to execute 'fast' subset of ptests
- resulttool: Add log subcommand
- resulttool: enable loading results directly from an http/https URL
- resulttool: add manual test case configuration option
- resulttool: Add option to dump all ptest logs
* poky-lsb replaced by poky-altcfg for alternate configurations to be tested on the autobuilder (as well as an example of subclassing a distro config)
* Added minver and maxver parameters for patches in SRC_URI for more flexibility in bbappends and common inc files
* PRIVATE_LIBS variable now supports shell-style wildcards for matching libraries
* Adoption of SPDX license identifiers throughout Yocto Project's components
* Added bbverbnote shell log command (consistent with bbwarn, bberror etc.)
* New OE_EXTRA_IMPORTS variable to make it easier to import custom modules into BitBake python environment
* busybox: enabled unicode support by default
* cmake: Use compiler launcher variable when ccache is enabled so that it can be disabled by build scripts if needed
* db: add new "verify" PACKAGECONFIG option for enabling database verification with db_verify command (default disabled)
* distcc: split into client and server packages
* dropbear: new "disable-weak-ciphers" PACKAGECONFIG option to disable older weak ciphers
* grub-efi-native: install grub-editenv
* lttng-modules: added git based recipe
* opkg: allow overriding OPKGLIBDIR
* ovmf: Generate test Platform key and first Key Exchange Key
* New PKGDATA_VARS variable to specify variables written out to pkgdata
* Obsolete stress recipe replaced by stress-ng
* uboot-sign: add support for different u-boot configurations
* update-rc.d: support enable/disable options
* waffle: support building without x11
* weston-init: Add possibility to run weston as non-root user
* python3: support recommends in manifest
* package_deb: add DPKG_BUILDCMD variable to allow customising dpkg command
* chrpath.bbclass: Add break_hardlinks parameter to allow breaking hardlinks when processing rpaths
* New "Apache-2.0-with-LLVM-exception" common license file
* screen: add /etc/screenrc as global config file
* utils/multiprocess_launch: Improve failing subprocess output
* Added local.conf/auto.conf into error report submitted by report-error.bbclass
* Added OpenEmbedded logo .svg file to repository (from OE-Classic)

Recipe Upgrades
---------------
* acpica: update to 20190816
* acpid: upgrade 2.0.31 -> 2.0.32
* adwaita-icon-theme: upgrade 3.30.1 -> 3.32.0
* alsa-lib: upgrade 1.1.8 -> 1.1.9
* alsa-plugins: upgrade 1.1.8 -> 1.1.9
* alsa-utils: upgrade 1.1.8 -> 1.1.9
* apr: upgrade 1.6.5 -> 1.7.0
* apt: update to 1.2.31
* aspell: update to 0.60.7
* atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-core: upgrade 2.30.0 -> 2.32.1
* autoconf-archive: update to 2019.01.06
* babeltrace: update to 1.5.7
* bash-completion: upgrade 2.8 -> 2.9
* bash: upgrade 4.4.18 -> 5.0
* bison: upgrade 3.0.4 -> 3.4.1
* boost: update to 1.71.0
* btrfs-tools: upgrade 4.20.1 -> 5.2.2
* build-compare: 2015.02.10 -> 2019.08.14
* busybox: 1.30.1 -> 1.31.0
* bzip2: update to 1.0.8
* ccache: upgrade 3.6 -> 3.7.3
* cmake: 3.14.1 -> 3.15.3
* cogl: upgrade 1.22.2 -> 1.22.4
* connman: update to 1.37
* coreutils: update to 8.31
* createrepo-c: update to 0.15.0
* cronie: update to 1.5.4
* cups: update to 2.2.12
* curl: update to 7.66.0
* dbus-test: Upgrade 1.12.12 -> 1.12.16
* dbus: Upgrade 1.12.12 -> 1.12.16
* debianutils: upgrade 4.8.6.1 -> 4.8.6.3
* desktop-file-utils: upgrade 0.23 -> 0.24
* distcc: upgrade 3.3.2 -> 3.3.3
* dnf: upgrade 4.1.0 -> 4.2.2
* dpkg: update to 1.19.7
* dropbear: update to 2019.78
* dtc: upgrade 1.4.7 -> 1.5.1
* e2fsprogs: 1.44.5 -> 1.45.3
* elfutils: 0.176 -> 0.177
* ell: update to 0.22
* encodings: update to 1.0.5
* epiphany: update to 3.32.4
* ethtool: update to 5.2
* eudev: update to 3.2.8
* expat: update to 2.2.8
* ffmpeg: update to 4.2.1
* file: update to 5.37
* flac: Upgrade 1.3.2 -> 1.3.3
* fontconfig: update to 2.13.1
* font-util: update to 1.3.2
* freetype: upgrade 2.9.1 -> 2.10.1
* gawk: upgrade 4.2.1 -> 5.0.1
* gcc-9: Upgrade to 9.2
* gdb: Upgrade from 8.2.1 to 8.3.1
* gdk-pixbuf: update 2.38.0 -> 2.38.2
* ghostscript: 9.26 -> 9.27
* git: update to 2.23.0
* glib-2.0: udpate 2.58.3 -> 2.60.7
* glibc: Update to glibc 2.30
* glib-networking: upgrade 2.60.1 -> 2.60.3
* gnu-config: Update to latest SHA
* gnupg: update to 2.2.17
* gnutls: upgrade 3.6.5 -> 3.6.8
* go-1.12: update to 1.12.9 minor release
* gobject-introspection: update to 1.60.2
* go-dep: update to 0.5.4
* go: update 1.12.1->1.12.6
* gpgme: upgrade 1.12.0 -> 1.13.1
* groff: upgrade 1.22.3 -> 1.22.4
* grub: upgrade 2.02 -> 2.04
* gsettings-desktop-schemas: upgrade 3.28.1 -> 3.32.0
* gst-examples: upgrade to 1.16.0
* gstreamer1.0-libav: upgrade to version 1.16.0
* gstreamer1.0-omx: upgrade to version 1.16.0
* gstreamer1.0-plugins-bad: upgrade to version 1.16.0
* gstreamer1.0-plugins-base: upgrade to version 1.16.0
* gstreamer1.0-plugins-good: upgrade to version 1.16.0
* gstreamer1.0-plugins-ugly: upgrade to version 1.16.0
* gstreamer1.0-python: upgrade to version 1.16.0
* gstreamer1.0-rtsp-server: upgrade to version 1.16.0
* gstreamer1.0: upgrade to version 1.16.0
* gstreamer1.0-vaapi: upgrade to version 1.16.0
* gst-validate: upgrade to version 1.16.0
* gtk+3: update 3.24.5 -> 3.24.8
* gtk-doc: upgrade 1.29 -> 1.31
* harfbuzz: upgrade 2.3.1 -> 2.6.1
* help2man-native: update to 1.47.11
* icu: update to 64.2
* ifupdown: update to 0.8.22
* iproute2: update to 5.2.0
* iptables: upgrade 1.6.2 -> 1.8.3
* iputils: upgrade to s20190709
* iso-codes: upgrade 4.2 -> 4.3
* iw: upgrade 4.14 -> 5.3
* kmscube: Bump revision to f632b23
* less: upgrade 550 -> 551
* libarchive: upgrade 3.3.3 -> 3.4.0
* libatomic-ops: upgrade 7.6.8 -> 7.6.10
* libbsd: upgrade 0.9.1 -> 0.10.0
* libcap: update to 2.27
* libcomps: upgrade 0.1.10 -> 0.1.11
* libcroco: update to 0.6.13
* libdazzle: update to 3.32.3
* libdnf: update to 0.28.1
* libdrm: update to 2.4.99
* libevdev: upgrade 1.6.0 -> 1.8.0
* libevent: upgrade 2.1.8 -> 2.1.11
* libffi: Upgrade to 3.3-rc0
* libglu: upgrade 9.0.0 -> 9.0.1
* libgpg-error: upgrade 1.35 -> 1.36
* libgudev: upgrade 232 -> 233
* libical: upgrade to 3.0.6
* libice: upgrade 1.0.9 -> 1.0.10
* libidn2: upgrade to 2.2.0
* libinput: update to 1.14.1
* libjpeg-turbo: upgrade 2.0.2 -> 2.0.3
* libmodule-build-perl: upgrade 0.4224 -> 0.4229
* libmodulemd: update to 2.6.0
* libnewt: upgrade 0.52.20 -> 0.52.21
* libnl: upgrade to 3.5.0
* libnotify: update to 0.7.8
* libnss-nis: upgrade 3.0 -> 3.1
* libogg: upgrade 1.3.3 -> 1.3.4
* libpam: Upgrade 1.3.0 -> 1.3.1
* libpcap: upgrade 1.9.0 -> 1.9.1
* libpciaccess: upgrade 0.14 -> 0.16
* libpcre2: upgrade 10.32 -> 10.33
* libpng: update to 1.6.37
* libpsl: update to 0.21.0
* librepo: update to 1.10.5
* libsdl2: upgrade 2.0.9 -> 2.0.10
* libsecret: 0.19.0
* libsolf: update to 0.7.5
* libsolv: update to 0.7.6
* libsoup-2.4: upgrade 2.66.1 -> 2.66.2
* libsoup: Upgrade from 2.64.2 to 2.66.1
* libtasn1: upgrade 4.13 -> 4.14
* libtest-needs-perl: upgrade 0.002005 -> 0.002006
* libtirpc: upgrade 1.0.3 -> 1.1.4
* liburcu: update to 0.11.1
* libva: upgrade 2.4.0 -> 2.5.0
* libva-utils: upgrade 2.4.0 -> 2.5.0
* libwebp: upgrade 1.0.2 -> 1.0.3
* libx11-compose-data: upgrade 1.6.7 -> 1.6.8
* libx11: update to 1.6.8
* libxcrypt: update to 4.4.8
* libxdmcp: update to 1.1.3
* libxext: update to 1.3.4
* libxft: upgrade 2.3.2 -> 2.3.3
* libxi: update to 1.7.10
* libxkbfile: update 1.1.0
* libxml2: upgrade 2.9.8 -> 2.9.9
* libxml-sax-perl: upgrade 1.00 -> 1.02
* libxmu: update to 1.1.3
* libxrandr: update to 1.5.2
* libxt: update to 1.2.0
* libxvmc: update to 1.0.11
* libyaml: update to 0.2.2
* lighttpd: Upgrade 1.4.53 -> 1.4.54
* linux-firmware: Upgrade to 20190815
* linux-libc-headers: update to v5.2 headers
* linux-yocto/4.19: update to 4.19.72 and -rt22
* linux-yocto-dev: bump to 5.3-rcX
* linux-yocto: introduce 5.2.17 recipes
* linux-yocto-rt: update to 5.0.5-rt9
* llvm: Update to 8.0.1
* logrotate: upgrade 3.15.0 -> 3.15.1
* ltp: upgrade 20190115 -> 20190517
* lttng-modules: upgrade 2.10.8 -> 2.10.11
* lttng-tools: update to 2.10.7
* lttng-ust: upgrade 2.10.3 -> 2.10.5
* lz4: update to 1.9.2
* makedepend: update to 1.0.6
* man-db: upgrade 2.8.4 -> 2.8.7
* man-pages: upgrade 4.16 -> 5.01
* mc: update to 4.8.23
* mesa-demos: update to 8.4.0
* mesa: Update 19.0.1 -> 19.1.6
* meson: update to 0.51.2
* mmc-utils: update to the latest upstream code
* mobile-broadband-provider-info: upgrade 20190116 -> 20190618
* mpg123: upgrade 1.25.10 -> 1.25.11
* msmtp: 1.6.6 -> 1.8.5
* mtd-utils: Upgrade to 2.1.1
* mtools: update to 4.0.23
* musl: Update to latest master
* ncurses: upgrade 6.1+20181013 -> 6.1+20190803
* nettle: upgrade 3.4.1 -> 3.5.1
* newlib: Upgrade to 3.1.0
* nfs-utils: 2.3.3 -> 2.4.1
* nss: upgrade 3.42.1 -> 3.45
* ofono: upgrade 1.25 -> 1.30
* opensbi: Update from 0.3 to 0.4
* openssh: Upgrade 7.9p1 -> 8.0p1
* openssl: Upgrade 1.1.1b -> 1.1.1d
* opkg: upgrade to version 0.4.1
* opkg-utils: upgrade to version 0.4.1
* orc: update to 0.4.29
* ovmf: Update to version edk2-stable201905
* p11-kit: update to 0.23.16.1
* pango: upgrade 1.42.4 -> 1.44.6
* patchelf: Upgrade 0.9 -> 0.10
* perl: Move perl-sanity -> perl
* perl: update to 5.30.0
* piglit: upgrade to latest revision
* pixman: update to 0.38.4
* pkgconf: upgrade 1.6.0 -> 1.6.3
* ptest-runner: update from 2.3.1 to 2.3.2
* python3-dbus: upgrade 1.2.8 -> 1.2.12
* python3-docutils: update to 0.15
* python3-git: update to 3.0.2
* python3-mako: update to 1.1.0
* python3-numpy: update to 1.17.0
* python3-pbr: update to 5.4.3
* python3-pip: update to 19.2.3
* python3-pycairo: update to 1.18.1
* python3-pygobject: update to 3.34.0
* python3-scons: update to 3.1.1
* python3: upgrade 3.7.3 -> 3.7.4
* python-numpy: update to 1.16.3
* python-scons: update to 3.1.0
* python-setuptools: update to 41.2.0
* python: update to 3.7.3
* qemu: Upgrade from 3.1.0 to 4.1
* quilt: update to 0.66
* quota: update to 4.05
* rng-tools: 6.6 -> 6.7
* ruby: update to 2.5.5
* socat: upgrade 1.7.3.2 -> 1.7.3.3
* sqlite3: update to 3.29.0
* squashfs-tools: upgrade to commit f95864afe883
* strace: Upgrade to 5.3
* subversion: upgrade 1.11.1 -> 1.12.2
* sysprof: upgrade 3.30.2 -> 3.32.0
* sysstat: 12.1.3 -> 12.1.6
* systemd: upgrade to 243
* systemtap: update to 57c9aca9f1ff32a6add10e02ecd33b7314fad499
* tar: update to 1.32
* timezone: update to 2019c
* u-boot: Upgrade from 2019.01 to 2019.07
* uninative: Update to 2.7 release
* usbutils: upgrade 010->012
* util-linux: upgrade to 2.34
* vala: update to 0.44.7
* valgrind: update from 3.14.0 to 3.15.0
* vim: Update to 8.1.1240
* virglrenderer: update 0.7.0 -> 0.8.0
* vte: upgrade 0.52.2 -> 0.56.3
* waffle: upgrade 1.5.2 -> 1.6.0
* wayland-protocols: upgrade 1.17 -> 1.18
* webkitgtk: update to 2.24.4
* weston: upgrade 5.0.0 -> 7.0.0
* wget: update to 1.20.3
* wpa-supplicant: update to 2.9
* x11perf: update to 1.6.1
* x264: upgrade to latest revision
* xauth: upgrade 1.0.10 -> 1.1
* xf86-input-libinput: update to 0.29.0
* xinput: update to 1.6.3
* xkeyboard: upgrade 2.26 -> 2.27
* xorgproto: update to 2019.1
* xrandr: update to 1.5.1
* xserver-xorg: update to 1.20.5
* xtrans: upgrade 1.3.5 -> 1.4.0
* xwininfo: upgrade 1.1.4 -> 1.1.5

license
-------

Known Issues
------------
*Bug 13594: mpc8315e-rdb: the stap oeqa test causes OOM.
This issue is on a platform with minimal support and works outside the framework.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13594

*Bug 13595: strace ptest failed .
strace issue is two individual test regressions which is an improvement on the test timeouts we had previously.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13595

3.0 Release Notes WIP

2019-10-18T03:58:56Z

PaulEggleton: Major work on new features / enhancements section

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|NOTE: The formatting in this page is not meant to look good in the wiki - it's just a convenient place to collaborate. We need to stick to the text formatting that will end up in the actual release notes.
|}

Security Fixes
--------------
* binutils: CVE-2019-12972, CVE-2019-14250, CVE-2019-14444, CVE-2019-9070, CVE-2019-9071, CVE-2019-9074, CVE-2019-9075, CVE-2019-9076, CVE-2019-9077
* dbus: CVE-2019-12749
* gcc: CVE-2019-14250, CVE-2018-12886, CVE-2018-18484, CVE-2019-15847
* gdb: CVE-2017-9778
* ghostscript: CVE-2019-14811, CVE-2019-14817
* glib-2.0: CVE-2019-12450
* glibc: CVE-2018-20796 (same as CVE-2019-9169)
* gnupg: CVE-2019-13050
* gnutls: GNUTLS-SA-2019-03-27
* iptables: CVE-2019-11360
* libid3tag: CVE-2017-11550, CVE-2017-11551 (same as CVE-2004-2779)
* libxslt: CVE-2019-11068, CVE-2019-13117, CVE-2019-13118
* linux-yocto/4.19: CVE-2019-3887
* linux-yocto/5.0: CVE-2019-3887
* ltp: CVE-2017-17052
* nasm: CVE-2018-19755
* openssh: CVE-2018-20685, CVE-2019-6109, CVE-2019-6111
* patch: CVE-2018-1000156 (improved fix), CVE-2019-13636, CVE-2019-13638
* python3: CVE-2019-9740, CVE-2019-9948
* python: CVE-2018-20852, CVE-2019-9740, CVE-2019-9947 (same as CVE-2019-9740), CVE-2019-9948, CVE-2019-9636
* qemu: CVE-2019-12155, CVE-2019-15890
* rsync: CVE-2016-9840, CVE-2016-9841, CVE-2016-9842, CVE-2016-9843
* squashfs-tools: CVE-2015-4645, CVE-2015-4646
* tiff: CVE-2019-6128, CVE-2019-7663, CVE-2019-14973
* u-boot: CVE-2019-13103, CVE-2019-13104, CVE-2019-13105, CVE-2019-13106, CVE-2019-14192, CVE-2019-14193, CVE-2019-14194, CVE-2019-14195, CVE-2019-14196, CVE-2019-14197, CVE-2019-14198, CVE-2019-14199, CVE-2019-14200, CVE-2019-14201, CVE-2019-14202, CVE-2019-14203, CVE-2019-14204
* unzip: CVE-2019-13232
* vim: CVE-2019-12735

New Features / Enhancements
---------------------------
* Linux kernel 5.2/4.19, gcc 9.2, glibc 2.30 and ~260 other recipe upgrades
* Build change equivalence is detected and used to avoid rebuilding unchanged components (BETA)
* Architecture / machine-specific enhancements:
- New "qemuriscv64" emulated RISC-V 64-bit machine
- qemu: Add ppc64 to QEMU_TARGETS
- qemuarm64: Add QB_CPU_KVM to allow kvm acceleration
- New tune file for ARM Cortex-A53-Cortex-A57
- New tune file for arm1176jz-s CPU
- meson.bbclass: Handle microblaze* mapping to cpu family
- meson.bbclass: Make meson support aarch64_be.
- libffi: added RISC-V support
- icu: added armeb support
- runqemu: added support for kvm on aarch64
- beaglebone-yocto machine now set up to support booting images with runqemu
- qemux86: make it possible to use higher tunes using DEFAULTTUNE
* Kernel improvements:
- kernel-fitimage: introduce FIT_HASH_ALG
- kernel-module-split.bbclass: support CONFIG_MODULE_COMPRESS=y
- kernel-yocto: import security fragments from meta-security
- linux-yocto: add drm-bochs support
- linux-yocto: bsp/beaglebone: support qemu -machine virt
* multiconfig builds now reach their full potential:
- Many bugfixes and improvements
- sstate cache is now shared between configurations being built concurrently
- multiconfig configurations can be contained in layers
* Significant removal of old/obsolete software/patches ensuring we have a modern and up to date core Linux software stack:
- LSB support removed
- GTK+ 2 moved out to meta-oe
- Python 2 dependencies minimised
- Many obsolete patches dropped
* CVE checking enhancements:
- New cve-update-db recipe that reads from NVD JSON data feeds and supports network proxies
- Support for CVSSv3 scoring
- CVE_PRODUCT entries can now contain strings to match the vendor as well as product (vendor:product syntax)
* New INIT_MANAGER variable to make it easy to select the init manager (sysvinit, systemd, mdev-busybox)
* New recipes: binutils-cross-testsuite, core-image-sato-ptest-fast, dejagnu, efibootmgr, efivar, ell, glibc-testsuite, libcap-ng-python, libedit, libmodule-build-perl, libx11-compose-data, libxcrypt-compat, lsb-release, musl-obstack, opensbi, python3-pygments, python3-scons, python3-scons-native, stress-ng, vulkan-headers, vulkan-loader, vulkan-tools, wireless-regdb
* Added native variant to: glib-networking, grub, libsoup, python3-dbus
* BitBake improvements:
- Merged setscene tasks into the main runqueue so they can run in parallel
- fetch2/git: added sanity checking for git-lfs
- fetch2/svn: prevent from directly pulling from an externals w/o fetcher
- fetch2/npm: use npm pack to download node modules instead of wget
- Added --skip-setscene option
- Respect -f/--force option in conjunction with --runall or --runonly
- bitbake -e now supports showing base multiconfig configuration (using mc: prefix)
- "mc:" prefix now supported as a shorter version of multiconfig:
- Print more information when basehashes are mismatched
- Show task elapsed time in hours, minutes, and seconds
- Report all nonexistent directories in BBLAYERS in error message instead of just the first
- Improve validation of addtask and deltask arguments
- Added support for custom progress handlers injected via OE_EXTRA_IMPORTS
- Enable console keepalive to help usage with remote sessions
- Symlink the current cache file
* systemd-related improvements:
- serial-getty@.service: Allow device to fast fail if it does not exist
- Rewrote systemctl-native in Python supporting preset-all and mask
- Added partial support of drop-in configuration files to systemd-systemctl-native
- systemd-conf: added default configuration for wired network with DHCP
- systemd-conf: simplified creation of machine-specific configuration
- Create preset files and allow systemd to populate /etc/systemd/system instead of populating explicitly
- Added systemd helper unit to load/restore iptables rules
* runqemu improvements:
- Added support to pass multiple ports to tcpserial parameter
- Added support for a BIOS command-line variable (consistent with KERNEL)
- New QB_FSINFO variable supporting "wic:no-kernel-in-fs" and "wic:kernel-in-fs" for wic images
- Added support to handle EnrollDefaultKeys PK/KEK1 certificate
- Decoupled gtk and gl options
* wic improvements:
- New partition type for msdos partition tables
- New "bootimg-biosplusefi" source type that supports both BIOS and EFI
- Support for kernel with initramfs bundled
- bootimg-efi: add label source parameter
- bootimg-efi: allow multiple initrd
- bootimg-efi: replace hardcoded volume name with label
- Include .wks.in in wic search and list
- Use KERNEL_IMAGETYPE instead of hardcoding bzImage
- Added global debug option
* Other image-related improvements:
- Centralised default UEFI image configuration in conf/distro/image-uefi.conf
- Make gzipped images rsyncable
- initramfs-framework: support PARTLABEL option
- New bash-completion IMAGE_FEATURES item to add bash-completion support for all installed packages
* devtool/recipetool improvements:
- New "devtool menuconfig" subcommand
- devtool build now also runs do_deploy if applicable
- devtool finish now supports a --no-clean option
- devtool finish now warns if multiple layers have the same base name
- recipetool now supports creating recipes for Python 3
* Other script improvements:
- buildstats-diff: added option to filter tasks
- bitbake-layers: added several options to to make it easier to get plain output (for scripting)
- ddimage: replaced target device blacklist with mount check
- yocto-check-layer: Allow any case for README file detection
* SDK-related changes:
- New SDK_ARCHIVE_TYPE variable to control SDK archive format
- Introduce mechanism to keep nativesdk* sstate in eSDK
- Added nativesdk variant to: dnf, gzip, libtasn1, python3-dbus
* buildhistory improvements:
- Record sysroot changes in addition to runtime content
- Show time spent writing buildhistory
* Recipe sanity checking improvements:
- Added check to ensure perllocal.pod is not installed by non-CPAN perl recipes
- Added sanity checks for ${PN} vs ${BPN} and github archives in SRC_URI
- Check if a recipe incorrectly uses DEPENDS_${PN}
- Improved buildpath warning messages
- Simplified paths in host contamination warnings
* Automated testing improvements:
- Enabled test suites for gcc, glibc, binutils
- testimage: consider QB_DEFAULT_FSTYPE
- oe-selftest: implement console keepalive output
- Support for LTP / LTP compliance
- resulttool: Add log subcommand
- resulttool: enable loading results directly from an http/https URL
- resulttool: add manual test case configuration option
* poky-lsb replaced by poky-altcfg for alternate configurations to be tested on the autobuilder (as well as an example of subclassing a distro config)
* Added minver and maxver parameters for patches in SRC_URI for more flexibility in bbappends and common inc files
* PRIVATE_LIBS variable now supports shell-style wildcards for matching libraries
* Adoption of SPDX license identifiers throughout Yocto Project's components
* Added bbverbnote shell log command (consistent with bbwarn, bberror etc.)
* New OE_EXTRA_IMPORTS variable to make it easier to import custom modules into BitBake python environment
* busybox: enabled unicode support by default
* cmake: Use compiler launcher variable when ccache is enabled so that it can be disabled by build scripts if needed
* db: add new "verify" PACKAGECONFIG option for enabling database verification with db_verify command (default disabled)
* distcc: split into client and server packages
* dropbear: new "disable-weak-ciphers" PACKAGECONFIG option to disable older weak ciphers
* grub-efi-native: install grub-editenv
* lttng-modules: added git based recipe
* opkg: allow overriding OPKGLIBDIR
* ovmf: Generate test Platform key and first Key Exchange Key
* New PKGDATA_VARS variable to specify variables written out to pkgdata
* Obsolete stress recipe replaced by stress-ng
* uboot-sign: add support for different u-boot configurations
* update-rc.d: support enable/disable options
* waffle: support building without x11
* weston-init: Add possibility to run weston as non-root user
* python3: support recommends in manifest
* package_deb: add DPKG_BUILDCMD variable to allow customising dpkg command
* chrpath.bbclass: Add break_hardlinks parameter to allow breaking hardlinks when processing rpaths
* New "Apache-2.0-with-LLVM-exception" common license file
* screen: add /etc/screenrc as global config file
* utils/multiprocess_launch: Improve failing subprocess output
* Added local.conf/auto.conf into error report submitted by report-error.bbclass
* Added OpenEmbedded logo .svg file to repository (from OE-Classic)

Recipe Upgrades
---------------
* acpica: update to 20190816
* acpid: upgrade 2.0.31 -> 2.0.32
* adwaita-icon-theme: upgrade 3.30.1 -> 3.32.0
* alsa-lib: upgrade 1.1.8 -> 1.1.9
* alsa-plugins: upgrade 1.1.8 -> 1.1.9
* alsa-utils: upgrade 1.1.8 -> 1.1.9
* apr: upgrade 1.6.5 -> 1.7.0
* apt: update to 1.2.31
* aspell: update to 0.60.7
* atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-core: upgrade 2.30.0 -> 2.32.1
* autoconf-archive: update to 2019.01.06
* babeltrace: update to 1.5.7
* bash-completion: upgrade 2.8 -> 2.9
* bash: upgrade 4.4.18 -> 5.0
* bison: upgrade 3.0.4 -> 3.4.1
* boost: update to 1.71.0
* btrfs-tools: upgrade 4.20.1 -> 5.2.2
* build-compare: 2015.02.10 -> 2019.08.14
* busybox: 1.30.1 -> 1.31.0
* bzip2: update to 1.0.8
* ccache: upgrade 3.6 -> 3.7.3
* cmake: 3.14.1 -> 3.15.3
* cogl: upgrade 1.22.2 -> 1.22.4
* connman: update to 1.37
* coreutils: update to 8.31
* createrepo-c: update to 0.15.0
* cronie: update to 1.5.4
* cups: update to 2.2.12
* curl: update to 7.66.0
* dbus-test: Upgrade 1.12.12 -> 1.12.16
* dbus: Upgrade 1.12.12 -> 1.12.16
* debianutils: upgrade 4.8.6.1 -> 4.8.6.3
* desktop-file-utils: upgrade 0.23 -> 0.24
* distcc: upgrade 3.3.2 -> 3.3.3
* dnf: upgrade 4.1.0 -> 4.2.2
* dpkg: update to 1.19.7
* dropbear: update to 2019.78
* dtc: upgrade 1.4.7 -> 1.5.1
* e2fsprogs: 1.44.5 -> 1.45.3
* elfutils: 0.176 -> 0.177
* ell: update to 0.22
* encodings: update to 1.0.5
* epiphany: update to 3.32.4
* ethtool: update to 5.2
* eudev: update to 3.2.8
* expat: update to 2.2.8
* ffmpeg: update to 4.2.1
* file: update to 5.37
* flac: Upgrade 1.3.2 -> 1.3.3
* fontconfig: update to 2.13.1
* font-util: update to 1.3.2
* freetype: upgrade 2.9.1 -> 2.10.1
* gawk: upgrade 4.2.1 -> 5.0.1
* gcc-9: Upgrade to 9.2
* gdb: Upgrade from 8.2.1 to 8.3.1
* gdk-pixbuf: update 2.38.0 -> 2.38.2
* ghostscript: 9.26 -> 9.27
* git: update to 2.23.0
* glib-2.0: udpate 2.58.3 -> 2.60.7
* glibc: Update to glibc 2.30
* glib-networking: upgrade 2.60.1 -> 2.60.3
* gnu-config: Update to latest SHA
* gnupg: update to 2.2.17
* gnutls: upgrade 3.6.5 -> 3.6.8
* go-1.12: update to 1.12.9 minor release
* gobject-introspection: update to 1.60.2
* go-dep: update to 0.5.4
* go: update 1.12.1->1.12.6
* gpgme: upgrade 1.12.0 -> 1.13.1
* groff: upgrade 1.22.3 -> 1.22.4
* grub: upgrade 2.02 -> 2.04
* gsettings-desktop-schemas: upgrade 3.28.1 -> 3.32.0
* gst-examples: upgrade to 1.16.0
* gstreamer1.0-libav: upgrade to version 1.16.0
* gstreamer1.0-omx: upgrade to version 1.16.0
* gstreamer1.0-plugins-bad: upgrade to version 1.16.0
* gstreamer1.0-plugins-base: upgrade to version 1.16.0
* gstreamer1.0-plugins-good: upgrade to version 1.16.0
* gstreamer1.0-plugins-ugly: upgrade to version 1.16.0
* gstreamer1.0-python: upgrade to version 1.16.0
* gstreamer1.0-rtsp-server: upgrade to version 1.16.0
* gstreamer1.0: upgrade to version 1.16.0
* gstreamer1.0-vaapi: upgrade to version 1.16.0
* gst-validate: upgrade to version 1.16.0
* gtk+3: update 3.24.5 -> 3.24.8
* gtk-doc: upgrade 1.29 -> 1.31
* harfbuzz: upgrade 2.3.1 -> 2.6.1
* help2man-native: update to 1.47.11
* icu: update to 64.2
* ifupdown: update to 0.8.22
* iproute2: update to 5.2.0
* iptables: upgrade 1.6.2 -> 1.8.3
* iputils: upgrade to s20190709
* iso-codes: upgrade 4.2 -> 4.3
* iw: upgrade 4.14 -> 5.3
* kmscube: Bump revision to f632b23
* less: upgrade 550 -> 551
* libarchive: upgrade 3.3.3 -> 3.4.0
* libatomic-ops: upgrade 7.6.8 -> 7.6.10
* libbsd: upgrade 0.9.1 -> 0.10.0
* libcap: update to 2.27
* libcomps: upgrade 0.1.10 -> 0.1.11
* libcroco: update to 0.6.13
* libdazzle: update to 3.32.3
* libdnf: update to 0.28.1
* libdrm: update to 2.4.99
* libevdev: upgrade 1.6.0 -> 1.8.0
* libevent: upgrade 2.1.8 -> 2.1.11
* libffi: Upgrade to 3.3-rc0
* libglu: upgrade 9.0.0 -> 9.0.1
* libgpg-error: upgrade 1.35 -> 1.36
* libgudev: upgrade 232 -> 233
* libical: upgrade to 3.0.6
* libice: upgrade 1.0.9 -> 1.0.10
* libidn2: upgrade to 2.2.0
* libinput: update to 1.14.1
* libjpeg-turbo: upgrade 2.0.2 -> 2.0.3
* libmodule-build-perl: upgrade 0.4224 -> 0.4229
* libmodulemd: update to 2.6.0
* libnewt: upgrade 0.52.20 -> 0.52.21
* libnl: upgrade to 3.5.0
* libnotify: update to 0.7.8
* libnss-nis: upgrade 3.0 -> 3.1
* libogg: upgrade 1.3.3 -> 1.3.4
* libpam: Upgrade 1.3.0 -> 1.3.1
* libpcap: upgrade 1.9.0 -> 1.9.1
* libpciaccess: upgrade 0.14 -> 0.16
* libpcre2: upgrade 10.32 -> 10.33
* libpng: update to 1.6.37
* libpsl: update to 0.21.0
* librepo: update to 1.10.5
* libsdl2: upgrade 2.0.9 -> 2.0.10
* libsecret: 0.19.0
* libsolf: update to 0.7.5
* libsolv: update to 0.7.6
* libsoup-2.4: upgrade 2.66.1 -> 2.66.2
* libsoup: Upgrade from 2.64.2 to 2.66.1
* libtasn1: upgrade 4.13 -> 4.14
* libtest-needs-perl: upgrade 0.002005 -> 0.002006
* libtirpc: upgrade 1.0.3 -> 1.1.4
* liburcu: update to 0.11.1
* libva: upgrade 2.4.0 -> 2.5.0
* libva-utils: upgrade 2.4.0 -> 2.5.0
* libwebp: upgrade 1.0.2 -> 1.0.3
* libx11-compose-data: upgrade 1.6.7 -> 1.6.8
* libx11: update to 1.6.8
* libxcrypt: update to 4.4.8
* libxdmcp: update to 1.1.3
* libxext: update to 1.3.4
* libxft: upgrade 2.3.2 -> 2.3.3
* libxi: update to 1.7.10
* libxkbfile: update 1.1.0
* libxml2: upgrade 2.9.8 -> 2.9.9
* libxml-sax-perl: upgrade 1.00 -> 1.02
* libxmu: update to 1.1.3
* libxrandr: update to 1.5.2
* libxt: update to 1.2.0
* libxvmc: update to 1.0.11
* libyaml: update to 0.2.2
* lighttpd: Upgrade 1.4.53 -> 1.4.54
* linux-firmware: Upgrade to 20190815
* linux-libc-headers: update to v5.2 headers
* linux-yocto/4.19: update to 4.19.72 and -rt22
* linux-yocto-dev: bump to 5.3-rcX
* linux-yocto: introduce 5.2.17 recipes
* linux-yocto-rt: update to 5.0.5-rt9
* llvm: Update to 8.0.1
* logrotate: upgrade 3.15.0 -> 3.15.1
* ltp: upgrade 20190115 -> 20190517
* lttng-modules: upgrade 2.10.8 -> 2.10.11
* lttng-tools: update to 2.10.7
* lttng-ust: upgrade 2.10.3 -> 2.10.5
* lz4: update to 1.9.2
* makedepend: update to 1.0.6
* man-db: upgrade 2.8.4 -> 2.8.7
* man-pages: upgrade 4.16 -> 5.01
* mc: update to 4.8.23
* mesa-demos: update to 8.4.0
* mesa: Update 19.0.1 -> 19.1.6
* meson: update to 0.51.2
* mmc-utils: update to the latest upstream code
* mobile-broadband-provider-info: upgrade 20190116 -> 20190618
* mpg123: upgrade 1.25.10 -> 1.25.11
* msmtp: 1.6.6 -> 1.8.5
* mtd-utils: Upgrade to 2.1.1
* mtools: update to 4.0.23
* musl: Update to latest master
* ncurses: upgrade 6.1+20181013 -> 6.1+20190803
* nettle: upgrade 3.4.1 -> 3.5.1
* newlib: Upgrade to 3.1.0
* nfs-utils: 2.3.3 -> 2.4.1
* nss: upgrade 3.42.1 -> 3.45
* ofono: upgrade 1.25 -> 1.30
* opensbi: Update from 0.3 to 0.4
* openssh: Upgrade 7.9p1 -> 8.0p1
* openssl: Upgrade 1.1.1b -> 1.1.1d
* opkg: upgrade to version 0.4.1
* opkg-utils: upgrade to version 0.4.1
* orc: update to 0.4.29
* ovmf: Update to version edk2-stable201905
* p11-kit: update to 0.23.16.1
* pango: upgrade 1.42.4 -> 1.44.6
* patchelf: Upgrade 0.9 -> 0.10
* perl: Move perl-sanity -> perl
* perl: update to 5.30.0
* piglit: upgrade to latest revision
* pixman: update to 0.38.4
* pkgconf: upgrade 1.6.0 -> 1.6.3
* ptest-runner: update from 2.3.1 to 2.3.2
* python3-dbus: upgrade 1.2.8 -> 1.2.12
* python3-docutils: update to 0.15
* python3-git: update to 3.0.2
* python3-mako: update to 1.1.0
* python3-numpy: update to 1.17.0
* python3-pbr: update to 5.4.3
* python3-pip: update to 19.2.3
* python3-pycairo: update to 1.18.1
* python3-pygobject: update to 3.34.0
* python3-scons: update to 3.1.1
* python3: upgrade 3.7.3 -> 3.7.4
* python-numpy: update to 1.16.3
* python-scons: update to 3.1.0
* python-setuptools: update to 41.2.0
* python: update to 3.7.3
* qemu: Upgrade from 3.1.0 to 4.1
* quilt: update to 0.66
* quota: update to 4.05
* rng-tools: 6.6 -> 6.7
* ruby: update to 2.5.5
* socat: upgrade 1.7.3.2 -> 1.7.3.3
* sqlite3: update to 3.29.0
* squashfs-tools: upgrade to commit f95864afe883
* strace: Upgrade to 5.3
* subversion: upgrade 1.11.1 -> 1.12.2
* sysprof: upgrade 3.30.2 -> 3.32.0
* sysstat: 12.1.3 -> 12.1.6
* systemd: upgrade to 243
* systemtap: update to 57c9aca9f1ff32a6add10e02ecd33b7314fad499
* tar: update to 1.32
* timezone: update to 2019c
* u-boot: Upgrade from 2019.01 to 2019.07
* uninative: Update to 2.7 release
* usbutils: upgrade 010->012
* util-linux: upgrade to 2.34
* vala: update to 0.44.7
* valgrind: update from 3.14.0 to 3.15.0
* vim: Update to 8.1.1240
* virglrenderer: update 0.7.0 -> 0.8.0
* vte: upgrade 0.52.2 -> 0.56.3
* waffle: upgrade 1.5.2 -> 1.6.0
* wayland-protocols: upgrade 1.17 -> 1.18
* webkitgtk: update to 2.24.4
* weston: upgrade 5.0.0 -> 7.0.0
* wget: update to 1.20.3
* wpa-supplicant: update to 2.9
* x11perf: update to 1.6.1
* x264: upgrade to latest revision
* xauth: upgrade 1.0.10 -> 1.1
* xf86-input-libinput: update to 0.29.0
* xinput: update to 1.6.3
* xkeyboard: upgrade 2.26 -> 2.27
* xorgproto: update to 2019.1
* xrandr: update to 1.5.1
* xserver-xorg: update to 1.20.5
* xtrans: upgrade 1.3.5 -> 1.4.0
* xwininfo: upgrade 1.1.4 -> 1.1.5

license
-------

Known Issues
------------
*Bug 13594: mpc8315e-rdb: the stap oeqa test causes OOM.
This issue is on a platform with minimal support and works outside the framework.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13594

*Bug 13595: strace ptest failed .
strace issue is two individual test regressions which is an improvement on the test timeouts we had previously.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13595

3.0 Release Notes WIP

2019-10-18T03:57:48Z

PaulEggleton: Tidy up CVEs

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|NOTE: The formatting in this page is not meant to look good in the wiki - it's just a convenient place to collaborate. We need to stick to the text formatting that will end up in the actual release notes.
|}

Security Fixes
--------------
* binutils: CVE-2019-12972, CVE-2019-14250, CVE-2019-14444, CVE-2019-9070, CVE-2019-9071, CVE-2019-9074, CVE-2019-9075, CVE-2019-9076, CVE-2019-9077
* dbus: CVE-2019-12749
* gcc: CVE-2019-14250, CVE-2018-12886, CVE-2018-18484, CVE-2019-15847
* gdb: CVE-2017-9778
* ghostscript: CVE-2019-14811, CVE-2019-14817
* glib-2.0: CVE-2019-12450
* glibc: CVE-2018-20796 (same as CVE-2019-9169)
* gnupg: CVE-2019-13050
* gnutls: GNUTLS-SA-2019-03-27
* iptables: CVE-2019-11360
* libid3tag: CVE-2017-11550, CVE-2017-11551 (same as CVE-2004-2779)
* libxslt: CVE-2019-11068, CVE-2019-13117, CVE-2019-13118
* linux-yocto/4.19: CVE-2019-3887
* linux-yocto/5.0: CVE-2019-3887
* ltp: CVE-2017-17052
* nasm: CVE-2018-19755
* openssh: CVE-2018-20685, CVE-2019-6109, CVE-2019-6111
* patch: CVE-2018-1000156 (improved fix), CVE-2019-13636, CVE-2019-13638
* python3: CVE-2019-9740, CVE-2019-9948
* python: CVE-2018-20852, CVE-2019-9740, CVE-2019-9947 (same as CVE-2019-9740), CVE-2019-9948, CVE-2019-9636
* qemu: CVE-2019-12155, CVE-2019-15890
* rsync: CVE-2016-9840, CVE-2016-9841, CVE-2016-9842, CVE-2016-9843
* squashfs-tools: CVE-2015-4645, CVE-2015-4646
* tiff: CVE-2019-6128, CVE-2019-7663, CVE-2019-14973
* u-boot: CVE-2019-13103, CVE-2019-13104, CVE-2019-13105, CVE-2019-13106, CVE-2019-14192, CVE-2019-14193, CVE-2019-14194, CVE-2019-14195, CVE-2019-14196, CVE-2019-14197, CVE-2019-14198, CVE-2019-14199, CVE-2019-14200, CVE-2019-14201, CVE-2019-14202, CVE-2019-14203, CVE-2019-14204
* unzip: CVE-2019-13232
* vim: CVE-2019-12735

New Features / Enhancements
---------------------------
* Linux kernel 5.2/4.19, gcc 9.2, glibc 2.30 and ~260 other recipe upgrades
* New INIT_MANAGER variable to make it easy to select the init manager (sysvinit, systemd, mdev-busybox)
* poky-lsb replaced by poky-altcfg for alternate configurations to be tested on the autobuilder (as well as an example of subclassing a distro config)
* New recipes: binutils-cross-testsuite, core-image-sato-ptest-fast, dejagnu, efibootmgr, efivar, ell, glibc-testsuite, libcap-ng-python, libedit, libmodule-build-perl, libx11-compose-data, libxcrypt-compat, lsb-release, musl-obstack, opensbi, python3-pygments, python3-scons, python3-scons-native, stress-ng, vulkan-headers, vulkan-loader, vulkan-tools, wireless-regdb
* Significant removal of old/obsolete software/patches ensuring we have a modern and up to date core Linux software stack.
- LSB support moved to separate layer [was it??]
- GTK+ 2 moved out to meta-oe
- Python 2 dependencies minimised
- many obsolete patches dropped
* Build change equivalence is detected and used to avoid rebuilding unchanged components
* Adoption of SPDX license identifiers throughout Yocto Project's components
* "Multi-Config" builds reaching their full potential
- Many bugfixes and improvements
- sstate cache is now shared between configurations being built concurrently
- multiconfig configurations can be contained in layers
* CVE checking enhancements:
- New cve-update-db recipe that reads from NVD JSON data feeds and supports network proxies
- Support for CVSSv3 scoring
- CVE_PRODUCT entries can now contain strings to match the vendor as well as product (vendor:product syntax)
* Add nativesdk variant to: dnf, gzip, libtasn1, python3-dbus
* Add native variant to: glib-networking, grub, libsoup, python3-dbus

* Added bbverbnote shell log command
* Added support for arm1176jz-s CPU specific tuning
* Apache-2.0-with-LLVM-exception: Add new license file
* base.bbclass: Add OE_EXTRA_IMPORTS
* bash-completion: add image feature
* binutils-cross-testsuite: Create recipe for test suite execution
* bitbake: BBHandler: Fix addtask and deltask
* bitbake: bb: siggen: Make dump_sigfile and compare_sigfiles print uuid4
* bitbake: bb: siggen: Print more info when basehash are mis-matched
* bitbake: bitbake: Add --skip-setscene option
* bitbake: bitbake: fetch2/git: git-lfs check
* bitbake: bitbake-layers: show-recipes: Enable bare output
* bitbake: bitbake-layers: show-recipes: Select recipes from selected layer
* bitbake: bitbake-layers: show-recipes: Show recipes only
* bitbake: bitbake: respect force flag in runall and runonly
* bitbake: bitbake: Rework hash equivalence
* bitbake: bitbake: Show base multiconfig environment
* bitbake: build: implement custom progress handlers injected via OE_EXTRA_IMPORTS
* bitbake: build.py: check dependendent task for addtask
* bitbake: cache: Add SimpleCache class
* bitbake: cache: Create a symlink for current cachefile
* bitbake.conf: add git-lfs to HOSTTOOLS_NONFATAL
* bitbake: cooker/hashserv: Allow autostarting of a local hash server using BB_HASHSERVE
* bitbake: cooker: list all nonexistent bblayer directories
* bitbake: fetch2/git: add git-lfs toggle option
* bitbake: fetch2/npm: Use npm pack to download node modules instead of wget
* bitbake: knotty: Implement console 'keepalive' output
* bitbake: knotty: Pretty print task elapsed time
* bitbake: runqueue: Enable dynamic task adjustment to hash equivalency
* bitbake: runqueue: Merge scenequeue and real task queue code together
* bitbake: runqueue: Merge the queues and execute setscene and normal tasks in parallel
* bitbake: siggen: Use unique hashes for tasks
* bitbake: svn.py: Stop SVN from directly pulling from an external layer w/o fetcher
* buildhistory: report sysroot changes
* buildhistory: show time spent writting buildhistory
* buildhistory: write the contents of the sysroot
* busybox: enable unicode support
* chrpath.bbclass: Add break_hardlinks kwarg to allow breaking hardlinks
* cmake: Use compiler launcher variable when ccache is enabled
* db: add switch for building database verification
* deb: allow custom dpkg command
* devtool: build: Also run deploy for devtool build if applicable
* devtool: finish: Add suppport for the --no-clean option
* devtool: provide support for devtool menuconfig command
* devtool/standard.py: Create a copy of kernel source within work-shared if not present
* devtool/standard.py: Update devtool modify to copy source from work-shared if its already downloaded
* devtool: warn user about multiple layer having the same base name
* distcc: split into client and server packages
* dropbear: new feature: disable-weak-ciphers
* gcc-runtime: Add do_check task for executing gcc test suites
* glibc-testsuite: Create a recipe to implement glibc test suite
* grub-efi-native: Install grub-editenv
* icu: Added armeb support.
* image_types.bbclass: make gzipped images rsyncable
* image-uefi.conf: add config file holding configuration for UEFI images
* initramfs-framework: support PARTLABEL option
* insane: add check for perllocal.pod
* insane: add sanity checks to SRC_URI
* insane: check if the recipe incorrectly uses DEPENDS_${PN}
* insane: improve buildpath warning messages
* insane: use clean_path for the host contamination warnings
* iptables: add systemd helper unit to load/restore rules
* kernel-fitimage: introduce FIT_HASH_ALG
* kernel-module-split.bbclass: support CONFIG_MODULE_COMPRESS=y
* kernel-yocto: import security fragments from meta-security
* libffi: Add RISC-V support
* libmodule-build-perl: move from meta-perl
* linux-yocto/4.19: make drm-bochs feature available
* linux-yocto/5.0: bsp: add basic xilinx zynqmp support
* linux-yocto/5.0: make scsi-debug include scsi core configs
* linux-yocto/5.2: config tweaks and kallsyms fix
* linux-yocto: add drm-bochs support
* linux-yocto: bsp/beaglebone: support qemu -machine virt
* live-vm-common.bbclass: provide efi population functions for live images
* local.conf.sample: Add Hash Equivalence
* logparser: Add decoding ltp logs
* logparser: Add LTP compliance section
* ltp: add runtime test
* ltp_compliance: add new runtime
* lttng-modules: Add git based recipe
* meson.bbclass: Handle microblaze* mapping to cpu family
* meson.bbclass: Make meson support aarch64_be.
* oe-selftest: Implement console 'keepalive' output
* oe.svg: Copy artwork from openembedded-classic.
* opensbi: Initial commit of OpenSBI
* opkg/package/rootfs_ipk: allow overwriting OPKGLIBDIR
* ovmf: Generate test Platform key and first Key Exchange Key
* package.bbclass: allow shell-style wildcards in PRIVATE_LIBS
* package.bbclass: Clean up writing of runtime pkgdata files
* patch: add minver and maxver parameters
* populate_sdk_base: provide options to set sdk type
* populate_sdk_ext: Introduce mechanism to keep nativesdk* sstate in esdk
* python3-scons-{native}: add recipe
* python3: support recommends in manifest
* qemu: Add ppc64 to QEMU_TARGETS
* qemuarm64: Add QB_CPU_KVM to allow kvm acceleration
* qemuriscv64: Add the QEMU RISC-V 64-bit machine
* qemurunner.py: Be more verbose about problems
* qemux86: Allow higher tunes
* recipetool: add python3 support
* report-error.bbclass: add local.conf/auto.conf into error report
* resulttool: Add log subcommand
* resulttool: add LTP compliance section
* resulttool: add ltp test support
* resulttool: Load results from URL
* resulttool/manualexecution: Enable test case configuration option
* runqemu: Add support for kvm on aarch64
* runqemu: Add support to handle EnrollDefaultKeys PK/KEK1 certificate
* runqemu: Add the support to pass multi ports to tcpserial parameter
* runqemu: decouple gtk and gl options
* runqemu: QB_FSINFO to support fstype wic images
* screen: add /etc/screenrc as global config file
* scripts/buildstats-diff: Add option to filter tasks
* scripts/contrib/ddimage: replace blacklist with mount check
* scripts/runqemu: Add support for the BIOS variable
* serial-getty@.service: Allow device to fast fail if it does not exist
* stress-ng: add a recipe that replaces the original stress
* systemctl-native: Rewrite in Python supporting preset-all and mask
* systemd: Add partial support of drop-in configuration files to systemd-systemctl-native
* systemd-conf: configure wired network with dhcp
* systemd-conf: simplify creation of machine-specific configuration
* systemd: create preset files instead of installing in image
* testimage: consider QB_DEFAULT_FSTYPE
* tune-cortexa57-cortexa53: add tunes for ARM Cortex-A53-Cortex-A57
* uboot-sign: add support for different u-boot configurations
* update-rc.d: support enable/disable options
* utils/multiprocess_launch: Improve failing subprocess output
* waffle: supprt build waffle without x11
* weston-init: Add possibility to run weston as non-root user
* weston-init: Add support for non-root start
* wic: add global debug option
* wic: Add partition type for msdos partition tables
* wic: add support for kernel with initramfs bundled
* wic: bootimg-efi: add label source parameter
* wic/bootimg-efi: allow multiple initrd
* wic/bootimg-efi: replace hardcoded volume name with label
* wic/engine: include .wks.in in wic search and list
* wic/plugins: kernel image refer to KERNEL_IMAGETYPE
* wic/plugins: Source that support both EFI and BIOS
* wireless-regdb: Add recipe
* yocto-bsp: runqemu runs beaglebone-yocto
* yocto-check-layer: Allow any case for README file detection

Recipe Upgrades
---------------
* acpica: update to 20190816
* acpid: upgrade 2.0.31 -> 2.0.32
* adwaita-icon-theme: upgrade 3.30.1 -> 3.32.0
* alsa-lib: upgrade 1.1.8 -> 1.1.9
* alsa-plugins: upgrade 1.1.8 -> 1.1.9
* alsa-utils: upgrade 1.1.8 -> 1.1.9
* apr: upgrade 1.6.5 -> 1.7.0
* apt: update to 1.2.31
* aspell: update to 0.60.7
* atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-core: upgrade 2.30.0 -> 2.32.1
* autoconf-archive: update to 2019.01.06
* babeltrace: update to 1.5.7
* bash-completion: upgrade 2.8 -> 2.9
* bash: upgrade 4.4.18 -> 5.0
* bison: upgrade 3.0.4 -> 3.4.1
* boost: update to 1.71.0
* btrfs-tools: upgrade 4.20.1 -> 5.2.2
* build-compare: 2015.02.10 -> 2019.08.14
* busybox: 1.30.1 -> 1.31.0
* bzip2: update to 1.0.8
* ccache: upgrade 3.6 -> 3.7.3
* cmake: 3.14.1 -> 3.15.3
* cogl: upgrade 1.22.2 -> 1.22.4
* connman: update to 1.37
* coreutils: update to 8.31
* createrepo-c: update to 0.15.0
* cronie: update to 1.5.4
* cups: update to 2.2.12
* curl: update to 7.66.0
* dbus-test: Upgrade 1.12.12 -> 1.12.16
* dbus: Upgrade 1.12.12 -> 1.12.16
* debianutils: upgrade 4.8.6.1 -> 4.8.6.3
* desktop-file-utils: upgrade 0.23 -> 0.24
* distcc: upgrade 3.3.2 -> 3.3.3
* dnf: upgrade 4.1.0 -> 4.2.2
* dpkg: update to 1.19.7
* dropbear: update to 2019.78
* dtc: upgrade 1.4.7 -> 1.5.1
* e2fsprogs: 1.44.5 -> 1.45.3
* elfutils: 0.176 -> 0.177
* ell: update to 0.22
* encodings: update to 1.0.5
* epiphany: update to 3.32.4
* ethtool: update to 5.2
* eudev: update to 3.2.8
* expat: update to 2.2.8
* ffmpeg: update to 4.2.1
* file: update to 5.37
* flac: Upgrade 1.3.2 -> 1.3.3
* fontconfig: update to 2.13.1
* font-util: update to 1.3.2
* freetype: upgrade 2.9.1 -> 2.10.1
* gawk: upgrade 4.2.1 -> 5.0.1
* gcc-9: Upgrade to 9.2
* gdb: Upgrade from 8.2.1 to 8.3.1
* gdk-pixbuf: update 2.38.0 -> 2.38.2
* ghostscript: 9.26 -> 9.27
* git: update to 2.23.0
* glib-2.0: udpate 2.58.3 -> 2.60.7
* glibc: Update to glibc 2.30
* glib-networking: upgrade 2.60.1 -> 2.60.3
* gnu-config: Update to latest SHA
* gnupg: update to 2.2.17
* gnutls: upgrade 3.6.5 -> 3.6.8
* go-1.12: update to 1.12.9 minor release
* gobject-introspection: update to 1.60.2
* go-dep: update to 0.5.4
* go: update 1.12.1->1.12.6
* gpgme: upgrade 1.12.0 -> 1.13.1
* groff: upgrade 1.22.3 -> 1.22.4
* grub: upgrade 2.02 -> 2.04
* gsettings-desktop-schemas: upgrade 3.28.1 -> 3.32.0
* gst-examples: upgrade to 1.16.0
* gstreamer1.0-libav: upgrade to version 1.16.0
* gstreamer1.0-omx: upgrade to version 1.16.0
* gstreamer1.0-plugins-bad: upgrade to version 1.16.0
* gstreamer1.0-plugins-base: upgrade to version 1.16.0
* gstreamer1.0-plugins-good: upgrade to version 1.16.0
* gstreamer1.0-plugins-ugly: upgrade to version 1.16.0
* gstreamer1.0-python: upgrade to version 1.16.0
* gstreamer1.0-rtsp-server: upgrade to version 1.16.0
* gstreamer1.0: upgrade to version 1.16.0
* gstreamer1.0-vaapi: upgrade to version 1.16.0
* gst-validate: upgrade to version 1.16.0
* gtk+3: update 3.24.5 -> 3.24.8
* gtk-doc: upgrade 1.29 -> 1.31
* harfbuzz: upgrade 2.3.1 -> 2.6.1
* help2man-native: update to 1.47.11
* icu: update to 64.2
* ifupdown: update to 0.8.22
* iproute2: update to 5.2.0
* iptables: upgrade 1.6.2 -> 1.8.3
* iputils: upgrade to s20190709
* iso-codes: upgrade 4.2 -> 4.3
* iw: upgrade 4.14 -> 5.3
* kmscube: Bump revision to f632b23
* less: upgrade 550 -> 551
* libarchive: upgrade 3.3.3 -> 3.4.0
* libatomic-ops: upgrade 7.6.8 -> 7.6.10
* libbsd: upgrade 0.9.1 -> 0.10.0
* libcap: update to 2.27
* libcomps: upgrade 0.1.10 -> 0.1.11
* libcroco: update to 0.6.13
* libdazzle: update to 3.32.3
* libdnf: update to 0.28.1
* libdrm: update to 2.4.99
* libevdev: upgrade 1.6.0 -> 1.8.0
* libevent: upgrade 2.1.8 -> 2.1.11
* libffi: Upgrade to 3.3-rc0
* libglu: upgrade 9.0.0 -> 9.0.1
* libgpg-error: upgrade 1.35 -> 1.36
* libgudev: upgrade 232 -> 233
* libical: upgrade to 3.0.6
* libice: upgrade 1.0.9 -> 1.0.10
* libidn2: upgrade to 2.2.0
* libinput: update to 1.14.1
* libjpeg-turbo: upgrade 2.0.2 -> 2.0.3
* libmodule-build-perl: upgrade 0.4224 -> 0.4229
* libmodulemd: update to 2.6.0
* libnewt: upgrade 0.52.20 -> 0.52.21
* libnl: upgrade to 3.5.0
* libnotify: update to 0.7.8
* libnss-nis: upgrade 3.0 -> 3.1
* libogg: upgrade 1.3.3 -> 1.3.4
* libpam: Upgrade 1.3.0 -> 1.3.1
* libpcap: upgrade 1.9.0 -> 1.9.1
* libpciaccess: upgrade 0.14 -> 0.16
* libpcre2: upgrade 10.32 -> 10.33
* libpng: update to 1.6.37
* libpsl: update to 0.21.0
* librepo: update to 1.10.5
* libsdl2: upgrade 2.0.9 -> 2.0.10
* libsecret: 0.19.0
* libsolf: update to 0.7.5
* libsolv: update to 0.7.6
* libsoup-2.4: upgrade 2.66.1 -> 2.66.2
* libsoup: Upgrade from 2.64.2 to 2.66.1
* libtasn1: upgrade 4.13 -> 4.14
* libtest-needs-perl: upgrade 0.002005 -> 0.002006
* libtirpc: upgrade 1.0.3 -> 1.1.4
* liburcu: update to 0.11.1
* libva: upgrade 2.4.0 -> 2.5.0
* libva-utils: upgrade 2.4.0 -> 2.5.0
* libwebp: upgrade 1.0.2 -> 1.0.3
* libx11-compose-data: upgrade 1.6.7 -> 1.6.8
* libx11: update to 1.6.8
* libxcrypt: update to 4.4.8
* libxdmcp: update to 1.1.3
* libxext: update to 1.3.4
* libxft: upgrade 2.3.2 -> 2.3.3
* libxi: update to 1.7.10
* libxkbfile: update 1.1.0
* libxml2: upgrade 2.9.8 -> 2.9.9
* libxml-sax-perl: upgrade 1.00 -> 1.02
* libxmu: update to 1.1.3
* libxrandr: update to 1.5.2
* libxt: update to 1.2.0
* libxvmc: update to 1.0.11
* libyaml: update to 0.2.2
* lighttpd: Upgrade 1.4.53 -> 1.4.54
* linux-firmware: Upgrade to 20190815
* linux-libc-headers: update to v5.2 headers
* linux-yocto/4.19: update to 4.19.72 and -rt22
* linux-yocto-dev: bump to 5.3-rcX
* linux-yocto: introduce 5.2.17 recipes
* linux-yocto-rt: update to 5.0.5-rt9
* llvm: Update to 8.0.1
* logrotate: upgrade 3.15.0 -> 3.15.1
* ltp: upgrade 20190115 -> 20190517
* lttng-modules: upgrade 2.10.8 -> 2.10.11
* lttng-tools: update to 2.10.7
* lttng-ust: upgrade 2.10.3 -> 2.10.5
* lz4: update to 1.9.2
* makedepend: update to 1.0.6
* man-db: upgrade 2.8.4 -> 2.8.7
* man-pages: upgrade 4.16 -> 5.01
* mc: update to 4.8.23
* mesa-demos: update to 8.4.0
* mesa: Update 19.0.1 -> 19.1.6
* meson: update to 0.51.2
* mmc-utils: update to the latest upstream code
* mobile-broadband-provider-info: upgrade 20190116 -> 20190618
* mpg123: upgrade 1.25.10 -> 1.25.11
* msmtp: 1.6.6 -> 1.8.5
* mtd-utils: Upgrade to 2.1.1
* mtools: update to 4.0.23
* musl: Update to latest master
* ncurses: upgrade 6.1+20181013 -> 6.1+20190803
* nettle: upgrade 3.4.1 -> 3.5.1
* newlib: Upgrade to 3.1.0
* nfs-utils: 2.3.3 -> 2.4.1
* nss: upgrade 3.42.1 -> 3.45
* ofono: upgrade 1.25 -> 1.30
* opensbi: Update from 0.3 to 0.4
* openssh: Upgrade 7.9p1 -> 8.0p1
* openssl: Upgrade 1.1.1b -> 1.1.1d
* opkg: upgrade to version 0.4.1
* opkg-utils: upgrade to version 0.4.1
* orc: update to 0.4.29
* ovmf: Update to version edk2-stable201905
* p11-kit: update to 0.23.16.1
* pango: upgrade 1.42.4 -> 1.44.6
* patchelf: Upgrade 0.9 -> 0.10
* perl: Move perl-sanity -> perl
* perl: update to 5.30.0
* piglit: upgrade to latest revision
* pixman: update to 0.38.4
* pkgconf: upgrade 1.6.0 -> 1.6.3
* ptest-runner: update from 2.3.1 to 2.3.2
* python3-dbus: upgrade 1.2.8 -> 1.2.12
* python3-docutils: update to 0.15
* python3-git: update to 3.0.2
* python3-mako: update to 1.1.0
* python3-numpy: update to 1.17.0
* python3-pbr: update to 5.4.3
* python3-pip: update to 19.2.3
* python3-pycairo: update to 1.18.1
* python3-pygobject: update to 3.34.0
* python3-scons: update to 3.1.1
* python3: upgrade 3.7.3 -> 3.7.4
* python-numpy: update to 1.16.3
* python-scons: update to 3.1.0
* python-setuptools: update to 41.2.0
* python: update to 3.7.3
* qemu: Upgrade from 3.1.0 to 4.1
* quilt: update to 0.66
* quota: update to 4.05
* rng-tools: 6.6 -> 6.7
* ruby: update to 2.5.5
* socat: upgrade 1.7.3.2 -> 1.7.3.3
* sqlite3: update to 3.29.0
* squashfs-tools: upgrade to commit f95864afe883
* strace: Upgrade to 5.3
* subversion: upgrade 1.11.1 -> 1.12.2
* sysprof: upgrade 3.30.2 -> 3.32.0
* sysstat: 12.1.3 -> 12.1.6
* systemd: upgrade to 243
* systemtap: update to 57c9aca9f1ff32a6add10e02ecd33b7314fad499
* tar: update to 1.32
* timezone: update to 2019c
* u-boot: Upgrade from 2019.01 to 2019.07
* uninative: Update to 2.7 release
* usbutils: upgrade 010->012
* util-linux: upgrade to 2.34
* vala: update to 0.44.7
* valgrind: update from 3.14.0 to 3.15.0
* vim: Update to 8.1.1240
* virglrenderer: update 0.7.0 -> 0.8.0
* vte: upgrade 0.52.2 -> 0.56.3
* waffle: upgrade 1.5.2 -> 1.6.0
* wayland-protocols: upgrade 1.17 -> 1.18
* webkitgtk: update to 2.24.4
* weston: upgrade 5.0.0 -> 7.0.0
* wget: update to 1.20.3
* wpa-supplicant: update to 2.9
* x11perf: update to 1.6.1
* x264: upgrade to latest revision
* xauth: upgrade 1.0.10 -> 1.1
* xf86-input-libinput: update to 0.29.0
* xinput: update to 1.6.3
* xkeyboard: upgrade 2.26 -> 2.27
* xorgproto: update to 2019.1
* xrandr: update to 1.5.1
* xserver-xorg: update to 1.20.5
* xtrans: upgrade 1.3.5 -> 1.4.0
* xwininfo: upgrade 1.1.4 -> 1.1.5

license
-------

Known Issues
------------
*Bug 13594: mpc8315e-rdb: the stap oeqa test causes OOM.
This issue is on a platform with minimal support and works outside the framework.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13594

*Bug 13595: strace ptest failed .
strace issue is two individual test regressions which is an improvement on the test timeouts we had previously.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13595

FutureMigrationGuide

2019-10-16T12:19:53Z

PaulEggleton:

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|This page should be used to keep track of items which should be added to the [http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration migration guide] in the YP Reference Manual. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.

Once the migration guide for a release has been completed the contents of this page should be cleared out.
|}

=3.0 Migration Guide items=

== Init system selection ==

Changing the init system manager previously required setting a number of different variables; this can now be accomplished by setting the INIT_MANAGER variable and corresponding include files (conf/distro/include/init-manager-*.conf); include files are provided for four values - "none", "sysvinit", "systemd" and "mdev-busybox". The default value "none" for INIT_MANAGER should allow your current settings to continue working, but it is advisable to set INIT_MANAGER explicitly.

== LSB support removed ==

LSB as a standard isn't current, and isn't well suited to embedded applications. Support may be continued in a separate layer if needed but at present it has been removed from the core.

Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

== Removed recipes ==

* core-image-lsb-dev: part of removed LSB support
* core-image-lsb: part of removed LSB support
* core-image-lsb-sdk: part of removed LSB support
* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
* gcc-8.3: remove 8.3 from zeus
* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
* irda-utils: obsolete - IrDA support has been removed from the Linux kernel in version 4.17 and later.
* libnewt-python: libnewt Python support merged into main libnewt recipe
* libsdl: replaced by newer libsdl2
* libx11-diet: obsolete
* libxx86dga: remove obsolete client libary
* libxx86misc: remove this now redundant library
* linux-yocto: version 5.0 removed
* lsbinitscripts: part of removed LSB support
* lsb: part of removed LSB support
* lsbtest: part of removed LSB support
* openssl10: replaced by newer openssl 1.1
* packagegroup-core-lsb: part of removed LSB support
* python-nose: remove the python 2.x version of the recipe
* python-numpy: remove the python 2.x version of the recipe
* python-scons: remove the python 2.x version of the recipe
* source-highlight: no longer needed
* stress: replaced by stress-ng
* vulkan: split into vulkan-loader, vulkan-headers and vulkan-tools
* weston-conf: functionality moved to weston-init

== Packaging changes ==

* The epiphany browser has been dropped from packagegroup-self-hosted as it has not been needed inside build-appliance-image for a long time and was causing resource problems.
* libcap-ng python support has been moved to a separate libcap-ng-python recipe to streamline the build process when the python bindings aren't needed
* libdrm now packages the amdgpu.ids file into a separate libdrm-amdgpu package
* python3: the runpy module is now in the python3-core package as it is required to support the common "python3 -m" command usage.
* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

== CVE checking ==

cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 scoring and makes other improvements.

Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

== Bitbake changes ==

* addtask statements now properly validate dependent tasks - previously an invalid task here would be silently ignored, now it will generate a warning.
* Other invalid addtask and deltask usages will now trigger warnings (multiple target tasks arguments with addtask / deltask, multiple before/after clauses)
* The "multiconfig" prefix is now shortened to "mc"; "multiconfig" will continue to work, however it may be removed in a future release.
* bitbake -g no longer generates a recipe-depends.dot file as the contents (a reprocessed version of task-depends.dot) were confusing.
* The bb.build.FuncFailed exception, previously raised by bb.build.exec_func() when certain other exceptions have occurred, has been removed. The real underlying exceptions will be raised instead. If you have calls to bb.build.exec_func() in custom classes or tinfoil-using scripts, any references to bb.build.FuncFailed should be cleaned up.
* Additionally, the bb.build.exec_func() no longer accepts the "pythonexception" parameter - it now always raises exceptions. Remove this argument in any calls to bb.build.exec_func() in custom classes or scripts.
* The BB_SETSCENE_VERIFY_FUNCTION2 is no longer used - in the unlikely event that you have any references to it, they should be removed.
* The RunQueueExecuteScenequeue and RunQueueExecuteTasks events have been removed since setscene tasks are now executed as part of the normal runqueue. Any event handling code in custom classes or scripts that handles these two events will need to be updated.
* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

== Sanity checks ==

* SRC_URI is now checked for usage of two problematic items:
*# "${PN}" - instead "${BPN}" should be used to avoid problems when PN is prefixed or suffixed e.g. with multiconfig.
*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
* The file-rdeps runtime dependency check no longer expands RDEPENDS recursively as there is no mechanism to ensure they can be fully computed, and thus races sometimes resulted in errors showing up and sometimes not. Thus you may now see errors for missing runtime dependencies that were previously satisfied recursively e.g. package A contains a shell script starting with #!/bin/bash but has no dependency on bash, but depends on package B that does depend on bash. Add the missing dependency / dependencies to resolve the warning.
* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

== Miscellaneous ==

* The gnome class has been removed, as it did not do very much anymore. Recipes that previously inherited this class should be updated to do the following:
inherit gnomebase gtk-icon-cache gconf mime
* The meta/recipes-kernel/linux/linux-dtb.inc file has been removed. It was previously deprecated (in favour of setting KERNEL_DEVICETREE in any kernel recipe) and only produced a warning. Remove any include/require statements pointing to this file.
* TARGET_CFLAGS, TARGET_CPPFLAGS, TARGET_CXXFLAGS, and TARGET_LDFLAGS are no longer exported to the external environment. This has not required changes to any recipes, but if for some reason the software being built by one of your recipes is expecting these variables to be set then it will now fail, and you will need to either export the variable(s) in the recipe or change the scripts so that that isn't necessary.
* The host distro identifier as used in NATIVELSBSTRING (when not using uninative) and SANITY_TESTED_DISTROS is now always lowercased even if it does not contain a version number.
* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. However, this should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.
* conf/distro/include/world-broken.inc has been removed - where we need to disable certain recipes when using the musl C library, individual recipes now have COMPATIBLE_HOST_libc-musl set with a comment explaining why.

FutureMigrationGuide

2019-10-16T12:19:04Z

PaulEggleton:

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|This page should be used to keep track of items which should be added to the [http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration migration guide] in the YP Reference Manual. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.

Once the migration guide for a release has been completed the contents of this page should be cleared out.
|}

=3.0 Migration Guide items=

== Init system selection ==

Changing the init system manager previously required setting a number of different variables; this can now be accomplished by setting the INIT_MANAGER variable and corresponding include files (conf/distro/include/init-manager-*.conf); include files are provided for four values - "none", "sysvinit", "systemd" and "mdev-busybox". The default value "none" for INIT_MANAGER should allow your current settings to continue working, but it is advisable to set INIT_MANAGER explicitly.

== LSB support removed ==

LSB as a standard isn't current, and isn't well suited to embedded applications. Support may be continued in a separate layer if needed but at present it has been removed from the core.

Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

== Removed recipes ==

* core-image-lsb-dev: part of removed LSB support
* core-image-lsb: part of removed LSB support
* core-image-lsb-sdk: part of removed LSB support
* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
* gcc-8.3: remove 8.3 from zeus
* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
* irda-utils: obsolete - IrDA support has been removed from the Linux kernel in version 4.17 and later.
* libnewt-python: libnewt Python support merged into main libnewt recipe
* libsdl: replaced by newer libsdl2
* libx11-diet: obsolete
* libxx86dga: remove obsolete client libary
* libxx86misc: remove this now redundant library
* linux-yocto: version 5.0 removed
* lsbinitscripts: part of removed LSB support
* lsb: part of removed LSB support
* lsbtest: part of removed LSB support
* openssl10: replaced by newer openssl 1.1
* packagegroup-core-lsb: part of removed LSB support
* python-nose: remove the python 2.x version of the recipe
* python-numpy: remove the python 2.x version of the recipe
* python-scons: remove the python 2.x version of the recipe
* source-highlight: no longer needed
* stress: replaced by stress-ng
* vulkan: split into vulkan-loader, vulkan-headers and vulkan-tools
* weston-conf: functionality moved to weston-init

== Packaging changes ==

* The epiphany browser has been dropped from packagegroup-self-hosted as it has not been needed inside build-appliance-image for a long time and was causing resource problems.
* libcap-ng python support has been moved to a separate libcap-ng-python recipe to streamline the build process when the python bindings aren't needed
* libdrm now packages the amdgpu.ids file into a separate libdrm-amdgpu package
* python3: the runpy module is now in the python3-core package as it is required to support the common "python3 -m" command usage.
* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

== CVE checking ==

cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 scoring and makes other improvements.

Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

== Bitbake changes ==

* addtask statements now properly validate dependent tasks - previously an invalid task here would be silently ignored, now it will generate a warning.
* Other invalid addtask and deltask usages will now trigger warnings (multiple target tasks arguments with addtask / deltask, multiple before/after clauses)
* The "multiconfig" prefix is now shortened to "mc"; "multiconfig" will continue to work, however it may be removed in a future release.
* bitbake -g no longer generates a recipe-depends.dot file as the contents (a reprocessed version of task-depends.dot) were confusing.
* The bb.build.FuncFailed exception, previously raised by bb.build.exec_func() when certain other exceptions have occurred, has been removed. The real underlying exceptions will be raised instead. If you have calls to bb.build.exec_func() in custom classes or tinfoil-using scripts, any references to bb.build.FuncFailed should be cleaned up.
* Additionally, the bb.build.exec_func() no longer accepts the "pythonexception" parameter - it now always raises exceptions. Remove this argument in any calls to bb.build.exec_func() in custom classes or scripts.
* The BB_SETSCENE_VERIFY_FUNCTION2 is no longer used - in the unlikely event that you have any references to it, they should be removed.
* The RunQueueExecuteScenequeue and RunQueueExecuteTasks events have been removed since setscene tasks are now executed as part of the normal runqueue. Any event handling code in custom classes or scripts that handles these two events will need to be updated.
* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

== Sanity checks ==

* SRC_URI is now checked for usage of two problematic items:
*# "${PN}" - instead "${BPN}" should be used to avoid problems when PN is prefixed or suffixed e.g. with multiconfig.
*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
* The file-rdeps runtime dependency check no longer expands RDEPENDS recursively as there is no mechanism to ensure they can be fully computed, and thus races sometimes resulted in errors showing up and sometimes not. Thus you may now see errors for missing runtime dependencies that were previously satisfied recursively e.g. package A contains a shell script starting with #!/bin/bash but has no dependency on bash, but depends on package B that does depend on bash. Add the missing dependency / dependencies to resolve the warning.
* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

== Miscellaneous ==

* The gnome class has been removed, as it did not do very much anymore. Recipes that previously inherited this class should be updated to do the following:
inherit gnomebase gtk-icon-cache gconf mime
* The meta/recipes-kernel/linux/linux-dtb.inc file has been removed. It was previously deprecated (in favour of setting KERNEL_DEVICETREE in any kernel recipe) and only produced a warning. Remove any include/require statements pointing to this file.
* TARGET_CFLAGS, TARGET_CPPFLAGS, TARGET_CXXFLAGS, and TARGET_LDFLAGS are no longer exported to the external environment. This has not required changes to any recipes, but if for some reason the software being built by one of your recipes is expecting these variables to be set then it will now fail, and you will need to either export the variable(s) in the recipe or change the scripts so that that isn't necessary.
* The host distro identifier as used in NATIVELSBSTRING (when not using uninative) and SANITY_TESTED_DISTROS is now always lowercased even if it does not contain a version number.
* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before. <span style="color: red; font-weight:bold;">[needs clarification]</span>
* conf/distro/include/world-broken.inc has been removed - where we need to disable certain recipes when using the musl C library, individual recipes now have COMPATIBLE_HOST_libc-musl set with a comment explaining why.

FutureMigrationGuide

2019-10-16T12:18:51Z

PaulEggleton:

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|This page should be used to keep track of items which should be added to the [http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration migration guide] in the YP Reference Manual. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.

Once the migration guide for a release has been completed the contents of this page should be cleared out.
|}

=3.0 Migration Guide items=

== Init system selection ==

Changing the init system manager previously required setting a number of different variables; this can now be accomplished by setting the INIT_MANAGER variable and corresponding include files (conf/distro/include/init-manager-*.conf); include files are provided for four values - "none", "sysvinit", "systemd" and "mdev-busybox". The default value "none" for INIT_MANAGER should allow your current settings to continue working, but it is advisable to set INIT_MANAGER explicitly.

== LSB support removed ==

LSB as a standard isn't current, and isn't well suited to embedded applications. Support may be continued in a separate layer if needed but at present it has been removed from the core.

Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

== Removed recipes ==

* core-image-lsb-dev: part of removed LSB support
* core-image-lsb: part of removed LSB support
* core-image-lsb-sdk: part of removed LSB support
* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
* gcc-8.3: remove 8.3 from zeus
* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
* irda-utils: obsolete - IrDA support has been removed from the Linux kernel in version 4.17 and later.
* libnewt-python: libnewt Python support merged into main libnewt recipe
* libsdl: replaced by newer libsdl2
* libx11-diet: obsolete
* libxx86dga: remove obsolete client libary
* libxx86misc: remove this now redundant library
* linux-yocto: version 5.0 removed
* lsbinitscripts: part of removed LSB support
* lsb: part of removed LSB support
* lsbtest: part of removed LSB support
* openssl10: replaced by newer openssl 1.1
* packagegroup-core-lsb: part of removed LSB support
* python-nose: remove the python 2.x version of the recipe
* python-numpy: remove the python 2.x version of the recipe
* python-scons: remove the python 2.x version of the recipe
* source-highlight: no longer needed
* stress: replaced by stress-ng
* vulkan: split into vulkan-loader, vulkan-headers and vulkan-tools
* weston-conf: functionality moved to weston-init

== Packaging changes ==

* The epiphany browser has been dropped from packagegroup-self-hosted as it has not been needed inside build-appliance-image for a long time and was causing resource problems.
* libcap-ng python support has been moved to a separate libcap-ng-python recipe to streamline the build process when the python bindings aren't needed
* libdrm now packages the amdgpu.ids file into a separate libdrm-amdgpu package
* python3: the runpy module is now in the python3-core package as it is required to support the common "python3 -m" command usage.
* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

== CVE checking ==

cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 scoring and makes other improvements.

Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

== Bitbake changes ==

* addtask statements now properly validate dependent tasks - previously an invalid task here would be silently ignored, now it will generate a warning.
* Other invalid addtask and deltask usages will now trigger warnings (multiple target tasks arguments with addtask / deltask, multiple before/after clauses)
* The "multiconfig" prefix is now shortened to "mc"; "multiconfig" will continue to work, however it may be removed in a future release.
* bitbake -g no longer generates a recipe-depends.dot file as the contents (a reprocessed version of task-depends.dot) were confusing.
* The bb.build.FuncFailed exception, previously raised by bb.build.exec_func() when certain other exceptions have occurred, has been removed. The real underlying exceptions will be raised instead. If you have calls to bb.build.exec_func() in custom classes or tinfoil-using scripts, any references to bb.build.FuncFailed should be cleaned up.
* Additionally, the bb.build.exec_func() no longer accepts the "pythonexception" parameter - it now always raises exceptions. Remove this argument in any calls to bb.build.exec_func() in custom classes or scripts.
* The BB_SETSCENE_VERIFY_FUNCTION2 is no longer used - in the unlikely event that you have any references to it, they should be removed.
* The RunQueueExecuteScenequeue and RunQueueExecuteTasks events have been removed since setscene tasks are now executed as part of the normal runqueue. Any event handling code in custom classes or scripts that handles these two events will need to be updated.
* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

== Sanity checks ==

* SRC_URI is now checked for usage of two problematic items:
*# "${PN}" - instead "${BPN}" should be used to avoid problems when PN is prefixed or suffixed e.g. with multiconfig.
*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
* The file-rdeps runtime dependency check no longer expands RDEPENDS recursively as there is no mechanism to ensure they can be fully computed, and thus races sometimes resulted in errors showing up and sometimes not. Thus you may now see errors for missing runtime dependencies that were previously satisfied recursively e.g. package A contains a shell script starting with #!/bin/bash but has no dependency on bash, but depends on package B that does depend on bash. Add the missing dependency / dependencies to resolve the warning.

* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

== Miscellaneous ==

* The gnome class has been removed, as it did not do very much anymore. Recipes that previously inherited this class should be updated to do the following:
inherit gnomebase gtk-icon-cache gconf mime
* The meta/recipes-kernel/linux/linux-dtb.inc file has been removed. It was previously deprecated (in favour of setting KERNEL_DEVICETREE in any kernel recipe) and only produced a warning. Remove any include/require statements pointing to this file.
* TARGET_CFLAGS, TARGET_CPPFLAGS, TARGET_CXXFLAGS, and TARGET_LDFLAGS are no longer exported to the external environment. This has not required changes to any recipes, but if for some reason the software being built by one of your recipes is expecting these variables to be set then it will now fail, and you will need to either export the variable(s) in the recipe or change the scripts so that that isn't necessary.
* The host distro identifier as used in NATIVELSBSTRING (when not using uninative) and SANITY_TESTED_DISTROS is now always lowercased even if it does not contain a version number.
* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before. <span style="color: red; font-weight:bold;">[needs clarification]</span>
* conf/distro/include/world-broken.inc has been removed - where we need to disable certain recipes when using the musl C library, individual recipes now have COMPATIBLE_HOST_libc-musl set with a comment explaining why.

3.0 Release Notes WIP

2019-10-16T04:43:50Z

PaulEggleton:

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|NOTE: The formatting in this page is not meant to look good in the wiki - it's just a convenient place to collaborate. We need to stick to the text formatting that will end up in the actual release notes.
|}

Security Fixes
--------------

New Features / Enhancements
---------------------------
* Linux kernel 5.2/4.19, gcc 9.2, glibc 2.30 and ~260 other recipe upgrades
* New INIT_MANAGER variable to make it easy to select the init manager (sysvinit, systemd, mdev-busybox)
* poky-lsb replaced by poky-altcfg for alternate configurations to be tested on the autobuilder (as well as an example of subclassing a distro config)
* New recipes: binutils-cross-testsuite, core-image-sato-ptest-fast, dejagnu, efibootmgr, efivar, ell, glibc-testsuite, libcap-ng-python, libedit, libmodule-build-perl, libx11-compose-data, libxcrypt-compat, lsb-release, musl-obstack, opensbi, python3-pygments, python3-scons, python3-scons-native, stress-ng, vulkan-headers, vulkan-loader, vulkan-tools, wireless-regdb
* Significant removal of old/obsolete software/patches ensuring we have a modern and up to date core Linux software stack.
- LSB support moved to separate layer [was it??]
- GTK+ 2 moved out to meta-oe
- Python 2 dependencies minimised
- many obsolete patches dropped
* Build change equivalence is detected and used to avoid rebuilding unchanged components
* Adoption of SPDX license identifiers throughout Yocto Project's components
* "Multi-Config" builds reaching their full potential
- Many bugfixes and improvements
- sstate cache is now shared between configurations being built concurrently
- multiconfig configurations can be contained in layers
* CVE checking enhancements:
- New cve-update-db recipe that reads from NVD JSON data feeds and supports network proxies
- Support for CVSSv3 scoring
- CVE_PRODUCT entries can now contain strings to match the vendor as well as product (vendor:product syntax)
* Add nativesdk variant to: dnf, gzip, libtasn1, python3-dbus
* Add native variant to: glib-networking, grub, libsoup, python3-dbus

* Added bbverbnote shell log command
* Added support for arm1176jz-s CPU specific tuning
* Apache-2.0-with-LLVM-exception: Add new license file
* base.bbclass: Add OE_EXTRA_IMPORTS
* bash-completion: add image feature
* binutils-cross-testsuite: Create recipe for test suite execution
* bitbake: BBHandler: Fix addtask and deltask
* bitbake: bb: siggen: Make dump_sigfile and compare_sigfiles print uuid4
* bitbake: bb: siggen: Print more info when basehash are mis-matched
* bitbake: bitbake: Add --skip-setscene option
* bitbake: bitbake: fetch2/git: git-lfs check
* bitbake: bitbake-layers: show-recipes: Enable bare output
* bitbake: bitbake-layers: show-recipes: Select recipes from selected layer
* bitbake: bitbake-layers: show-recipes: Show recipes only
* bitbake: bitbake: respect force flag in runall and runonly
* bitbake: bitbake: Rework hash equivalence
* bitbake: bitbake: Show base multiconfig environment
* bitbake: build: implement custom progress handlers injected via OE_EXTRA_IMPORTS
* bitbake: build.py: check dependendent task for addtask
* bitbake: cache: Add SimpleCache class
* bitbake: cache: Create a symlink for current cachefile
* bitbake.conf: add git-lfs to HOSTTOOLS_NONFATAL
* bitbake: cooker/hashserv: Allow autostarting of a local hash server using BB_HASHSERVE
* bitbake: cooker: list all nonexistent bblayer directories
* bitbake: fetch2/git: add git-lfs toggle option
* bitbake: fetch2/npm: Use npm pack to download node modules instead of wget
* bitbake: knotty: Implement console 'keepalive' output
* bitbake: knotty: Pretty print task elapsed time
* bitbake: runqueue: Enable dynamic task adjustment to hash equivalency
* bitbake: runqueue: Merge scenequeue and real task queue code together
* bitbake: runqueue: Merge the queues and execute setscene and normal tasks in parallel
* bitbake: siggen: Use unique hashes for tasks
* bitbake: svn.py: Stop SVN from directly pulling from an external layer w/o fetcher
* buildhistory: report sysroot changes
* buildhistory: show time spent writting buildhistory
* buildhistory: write the contents of the sysroot
* busybox: enable unicode support
* chrpath.bbclass: Add break_hardlinks kwarg to allow breaking hardlinks
* cmake: Use compiler launcher variable when ccache is enabled
* db: add switch for building database verification
* deb: allow custom dpkg command
* devtool: build: Also run deploy for devtool build if applicable
* devtool: finish: Add suppport for the --no-clean option
* devtool: provide support for devtool menuconfig command
* devtool/standard.py: Create a copy of kernel source within work-shared if not present
* devtool/standard.py: Update devtool modify to copy source from work-shared if its already downloaded
* devtool: warn user about multiple layer having the same base name
* distcc: split into client and server packages
* dropbear: new feature: disable-weak-ciphers
* gcc-runtime: Add do_check task for executing gcc test suites
* glibc-testsuite: Create a recipe to implement glibc test suite
* grub-efi-native: Install grub-editenv
* icu: Added armeb support.
* image_types.bbclass: make gzipped images rsyncable
* image-uefi.conf: add config file holding configuration for UEFI images
* initramfs-framework: support PARTLABEL option
* insane: add check for perllocal.pod
* insane: add sanity checks to SRC_URI
* insane: check if the recipe incorrectly uses DEPENDS_${PN}
* insane: improve buildpath warning messages
* insane: use clean_path for the host contamination warnings
* iptables: add systemd helper unit to load/restore rules
* kernel-fitimage: introduce FIT_HASH_ALG
* kernel-module-split.bbclass: support CONFIG_MODULE_COMPRESS=y
* kernel-yocto: import security fragments from meta-security
* libffi: Add RISC-V support
* libmodule-build-perl: move from meta-perl
* linux-yocto/4.19: make drm-bochs feature available
* linux-yocto/5.0: bsp: add basic xilinx zynqmp support
* linux-yocto/5.0: make scsi-debug include scsi core configs
* linux-yocto/5.2: config tweaks and kallsyms fix
* linux-yocto: add drm-bochs support
* linux-yocto: bsp/beaglebone: support qemu -machine virt
* live-vm-common.bbclass: provide efi population functions for live images
* local.conf.sample: Add Hash Equivalence
* logparser: Add decoding ltp logs
* logparser: Add LTP compliance section
* ltp: add runtime test
* ltp_compliance: add new runtime
* lttng-modules: Add git based recipe
* meson.bbclass: Handle microblaze* mapping to cpu family
* meson.bbclass: Make meson support aarch64_be.
* oe-selftest: Implement console 'keepalive' output
* oe.svg: Copy artwork from openembedded-classic.
* opensbi: Initial commit of OpenSBI
* opkg/package/rootfs_ipk: allow overwriting OPKGLIBDIR
* ovmf: Generate test Platform key and first Key Exchange Key
* package.bbclass: allow shell-style wildcards in PRIVATE_LIBS
* package.bbclass: Clean up writing of runtime pkgdata files
* patch: add minver and maxver parameters
* populate_sdk_base: provide options to set sdk type
* populate_sdk_ext: Introduce mechanism to keep nativesdk* sstate in esdk
* python3-scons-{native}: add recipe
* python3: support recommends in manifest
* qemu: Add ppc64 to QEMU_TARGETS
* qemuarm64: Add QB_CPU_KVM to allow kvm acceleration
* qemuriscv64: Add the QEMU RISC-V 64-bit machine
* qemurunner.py: Be more verbose about problems
* qemux86: Allow higher tunes
* recipetool: add python3 support
* report-error.bbclass: add local.conf/auto.conf into error report
* resulttool: Add log subcommand
* resulttool: add LTP compliance section
* resulttool: add ltp test support
* resulttool: Load results from URL
* resulttool/manualexecution: Enable test case configuration option
* runqemu: Add support for kvm on aarch64
* runqemu: Add support to handle EnrollDefaultKeys PK/KEK1 certificate
* runqemu: Add the support to pass multi ports to tcpserial parameter
* runqemu: decouple gtk and gl options
* runqemu: QB_FSINFO to support fstype wic images
* screen: add /etc/screenrc as global config file
* scripts/buildstats-diff: Add option to filter tasks
* scripts/contrib/ddimage: replace blacklist with mount check
* scripts/runqemu: Add support for the BIOS variable
* serial-getty@.service: Allow device to fast fail if it does not exist
* stress-ng: add a recipe that replaces the original stress
* systemctl-native: Rewrite in Python supporting preset-all and mask
* systemd: Add partial support of drop-in configuration files to systemd-systemctl-native
* systemd-conf: configure wired network with dhcp
* systemd-conf: simplify creation of machine-specific configuration
* systemd: create preset files instead of installing in image
* testimage: consider QB_DEFAULT_FSTYPE
* tune-cortexa57-cortexa53: add tunes for ARM Cortex-A53-Cortex-A57
* uboot-sign: add support for different u-boot configurations
* update-rc.d: support enable/disable options
* utils/multiprocess_launch: Improve failing subprocess output
* waffle: supprt build waffle without x11
* weston-init: Add possibility to run weston as non-root user
* weston-init: Add support for non-root start
* wic: add global debug option
* wic: Add partition type for msdos partition tables
* wic: add support for kernel with initramfs bundled
* wic: bootimg-efi: add label source parameter
* wic/bootimg-efi: allow multiple initrd
* wic/bootimg-efi: replace hardcoded volume name with label
* wic/engine: include .wks.in in wic search and list
* wic/plugins: kernel image refer to KERNEL_IMAGETYPE
* wic/plugins: Source that support both EFI and BIOS
* wireless-regdb: Add recipe
* yocto-bsp: runqemu runs beaglebone-yocto
* yocto-check-layer: Allow any case for README file detection

Recipe Upgrades
---------------
* acpica: update to 20190816
* acpid: upgrade 2.0.31 -> 2.0.32
* adwaita-icon-theme: upgrade 3.30.1 -> 3.32.0
* alsa-lib: upgrade 1.1.8 -> 1.1.9
* alsa-plugins: upgrade 1.1.8 -> 1.1.9
* alsa-utils: upgrade 1.1.8 -> 1.1.9
* apr: upgrade 1.6.5 -> 1.7.0
* apt: update to 1.2.31
* aspell: update to 0.60.7
* atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-core: upgrade 2.30.0 -> 2.32.1
* autoconf-archive: update to 2019.01.06
* babeltrace: update to 1.5.7
* bash-completion: upgrade 2.8 -> 2.9
* bash: upgrade 4.4.18 -> 5.0
* bison: upgrade 3.0.4 -> 3.4.1
* boost: update to 1.71.0
* btrfs-tools: upgrade 4.20.1 -> 5.2.2
* build-compare: 2015.02.10 -> 2019.08.14
* busybox: 1.30.1 -> 1.31.0
* bzip2: update to 1.0.8
* ccache: upgrade 3.6 -> 3.7.3
* cmake: 3.14.1 -> 3.15.3
* cogl: upgrade 1.22.2 -> 1.22.4
* connman: update to 1.37
* coreutils: update to 8.31
* createrepo-c: update to 0.15.0
* cronie: update to 1.5.4
* cups: update to 2.2.12
* curl: update to 7.66.0
* dbus-test: Upgrade 1.12.12 -> 1.12.16
* dbus: Upgrade 1.12.12 -> 1.12.16
* debianutils: upgrade 4.8.6.1 -> 4.8.6.3
* desktop-file-utils: upgrade 0.23 -> 0.24
* distcc: upgrade 3.3.2 -> 3.3.3
* dnf: upgrade 4.1.0 -> 4.2.2
* dpkg: update to 1.19.7
* dropbear: update to 2019.78
* dtc: upgrade 1.4.7 -> 1.5.1
* e2fsprogs: 1.44.5 -> 1.45.3
* elfutils: 0.176 -> 0.177
* ell: update to 0.22
* encodings: update to 1.0.5
* epiphany: update to 3.32.4
* ethtool: update to 5.2
* eudev: update to 3.2.8
* expat: update to 2.2.8
* ffmpeg: update to 4.2.1
* file: update to 5.37
* flac: Upgrade 1.3.2 -> 1.3.3
* fontconfig: update to 2.13.1
* font-util: update to 1.3.2
* freetype: upgrade 2.9.1 -> 2.10.1
* gawk: upgrade 4.2.1 -> 5.0.1
* gcc-9: Upgrade to 9.2
* gdb: Upgrade from 8.2.1 to 8.3.1
* gdk-pixbuf: update 2.38.0 -> 2.38.2
* ghostscript: 9.26 -> 9.27
* git: update to 2.23.0
* glib-2.0: udpate 2.58.3 -> 2.60.7
* glibc: Update to glibc 2.30
* glib-networking: upgrade 2.60.1 -> 2.60.3
* gnu-config: Update to latest SHA
* gnupg: update to 2.2.17
* gnutls: upgrade 3.6.5 -> 3.6.8
* go-1.12: update to 1.12.9 minor release
* gobject-introspection: update to 1.60.2
* go-dep: update to 0.5.4
* go: update 1.12.1->1.12.6
* gpgme: upgrade 1.12.0 -> 1.13.1
* groff: upgrade 1.22.3 -> 1.22.4
* grub: upgrade 2.02 -> 2.04
* gsettings-desktop-schemas: upgrade 3.28.1 -> 3.32.0
* gst-examples: upgrade to 1.16.0
* gstreamer1.0-libav: upgrade to version 1.16.0
* gstreamer1.0-omx: upgrade to version 1.16.0
* gstreamer1.0-plugins-bad: upgrade to version 1.16.0
* gstreamer1.0-plugins-base: upgrade to version 1.16.0
* gstreamer1.0-plugins-good: upgrade to version 1.16.0
* gstreamer1.0-plugins-ugly: upgrade to version 1.16.0
* gstreamer1.0-python: upgrade to version 1.16.0
* gstreamer1.0-rtsp-server: upgrade to version 1.16.0
* gstreamer1.0: upgrade to version 1.16.0
* gstreamer1.0-vaapi: upgrade to version 1.16.0
* gst-validate: upgrade to version 1.16.0
* gtk+3: update 3.24.5 -> 3.24.8
* gtk-doc: upgrade 1.29 -> 1.31
* harfbuzz: upgrade 2.3.1 -> 2.6.1
* help2man-native: update to 1.47.11
* icu: update to 64.2
* ifupdown: update to 0.8.22
* iproute2: update to 5.2.0
* iptables: upgrade 1.6.2 -> 1.8.3
* iputils: upgrade to s20190709
* iso-codes: upgrade 4.2 -> 4.3
* iw: upgrade 4.14 -> 5.3
* kmscube: Bump revision to f632b23
* less: upgrade 550 -> 551
* libarchive: upgrade 3.3.3 -> 3.4.0
* libatomic-ops: upgrade 7.6.8 -> 7.6.10
* libbsd: upgrade 0.9.1 -> 0.10.0
* libcap: update to 2.27
* libcomps: upgrade 0.1.10 -> 0.1.11
* libcroco: update to 0.6.13
* libdazzle: update to 3.32.3
* libdnf: update to 0.28.1
* libdrm: update to 2.4.99
* libevdev: upgrade 1.6.0 -> 1.8.0
* libevent: upgrade 2.1.8 -> 2.1.11
* libffi: Upgrade to 3.3-rc0
* libglu: upgrade 9.0.0 -> 9.0.1
* libgpg-error: upgrade 1.35 -> 1.36
* libgudev: upgrade 232 -> 233
* libical: upgrade to 3.0.6
* libice: upgrade 1.0.9 -> 1.0.10
* libidn2: upgrade to 2.2.0
* libinput: update to 1.14.1
* libjpeg-turbo: upgrade 2.0.2 -> 2.0.3
* libmodule-build-perl: upgrade 0.4224 -> 0.4229
* libmodulemd: update to 2.6.0
* libnewt: upgrade 0.52.20 -> 0.52.21
* libnl: upgrade to 3.5.0
* libnotify: update to 0.7.8
* libnss-nis: upgrade 3.0 -> 3.1
* libogg: upgrade 1.3.3 -> 1.3.4
* libpam: Upgrade 1.3.0 -> 1.3.1
* libpcap: upgrade 1.9.0 -> 1.9.1
* libpciaccess: upgrade 0.14 -> 0.16
* libpcre2: upgrade 10.32 -> 10.33
* libpng: update to 1.6.37
* libpsl: update to 0.21.0
* librepo: update to 1.10.5
* libsdl2: upgrade 2.0.9 -> 2.0.10
* libsecret: 0.19.0
* libsolf: update to 0.7.5
* libsolv: update to 0.7.6
* libsoup-2.4: upgrade 2.66.1 -> 2.66.2
* libsoup: Upgrade from 2.64.2 to 2.66.1
* libtasn1: upgrade 4.13 -> 4.14
* libtest-needs-perl: upgrade 0.002005 -> 0.002006
* libtirpc: upgrade 1.0.3 -> 1.1.4
* liburcu: update to 0.11.1
* libva: upgrade 2.4.0 -> 2.5.0
* libva-utils: upgrade 2.4.0 -> 2.5.0
* libwebp: upgrade 1.0.2 -> 1.0.3
* libx11-compose-data: upgrade 1.6.7 -> 1.6.8
* libx11: update to 1.6.8
* libxcrypt: update to 4.4.8
* libxdmcp: update to 1.1.3
* libxext: update to 1.3.4
* libxft: upgrade 2.3.2 -> 2.3.3
* libxi: update to 1.7.10
* libxkbfile: update 1.1.0
* libxml2: upgrade 2.9.8 -> 2.9.9
* libxml-sax-perl: upgrade 1.00 -> 1.02
* libxmu: update to 1.1.3
* libxrandr: update to 1.5.2
* libxt: update to 1.2.0
* libxvmc: update to 1.0.11
* libyaml: update to 0.2.2
* lighttpd: Upgrade 1.4.53 -> 1.4.54
* linux-firmware: Upgrade to 20190815
* linux-libc-headers: update to v5.2 headers
* linux-yocto/4.19: update to 4.19.72 and -rt22
* linux-yocto-dev: bump to 5.3-rcX
* linux-yocto: introduce 5.2.17 recipes
* linux-yocto-rt: update to 5.0.5-rt9
* llvm: Update to 8.0.1
* logrotate: upgrade 3.15.0 -> 3.15.1
* ltp: upgrade 20190115 -> 20190517
* lttng-modules: upgrade 2.10.8 -> 2.10.11
* lttng-tools: update to 2.10.7
* lttng-ust: upgrade 2.10.3 -> 2.10.5
* lz4: update to 1.9.2
* makedepend: update to 1.0.6
* man-db: upgrade 2.8.4 -> 2.8.7
* man-pages: upgrade 4.16 -> 5.01
* mc: update to 4.8.23
* mesa-demos: update to 8.4.0
* mesa: Update 19.0.1 -> 19.1.6
* meson: update to 0.51.2
* mmc-utils: update to the latest upstream code
* mobile-broadband-provider-info: upgrade 20190116 -> 20190618
* mpg123: upgrade 1.25.10 -> 1.25.11
* msmtp: 1.6.6 -> 1.8.5
* mtd-utils: Upgrade to 2.1.1
* mtools: update to 4.0.23
* musl: Update to latest master
* ncurses: upgrade 6.1+20181013 -> 6.1+20190803
* nettle: upgrade 3.4.1 -> 3.5.1
* newlib: Upgrade to 3.1.0
* nfs-utils: 2.3.3 -> 2.4.1
* nss: upgrade 3.42.1 -> 3.45
* ofono: upgrade 1.25 -> 1.30
* opensbi: Update from 0.3 to 0.4
* openssh: Upgrade 7.9p1 -> 8.0p1
* openssl: Upgrade 1.1.1b -> 1.1.1d
* opkg: upgrade to version 0.4.1
* opkg-utils: upgrade to version 0.4.1
* orc: update to 0.4.29
* ovmf: Update to version edk2-stable201905
* p11-kit: update to 0.23.16.1
* pango: upgrade 1.42.4 -> 1.44.6
* patchelf: Upgrade 0.9 -> 0.10
* perl: Move perl-sanity -> perl
* perl: update to 5.30.0
* piglit: upgrade to latest revision
* pixman: update to 0.38.4
* pkgconf: upgrade 1.6.0 -> 1.6.3
* ptest-runner: update from 2.3.1 to 2.3.2
* python3-dbus: upgrade 1.2.8 -> 1.2.12
* python3-docutils: update to 0.15
* python3-git: update to 3.0.2
* python3-mako: update to 1.1.0
* python3-numpy: update to 1.17.0
* python3-pbr: update to 5.4.3
* python3-pip: update to 19.2.3
* python3-pycairo: update to 1.18.1
* python3-pygobject: update to 3.34.0
* python3-scons: update to 3.1.1
* python3: upgrade 3.7.3 -> 3.7.4
* python-numpy: update to 1.16.3
* python-scons: update to 3.1.0
* python-setuptools: update to 41.2.0
* python: update to 3.7.3
* qemu: Upgrade from 3.1.0 to 4.1
* quilt: update to 0.66
* quota: update to 4.05
* rng-tools: 6.6 -> 6.7
* ruby: update to 2.5.5
* socat: upgrade 1.7.3.2 -> 1.7.3.3
* sqlite3: update to 3.29.0
* squashfs-tools: upgrade to commit f95864afe883
* strace: Upgrade to 5.3
* subversion: upgrade 1.11.1 -> 1.12.2
* sysprof: upgrade 3.30.2 -> 3.32.0
* sysstat: 12.1.3 -> 12.1.6
* systemd: upgrade to 243
* systemtap: update to 57c9aca9f1ff32a6add10e02ecd33b7314fad499
* tar: update to 1.32
* timezone: update to 2019c
* u-boot: Upgrade from 2019.01 to 2019.07
* uninative: Update to 2.7 release
* usbutils: upgrade 010->012
* util-linux: upgrade to 2.34
* vala: update to 0.44.7
* valgrind: update from 3.14.0 to 3.15.0
* vim: Update to 8.1.1240
* virglrenderer: update 0.7.0 -> 0.8.0
* vte: upgrade 0.52.2 -> 0.56.3
* waffle: upgrade 1.5.2 -> 1.6.0
* wayland-protocols: upgrade 1.17 -> 1.18
* webkitgtk: update to 2.24.4
* weston: upgrade 5.0.0 -> 7.0.0
* wget: update to 1.20.3
* wpa-supplicant: update to 2.9
* x11perf: update to 1.6.1
* x264: upgrade to latest revision
* xauth: upgrade 1.0.10 -> 1.1
* xf86-input-libinput: update to 0.29.0
* xinput: update to 1.6.3
* xkeyboard: upgrade 2.26 -> 2.27
* xorgproto: update to 2019.1
* xrandr: update to 1.5.1
* xserver-xorg: update to 1.20.5
* xtrans: upgrade 1.3.5 -> 1.4.0
* xwininfo: upgrade 1.1.4 -> 1.1.5

license
-------

Known Issues
------------

FutureMigrationGuide

2019-10-16T04:42:25Z

PaulEggleton:

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|This page should be used to keep track of items which should be added to the [http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration migration guide] in the YP Reference Manual. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.

Once the migration guide for a release has been completed the contents of this page should be cleared out.
|}

=3.0 Migration Guide items=

== Init system selection ==

Changing the init system manager previously required setting a number of different variables; this can now be accomplished by setting the INIT_MANAGER variable and corresponding include files (conf/distro/include/init-manager-*.conf); include files are provided for four values - "none", "sysvinit", "systemd" and "mdev-busybox". The default value "none" for INIT_MANAGER should allow your current settings to continue working, but it is advisable to set INIT_MANAGER explicitly.

== LSB support removed ==

LSB as a standard isn't current, and isn't well suited to embedded applications. Support may be continued in a separate layer if needed but at present it has been removed from the core.

Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

== Removed recipes ==

* core-image-lsb-dev: part of removed LSB support
* core-image-lsb: part of removed LSB support
* core-image-lsb-sdk: part of removed LSB support
* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
* gcc-8.3: remove 8.3 from zeus
* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
* irda-utils: obsolete - IrDA support has been removed from the Linux kernel in version 4.17 and later.
* libnewt-python: libnewt Python support merged into main libnewt recipe
* libsdl: replaced by newer libsdl2
* libx11-diet: obsolete
* libxx86dga: remove obsolete client libary
* libxx86misc: remove this now redundant library
* linux-yocto: version 5.0 removed
* lsbinitscripts: part of removed LSB support
* lsb: part of removed LSB support
* lsbtest: part of removed LSB support
* openssl10: replaced by newer openssl 1.1
* packagegroup-core-lsb: part of removed LSB support
* python-nose: remove the python 2.x version of the recipe
* python-numpy: remove the python 2.x version of the recipe
* python-scons: remove the python 2.x version of the recipe
* source-highlight: no longer needed
* stress: replaced by stress-ng
* vulkan: split into vulkan-loader, vulkan-headers and vulkan-tools
* weston-conf: functionality moved to weston-init

== Packaging changes ==

* The epiphany browser has been dropped from packagegroup-self-hosted as it has not been needed inside build-appliance-image for a long time and was causing resource problems.
* libcap-ng python support has been moved to a separate libcap-ng-python recipe to streamline the build process when the python bindings aren't needed
* libdrm now packages the amdgpu.ids file into a separate libdrm-amdgpu package
* python3: the runpy module is now in the python3-core package as it is required to support the common "python3 -m" command usage.
* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

== CVE checking ==

cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 scoring and makes other improvements.

Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

== Bitbake changes ==

* addtask statements now properly validate dependent tasks - previously an invalid task here would be silently ignored, now it will generate a warning.
* Other invalid addtask and deltask usages will now trigger warnings (multiple target tasks arguments with addtask / deltask, multiple before/after clauses)
* The "multiconfig" prefix is now shortened to "mc"; "multiconfig" will continue to work, however it may be removed in a future release.
* bitbake -g no longer generates a recipe-depends.dot file as the contents (a reprocessed version of task-depends.dot) were confusing.
* The bb.build.FuncFailed exception, previously raised by bb.build.exec_func() when certain other exceptions have occurred, has been removed. The real underlying exceptions will be raised instead. If you have calls to bb.build.exec_func() in custom classes or tinfoil-using scripts, any references to bb.build.FuncFailed should be cleaned up.
* Additionally, the bb.build.exec_func() no longer accepts the "pythonexception" parameter - it now always raises exceptions. Remove this argument in any calls to bb.build.exec_func() in custom classes or scripts.
* The BB_SETSCENE_VERIFY_FUNCTION2 is no longer used - in the unlikely event that you have any references to it, they should be removed.
* The RunQueueExecuteScenequeue and RunQueueExecuteTasks events have been removed since setscene tasks are now executed as part of the normal runqueue. Any event handling code in custom classes or scripts that handles these two events will need to be updated.
* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

== Package runtime dependencies no longer recursive ==

RDEPENDS are no longer automatically expanded recursively when packaging, as there is no mechanism to ensure they were fully computed and thus races were observed. When setting RDEPENDS explicitly in a recipe, you will need to ensure the runtime dependencies are fully specified. <span style="color: red; font-weight:bold;">[needs clarification]</span>

== Sanity checks ==

* SRC_URI is now checked for usage of two problematic items:
*# "${PN}" - instead "${BPN}" should be used to avoid problems when PN is prefixed or suffixed e.g. with multiconfig.
*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

== Miscellaneous ==

* The gnome class has been removed, as it did not do very much anymore. Recipes that previously inherited this class should be updated to do the following:
inherit gnomebase gtk-icon-cache gconf mime
* The meta/recipes-kernel/linux/linux-dtb.inc file has been removed. It was previously deprecated (in favour of setting KERNEL_DEVICETREE in any kernel recipe) and only produced a warning. Remove any include/require statements pointing to this file.
* TARGET_CFLAGS, TARGET_CPPFLAGS, TARGET_CXXFLAGS, and TARGET_LDFLAGS are no longer exported to the external environment. This has not required changes to any recipes, but if for some reason the software being built by one of your recipes is expecting these variables to be set then it will now fail, and you will need to either export the variable(s) in the recipe or change the scripts so that that isn't necessary.
* The host distro identifier as used in NATIVELSBSTRING (when not using uninative) and SANITY_TESTED_DISTROS is now always lowercased even if it does not contain a version number.
* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before. <span style="color: red; font-weight:bold;">[needs clarification]</span>
* conf/distro/include/world-broken.inc has been removed - where we need to disable certain recipes when using the musl C library, individual recipes now have COMPATIBLE_HOST_libc-musl set with a comment explaining why.

3.0 Release Notes WIP

2019-10-16T04:33:25Z

PaulEggleton:

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|NOTE: The formatting in this page is not meant to look good in the wiki - it's just a convenient place to collaborate. We need to stick to the text formatting that will end up in the actual release notes.
|}

Security Fixes
--------------

New Features / Enhancements
---------------------------
* Linux kernel 5.2/4.19, gcc 9.2, glibc 2.30 and ~260 other recipe upgrades
* New INIT_MANAGER variable to make it easy to select the init manager (sysvinit, systemd, mdev-busybox)
* poky-lsb replaced by poky-altcfg for alternate configurations to be tested on the autobuilder (as well as an example of subclassing a distro config)
* New recipes: binutils-cross-testsuite, core-image-sato-ptest-fast, dejagnu, efibootmgr, efivar, ell, glibc-testsuite, libcap-ng-python, libedit, libmodule-build-perl, libx11-compose-data, libxcrypt-compat, lsb-release, musl-obstack, opensbi, python3-pygments, python3-scons, python3-scons-native, stress-ng, vulkan-headers, vulkan-loader, vulkan-tools, wireless-regdb
* Significant removal of old/obsolete software/patches ensuring we have a modern and up to date core Linux software stack.
- LSB support moved to separate layer [was it??]
- GTK+ 2 moved out to meta-oe
- Python 2 dependencies minimised
- many obsolete patches dropped
* Build change equivalence is detected and used to avoid rebuilding unchanged components
* Adoption of SPDX license identifiers throughout Yocto Project's components
* "Multi-Config" builds reaching their full potential
- Many bugfixes and improvements
- sstate cache is now shared between configurations being built concurrently
- multiconfig configurations can be contained in layers
* New cve-update-db recipe and enhanced cve-check class uses NVD JSON data feeds, supports CVSSv3 scoring, improved product matching and network proxies

* Add nativesdk variant to: dnf, gzip, libtasn1, python3-dbus
* Add native variant to: glib-networking, grub, libsoup, python3-dbus

* Added bbverbnote shell log command
* Added support for arm1176jz-s CPU specific tuning
* Apache-2.0-with-LLVM-exception: Add new license file
* base.bbclass: Add OE_EXTRA_IMPORTS
* bash-completion: add image feature
* binutils-cross-testsuite: Create recipe for test suite execution
* bitbake: BBHandler: Fix addtask and deltask
* bitbake: bb: siggen: Make dump_sigfile and compare_sigfiles print uuid4
* bitbake: bb: siggen: Print more info when basehash are mis-matched
* bitbake: bitbake: Add --skip-setscene option
* bitbake: bitbake: fetch2/git: git-lfs check
* bitbake: bitbake-layers: show-recipes: Enable bare output
* bitbake: bitbake-layers: show-recipes: Select recipes from selected layer
* bitbake: bitbake-layers: show-recipes: Show recipes only
* bitbake: bitbake: respect force flag in runall and runonly
* bitbake: bitbake: Rework hash equivalence
* bitbake: bitbake: Show base multiconfig environment
* bitbake: build: implement custom progress handlers injected via OE_EXTRA_IMPORTS
* bitbake: build.py: check dependendent task for addtask
* bitbake: cache: Add SimpleCache class
* bitbake: cache: Create a symlink for current cachefile
* bitbake.conf: add git-lfs to HOSTTOOLS_NONFATAL
* bitbake: cooker/hashserv: Allow autostarting of a local hash server using BB_HASHSERVE
* bitbake: cooker: list all nonexistent bblayer directories
* bitbake: fetch2/git: add git-lfs toggle option
* bitbake: fetch2/npm: Use npm pack to download node modules instead of wget
* bitbake: knotty: Implement console 'keepalive' output
* bitbake: knotty: Pretty print task elapsed time
* bitbake: runqueue: Enable dynamic task adjustment to hash equivalency
* bitbake: runqueue: Merge scenequeue and real task queue code together
* bitbake: runqueue: Merge the queues and execute setscene and normal tasks in parallel
* bitbake: siggen: Use unique hashes for tasks
* bitbake: svn.py: Stop SVN from directly pulling from an external layer w/o fetcher
* buildhistory: report sysroot changes
* buildhistory: show time spent writting buildhistory
* buildhistory: write the contents of the sysroot
* busybox: enable unicode support
* chrpath.bbclass: Add break_hardlinks kwarg to allow breaking hardlinks
* cmake: Use compiler launcher variable when ccache is enabled
* db: add switch for building database verification
* deb: allow custom dpkg command
* devtool: build: Also run deploy for devtool build if applicable
* devtool: finish: Add suppport for the --no-clean option
* devtool: provide support for devtool menuconfig command
* devtool/standard.py: Create a copy of kernel source within work-shared if not present
* devtool/standard.py: Update devtool modify to copy source from work-shared if its already downloaded
* devtool: warn user about multiple layer having the same base name
* distcc: split into client and server packages
* dropbear: new feature: disable-weak-ciphers
* gcc-runtime: Add do_check task for executing gcc test suites
* glibc-testsuite: Create a recipe to implement glibc test suite
* grub-efi-native: Install grub-editenv
* icu: Added armeb support.
* image_types.bbclass: make gzipped images rsyncable
* image-uefi.conf: add config file holding configuration for UEFI images
* initramfs-framework: support PARTLABEL option
* insane: add check for perllocal.pod
* insane: add sanity checks to SRC_URI
* insane: check if the recipe incorrectly uses DEPENDS_${PN}
* insane: improve buildpath warning messages
* insane: use clean_path for the host contamination warnings
* iptables: add systemd helper unit to load/restore rules
* kernel-fitimage: introduce FIT_HASH_ALG
* kernel-module-split.bbclass: support CONFIG_MODULE_COMPRESS=y
* kernel-yocto: import security fragments from meta-security
* libffi: Add RISC-V support
* libmodule-build-perl: move from meta-perl
* linux-yocto/4.19: make drm-bochs feature available
* linux-yocto/5.0: bsp: add basic xilinx zynqmp support
* linux-yocto/5.0: make scsi-debug include scsi core configs
* linux-yocto/5.2: config tweaks and kallsyms fix
* linux-yocto: add drm-bochs support
* linux-yocto: bsp/beaglebone: support qemu -machine virt
* live-vm-common.bbclass: provide efi population functions for live images
* local.conf.sample: Add Hash Equivalence
* logparser: Add decoding ltp logs
* logparser: Add LTP compliance section
* ltp: add runtime test
* ltp_compliance: add new runtime
* lttng-modules: Add git based recipe
* meson.bbclass: Handle microblaze* mapping to cpu family
* meson.bbclass: Make meson support aarch64_be.
* oe-selftest: Implement console 'keepalive' output
* oe.svg: Copy artwork from openembedded-classic.
* opensbi: Initial commit of OpenSBI
* opkg/package/rootfs_ipk: allow overwriting OPKGLIBDIR
* ovmf: Generate test Platform key and first Key Exchange Key
* package.bbclass: allow shell-style wildcards in PRIVATE_LIBS
* package.bbclass: Clean up writing of runtime pkgdata files
* patch: add minver and maxver parameters
* populate_sdk_base: provide options to set sdk type
* populate_sdk_ext: Introduce mechanism to keep nativesdk* sstate in esdk
* python3-scons-{native}: add recipe
* python3: support recommends in manifest
* qemu: Add ppc64 to QEMU_TARGETS
* qemuarm64: Add QB_CPU_KVM to allow kvm acceleration
* qemuriscv64: Add the QEMU RISC-V 64-bit machine
* qemurunner.py: Be more verbose about problems
* qemux86: Allow higher tunes
* recipetool: add python3 support
* report-error.bbclass: add local.conf/auto.conf into error report
* resulttool: Add log subcommand
* resulttool: add LTP compliance section
* resulttool: add ltp test support
* resulttool: Load results from URL
* resulttool/manualexecution: Enable test case configuration option
* runqemu: Add support for kvm on aarch64
* runqemu: Add support to handle EnrollDefaultKeys PK/KEK1 certificate
* runqemu: Add the support to pass multi ports to tcpserial parameter
* runqemu: decouple gtk and gl options
* runqemu: QB_FSINFO to support fstype wic images
* screen: add /etc/screenrc as global config file
* scripts/buildstats-diff: Add option to filter tasks
* scripts/contrib/ddimage: replace blacklist with mount check
* scripts/runqemu: Add support for the BIOS variable
* serial-getty@.service: Allow device to fast fail if it does not exist
* stress-ng: add a recipe that replaces the original stress
* systemctl-native: Rewrite in Python supporting preset-all and mask
* systemd: Add partial support of drop-in configuration files to systemd-systemctl-native
* systemd-conf: configure wired network with dhcp
* systemd-conf: simplify creation of machine-specific configuration
* systemd: create preset files instead of installing in image
* testimage: consider QB_DEFAULT_FSTYPE
* tune-cortexa57-cortexa53: add tunes for ARM Cortex-A53-Cortex-A57
* uboot-sign: add support for different u-boot configurations
* update-rc.d: support enable/disable options
* utils/multiprocess_launch: Improve failing subprocess output
* waffle: supprt build waffle without x11
* weston-init: Add possibility to run weston as non-root user
* weston-init: Add support for non-root start
* wic: add global debug option
* wic: Add partition type for msdos partition tables
* wic: add support for kernel with initramfs bundled
* wic: bootimg-efi: add label source parameter
* wic/bootimg-efi: allow multiple initrd
* wic/bootimg-efi: replace hardcoded volume name with label
* wic/engine: include .wks.in in wic search and list
* wic/plugins: kernel image refer to KERNEL_IMAGETYPE
* wic/plugins: Source that support both EFI and BIOS
* wireless-regdb: Add recipe
* yocto-bsp: runqemu runs beaglebone-yocto
* yocto-check-layer: Allow any case for README file detection

Recipe Upgrades
---------------
* acpica: update to 20190816
* acpid: upgrade 2.0.31 -> 2.0.32
* adwaita-icon-theme: upgrade 3.30.1 -> 3.32.0
* alsa-lib: upgrade 1.1.8 -> 1.1.9
* alsa-plugins: upgrade 1.1.8 -> 1.1.9
* alsa-utils: upgrade 1.1.8 -> 1.1.9
* apr: upgrade 1.6.5 -> 1.7.0
* apt: update to 1.2.31
* aspell: update to 0.60.7
* atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-atk: upgrade 2.30.0 -> 2.32.0
* at-spi2-core: upgrade 2.30.0 -> 2.32.1
* autoconf-archive: update to 2019.01.06
* babeltrace: update to 1.5.7
* bash-completion: upgrade 2.8 -> 2.9
* bash: upgrade 4.4.18 -> 5.0
* bison: upgrade 3.0.4 -> 3.4.1
* boost: update to 1.71.0
* btrfs-tools: upgrade 4.20.1 -> 5.2.2
* build-compare: 2015.02.10 -> 2019.08.14
* busybox: 1.30.1 -> 1.31.0
* bzip2: update to 1.0.8
* ccache: upgrade 3.6 -> 3.7.3
* cmake: 3.14.1 -> 3.15.3
* cogl: upgrade 1.22.2 -> 1.22.4
* connman: update to 1.37
* coreutils: update to 8.31
* createrepo-c: update to 0.15.0
* cronie: update to 1.5.4
* cups: update to 2.2.12
* curl: update to 7.66.0
* dbus-test: Upgrade 1.12.12 -> 1.12.16
* dbus: Upgrade 1.12.12 -> 1.12.16
* debianutils: upgrade 4.8.6.1 -> 4.8.6.3
* desktop-file-utils: upgrade 0.23 -> 0.24
* distcc: upgrade 3.3.2 -> 3.3.3
* dnf: upgrade 4.1.0 -> 4.2.2
* dpkg: update to 1.19.7
* dropbear: update to 2019.78
* dtc: upgrade 1.4.7 -> 1.5.1
* e2fsprogs: 1.44.5 -> 1.45.3
* elfutils: 0.176 -> 0.177
* ell: update to 0.22
* encodings: update to 1.0.5
* epiphany: update to 3.32.4
* ethtool: update to 5.2
* eudev: update to 3.2.8
* expat: update to 2.2.8
* ffmpeg: update to 4.2.1
* file: update to 5.37
* flac: Upgrade 1.3.2 -> 1.3.3
* fontconfig: update to 2.13.1
* font-util: update to 1.3.2
* freetype: upgrade 2.9.1 -> 2.10.1
* gawk: upgrade 4.2.1 -> 5.0.1
* gcc-9: Upgrade to 9.2
* gdb: Upgrade from 8.2.1 to 8.3.1
* gdk-pixbuf: update 2.38.0 -> 2.38.2
* ghostscript: 9.26 -> 9.27
* git: update to 2.23.0
* glib-2.0: udpate 2.58.3 -> 2.60.7
* glibc: Update to glibc 2.30
* glib-networking: upgrade 2.60.1 -> 2.60.3
* gnu-config: Update to latest SHA
* gnupg: update to 2.2.17
* gnutls: upgrade 3.6.5 -> 3.6.8
* go-1.12: update to 1.12.9 minor release
* gobject-introspection: update to 1.60.2
* go-dep: update to 0.5.4
* go: update 1.12.1->1.12.6
* gpgme: upgrade 1.12.0 -> 1.13.1
* groff: upgrade 1.22.3 -> 1.22.4
* grub: upgrade 2.02 -> 2.04
* gsettings-desktop-schemas: upgrade 3.28.1 -> 3.32.0
* gst-examples: upgrade to 1.16.0
* gstreamer1.0-libav: upgrade to version 1.16.0
* gstreamer1.0-omx: upgrade to version 1.16.0
* gstreamer1.0-plugins-bad: upgrade to version 1.16.0
* gstreamer1.0-plugins-base: upgrade to version 1.16.0
* gstreamer1.0-plugins-good: upgrade to version 1.16.0
* gstreamer1.0-plugins-ugly: upgrade to version 1.16.0
* gstreamer1.0-python: upgrade to version 1.16.0
* gstreamer1.0-rtsp-server: upgrade to version 1.16.0
* gstreamer1.0: upgrade to version 1.16.0
* gstreamer1.0-vaapi: upgrade to version 1.16.0
* gst-validate: upgrade to version 1.16.0
* gtk+3: update 3.24.5 -> 3.24.8
* gtk-doc: upgrade 1.29 -> 1.31
* harfbuzz: upgrade 2.3.1 -> 2.6.1
* help2man-native: update to 1.47.11
* icu: update to 64.2
* ifupdown: update to 0.8.22
* iproute2: update to 5.2.0
* iptables: upgrade 1.6.2 -> 1.8.3
* iputils: upgrade to s20190709
* iso-codes: upgrade 4.2 -> 4.3
* iw: upgrade 4.14 -> 5.3
* kmscube: Bump revision to f632b23
* less: upgrade 550 -> 551
* libarchive: upgrade 3.3.3 -> 3.4.0
* libatomic-ops: upgrade 7.6.8 -> 7.6.10
* libbsd: upgrade 0.9.1 -> 0.10.0
* libcap: update to 2.27
* libcomps: upgrade 0.1.10 -> 0.1.11
* libcroco: update to 0.6.13
* libdazzle: update to 3.32.3
* libdnf: update to 0.28.1
* libdrm: update to 2.4.99
* libevdev: upgrade 1.6.0 -> 1.8.0
* libevent: upgrade 2.1.8 -> 2.1.11
* libffi: Upgrade to 3.3-rc0
* libglu: upgrade 9.0.0 -> 9.0.1
* libgpg-error: upgrade 1.35 -> 1.36
* libgudev: upgrade 232 -> 233
* libical: upgrade to 3.0.6
* libice: upgrade 1.0.9 -> 1.0.10
* libidn2: upgrade to 2.2.0
* libinput: update to 1.14.1
* libjpeg-turbo: upgrade 2.0.2 -> 2.0.3
* libmodule-build-perl: upgrade 0.4224 -> 0.4229
* libmodulemd: update to 2.6.0
* libnewt: upgrade 0.52.20 -> 0.52.21
* libnl: upgrade to 3.5.0
* libnotify: update to 0.7.8
* libnss-nis: upgrade 3.0 -> 3.1
* libogg: upgrade 1.3.3 -> 1.3.4
* libpam: Upgrade 1.3.0 -> 1.3.1
* libpcap: upgrade 1.9.0 -> 1.9.1
* libpciaccess: upgrade 0.14 -> 0.16
* libpcre2: upgrade 10.32 -> 10.33
* libpng: update to 1.6.37
* libpsl: update to 0.21.0
* librepo: update to 1.10.5
* libsdl2: upgrade 2.0.9 -> 2.0.10
* libsecret: 0.19.0
* libsolf: update to 0.7.5
* libsolv: update to 0.7.6
* libsoup-2.4: upgrade 2.66.1 -> 2.66.2
* libsoup: Upgrade from 2.64.2 to 2.66.1
* libtasn1: upgrade 4.13 -> 4.14
* libtest-needs-perl: upgrade 0.002005 -> 0.002006
* libtirpc: upgrade 1.0.3 -> 1.1.4
* liburcu: update to 0.11.1
* libva: upgrade 2.4.0 -> 2.5.0
* libva-utils: upgrade 2.4.0 -> 2.5.0
* libwebp: upgrade 1.0.2 -> 1.0.3
* libx11-compose-data: upgrade 1.6.7 -> 1.6.8
* libx11: update to 1.6.8
* libxcrypt: update to 4.4.8
* libxdmcp: update to 1.1.3
* libxext: update to 1.3.4
* libxft: upgrade 2.3.2 -> 2.3.3
* libxi: update to 1.7.10
* libxkbfile: update 1.1.0
* libxml2: upgrade 2.9.8 -> 2.9.9
* libxml-sax-perl: upgrade 1.00 -> 1.02
* libxmu: update to 1.1.3
* libxrandr: update to 1.5.2
* libxt: update to 1.2.0
* libxvmc: update to 1.0.11
* libyaml: update to 0.2.2
* lighttpd: Upgrade 1.4.53 -> 1.4.54
* linux-firmware: Upgrade to 20190815
* linux-libc-headers: update to v5.2 headers
* linux-yocto/4.19: update to 4.19.72 and -rt22
* linux-yocto-dev: bump to 5.3-rcX
* linux-yocto: introduce 5.2.17 recipes
* linux-yocto-rt: update to 5.0.5-rt9
* llvm: Update to 8.0.1
* logrotate: upgrade 3.15.0 -> 3.15.1
* ltp: upgrade 20190115 -> 20190517
* lttng-modules: upgrade 2.10.8 -> 2.10.11
* lttng-tools: update to 2.10.7
* lttng-ust: upgrade 2.10.3 -> 2.10.5
* lz4: update to 1.9.2
* makedepend: update to 1.0.6
* man-db: upgrade 2.8.4 -> 2.8.7
* man-pages: upgrade 4.16 -> 5.01
* mc: update to 4.8.23
* mesa-demos: update to 8.4.0
* mesa: Update 19.0.1 -> 19.1.6
* meson: update to 0.51.2
* mmc-utils: update to the latest upstream code
* mobile-broadband-provider-info: upgrade 20190116 -> 20190618
* mpg123: upgrade 1.25.10 -> 1.25.11
* msmtp: 1.6.6 -> 1.8.5
* mtd-utils: Upgrade to 2.1.1
* mtools: update to 4.0.23
* musl: Update to latest master
* ncurses: upgrade 6.1+20181013 -> 6.1+20190803
* nettle: upgrade 3.4.1 -> 3.5.1
* newlib: Upgrade to 3.1.0
* nfs-utils: 2.3.3 -> 2.4.1
* nss: upgrade 3.42.1 -> 3.45
* ofono: upgrade 1.25 -> 1.30
* opensbi: Update from 0.3 to 0.4
* openssh: Upgrade 7.9p1 -> 8.0p1
* openssl: Upgrade 1.1.1b -> 1.1.1d
* opkg: upgrade to version 0.4.1
* opkg-utils: upgrade to version 0.4.1
* orc: update to 0.4.29
* ovmf: Update to version edk2-stable201905
* p11-kit: update to 0.23.16.1
* pango: upgrade 1.42.4 -> 1.44.6
* patchelf: Upgrade 0.9 -> 0.10
* perl: Move perl-sanity -> perl
* perl: update to 5.30.0
* piglit: upgrade to latest revision
* pixman: update to 0.38.4
* pkgconf: upgrade 1.6.0 -> 1.6.3
* ptest-runner: update from 2.3.1 to 2.3.2
* python3-dbus: upgrade 1.2.8 -> 1.2.12
* python3-docutils: update to 0.15
* python3-git: update to 3.0.2
* python3-mako: update to 1.1.0
* python3-numpy: update to 1.17.0
* python3-pbr: update to 5.4.3
* python3-pip: update to 19.2.3
* python3-pycairo: update to 1.18.1
* python3-pygobject: update to 3.34.0
* python3-scons: update to 3.1.1
* python3: upgrade 3.7.3 -> 3.7.4
* python-numpy: update to 1.16.3
* python-scons: update to 3.1.0
* python-setuptools: update to 41.2.0
* python: update to 3.7.3
* qemu: Upgrade from 3.1.0 to 4.1
* quilt: update to 0.66
* quota: update to 4.05
* rng-tools: 6.6 -> 6.7
* ruby: update to 2.5.5
* socat: upgrade 1.7.3.2 -> 1.7.3.3
* sqlite3: update to 3.29.0
* squashfs-tools: upgrade to commit f95864afe883
* strace: Upgrade to 5.3
* subversion: upgrade 1.11.1 -> 1.12.2
* sysprof: upgrade 3.30.2 -> 3.32.0
* sysstat: 12.1.3 -> 12.1.6
* systemd: upgrade to 243
* systemtap: update to 57c9aca9f1ff32a6add10e02ecd33b7314fad499
* tar: update to 1.32
* timezone: update to 2019c
* u-boot: Upgrade from 2019.01 to 2019.07
* uninative: Update to 2.7 release
* usbutils: upgrade 010->012
* util-linux: upgrade to 2.34
* vala: update to 0.44.7
* valgrind: update from 3.14.0 to 3.15.0
* vim: Update to 8.1.1240
* virglrenderer: update 0.7.0 -> 0.8.0
* vte: upgrade 0.52.2 -> 0.56.3
* waffle: upgrade 1.5.2 -> 1.6.0
* wayland-protocols: upgrade 1.17 -> 1.18
* webkitgtk: update to 2.24.4
* weston: upgrade 5.0.0 -> 7.0.0
* wget: update to 1.20.3
* wpa-supplicant: update to 2.9
* x11perf: update to 1.6.1
* x264: upgrade to latest revision
* xauth: upgrade 1.0.10 -> 1.1
* xf86-input-libinput: update to 0.29.0
* xinput: update to 1.6.3
* xkeyboard: upgrade 2.26 -> 2.27
* xorgproto: update to 2019.1
* xrandr: update to 1.5.1
* xserver-xorg: update to 1.20.5
* xtrans: upgrade 1.3.5 -> 1.4.0
* xwininfo: upgrade 1.1.4 -> 1.1.5

license
-------

Known Issues
------------

3.0 Release Notes WIP

2019-10-16T04:15:01Z

PaulEggleton:

FutureMigrationGuide

2019-10-16T03:49:49Z

PaulEggleton: Add world-broken.inc

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|This page should be used to keep track of items which should be added to the [http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration migration guide] in the YP Reference Manual. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.

Once the migration guide for a release has been completed the contents of this page should be cleared out.
|}

=3.0 Migration Guide items=

== Init system selection ==

Changing the init system manager previously required setting a number of different variables; this can now be accomplished by setting the INIT_MANAGER variable and corresponding include files (conf/distro/include/init-manager-*.conf); include files are provided for four values - "none", "sysvinit", "systemd" and "mdev-busybox". The default value "none" for INIT_MANAGER should allow your current settings to continue working, but it is advisable to set INIT_MANAGER explicitly.

== LSB support removed ==

LSB as a standard isn't current, and isn't well suited to embedded applications. Support may be continued in a separate layer if needed but at present it has been removed from the core.

Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

== Removed recipes ==

* core-image-lsb-dev: part of removed LSB support
* core-image-lsb: part of removed LSB support
* core-image-lsb-sdk: part of removed LSB support
* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
* gcc-8.3: remove 8.3 from zeus
* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
* irda-utils: obsolete - IrDA support has been removed from the Linux kernel in version 4.17 and later.
* libnewt-python: libnewt Python support merged into main libnewt recipe
* libsdl: replaced by newer libsdl2
* libx11-diet: obsolete
* libxx86dga: remove obsolete client libary
* libxx86misc: remove this now redundant library
* linux-yocto: version 5.0 removed
* lsbinitscripts: part of removed LSB support
* lsb: part of removed LSB support
* lsbtest: part of removed LSB support
* openssl10: replaced by newer openssl 1.1
* packagegroup-core-lsb: part of removed LSB support
* python-nose: remove the python 2.x version of the recipe
* python-numpy: remove the python 2.x version of the recipe
* python-scons: remove the python 2.x version of the recipe
* source-highlight: no longer needed
* stress: replaced by stress-ng
* vulkan: split into vulkan-loader, vulkan-headers and vulkan-tools
* weston-conf: functionality moved to weston-init

== Packaging changes ==

* The epiphany browser has been dropped from packagegroup-self-hosted as it has not been needed inside build-appliance-image for a long time and was causing resource problems.
* libcap-ng python support has been moved to a separate libcap-ng-python recipe to streamline the build process when the python bindings aren't needed
* libdrm now packages the amdgpu.ids file into a separate libdrm-amdgpu package
* python3: the runpy module is now in the python3-core package as it is required to support the common "python3 -m" command usage.
* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

== CVE checking ==

cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 and makes other improvements.

Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

== Bitbake changes ==

* addtask statements now properly validate dependent tasks - previously an invalid task here would be silently ignored, now it will generate a warning.
* Other invalid addtask and deltask usages will now trigger warnings (multiple target tasks arguments with addtask / deltask, multiple before/after clauses)
* The "multiconfig" prefix is now shortened to "mc"; "multiconfig" will continue to work, however it may be removed in a future release.
* bitbake -g no longer generates a recipe-depends.dot file as the contents (a reprocessed version of task-depends.dot) were confusing.
* The bb.build.FuncFailed exception, previously raised by bb.build.exec_func() when certain other exceptions have occurred, has been removed. The real underlying exceptions will be raised instead. If you have calls to bb.build.exec_func() in custom classes or tinfoil-using scripts, any references to bb.build.FuncFailed should be cleaned up.
* Additionally, the bb.build.exec_func() no longer accepts the "pythonexception" parameter - it now always raises exceptions. Remove this argument in any calls to bb.build.exec_func() in custom classes or scripts.
* The BB_SETSCENE_VERIFY_FUNCTION2 is no longer used - in the unlikely event that you have any references to it, they should be removed.
* The RunQueueExecuteScenequeue and RunQueueExecuteTasks events have been removed since setscene tasks are now executed as part of the normal runqueue. Any event handling code in custom classes or scripts that handles these two events will need to be updated.
* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

== Package runtime dependencies no longer recursive ==

RDEPENDS are no longer automatically expanded recursively when packaging, as there is no mechanism to ensure they were fully computed and thus races were observed. When setting RDEPENDS explicitly in a recipe, you will need to ensure the runtime dependencies are fully specified. <span style="color: red; font-weight:bold;">[needs clarification]</span>

== Sanity checks ==

* SRC_URI is now checked for usage of two problematic items:
*# "${PN}" - instead "${BPN}" should be used to avoid problems when PN is prefixed or suffixed e.g. with multiconfig.
*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

== Miscellaneous ==

* The gnome class has been removed, as it did not do very much anymore. Recipes that previously inherited this class should be updated to do the following:
inherit gnomebase gtk-icon-cache gconf mime
* The meta/recipes-kernel/linux/linux-dtb.inc file has been removed. It was previously deprecated (in favour of setting KERNEL_DEVICETREE in any kernel recipe) and only produced a warning. Remove any include/require statements pointing to this file.
* TARGET_CFLAGS, TARGET_CPPFLAGS, TARGET_CXXFLAGS, and TARGET_LDFLAGS are no longer exported to the external environment. This has not required changes to any recipes, but if for some reason the software being built by one of your recipes is expecting these variables to be set then it will now fail, and you will need to either export the variable(s) in the recipe or change the scripts so that that isn't necessary.
* The host distro identifier as used in NATIVELSBSTRING (when not using uninative) and SANITY_TESTED_DISTROS is now always lowercased even if it does not contain a version number.
* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before. <span style="color: red; font-weight:bold;">[needs clarification]</span>
* conf/distro/include/world-broken.inc has been removed - where we need to disable certain recipes when using the musl C library, individual recipes now have COMPATIBLE_HOST_libc-musl set with a comment explaining why.

3.0 Release Notes WIP

2019-10-16T03:24:25Z

PaulEggleton: Touch up recipe upgrades

FutureMigrationGuide

2019-10-16T02:39:32Z

PaulEggleton:

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|This page should be used to keep track of items which should be added to the [http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration migration guide] in the YP Reference Manual. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.

Once the migration guide for a release has been completed the contents of this page should be cleared out.
|}

=3.0 Migration Guide items=

== Init system selection ==

Changing the init system manager previously required setting a number of different variables; this can now be accomplished by setting the INIT_MANAGER variable and corresponding include files (conf/distro/include/init-manager-*.conf); include files are provided for four values - "none", "sysvinit", "systemd" and "mdev-busybox". The default value "none" for INIT_MANAGER should allow your current settings to continue working, but it is advisable to set INIT_MANAGER explicitly.

== LSB support removed ==

LSB as a standard isn't current, and isn't well suited to embedded applications. Support may be continued in a separate layer if needed but at present it has been removed from the core.

Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

== Removed recipes ==

* core-image-lsb-dev: part of removed LSB support
* core-image-lsb: part of removed LSB support
* core-image-lsb-sdk: part of removed LSB support
* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
* gcc-8.3: remove 8.3 from zeus
* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
* irda-utils: obsolete - IrDA support has been removed from the Linux kernel in version 4.17 and later.
* libnewt-python: libnewt Python support merged into main libnewt recipe
* libsdl: replaced by newer libsdl2
* libx11-diet: obsolete
* libxx86dga: remove obsolete client libary
* libxx86misc: remove this now redundant library
* linux-yocto: version 5.0 removed
* lsbinitscripts: part of removed LSB support
* lsb: part of removed LSB support
* lsbtest: part of removed LSB support
* openssl10: replaced by newer openssl 1.1
* packagegroup-core-lsb: part of removed LSB support
* python-nose: remove the python 2.x version of the recipe
* python-numpy: remove the python 2.x version of the recipe
* python-scons: remove the python 2.x version of the recipe
* source-highlight: no longer needed
* stress: replaced by stress-ng
* vulkan: split into vulkan-loader, vulkan-headers and vulkan-tools
* weston-conf: functionality moved to weston-init

== Packaging changes ==

* The epiphany browser has been dropped from packagegroup-self-hosted as it has not been needed inside build-appliance-image for a long time and was causing resource problems.
* libcap-ng python support has been moved to a separate libcap-ng-python recipe to streamline the build process when the python bindings aren't needed
* libdrm now packages the amdgpu.ids file into a separate libdrm-amdgpu package
* python3: the runpy module is now in the python3-core package as it is required to support the common "python3 -m" command usage.
* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

== CVE checking ==

cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 and makes other improvements.

Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

== Bitbake changes ==

* addtask statements now properly validate dependent tasks - previously an invalid task here would be silently ignored, now it will generate a warning.
* Other invalid addtask and deltask usages will now trigger warnings (multiple target tasks arguments with addtask / deltask, multiple before/after clauses)
* The "multiconfig" prefix is now shortened to "mc"; "multiconfig" will continue to work, however it may be removed in a future release.
* bitbake -g no longer generates a recipe-depends.dot file as the contents (a reprocessed version of task-depends.dot) were confusing.
* The bb.build.FuncFailed exception, previously raised by bb.build.exec_func() when certain other exceptions have occurred, has been removed. The real underlying exceptions will be raised instead. If you have calls to bb.build.exec_func() in custom classes or tinfoil-using scripts, any references to bb.build.FuncFailed should be cleaned up.
* Additionally, the bb.build.exec_func() no longer accepts the "pythonexception" parameter - it now always raises exceptions. Remove this argument in any calls to bb.build.exec_func() in custom classes or scripts.
* The BB_SETSCENE_VERIFY_FUNCTION2 is no longer used - in the unlikely event that you have any references to it, they should be removed.
* The RunQueueExecuteScenequeue and RunQueueExecuteTasks events have been removed since setscene tasks are now executed as part of the normal runqueue. Any event handling code in custom classes or scripts that handles these two events will need to be updated.
* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

== Package runtime dependencies no longer recursive ==

RDEPENDS are no longer automatically expanded recursively when packaging, as there is no mechanism to ensure they were fully computed and thus races were observed. When setting RDEPENDS explicitly in a recipe, you will need to ensure the runtime dependencies are fully specified. <span style="color: red; font-weight:bold;">[needs clarification]</span>

== Sanity checks ==

* SRC_URI is now checked for usage of two problematic items:
*# "${PN}" - instead "${BPN}" should be used to avoid problems when PN is prefixed or suffixed e.g. with multiconfig.
*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

== Miscellaneous ==

* The gnome class has been removed, as it did not do very much anymore. Recipes that previously inherited this class should be updated to do the following:
inherit gnomebase gtk-icon-cache gconf mime
* The meta/recipes-kernel/linux/linux-dtb.inc file has been removed. It was previously deprecated (in favour of setting KERNEL_DEVICETREE in any kernel recipe) and only produced a warning. Remove any include/require statements pointing to this file.
* TARGET_CFLAGS, TARGET_CPPFLAGS, TARGET_CXXFLAGS, and TARGET_LDFLAGS are no longer exported to the external environment. This has not required changes to any recipes, but if for some reason the software being built by one of your recipes is expecting these variables to be set then it will now fail, and you will need to either export the variable(s) in the recipe or change the scripts so that that isn't necessary.
* The host distro identifier as used in NATIVELSBSTRING (when not using uninative) and SANITY_TESTED_DISTROS is now always lowercased even if it does not contain a version number.
* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before. <span style="color: red; font-weight:bold;">[needs clarification]</span>

FutureMigrationGuide

2019-10-16T02:38:59Z

PaulEggleton:

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|This page should be used to keep track of items which should be added to the [http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration migration guide] in the YP Reference Manual. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.

Once the migration guide for a release has been completed the contents of this page should be cleared out.
|}

=3.0 Migration Guide items=

== Init system selection ==

Changing the init system manager previously required setting a number of different variables; this can now be accomplished by setting the INIT_MANAGER variable and corresponding include files (conf/distro/include/init-manager-*.conf); include files are provided for four values - "none", "sysvinit", "systemd" and "mdev-busybox". The default value "none" for INIT_MANAGER should allow your current settings to continue working, but it is advisable to set INIT_MANAGER explicitly.

== LSB support removed ==

LSB as a standard isn't current, and isn't well suited to embedded applications. Support may be continued in a separate layer if needed but at present it has been removed from the core.

Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

== Removed recipes ==

* core-image-lsb-dev: part of removed LSB support
* core-image-lsb: part of removed LSB support
* core-image-lsb-sdk: part of removed LSB support
* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
* gcc-8.3: remove 8.3 from zeus
* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
* irda-utils: obsolete - IrDA support has been removed from the Linux kernel in version 4.17 and later.
* libnewt-python: libnewt Python support merged into main libnewt recipe
* libsdl: replaced by newer libsdl2
* libx11-diet: obsolete
* libxx86dga: remove obsolete client libary
* libxx86misc: remove this now redundant library
* linux-yocto: version 5.0 removed
* lsbinitscripts: part of removed LSB support
* lsb: part of removed LSB support
* lsbtest: part of removed LSB support
* openssl10: replaced by newer openssl 1.1
* packagegroup-core-lsb: part of removed LSB support
* python-nose: remove the python 2.x version of the recipe
* python-numpy: remove the python 2.x version of the recipe
* python-scons: remove the python 2.x version of the recipe
* source-highlight: no longer needed
* stress: replaced by stress-ng
* vulkan: split into vulkan-loader, vulkan-headers and vulkan-tools
* weston-conf: functionality moved to weston-init

== Packaging changes ==

* The epiphany browser has been dropped from packagegroup-self-hosted as it has not been needed inside build-appliance-image for a long time and was causing resource problems.
* libcap-ng python support has been moved to a separate libcap-ng-python recipe to streamline the build process when the python bindings aren't needed
* libdrm now packages the amdgpu.ids file into a separate libdrm-amdgpu package
* python3: the runpy module is now in the python3-core package as it is required to support the common "python3 -m" command usage.
* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

== CVE checking ==

cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 and makes other improvements.

Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

== Bitbake changes ==

* addtask statements now properly validate dependent tasks - previously an invalid task here would be silently ignored, now it will generate a warning.
* Other invalid addtask and deltask usages will now trigger warnings (multiple target tasks arguments with addtask / deltask, multiple before/after clauses)
* The "multiconfig" prefix is now shortened to "mc"; "multiconfig" will continue to work, however it may be removed in a future release.
* bitbake -g no longer generates a recipe-depends.dot file as the contents (a reprocessed version of task-depends.dot) were confusing.
* The bb.build.FuncFailed exception, previously raised by bb.build.exec_func() when certain other exceptions have occurred, has been removed. The real underlying exceptions will be raised instead. If you have calls to bb.build.exec_func() in custom classes or tinfoil-using scripts, any references to bb.build.FuncFailed should be cleaned up.
* Additionally, the bb.build.exec_func() no longer accepts the "pythonexception" parameter - it now always raises exceptions. Remove this argument in any calls to bb.build.exec_func() in custom classes or scripts.
* The BB_SETSCENE_VERIFY_FUNCTION2 is no longer used - in the unlikely event that you have any references to it, they should be removed.
* The RunQueueExecuteScenequeue and RunQueueExecuteTasks events have been removed since setscene tasks are now executed as part of the normal runqueue. Any event handling code in custom classes or scripts that handles these two events will need to be updated.
* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

== Package runtime dependencies no longer recursive ==

RDEPENDS are no longer automatically expanded recursively when packaging, as there is no mechanism to ensure they were fully computed and thus races were observed. When setting RDEPENDS explicitly in a recipe, you will need to ensure the runtime dependencies are fully specified.<span style="color: red; font-weight:bold;">Needs clarification</span>

== Sanity checks ==

* SRC_URI is now checked for usage of two problematic items:
*# "${PN}" - instead "${BPN}" should be used to avoid problems when PN is prefixed or suffixed e.g. with multiconfig.
*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

== Miscellaneous ==

* The gnome class has been removed, as it did not do very much anymore. Recipes that previously inherited this class should be updated to do the following:
inherit gnomebase gtk-icon-cache gconf mime
* The meta/recipes-kernel/linux/linux-dtb.inc file has been removed. It was previously deprecated (in favour of setting KERNEL_DEVICETREE in any kernel recipe) and only produced a warning. Remove any include/require statements pointing to this file.
* TARGET_CFLAGS, TARGET_CPPFLAGS, TARGET_CXXFLAGS, and TARGET_LDFLAGS are no longer exported to the external environment. This has not required changes to any recipes, but if for some reason the software being built by one of your recipes is expecting these variables to be set then it will now fail, and you will need to either export the variable(s) in the recipe or change the scripts so that that isn't necessary.
* The host distro identifier as used in NATIVELSBSTRING (when not using uninative) and SANITY_TESTED_DISTROS is now always lowercased even if it does not contain a version number.
* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.<span style="color: red; font-weight:bold;">Needs clarification</span>

FutureMigrationGuide

2019-10-16T02:37:31Z

PaulEggleton:

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|This page should be used to keep track of items which should be added to the [http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration migration guide] in the YP Reference Manual. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.

Once the migration guide for a release has been completed the contents of this page should be cleared out.
|}

=3.0 Migration Guide items=

== Init system selection ==

Changing the init system manager previously required setting a number of different variables; this can now be accomplished by setting the INIT_MANAGER variable and corresponding include files (conf/distro/include/init-manager-*.conf); include files are provided for four values - "none", "sysvinit", "systemd" and "mdev-busybox". The default value "none" for INIT_MANAGER should allow your current settings to continue working, but it is advisable to set INIT_MANAGER explicitly.

== LSB support removed ==

LSB as a standard isn't current, and isn't well suited to embedded applications. Support may be continued in a separate layer if needed but at present it has been removed from the core.

Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

== Removed recipes ==

* core-image-lsb-dev: part of removed LSB support
* core-image-lsb: part of removed LSB support
* core-image-lsb-sdk: part of removed LSB support
* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
* gcc-8.3: remove 8.3 from zeus
* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
* irda-utils: obsolete - IrDA support has been removed from the Linux kernel in version 4.17 and later.
* libnewt-python: libnewt Python support merged into main libnewt recipe
* libsdl: replaced by newer libsdl2
* libx11-diet: obsolete
* libxx86dga: remove obsolete client libary
* libxx86misc: remove this now redundant library
* linux-yocto: version 5.0 removed
* lsbinitscripts: part of removed LSB support
* lsb: part of removed LSB support
* lsbtest: part of removed LSB support
* openssl10: replaced by newer openssl 1.1
* packagegroup-core-lsb: part of removed LSB support
* python-nose: remove the python 2.x version of the recipe
* python-numpy: remove the python 2.x version of the recipe
* python-scons: remove the python 2.x version of the recipe
* source-highlight: no longer needed
* stress: replaced by stress-ng
* vulkan: split into vulkan-loader, vulkan-headers and vulkan-tools
* weston-conf: functionality moved to weston-init

== Packaging changes ==

* The epiphany browser has been dropped from packagegroup-self-hosted as it has not been needed inside build-appliance-image for a long time and was causing resource problems.
* libcap-ng python support has been moved to a separate libcap-ng-python recipe to streamline the build process when the python bindings aren't needed
* libdrm now packages the amdgpu.ids file into a separate libdrm-amdgpu package
* python3: the runpy module is now in the python3-core package as it is required to support the common "python3 -m" command usage.
* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

== CVE checking ==

cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 and makes other improvements.

Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

== Bitbake changes ==

* addtask statements now properly validate dependent tasks - previously an invalid task here would be silently ignored, now it will generate a warning.
* Other invalid addtask and deltask usages will now trigger warnings (multiple target tasks arguments with addtask / deltask, multiple before/after clauses)
* The "multiconfig" prefix is now shortened to "mc"; "multiconfig" will continue to work, however it may be removed in a future release.
* bitbake -g no longer generates a recipe-depends.dot file as the contents (a reprocessed version of task-depends.dot) were confusing.
* The bb.build.FuncFailed exception, previously raised by bb.build.exec_func() when certain other exceptions have occurred, has been removed. The real underlying exceptions will be raised instead. If you have calls to bb.build.exec_func() in custom classes or tinfoil-using scripts, any references to bb.build.FuncFailed should be cleaned up.
* Additionally, the bb.build.exec_func() no longer accepts the "pythonexception" parameter - it now always raises exceptions. Remove this argument in any calls to bb.build.exec_func() in custom classes or scripts.
* The BB_SETSCENE_VERIFY_FUNCTION2 is no longer used - in the unlikely event that you have any references to it, they should be removed.
* The RunQueueExecuteScenequeue and RunQueueExecuteTasks events have been removed since setscene tasks are now executed as part of the normal runqueue. Any event handling code in custom classes or scripts that handles these two events will need to be updated.
* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

== Package runtime dependencies no longer recursive ==

RDEPENDS are no longer automatically expanded recursively when packaging, as there is no mechanism to ensure they were fully computed and thus races were observed. When setting RDEPENDS explicitly in a recipe, you will need to ensure the runtime dependencies are fully specified.{{font color|red|Needs clarification}}

== Sanity checks ==

* SRC_URI is now checked for usage of two problematic items:
*# "${PN}" - instead "${BPN}" should be used to avoid problems when PN is prefixed or suffixed e.g. with multiconfig.
*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

== Miscellaneous ==

* The gnome class has been removed, as it did not do very much anymore. Recipes that previously inherited this class should be updated to do the following:
inherit gnomebase gtk-icon-cache gconf mime
* The meta/recipes-kernel/linux/linux-dtb.inc file has been removed. It was previously deprecated (in favour of setting KERNEL_DEVICETREE in any kernel recipe) and only produced a warning. Remove any include/require statements pointing to this file.
* TARGET_CFLAGS, TARGET_CPPFLAGS, TARGET_CXXFLAGS, and TARGET_LDFLAGS are no longer exported to the external environment. This has not required changes to any recipes, but if for some reason the software being built by one of your recipes is expecting these variables to be set then it will now fail, and you will need to either export the variable(s) in the recipe or change the scripts so that that isn't necessary.
* The host distro identifier as used in NATIVELSBSTRING (when not using uninative) and SANITY_TESTED_DISTROS is now always lowercased even if it does not contain a version number.
* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.{{font color|red|Needs clarification}}

FutureMigrationGuide

2019-10-16T02:22:52Z

PaulEggleton:

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|This page should be used to keep track of items which should be added to the [http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration migration guide] in the YP Reference Manual. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.

Once the migration guide for a release has been completed the contents of this page should be cleared out.
|}

=3.0 Migration Guide items=

== Init system selection ==

Changing the init system manager previously required setting a number of different variables; this can now be accomplished by setting the INIT_MANAGER variable and corresponding include files (conf/distro/include/init-manager-*.conf); include files are provided for four values - "none", "sysvinit", "systemd" and "mdev-busybox". The default value "none" for INIT_MANAGER should allow your current settings to continue working, but it is advisable to set INIT_MANAGER explicitly.

== LSB support removed ==

LSB as a standard isn't current, and isn't well suited to embedded applications. Support may be continued in a separate layer if needed but at present it has been removed from the core.

Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

== Removed recipes ==

* core-image-lsb-dev: part of removed LSB support
* core-image-lsb: part of removed LSB support
* core-image-lsb-sdk: part of removed LSB support
* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
* gcc-8.3: remove 8.3 from zeus
* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
* irda-utils: obsolete - IrDA support has been removed from the Linux kernel in version 4.17 and later.
* libnewt-python: libnewt Python support merged into main libnewt recipe
* libsdl: replaced by newer libsdl2
* libx11-diet: obsolete
* libxx86dga: remove obsolete client libary
* libxx86misc: remove this now redundant library
* linux-yocto: version 5.0 removed
* lsbinitscripts: part of removed LSB support
* lsb: part of removed LSB support
* lsbtest: part of removed LSB support
* openssl10: replaced by newer openssl 1.1
* packagegroup-core-lsb: part of removed LSB support
* python-nose: remove the python 2.x version of the recipe
* python-numpy: remove the python 2.x version of the recipe
* python-scons: remove the python 2.x version of the recipe
* source-highlight: no longer needed
* stress: replaced by stress-ng
* vulkan: split into vulkan-loader, vulkan-headers and vulkan-tools
* weston-conf: functionality moved to weston-init

== Packaging changes ==

* The epiphany browser has been dropped from packagegroup-self-hosted as it has not been needed inside build-appliance-image for a long time and was causing resource problems.
* libcap-ng python support has been moved to a separate libcap-ng-python recipe to streamline the build process when the python bindings aren't needed
* libdrm now packages the amdgpu.ids file into a separate libdrm-amdgpu package
* python3: the runpy module is now in the python3-core package as it is required to support the common "python3 -m" command usage.
* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

== CVE checking ==

cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 and makes other improvements.

Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

== Bitbake changes ==

* addtask statements now properly validate dependent tasks - previously an invalid task here would be silently ignored, now it will generate a warning.
* Other invalid addtask and deltask usages will now trigger warnings (multiple target tasks arguments with addtask / deltask, multiple before/after clauses)
* The "multiconfig" prefix is now shortened to "mc"; "multiconfig" will continue to work, however it may be removed in a future release.
* bitbake -g no longer generates a recipe-depends.dot file as the contents (a reprocessed version of task-depends.dot) were confusing.
* The bb.build.FuncFailed exception, previously raised by bb.build.exec_func() when certain other exceptions have occurred, has been removed. The real underlying exceptions will be raised instead. If you have calls to bb.build.exec_func() in custom classes or tinfoil-using scripts, any references to bb.build.FuncFailed should be cleaned up.
* Additionally, the bb.build.exec_func() no longer accepts the "pythonexception" parameter - it now always raises exceptions. Remove this argument in any calls to bb.build.exec_func() in custom classes or scripts.
* The BB_SETSCENE_VERIFY_FUNCTION2 is no longer used - in the unlikely event that you have any references to it, they should be removed.
* The RunQueueExecuteScenequeue and RunQueueExecuteTasks events have been removed since setscene tasks are now executed as part of the normal runqueue. Any event handling code in custom classes or scripts that handles these two events will need to be updated.
* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

== Package runtime dependencies no longer recursive ==

RDEPENDS are no longer automatically expanded recursively when packaging, as there is no mechanism to ensure they were fully computed and thus races were observed. When setting RDEPENDS explicitly in a recipe, you will need to ensure the runtime dependencies are fully specified.

== Sanity checks ==

* SRC_URI is now checked for usage of two problematic items:
*# "${PN}" - instead "${BPN}" should be used to avoid problems when PN is prefixed or suffixed e.g. with multiconfig.
*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

== Miscellaneous ==

* The gnome class has been removed, as it did not do very much anymore. Recipes that previously inherited this class should be updated to do the following:
inherit gnomebase gtk-icon-cache gconf mime
* The meta/recipes-kernel/linux/linux-dtb.inc file has been removed. It was previously deprecated (in favour of setting KERNEL_DEVICETREE in any kernel recipe) and only produced a warning. Remove any include/require statements pointing to this file.
* TARGET_CFLAGS, TARGET_CPPFLAGS, TARGET_CXXFLAGS, and TARGET_LDFLAGS are no longer exported to the external environment. This has not required changes to any recipes, but if for some reason the software being built by one of your recipes is expecting these variables to be set then it will now fail, and you will need to either export the variable(s) in the recipe or change the scripts so that that isn't necessary.
* The host distro identifier as used in NATIVELSBSTRING (when not using uninative) and SANITY_TESTED_DISTROS is now always lowercased even if it does not contain a version number.
* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.