If BBLAYERS contains a layer providing a package for
virtual/bootloader, building for the beaglebone-yocto machine will
fail. Setting u-boot as the preferred provider for virtual/bootloader
ensures u-boot is choosen and the build succeeds.
(From meta-yocto rev: 2ffbaf54f4d88ba251d282c90755ea964d224ba6)
Signed-off-by: Vivien Didelot <vdidelot@pbsc.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some auxiliary u-boot recipes may need u-boot properly configured
(including *.cfg additions via bbappends) but aren't necessarily
building u-boot itself; to support such situations, here we split the
u-boot do_configure() out of u-boot.inc and into its own
u-boot-configure.inc.
(From OE-Core rev: e55e6fb4983a41f74c0e457bf54bd8dfa5608daa)
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
0001-btrfs-tools-include-linux-const.h-to-fix-build-with-.patch
removed since it is included in 5.16
Add 0001-btrfs-progs-kerncompat-add-local-definition-for-alig.patch
to fix "undefined reference to `__ALIGN_KERNEL'".
Changelog:
=========
- rescue: new subcommand clear-uuid-tree to fix failed mount due to bad uuid
subvolume keys, caught by tree-checker
- fi du: skip inaccessible files
- prop: properly resolve to symlink targets
- send, receive: fix crash after parent subvolume lookup errors
- build:
fix build on 5.12+ kernels due to changes in linux/kernel.h
fix build on musl with old kernel headers
- other:
error handling fixes, cleanups, refactoring
extent tree v2 preparatory work
lots of RST documentation updates (last release with asciidoc sources),
https://btrfs.readthedocs.io
(From OE-Core rev: 420191dc951f04b36645ffae2d946b50150feab0)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libavresample has been removed; libswresample is the replacement.
(From OE-Core rev: 5555bca01750024a786a1f78d573d02f12b45686)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove patch as upstream addressed the issue.
(From OE-Core rev: cf11425c460ee4ff6b7ac0221a21b13b2d2b7e1e)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
License-Update: license clarified to BSD-3-Clause only
(From OE-Core rev: 79201206b5f7867ad7ffd462705f34179b33c0d7)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream review and request to address it got no reaction
from the author, and the patches are an ongoing rebase burden,
so if someone needs this feature, please complete
the upstreaming work first.
(From OE-Core rev: c748945e9c91eb2b83b8a44828f35579bcd09146)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
License-Update: copyright years
(From OE-Core rev: d6515a7f58d0405efea21e3be4158681ed9edbe6)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop patch as issue resolved upstream.
(From OE-Core rev: a8accf2a042f8a8cbba350c6de20152efeddd747)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Backport patches to epiphany/gcr/g-i to address failures with new meson.
(From OE-Core rev: 2ab302edc33681f94b2cd85b564f6feebe154392)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This allows automated version updates when possible, and reduces friction in manual ones.
(From OE-Core rev: 54d4a767ab7beaa64cfc4c221317ea03b0b119ab)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This avoids various sstate fetch errors from weird silent failures in the sstate
archive testing code caused by lack of srcrev support in the crate fetcher.
(From OE-Core rev: 8205668a339946974b4460cf1ca7e6e7a645479b)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After the changes to the native outhash files to ensure populate_sysroot for
native recipes correctly accounts for runtime dependencies, this doesn't reset
the target output namespace and means reproducibility issues are still triggering
on our test infrastructure.
Bump the version being used for hashequiv to ensure we avoid these issues with
a new namespace.
(From OE-Core rev: 3510caa7245d1993b2dc54c7bf2c7a884dd10c88)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The bb.fatal() case where sstate failed to find/use an archive in setcene tasks
is suboptimal. Bitbakes handling of setscene tasks will be to warn but the fatal
will turn this into an error, despite the real task being rerun.
In these failure cases other messages would usually have been printed so turn
this into a warning and raise a handled exception status so that bitbake knows
to fail the task but not print more messages.
(From OE-Core rev: 7875baeca7a3ed216b2442fb8771e51efbfa5a4f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Errors like
SState: cannot test file://universal/5f/10/sstate:m4-native:x86_64-linux:1.4.19:r0:x86_64:7:5f108b175274798b17950b5ee686bf61445e90fb204d7f795e5b879b5603e88b_deploy_source_date_epoch.tar.zst: 'GIT_SSL_CAINFO'
aren't useful, try and improve on this.
(From OE-Core rev: 1701d40536db098adb26508799bae13733f1a6fd)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This imports the crate fetcher from OE-Core to resolve various module issues
and adds some very very basic tests of that new fetcher.
(Bitbake rev: 1f06f326fa8b47e2a4dce756d57a9369a2225201)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If an unexpected exception occurs in a setscene task, it is currently hidden
from the user and not recorded in any logs. This isn't helpful to debug
such failures.
Change the code so that even in the "silent" or "quiet" task case (setscene
tasks), a warning is shown with the traceback unless it was an "handled"
exception. This means the failing function can show it's own warning/error
instead if it wants to and then raise a handled event.
(Bitbake rev: 41dcdc61eb40def8c14a42e8d7bb9ce5a34afa57)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We're seeing random failures in the SystemTap tests in qemuarm on kernel
5.10. This might be related to the buffer between user and kernel space
being too small, so explicitly set the size.
If this cures the problem it should be considered a workaround and not
the solution.
[ YOCTO #14673 ]
(From OE-Core rev: 04c622387ea78920fdb9754fa977883cd6d621a4)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream mentioned our ptest-runner could likely be simplified. I had a
look at the output and yes, most of the code in the runner is now obsolete
as upstream output is compatible with what we need. Simplify accordingly.
(From OE-Core rev: 9a9f0a4a062a3c2adf2ac75b4fcdedbb7168335b)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Vivien Didelot
Zev Weiss
wangmy
Sundeep KOKKONDA
Alexander Kanavin
Richard Purdie
Ross Burton