summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2020-03-12qemu: fix CVE-2020-7039akuster/master-next_qemu_fixChangqing Li
Signed-off-by: Changqing Li <changqing.li@windriver.com>
2020-03-12bsp-guide: fix minor typos, wording, punctuationrpjday@crashcourse.ca
(From yocto-docs rev: 5877f94e31c580ed63770401507738c55f57739a) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12scripts/oe-buildenv-internal: Add BB_LOGCONFIGRichard Purdie
We should allow the logging configurations to be specificed from the environment, for example for autobuilder setups. (From OE-Core rev: 6b8ec5a58057464528fc33b3e0f82b8e545ffaa3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12fixupRichard Purdie
(From OE-Core rev: d485e77620c112c60efa586ffd582d08a9302b6a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12babeltrace2: initialize the other_entry pointerMingli Yu
When add below line to local.conf to enable debug build: DEBUG_BUILD = "1" There comes below failure when run "bitbake babeltrace2" | ../../../../../git/src/plugins/ctf/fs-src/fs.c: In function 'ds_index_insert_ds_index_entry_sorted': | ../../../../../git/src/plugins/ctf/fs-src/fs.c:702:5: error: 'other_entry' may be used uninitialized in this function [-Werror=maybe-uninitialized] | 702 | !ds_index_entries_equal(entry, other_entry)) { So initialize the other_entry pointer to fix the above error. (From OE-Core rev: 002f99c9fb2dc4d58a8305a588f8e823d75bb015) Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12oeqa: enable testresults.json for testexportStefan Kral
Add the option --json-result-dir to oeqa core context to enable testresults.json creation for test runs via testexport. Eg. oe-test runtime --json-result-dir . (From OE-Core rev: da1611af42ee4efd11e7eae73e2278e74ed3fb1a) Signed-off-by: Stefan Kral <sk@typedivision.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12weston-init: Allow use of weston without input devicesDomarys Correa
Don't force users to have input device in your targets. As the default option require-input is set to true, Weston only starts if we have a device in /dev/input/event* and this not a requirement for all applications, e.g. kiosk browser. (From OE-Core rev: 6d522f256d5cb23e992e68506d49e349c2f43b7c) Signed-off-by: Domarys Correa <domarys.correa@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12boost: fix reproducibilty issuesJeremy Puhlman
fix cmake file references of image dir path (From OE-Core rev: c7d155ddc2ed2223fd94f3d24dbc4bea6a7c94a5) Signed-off-by: Jeremy A. Puhlman <jpuhlman@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12dnf: fix reproducibilty issueJeremy Puhlman
Script points to native python3 (From OE-Core rev: 81a181a20bc806d18c5867ab00c4073c851c867a) Signed-off-by: Jeremy A. Puhlman <jpuhlman@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12gtk-doc: Fix reproducibity issuesJeremy Puhlman
path to pkg-config and python3 encoded in scripts (From OE-Core rev: 7270d6b1df82c89dc7652fc4b57cd2791e21bc3a) Signed-off-by: Jeremy A. Puhlman <jpuhlman@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12ltp: fix reproducibilty issuesJeremy Puhlman
Man pages are copied in to the target filesystem from the configured build, which leaks paths in to the work directory (From OE-Core rev: dde53e52ada07594836611509d6ddc84d915151d) Signed-off-by: Jeremy A. Puhlman <jpuhlman@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12qemu: Fix reproducibilty issuesJeremy Puhlman
tests/qemu-iotests/common.env is generated from configure which we pass ${HOSTTOOLS_DIR}/python3 as our python to use, which gets copied into the ptests. Correct python3 path. (From OE-Core rev: e69a9d8a9b7ec1e989755aaeaf9d0e9c748e07fb) Signed-off-by: Jeremy A. Puhlman <jpuhlman@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12strace: Fix reproducibility issuesJeremy Puhlman
gen_tests script encodes its full path to itself in each script (From OE-Core rev: 96ad323175ec76ee1eadc8a9a4bf8f58c580bb32) Signed-off-by: Jeremy A. Puhlman <jpuhlman@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12glib-2.0: Correct multilib conflictJeremy Puhlman
(From OE-Core rev: 6cedaf022998b144184d9d18b1b2c36ba498f0cd) Signed-off-by: Jeremy A. Puhlman <jpuhlman@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12babletrace2: make manpages multilib identicalJeremy Puhlman
(From OE-Core rev: c83046a95399cc1f945751b5577848f998596709) Signed-off-by: Jeremy A. Puhlman <jpuhlman@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12rootfs-postcommands: Remove spaces before ; in -ROOTFS_..._COMMANDAlex Kiernan
With spaces in ROOTFS_POSTPROCESS_COMMAND attempts to remove elements using ROOTFS_POSTPROCESS_COMMAND_remove causes parse failures of the form: bb.pysh.sherrors.ShellSyntaxError: LexToken(COMMA,';',0,0) followed by: LexToken(TOKEN,'write_image_test_data',0,0) LexToken(COMMA,';',0,0) LexToken(TOKEN,'set_systemd_default_target',0,0) LexToken(COMMA,';',0,0) LexToken(TOKEN,'systemd_create_users',0,0) Removing the spaces between the function name and semicolon allows the list to parse correctly. (From OE-Core rev: 07b7e388698b632d2d6f7e1ac8aadd235b744ceb) Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12HACK: signing: Add extra test debugRichard Purdie
(From OE-Core rev: edabeb8106c5888a52073589f0dbaecd31fbfbeb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: knotty: Update hash equivalence loggingJoshua Watt
Updates hash equivalence logging so that the interesting VERBOSE messages are always logged to the consolelog file so that issues in individual user builds can be diagnosed. The autobuilder logging config then updates this so that they also are shown on stdout, since the consolelog file is not capture there. In order to facilitate this, 2 new logging handlers were added, "BitBake.verbconsole" and "BitBake.verbconsolelog". Neither of these handlers are attached to anything by default, but they will log any messages that wouldn't otherwise be logged by the normal console or consolelog handlers. Users can attach whatever loggers the desire to this handler to get them to appear on the console or in the consolelog, as demonstrated by the autobuilderlog.json file. (Bitbake rev: fc726ebbc53be0387a1ce8290fecd547b5643173) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: Add autobuilder logging configurationJoshua Watt
Adds a configuration file that the autobuilder can use to capture interesting logging domains above the ones that show up for normal users on stdout/stderr. (Bitbake rev: 47d323fd226a1f1a713b0f29bf98279ed783daf6) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: runqueue: Lower setscene complete logging levelJoshua Watt
Lowers the level of the log message when setscene tasks have completed. This message can occur multiple times when hash equivalence is enabled, since the runqueue switches between executing setscene tasks and normal tasks. Since this is primarily of use when debugging hash equivalence, use the hash equivalence logger at VERBOSE level. [YOCTO #13813] (Bitbake rev: 242ef2c410e6493821334fd78b5c542b897d13e8) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: msg: Add helper to merge logging configsJoshua Watt
Adds a function that can be used by UI front ends to merge logging configuration fragments. (Bitbake rev: b7d5d1011eed2c1e4b907605d41408d37031b924) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: knotty: Add logging cleanupJoshua Watt
Adds code to close all loggers when bitbake exits. This prevents unclosed file ResourceWarnings. A form of this closing existed previously, but was removed in the new logging code. (Bitbake rev: 47ba09b47c7b1d4afc8394dd390fad23986bfad9) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake-user-manual: Add documentation for BB_LOGCONFIGJoshua Watt
Adds documentation describing how to use the BB_LOGCONFIG variable to enable custom logging. (Bitbake rev: 162df5b5a2fa142c6d5255b73573b97a68432153) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: Lower hash equivalence loggingJoshua Watt
Lowers the level at which hash equivalence messages are logged so as to not annoy the majority of users. The autobuilder can use a custom logging configuration to log these to a file for debugging (see contrib/autobuilderlog.json) [YOCTO #13813] (Bitbake rev: a0e22f7eb417109232bc0658bfc67f1640e44519) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: Log hash equivalence with a different loggerJoshua Watt
Switches the hash equivalence logging to use a different logger so that it can be easily filtered out with python's structured logging. (Bitbake rev: a8972a60452c2abef5da4c53f02eac6fad7e4185) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: worker: Remove unnecessary addDefaultLogFilterJoshua Watt
Adding the default log filter here is unnecessary because there are no defined logging domains when it is called, which means it does no actual filtering. (Bitbake rev: 23793c2c8fa51d92ee1ed7407b866c71d4fbe125) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: knotty: Setup logs with config helperJoshua Watt
Sets up logging in knotty to use python's structured logging config and the bb.msg.setLoggingConfig() helper to setup logging. This allows the user to specify additional logging mechanism in a config file with BB_LOGCONFIG (Bitbake rev: 37a013856aea99fd40db52182f33d836531820e4) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: knotty: Remove dependency on format variableJoshua Watt
Passing around the log formatter variable was unnecessary since the log levels of interest can be accesses as class members of bb.msg.BBLogFormatter. Switching to do this will make using the structured python logging much easier, since it can be difficult to extract out the formatter for a specific handler. (Bitbake rev: 2203fa30691ca1301869a90cbca85907e36ac745) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: lib/bb/msg.py: Add helper to set logging configJoshua Watt
Adds a helper function to setup the structure logging information in bitbake. The helper function takes a default configuration and an optional path to a user config file that can be merged into the default. (Bitbake rev: 175a267252f7df2217bbae473ccd3052b238b672) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: lib/bb/msg.py: Remove unused filtersJoshua Watt
Now that the filter are described using the python logging structure, these classes are no longer needed. (Bitbake rev: 28d758c4ddaa851f41ead61256e10ba3465f0863) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: lib/bb/msg.py: Add filter utilitiesJoshua Watt
Adds generic filter utilities that can be used to filter when the log level is greater than or equal to a defined value, or below a defined value, as well as a generic function to translate a string to a logging level (or bitbake logging level) (Bitbake rev: 22da31f26c98760097ced333caac49062b3f8cec) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: knotty: Add commented logging_tree codeJoshua Watt
Adds a comment section that can be easily uncommented to enable dumping the logging tree. This module is extremely useful for debugging issued with logging configuration (Bitbake rev: a383ec1f1e7ee36d2041efb25db423e220be9e04) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: lib/bb/msg.py: Add repr for BBLogFormatterJoshua Watt
Adds a __repr__ function for BBLogFormatter. This allows it to get a human readable string when printed using the logging_tree module (Bitbake rev: 6cdf80c289622db9f9fbb68890d4a8a0ce0aa386) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: lib/bb/msg.py: Use log level instead of debug countJoshua Watt
Passes around the actual logging level as the default log level variable instead of the debug count. This makes it easier to deal with logging levels since the conversion from debug count and verbose flag only has to occur once when logging is initialized and after that actual log levels can be used (Bitbake rev: 105db365cd16b5a703988693dd527b979e41cade) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: knotty: Handle logging messages with specific loggerJoshua Watt
Handles the log messages from the bitbake server with the specific logger that the event originated from. This allows hierarchical logging configurations to work as expected. (Bitbake rev: 3bde139fcd706d595719b5cc97cd46c900516288) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12bitbake: bitbake: lib/bb/msg.py: Convert default domains to a dictionaryJoshua Watt
Converts the default domain variable to a dictionary where the keys are the logging domains and the values are the logging level (instead of the debug count). This makes it easier to deal with the logging domains and the awkward conversion from a list to a dictionary only needs to be done once when logging is initialized. Finally, other code has been written that already assumes this variable is a dictionary, see: f04cd93109 ("bitbake: lib/bb: Optimise out debug messages from cooker") (Bitbake rev: 919216d5da7ec61cece92318f3e1f72304b5369c) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12curl: upgrade 7.69.0 -> 7.69.1Pierre-Jean Texier
Contains a number of fixes for issues discovered post-7.69.0. For details, see full changelog: https://curl.haxx.se/changes.html#7_69_1 (From OE-Core rev: d3af3cf801ab5b235bce427bc73d2e6b29083368) Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12oeqa/runtime/context.py: fix typoStefan Kral
(From OE-Core rev: bf959e6fd175d0841a1c042bf925c54200bea3d4) Signed-off-by: Stefan Kral <sk@typedivision.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12glew/curl: specify exclusive package configsKai Kang
Specify exclusive package configs for glew and curl to make sure that conflict package configs will NOT set at same time. (From OE-Core rev: 8579673bdb314dbc554f40fc4c4c1db3d0bb0d63) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-12base.bbclass: extend PACKAGECONFIG for conflict package configsKai Kang
There are mutually exclusive PACKAGECONFIGs in recipes. Though it declares that package configs are exclusive, it can't prevent users to set them at same time. Extend PACKAGECONFIG to support specifying conflicted package configs. (From OE-Core rev: 734475b3f86d88a548bc9eb91d836bd1b9335e9f) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-11bitbake: tests: Add test for gitsm fetcher with shallow mirror tarballsPaul Barker
(Bitbake rev: 2e26e97129d4c54bf86cdea8f9791696a06a36b4) Signed-off-by: Paul Barker <pbarker@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-11bitbake: fetch2/gitsm: Unpack shallow mirror tarballsPaul Barker
When a shallow mirror tarball is used to satisfy a gitsm URI it needs to be unpacked temporarily so that the .gitmodules file can be examined. (Bitbake rev: 3987db953e414255ce278bc25a5f6cec0f2a30c7) Signed-off-by: Paul Barker <pbarker@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-11manuals: Update YP manual notes with pointer to docs MLRobert P. J. Day
Update the "Manual Notes" section of numerous YP manuals with a reference to the recently-introduced YP documentation mailing list. (From yocto-docs rev: a10fe36c864b8f1a71c6a8eb7e1f6a4eef2f5171) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-11dev-manual: phrase should read "inherit packagegroup"Robert P. J. Day
(From yocto-docs rev: 446204632ac9e8de3ce0b22df6fa2bb7605b9bce) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-11documentation: Remove python from UBUNTU_HOST_PACKAGES_ESSENTIALKhem Raj
Ubuntu 20.04 doesn't have python package and therefore this list fails to install, python3 is required anyway so removing python is perhaps ok (From yocto-docs rev: a41567a4ee462c704a29ad5944a0c824d7eb840c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-11dev-manual-common-tasks: Fix runall referenceRichard Purdie
[YOCTO #13715] (From yocto-docs rev: 91fbf02ae126bcabfeb43525db620bbd36d5f583) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-11manuals: Updates to reflect that MACHINE defaults to qemux86-64Mark Asselstine
meta-yocto commit 69ddecdb1516 [local.conf.sample: change default MACHINE to qemux86-64] switched the default MACHINE from 'qemux86' to 'qemux86-64' but some documents which either explicitly mentioned the default, or where this was implicit didn't receive an equivalent update. Where it made sense we continue this change in default to the docs. In other places, such as the kernel-dev manual, we note the new default and instruct the user how to switch back to 'qemux86'. Eventually we should probably update the kernel-dev manual to use the default, but for now the intention was to limit the impact of these changes. Note that ext3 has also been replaced with ext4 for image generation, so while we are modifying runqemu lines to qemux86-64 we also make the change to reference ext4 such that the runqemu commands will function properly. (From yocto-docs rev: 8c1d8ab1170f47a2c2692beb903ab0b7c6835b7b) Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-11ref-manual: Add a tips on how to achieve whitelisting of licensesPeter Kjellerstedt
It is sometimes more appropriate to define the licenses that are allowed to be used rather than the ones that are not permitted. This adds a tips on how this can be achieved by using AVAILABLE_LICENSES and some Python set arithmetics. (From yocto-docs rev: dd26d8a9f89402a9828bf02f2e65054d4c0f406f) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-11ref-manual: Add a variable description for AVAILABLE_LICENSESPeter Kjellerstedt
(From yocto-docs rev: 275ea2bb30693315ebea659a82065b75066e13b6) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-03-11ref-manual: Update the documentation for USERADD_ERROR_DYNAMICPeter Kjellerstedt
* Update USERADD_ERROR_DYNAMIC[doc] and the first paragraph to match the definition in meta/conf/documentation.conf. * Add a note explaining the differences in behavior when setting USERADD_ERROR_DYNAMIC to "warn" and "error" respectively. [YOCTO #12932] (From yocto-docs rev: 28cd546f3fe1eadd73ba71f9fe9a558538e69b0f) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>