summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* libc-headers: bump to v5.14Bruce Ashfield2021-09-242-3/+5
| | | | | | | | | | | | The reference kernel is moving to 5.14, and 5.13 is EOL upstream, so we update the libc-headers to match. No patch issues were found for musl or glibc. (From OE-Core rev: 3cdaf2cb64303bc58ab8be40fce4091b5a7809b4) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-ust: fix do_compile error when PACKAGECONFIG examples is enabledChangqing Li2021-09-232-0/+36
| | | | | | | | | | | | when PACKAGECONFIG enabled examples, compile failed with error: fix below compile error during PACKGAGECONFIG examples is enabled: tmp/work/corei7-64-wrs-linux/lttng-ust/2_2.13.0-r0/recipe-sysroot-native/usr/bin/x86_64-wrs-linux/../../libexec/x86_64-wrs-linux/gcc/x86_64-wrs-linux/11.2.0/ld: warning: liblttng-ust-common.so.1, needed by ../../../src/lib/lttng-ust/.libs/liblttng-ust.so, not found (try using -rpath or -rpath-link) tmp/work/corei7-64-wrs-linux/lttng-ust/2_2.13.0-r0/recipe-sysroot-native/usr/bin/x86_64-wrs-linux/../../libexec/x86_64-wrs-linux/gcc/x86_64-wrs-linux/11.2.0/ld: warning: liblttng-ust-tracepoint.so.1, needed by ../../../src/lib/lttng-ust/.libs/liblttng-ust.so, not found (try using -rpath or -rpath-link) (From OE-Core rev: 907ebb5bb3d44dd5f68deb238098fb6f6413e2d4) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest: Add tests for bitbake shell/python task outputRichard Purdie2021-09-232-0/+128
| | | | | | | | | | We've seen issues where shell/python tasks lose their log file entries or output and also where output is duplicated. Add some tests to attempt to spot regressions in this area in future. (From OE-Core rev: 414020a9bd656ee61efe2f47db1b31d86b15c1c8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: build: Fix log flushing raceRichard Purdie2021-09-231-38/+38
| | | | | | | | | | | | | | There is a race between sending the TaskFailed event which could trigger the UI to look at the logs and flushing and closing the log files. Reverse the order of the finally clause and the exception handling to ensure we've handled the logfiles before sending the task events. This should fix a race seen in bblogging.BitBakeLogging.test_python_exit_logging (Bitbake rev: 032190aac31604d37740d8aecf6e74a5448de358) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: build: Make exception printing clearerRichard Purdie2021-09-231-1/+1
| | | | | | | | | | | | | | Shows: ERROR: SystemExit(1) instead of: ERROR: 1 (Bitbake rev: df89e37c33e4398a5f8ece9a8b973be3fe2ff361) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: build: Ensure python stdout/stderr is logged correctlyRichard Purdie2021-09-231-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | Currently we see things like: Log data follows: | DEBUG: Executing python function do_pythontest_exit | DEBUG: Python function do_pythontest_exit finished | ERROR: 1 | This is python stdout Whilst after the change we see things like: Log data follows: | DEBUG: Executing python function do_pythontest_exit | This is python stdout | DEBUG: Python function do_pythontest_exit finished | ERROR: 1 since the output is now correctly mixed with the log messages. In some cases the logging tests indicate the output is being lost entirely which is bad for debugging and makes things rather confusing. (Bitbake rev: 8966b43761500e0505333d8c9a3f0f2c3dbe7559) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ssate: Cleanup directtasks handlingRichard Purdie2021-09-231-14/+4
| | | | | | | | | | | | | There are several tasks which should only be triggered by direct dependencies. Some are listed in the dep loop, some are not. They should all be in both cases. Fix this by making a list and using the list in both cases to fix various inconsistencies. (From OE-Core rev: 29d285bc07bd7732c7ea39c0fd03c0b3c0d93e52) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Avoid deploy_source_date_epoch sstate when unneededRichard Purdie2021-09-231-0/+4
| | | | | | | | | | | | This sstate task is only needed when depended upon, it can be skipped if there are no tasks running that directly depend upon it. This reduced the number of sstate tasks in something like an image build. (From OE-Core rev: 601cee016da5c7505915e26641a085714de175ce) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure deploy tasks don't pull in toolchainsRichard Purdie2021-09-231-2/+2
| | | | | | | | | | | | | | If an image is built from sstate, the cross toolchain was being pulled in. This was due to the sstate dependencies for deploy tasks not being considered in the "depvalid" logic. do_deploy tasks do not need their populate_sysroot dependencies when installed from sstate so skip these. This reduces the sstate pulled in by an image build from sstate significantly. (From OE-Core rev: 8047c184f8266fc047c0e5a5524586d414528626) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Mark deploy an sstate taskRichard Purdie2021-09-231-0/+1
| | | | | | | | | | | | | | Deploy is a tricky task as it isn't in SSTATETASKS as it isn't always present. We do need to ensure dependency chains around do_deploy tasks are correctly handled as sstate tasks though. For now add to the list of sstate tasks manually (like the other locale task reference). Without this, missing manifest files could be reported now that do_deploy tasks no longer have their dependencies added by the depvalid function. (From OE-Core rev: 1fdbe550323b98ca67ed7130f5a0d7d626bd2c64) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: Drop useless classRichard Purdie2021-09-233-9/+1
| | | | | | | | | | | | | | | This class was added by me back in 2007 and has changed one for a whitespace issue since. It only has two lines and neither are particularly useful, one was replaced by the nopackages class, the other adding recursive dependencies also is now mainly problematic adding tons of unneeded dependencies. The name is hard to understand and the class doesn't have a clear purpose. Drop it. Remove the references in devtool (which may be the one reason to keep it around but in my view still not worth it). (From OE-Core rev: 6e2cbfc561dac89bf9183d24d90e52f7d9117826) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball/uninative-tarball/meta-ide-support: Drop useless meta classRichard Purdie2021-09-234-4/+1
| | | | | | | | | | | | The class adds an emtpy PACKAGES setting but most code now uses the nopackages class which is much clearer. It also adds recursive do_build dependencies which don't really serve any useful purpose any more. Simplify the code and drop the class use. (From OE-Core rev: 030d56e2e8ece93472adc51fe467221d846c9ac0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_base/images: Drop use of 'meta' class and hence do_build ↵Richard Purdie2021-09-231-1/+3
| | | | | | | | | | | | | | | | | | | dependencies The 'meta' is old and not very useful. It empties PACKAGES and creates recursive do_build dependencies. We shouldn't need such recursive build dependencies any more so simplify the code. This does cause behaviour changes as some dependencies are no longer built. It did show up issues with qemu-helper-native handling for example but those issues look like real races and the underlying dependency chains were not correct. 'bitbake XXX --runall build' would give the previous behaviour. (From OE-Core rev: 41d7f1aa2cc9ef5dba4db38435402d4c9c0a63e1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* reproducible_build/package_XXX: Ensure SDE task is in dependency chainRichard Purdie2021-09-234-3/+8
| | | | | | (From OE-Core rev: 938e4dfb68a465f61cb754b2cd28d0728616b5a9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_ipk/deb/rpm: Drop recursive do_build task dependenciesRichard Purdie2021-09-233-10/+3
| | | | | | | | | | | | | | | | | | | | | | | | | This is a controversial change which removes the recursive dependencies from the do_build target of packaging tasks of recipes. Currently this means when you "bitbake <image>" or "bitbake <recipe>", the packaging tasks run for all packaging backends enabled for all recipes in the dependency chain. The same therefore then applies to images. We don't actually need that, it is a convinience thing. Removing it massively simplifies the task graph and causes much fewer tasks to execute in many common scenarios. It also means less sstate is fetched for example when building an image. This means when building a recipe all package formats would be built but when building an image, only the format used by the image would be generated. This should be an improvement in most cases but some CI systems may need to be explict about what they're building. 'bitbake XXX --runall build' would give the previous behaviour. (From OE-Core rev: 220d29a5abb5be8b80c64d8f2f48949bc8c534a3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* siteinfo/autotools: Ensure task checksums reflect site filesRichard Purdie2021-09-235-9/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, if you change the site files, nothing rebuilds since they are not accounted for in task checksums. They could/should be through the file-checksums task flag. We need to cache all the files looked for, whether the exist or not so that if they do exist and didn't, the checksum also changes. This gets complicated by the need to clean out hardcoded build paths from the variable and that other layers can have site files. This patch adds this functionality. A new variable, SITEINFO_PATHVARS is added which controls which substitutions to make on the file-checksum values to remove the hardcoded paths. Layers adding site files will need to set this to a variable that has the layer path in it and is excluded from task hashes (COREBASE is the one the core layer uses). This patch will cause yocto-check-layer to fail for some layers where site files are added yet the layer isn't a machine specific layer. This is arguable correct since these additional site files apply to all recipes and things from a layer like core could be changed by such changes so it is right they should rebuild. There is a determinism issue potentially there if not. meta-openembedded does have some such references but looking at them they should move to core or likely just be removed as most look obsolete anyway. [YOCTO #13729] (From OE-Core rev: 29daffc2410f06f36b779d5bf1fd1ef6e900ca8f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image/qemu: Add explict depends for qemu-helper addto_recipe_sysroot taskRichard Purdie2021-09-232-2/+5
| | | | | | | | | | The populate_sysroot task isn't enough for qemu-helper-native, we need it's addto_recipe_sysroot task. This corrects what amounts to bad dependency information to be explicit. (From OE-Core rev: 55623420208bc4c77a61492d2bbcbc71d3123acd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* site: Drop ORBit2 relared cached variablesKhem Raj2021-09-238-113/+0
| | | | | | | | | ORBit2 is long gone (From OE-Core rev: a5c5dd9229553e0e364f083d661382fe0c15600c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* site: Drop caching libIDL_cv_long_long_formatKhem Raj2021-09-2314-42/+0
| | | | | | | | | recipe for libidl has long been deleted (From OE-Core rev: 587d0b51b09cd426dc4b2b7646fa063d10ae4f2f) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* connman: add CVE_PRODUCTSteve Sakoman2021-09-231-0/+2
| | | | | | | | | Upstream database uses both "connman" and "connection_manager" to report CVEs (From OE-Core rev: eadf7bb17289731be9747822e3d4084ab69cf109) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-publish-sdk: Disable git gc to avoid build errorsRichard Purdie2021-09-231-2/+2
| | | | | | | | | | I've puzzled over why I see local eSDK test failures. It is due to having a messy git tree locally, git then runs git gc in the background which races against the deletion code for the publish test. Disable git gc to avoid this. (From OE-Core rev: d938a74097202396beda2e3bb4f582342d6dfa1b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: tests/fetch2: Use our own git server for dtc test repoRichard Purdie2021-09-221-1/+1
| | | | | | (Bitbake rev: 36f6dce1b21a7d9f39a73f081395c71045960318) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/target/ssh: don't assume target_dumper is setRoss Burton2021-09-211-1/+3
| | | | | | | | | | The target_dumper property is only set by the QemuTarget subclass, so assign a default value and check it isn't None before calling it. (From OE-Core rev: add36cf85380bf7dc5339a9d65f951923317440b) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pybootchart: Avoid divide by zeroRichard Purdie2021-09-211-1/+4
| | | | | | | | | | Avoid a rare divide by zero error if there isn't data point spread. [YOCTO #14547] (From OE-Core rev: d7e36d01e87ddf89f76f164a0b7d98f597a53fa5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libsoup-2.4: remove obsolete intltool dependencyRoss Burton2021-09-211-1/+1
| | | | | | | | | This hasn't been needed since libsoup 2.65.2. (From OE-Core rev: 250a3f9a804917c8a9427d0209365d27b1b8fa4a) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shared-mime-info: use a more concise descriptionRoss Burton2021-09-211-1/+1
| | | | | | | | | For example we don't need to talk about historic build dependencies. (From OE-Core rev: b67ae98ef803b889fceb5713c539504d48f1a926) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cross: Drop unused do_installRichard Purdie2021-09-211-4/+0
| | | | | | | | | | | | | All the users of the cross class I could find redefine the do_install function. It is unusual and likely undesirable for the class to be changing this from the default and likely a leftover from different times. Remove it as it isn't doing anything. [YOCTO #9272] (From OE-Core rev: 72f0e03a6909e6856510d913863fc9301de32cec) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* avahi: remove obsolete intltool-native dependencyRoss Burton2021-09-211-1/+1
| | | | | | | | | intltool was replaced with gettext in the 0.8 release. (From OE-Core rev: 0438c8e73419c0a81bbb42f777eb3e36f4878e79) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* testimage: remove aarch64 xorg exclusionJon Mason2021-09-211-2/+0
| | | | | | | | | | aarch64/qemuarm64 has had graphics support for some time. Remove this exclusion and allow graphics tests to be against qemuarm64. (From OE-Core rev: 1b436e4894663fa76865636b0b41c0c1503cc3bf) Signed-off-by: Jon Mason <jdmason@kudzu.us> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu-native: add direct dependency on ninja-native and meson-nativeMartin Jansa2021-09-212-2/+2
| | | | | | | | | | | | | | | * with many native dependencies excluded in: layer.conf: Extend recipes not to install without explict dependencies this was now failing with: ERROR: Cannot find Ninja and after adding ninja-native to DEPENDS it was failing due to missing meson as well: /OE/build/oe-core/tmp-glibc/work/x86_64-linux/qemu-native/6.0.0-r0/qemu-6.0.0/configure: 6415: --version: not found /OE/build/oe-core/tmp-glibc/work/x86_64-linux/qemu-native/6.0.0-r0/qemu-6.0.0/configure: 6418: setup: not found (From OE-Core rev: 7b2dfb49105e6465c5436869863e6a9720c60bbd) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-tools: Add missing DEPENDS on bison-nativeRichard Purdie2021-09-211-1/+1
| | | | | | | | | | This was being provided by other pieces of the dependency chain but is specifically required by configure and could fail if those pieces come from sstate. Fix such builds by adding the missing dependency. (From OE-Core rev: ba2587beb2a3fb0ef9139f846e161542d2c5c4ae) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: Add missing pkgconfig inheritRichard Purdie2021-09-2113-12/+13
| | | | | | | | | | | | Various recipes were missing a pkgconfig inherit or pkgconfig-native dependency despite using pkgconfig. Add the inherit to igt-gpu-tools/gdb/libmodulemd/libwpe/xwayland/waffle shaderc/iputils/wpebackend-fdo/lttng-ust/cargo. (From OE-Core rev: 777d9744570c2dc119dc5d04985896bbb1da5885) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sqlite3: Exclude CVE-2021-36690 from cve checksRichard Purdie2021-09-211-0/+2
| | | | | | | | | Issue is in an experimental extension we don't have/use. Could also be windows only. (From OE-Core rev: 6f5770b49f06168e3d6914bd92f0594bd05f1f8f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgcrypt: Upgrade 1.9.3 -> 1.9.4Richard Purdie2021-09-211-1/+1
| | | | | | | | Includes a fix for CVE-2021-40528. (From OE-Core rev: 24664297abd3844902fa40c21e4e975d89f40383) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vim: Backport fix for CVE-2021-3770Richard Purdie2021-09-212-0/+209
| | | | | | (From OE-Core rev: 54d3d023ce55ba4a7160ed25a283f0918e7d8e2e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* testimage: symlink the task log and qemu console log to tmp/log/oeqaAlexander Kanavin2021-09-211-2/+10
| | | | | | | | | | | | | This makes it easier for the AB scripts (particularly, collect-results) to access and archive these items, as they can contain useful information when ptests or other qemu tests fail (and also if they don't fail). [YOCTO #14518] (From OE-Core rev: 1965b344abcff0ba584136f929b4a14645f1585e) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/svn: Allow peg-revision functionality to be disabledRichard Purdie2021-09-211-2/+8
| | | | | | | | | | | | Sometimes the peg revision functionality we use in the svn fetcher is not the correct option. Add a parameter nopegrevision which can be added to disable this behaviour. [YOCTO #6258] (Bitbake rev: ea26682b706f655a8e418f56bebe742e2d130a1d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: data_smart: Don't add None to ExpansionError varlistRichard Purdie2021-09-211-2/+3
| | | | | | | | | If a "None" value gets into the varlist, it doesn't display properly. Ensure we don't add one to have the exception display properly. (Bitbake rev: ee26e258888114143e66330c256b5bfe7d071c53) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: tests/fetch2: Fix quoting warningRichard Purdie2021-09-211-6/+6
| | | | | | | | | | | | Fix: lib/bb/tests/fetch.py:1288: DeprecationWarning: invalid escape sequence for several lines of the fetch tests. (Bitbake rev: 9d84fd557a3fcbae2cdd70b24e69325ad737a01e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/git: Use os.rename instead of mvRichard Purdie2021-09-211-4/+4
| | | | | | | | | os.rename will overwrite the destination file if present so we can use this instead of the process call overhead. (Bitbake rev: b3cccaa6a896c41d8c9be5eebc327f726542d16b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rust-common.bbclass: make sure ccache existKai Kang2021-09-191-1/+1
| | | | | | | | | | | | | | | | | It fails to run task rust_create_wrappers of recipe which inherit rust-common.bbclass such as rust-hello-world if no host ccache exists: | DEBUG: Executing shell function do_rust_create_wrappers | /path/to/project/tmp-glibc/work/core2-64-wrs-linux/rust-hello-world/git-r0/temp/run.do_rust_create_wrappers.3422: line 179: ccache: command not found Run task rust_create_wrappers before do_prepare_recipe_sysroot to make sure required tools such as ccache exist. (From OE-Core rev: 46575e0d5b9e722558b64e22ed928e6d7b2c654a) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cpan-base.bbclass: use raw string for regexpAlexander Kanavin2021-09-191-1/+1
| | | | | | | | | | This eliminates a deprecation warning and a future error as stipulated by https://docs.python.org/3/library/re.html (From OE-Core rev: 1753a8d8fd2e9d98255beb81428f70cdf3421321) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: keep rootfs_size as integerAlexander Kanavin2021-09-191-1/+1
| | | | | | | | | | | | | | The corrected line accidentally converted it to float, which causes problems later on with python 3.10: | File "/home/alex/development/poky/scripts/lib/wic/partition.py", line 278, in prepare_rootfs_ext | os.ftruncate(sparse.fileno(), rootfs_size * 1024) | TypeError: 'float' object cannot be interpreted as an integer (From OE-Core rev: d1d260dd2d196d10379ed9e238bcb34f39f3a3b7) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: correct collections vs collections.abc deprecationAlexander Kanavin2021-09-192-7/+3
| | | | | | | | | collections.abc is available since 3.3 and doesn't need special handling. (From OE-Core rev: 01152c9410ba00274c8415a5d914dc33dfd0cf46) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rng-tools: add systemd-udev-settle wants to serviceClaudius Heine2021-09-191-0/+1
| | | | | | | | | | | | | | | | | rngd needs to start after `systemd-udev-settle` in order for the kernel modules of the random source hardware to be loaded before it is started. However, since the `rngd.service` does not require or want `systemd-udev-settle.service` it might not be scheduled for start and the `After=systemd-udev-settle.service` there has no effect. Adding `Wants=systemd-udev-settle.service` provides a weak requirement to it, so that the `rngd` is started after it, if possible. (From OE-Core rev: e9715d4234eb7b45dee8b323799014646f0a1b07) Signed-off-by: Claudius Heine <ch@denx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* machine/qemuarm*: use virtio graphicsJon Mason2021-09-193-3/+4
| | | | | | | | | | | Switch to using virtio graphics for the Arm QEMU machines. You will noticed the difference in the dmesg by seeing: [ 2.693337] [drm] pci: virtio-gpu-pci detected at 0000:00:10.0 (From OE-Core rev: 961158653170f53de58672e474c41f1533f469fc) Signed-off-by: Jon Mason <jdmason@kudzu.us> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cookerdata: Show a readable error for invalid multiconfig nameRichard Purdie2021-09-191-0/+2
| | | | | | | | | | | | | | If a multiconfig starts with a digit, users would see pages of errors as we use the multiconfig as a python function name prefix and python functions cannot start with a digit. We could avoid doing that but it is easier just to ask users to name multiconfigs not starting with digits. This tweak ensures the user sees an easier to understand error. (Bitbake rev: f9cddaeef35b2ea0dadf717101ed896f6b857abd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: enable python warnings at the first opportunityAlexander Kanavin2021-09-1912-0/+21
| | | | | | | | | | | We really do want to see those, as they tend to turn into hard errors eventually, as what happened with collections vs collections.abc in python 3.10. (Bitbake rev: bc43fbb86361a21dc2d5deb910810c5a77fdabe8) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* releases: update to include 3.3.3Michael Halstead2021-09-183-5/+6
| | | | | | | | | Adding 3.3.3 to documentation switcher and release list. (From yocto-docs rev: cc88f73ea0e38f536cb3e05b504df80048856a84) Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: update output of "wic list images"Robert P. J. Day2021-09-181-5/+7
| | | | | | | | | | | Output order from "wic list images" is in different order, and was missing a couple entries. (From yocto-docs rev: 7df7356b8a306d7e77f0aab1f443fd1306c25620) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-07-08 23:01:40 +0000