[yocto-security] [OE-core CVE] branch sumo-next updated. 2018-04-461-g9155d04
cve-notice at lists.openembedded.org
cve-notice at lists.openembedded.org
Sun Mar 24 09:54:30 PDT 2019
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "".
The branch, sumo-next has been updated
via 9155d04a2ff50551e4bd3bfa9bf3bca9e089ba33 (commit)
via c16da198664e16d842f1c2b142e5bf4eb1d48c8d (commit)
via 659ff5c5ebda73ed499ef6569c00880f9aabc01c (commit)
via 50172220a4905921fc6beeb1f5783a1f890990fc (commit)
via 3685c4c10e9ee839a2010dd4a7f982b78a3fc87f (commit)
via 814293f7f1f1f69efebbf01ecf7be3aed070643b (commit)
via 5e396b15c1c966a9c5e6f73869cecd6ff3648819 (commit)
via 0aa11c0021f5a03bf47d293d752d322f5e2667be (commit)
via 7c5d14dd50411a0d5cd30ad021f0d7312453e0e4 (commit)
via e469b51739c3ca176f0ba03075219c5abb1e63f6 (commit)
via f5659709cf388e648f028224f028e988dd9ec90c (commit)
via 72ad46952ffe043c2679671e7f83e74faf124685 (commit)
via aaf8151811c7e4d26f5dea563a0ffd1506c51519 (commit)
via a5dcf0c4bd9a0be2f2484b0b1b3e77f1f2128dfc (commit)
via 342157b135e7493e5965b706ede93bee190fbe32 (commit)
via 607350d98aa4c65b71fe1f10900e205fad81d1ec (commit)
via 10fa35a75617e82650b12d3e353a554f05f036dd (commit)
via da41e48567eb21a47426a6fbe23ea07ce780cd3c (commit)
via ddbe969d0c9052a3ae17ef8f1cec8da847c722d3 (commit)
via d490839e881f3ff30a4bde8137cb04cb0fd37acd (commit)
via 3e8ba9af58253ed9db0f0376a8e2966e45ee089e (commit)
via 06bf145cee24b677ab076498fe8399126971bc43 (commit)
via 665b41d326654235d305649be4be69a1be8dc00b (commit)
via dfded083d9456c8d2bb168dbe8e08b2ffb3e1a26 (commit)
via 85e498a4671426999610d90c87c354d41cfe8443 (commit)
via 6d56e912fbbaa22830b4da5ab230586a3d15b23e (commit)
via b119872fb794a36b6eb9ef5e9c42a9c6c991e835 (commit)
via ee6a2e0ccb11e5f5267bc2e406203c78b0443415 (commit)
via c7c4920fc287bdb5f7a0bca7b2ec2ab7a43f58fd (commit)
via 8480fff287e660f85a99fcc28119fe80d517e0b2 (commit)
via 97e2d65d1c406bc58fe693e500fcc939459bac1a (commit)
via 9e1c69932add702b9c5bc1faa9ef5db975de0ee3 (commit)
via c0a3874799224c9ae0d6d7dc4d0a0acf364ccdab (commit)
via 3eb59559ecd2e93fb590a330b47de1db0750fc0b (commit)
via 9cb8353a4f0137823d6ed3e467db9dd7ead7b3de (commit)
via 8e23a3d59421f34961f39a7db512e93eb9647ec6 (commit)
via 4eac9a5337d93b6cbd3916af97f62bb04881c9cd (commit)
via a80498e62898110e2ed6b01cbb9f5dd85995d13b (commit)
via 76c66e061cdcdcbad73ed503668115120feb0ea3 (commit)
via 9188ef8d1edbba8041a73d3bb8a9bfd194db0e92 (commit)
via dab22dc58eabaeb421afa3c7de1cc08c5ec34c61 (commit)
via 1207949c986cc9f6b3940a99e87bc4d8cfb86d5b (commit)
via e4990ae01c9f3f486b4b745a2602795e9d496109 (commit)
via 544c56b6950f0598d5eaf62d9ae9d9de5fcb7eaf (commit)
via 03b7658369bb7c1c8fbbaac7d9e281617cc16135 (commit)
via babdd2f6addb06c23e4882107be07034ca49bcb8 (commit)
via bde50fc78ae75fd585f8914e458d65c328857fb2 (commit)
via e5bebaddab47b418013f3d329dbb105ce69118bf (commit)
via a2cbc5954d44b0922136fc3d75f891064a948298 (commit)
via 1ce378ce07d2c49f40054893a623456c8471e177 (commit)
via 61bca5a7f6b3fc03cd88cbf8867708d28e0a3522 (commit)
via 872c6e5101f4f27dcfc63d141d1b6568f46d2b5f (commit)
via 05896e2f83ffef5262ccd3a0fa20b81b2a878957 (commit)
via 9d8a97b43c42b87c56d3b2ac318cb5482e86c397 (commit)
via 643457d350a921379600248f99d73374e6a2f5a2 (commit)
via 8bf8cbb82472a0547b62f94fafa5790cf67ff9cb (commit)
via d82f2a0a17ecad5fdb2d2450f5048d00cf0448b1 (commit)
via 4b9641505f39718fe820eb199ed6554662d4d4cf (commit)
via eeee75d0a51ab7c15457b89233b7bb5254d7ee0b (commit)
via e1b050f53ece2a31cd6866d2d737d7c67a44cea4 (commit)
via 2fac83ff87d9ad934250f712d2d0fd91fccb8728 (commit)
via de1b80f7f7b787f6b5b62c576ca6c62d2440031c (commit)
via ae10351f4aa443fc6df5a674b0aae0731304254d (commit)
via 89dcc555f57ce13645c3876b42be3846fe3b7863 (commit)
via f8c111891066609ed40d11fee61ca9e29b5b6029 (commit)
via 1af1e9c23965637ab4a23b3eaf64192694c5448d (commit)
via 3383b1f9bb4aedfb88e888e88fe316e3f361c7bf (commit)
via d58fe9d352ae7de857e7f55b88f6e7d35b2cd706 (commit)
via 6c930a8f5c11947c3b916efe23f33af462701bee (commit)
via 40679b9ee29b600a514f2fb82865a0fecca70bf7 (commit)
via fc8a9e3929a6042bd3d68755799138f417413ab3 (commit)
via 94c5cc56031b8558cdb75d5d4df05f6715618ab3 (commit)
via 7fb953573635afb1b6482dbd9f51eb0f05731eae (commit)
via a0afcd457af14c3bf3a74514be0e8a029a4fcf63 (commit)
from 31f0c5e59c7fb0ae0915de584fbfcf3d95bbb061 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 9155d04a2ff50551e4bd3bfa9bf3bca9e089ba33
Author: Mazliana <mazliana.mohamad at intel.com>
Date: Mon Mar 11 16:30:33 2019 +0800
resulttool/manualexecution: To output right test case id
We found that manualexecution does not capture test suite values
correctly if there are more than one test suite in test cases.
After verification has made we found out we should retrieved
full test cases value <test_module.test_suite.test_case> from
oeqa/manual/ json file rather than split it them into new
variables test_suite and test_cases.
Signed-off-by: Mazliana <mazliana.mohamad at intel.com>
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit c16da198664e16d842f1c2b142e5bf4eb1d48c8d
Author: Yeoh Ee Peng <ee.peng.yeoh at intel.com>
Date: Tue Mar 12 13:05:28 2019 +0800
resulttool/report: Enable roll-up report for a commit
Enable roll-up all test results belong to a commit
and to provide a roll-up report.
Signed-off-by: Yeoh Ee Peng <ee.peng.yeoh at intel.com>
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit 659ff5c5ebda73ed499ef6569c00880f9aabc01c
Author: Yeoh Ee Peng <ee.peng.yeoh at intel.com>
Date: Thu Mar 7 12:49:08 2019 +0800
scripts/resulttool: Enable manual result store and regression
To enable store for testresults.json file from manualexecution,
add layers metadata to configuration and add "manual" map to
resultutils.store_map.
To enable regression for manual, add "manual" map to
resultutils.regression_map. Also added compulsory configurations
('MACHINE', 'IMAGE_BASENAME') to manualexecution.
Signed-off-by: Yeoh Ee Peng <ee.peng.yeoh at intel.com>
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit 50172220a4905921fc6beeb1f5783a1f890990fc
Author: Yeoh Ee Peng <ee.peng.yeoh at intel.com>
Date: Thu Feb 28 09:58:57 2019 +0800
resulttool/regression: Ensure regressoin results are sorted
Sorted regression results to provide friendly viewing of report.
Signed-off-by: Yeoh Ee Peng <ee.peng.yeoh at intel.com>
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit 3685c4c10e9ee839a2010dd4a7f982b78a3fc87f
Author: Richard Purdie <richard.purdie at linuxfoundation.org>
Date: Thu Feb 28 13:16:47 2019 +0000
resulttool/store: Fix missing variable causing testresult corruption
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit 814293f7f1f1f69efebbf01ecf7be3aed070643b
Author: Richard Purdie <richard.purdie at linuxfoundation.org>
Date: Wed Feb 27 17:10:19 2019 +0000
resulttool/report: Ensure ptest results are sorted
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit 5e396b15c1c966a9c5e6f73869cecd6ff3648819
Author: Richard Purdie <richard.purdie at linuxfoundation.org>
Date: Wed Feb 27 17:05:29 2019 +0000
resulttool/report: Ensure test suites with no results show up on the report
ptest suites with no results don't show up on the reports even though we have
a duration for them. Fix this so the fact they report no tests is visible.
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit 0aa11c0021f5a03bf47d293d752d322f5e2667be
Author: Richard Purdie <richard.purdie at linuxfoundation.org>
Date: Wed Feb 27 16:51:56 2019 +0000
resulttool/report: Handle missing metadata sections more cleanly
Currently some older results files cause the code to give tracebacks.
Handle these missing sections more cleanly.
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit 7c5d14dd50411a0d5cd30ad021f0d7312453e0e4
Author: Richard Purdie <richard.purdie at linuxfoundation.org>
Date: Wed Feb 27 11:59:54 2019 +0000
resulttool/store: Handle results files for multiple revisions
Currently we cant store results if the results files span multiple
different build revisons. Remove this limitation by iterating.
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit e469b51739c3ca176f0ba03075219c5abb1e63f6
Author: Richard Purdie <richard.purdie at linuxfoundation.org>
Date: Sat Feb 23 22:49:11 2019 +0000
resulttool/resultutils: Avoids tracebacks for missing logs
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit f5659709cf388e648f028224f028e988dd9ec90c
Author: Richard Purdie <richard.purdie at linuxfoundation.org>
Date: Sat Feb 16 18:13:00 2019 +0000
resulttool: Improvements to allow integration to the autobuilder
This is a combined patch of the various tweaks and improvements I
made to resulttool:
* Avoid subprocess.run() as its a python 3.6 feature and we
have autobuilder workers with 3.5.
* Avoid python keywords as variable names
* Simplify dict accesses using .get()
* Rename resultsutils -> resultutils to match the resultstool ->
resulttool rename
* Formalised the handling of "file_name" to "TESTSERIES" which the code
will now add into the json configuration data if its not present, based
on the directory name.
* When we don't have failed test cases, print something saying so
instead of an empty table
* Tweak the table headers in the report to be more readable (reference
"Test Series" instead if file_id and ID instead of results_id)
* Improve/simplify the max string length handling
* Merge the counts and percentage data into one table in the report
since printing two reports of the same data confuses the user
* Removed the confusing header in the regression report
* Show matches, then regressions, then unmatched runs in the regression
report, also remove chatting unneeded output
* Try harder to "pair" up matching configurations to reduce noise in
the regressions report
* Abstracted the "mapping" table concept used to pairing in the
regression code to general code in resultutils
* Created multiple mappings for results analysis, results storage and
'flattening' results data in a merge
* Simplify the merge command to take a source and a destination,
letting the destination be a directory or a file, removing the need for
an output directory parameter
* Add the 'IMAGE_PKGTYPE' and 'DISTRO' config options to the regression
mappings
* Have the store command place the testresults files in a layout from
the mapping, making commits into the git repo for results storage more
useful for simple comparison purposes
* Set the oe-git-archive tag format appropriately for oeqa results
storage (and simplify the commit messages closer to their defaults)
* Fix oe-git-archive to use the commit/branch data from the results file
* Cleaned up the command option help to match other changes
* Follow the model of git branch/tag processing used by oe-build-perf-report
and use that to read the data using git show to avoid branch change
* Add ptest summary to the report command
* Update the tests to match the above changes
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit 72ad46952ffe043c2679671e7f83e74faf124685
Author: Mazliana <mazliana.mohamad at intel.com>
Date: Thu Feb 14 13:50:38 2019 +0800
scripts/resulttool: enable manual execution and result creation
Integrated “manualexecution” operation to resulttool scripts.
Manual execution script is a helper script to execute all manual
test cases in baseline command, which consists of user guideline
steps and the expected results. The last step will ask user to
provide their input to execute result. The input options are
passed/failed/blocked/skipped status. The result given will be
written in testresults.json including log error from the user
input and configuration if there is any.The output test result
for json file is created by using OEQA library.
The configuration part is manually key-in by the user. The system
allow user to specify how many configuration they want to add and
they need to define the required configuration name and value pair.
In QA perspective, "configuration" means the test environments and
parameters used during QA setup before testing can be carry out.
Example of configurations: image used for boot up, host machine
distro used, poky configurations, etc.
The purpose of adding the configuration is to standardize the
output test result format between automation and manual execution.
To use these scripts, first source oe environment, then run the
entry point script to look for help.
$ resulttool
To execute manual test cases, execute the below
$ resulttool manualexecution <manualjsonfile>
By default testresults.json store in <build_dir>/tmp/log/manual/
[YOCTO #12651]
Signed-off-by: Mazliana <mazliana.mohamad at intel.com>
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit aaf8151811c7e4d26f5dea563a0ffd1506c51519
Author: Yeoh Ee Peng <ee.peng.yeoh at intel.com>
Date: Thu Feb 14 13:50:37 2019 +0800
resulttool: enable merge, store, report and regression analysis
OEQA outputs test results into json files and these files were
archived by Autobuilder during QA releases. Example: each oe-selftest
run by Autobuilder for different host distro generate a
testresults.json file.
These scripts were developed as a test result tools to manage
these testresults.json file.
Using the "store" operation, user can store multiple testresults.json
files as well as the pre-configured directories used to hold those files.
Using the "merge" operation, user can merge multiple testresults.json
files to a target file.
Using the "report" operation, user can view the test result summary
for all available testresults.json files inside a ordinary directory
or a git repository.
Using the "regression-file" operation, user can perform regression
analysis on testresults.json files specified. Using the "regression-dir"
and "regression-git" operations, user can perform regression analysis
on directory and git accordingly.
These resulttool operations expect the testresults.json file to use
the json format below.
{
"<testresult_1>": {
"configuration": {
"<config_name_1>": "<config_value_1>",
"<config_name_2>": "<config_value_2>",
...
"<config_name_n>": "<config_value_n>",
},
"result": {
"<testcase_namespace_1>": {
"status": "<PASSED or FAILED or ERROR or SKIPPED>",
"log": "<failure or error logging>"
},
"<testcase_namespace_2>": {
"status": "<PASSED or FAILED or ERROR or SKIPPED>",
"log": "<failure or error logging>"
},
...
"<testcase_namespace_n>": {
"status": "<PASSED or FAILED or ERROR or SKIPPED>",
"log": "<failure or error logging>"
},
}
},
...
"<testresult_n>": {
"configuration": {
"<config_name_1>": "<config_value_1>",
"<config_name_2>": "<config_value_2>",
...
"<config_name_n>": "<config_value_n>",
},
"result": {
"<testcase_namespace_1>": {
"status": "<PASSED or FAILED or ERROR or SKIPPED>",
"log": "<failure or error logging>"
},
"<testcase_namespace_2>": {
"status": "<PASSED or FAILED or ERROR or SKIPPED>",
"log": "<failure or error logging>"
},
...
"<testcase_namespace_n>": {
"status": "<PASSED or FAILED or ERROR or SKIPPED>",
"log": "<failure or error logging>"
},
}
},
}
To use these scripts, first source oe environment, then run the
entry point script to look for help.
$ resulttool
To store test result from oeqa automated tests, execute the below
$ resulttool store <source_dir> <git_branch>
To merge multiple testresults.json files, execute the below
$ resulttool merge <base_result_file> <target_result_file>
To report test report, execute the below
$ resulttool report <source_dir>
To perform regression file analysis, execute the below
$ resulttool regression-file <base_result_file> <target_result_file>
To perform regression dir analysis, execute the below
$ resulttool regression-dir <base_result_dir> <target_result_dir>
To perform regression git analysis, execute the below
$ resulttool regression-git <source_dir> <base_branch> <target_branch>
[YOCTO# 13012]
[YOCTO# 12654]
Signed-off-by: Yeoh Ee Peng <ee.peng.yeoh at intel.com>
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
-----------------------------------------------------------------------
Summary of changes:
.../lib/oeqa/runtime/cases/dnf_runtime.py | 2 +-
meta/classes/archiver.bbclass | 6 +
meta/classes/image_types.bbclass | 1 +
meta/classes/kernel.bbclass | 4 +-
meta/classes/multilib_script.bbclass | 32 +
meta/classes/package.bbclass | 26 +-
meta/classes/package_rpm.bbclass | 6 +-
meta/classes/patch.bbclass | 1 +
meta/classes/populate_sdk_ext.bbclass | 5 +-
meta/classes/testimage.bbclass | 78 +-
meta/classes/testsdk.bbclass | 2 +-
meta/lib/oe/types.py | 24 +
meta/lib/oeqa/core/target/qemu.py | 5 +-
meta/lib/oeqa/files/test.pl | 2 -
meta/lib/oeqa/files/testresults/testresults.json | 40 +
meta/lib/oeqa/runtime/cases/apt.py | 2 +-
meta/lib/oeqa/runtime/cases/buildcpio.py | 9 +-
meta/lib/oeqa/runtime/cases/buildgalculator.py | 9 +-
meta/lib/oeqa/runtime/cases/buildlzip.py | 12 +-
meta/lib/oeqa/runtime/cases/date.py | 2 +
meta/lib/oeqa/runtime/cases/df.py | 2 +
meta/lib/oeqa/runtime/cases/dnf.py | 48 +-
meta/lib/oeqa/runtime/cases/gcc.py | 19 +-
meta/lib/oeqa/runtime/cases/kernelmodule.py | 8 +-
meta/lib/oeqa/runtime/cases/logrotate.py | 6 +-
meta/lib/oeqa/runtime/cases/opkg.py | 6 +-
meta/lib/oeqa/runtime/cases/perl.py | 30 +-
meta/lib/oeqa/runtime/cases/ptest.py | 2 +
meta/lib/oeqa/runtime/cases/python.py | 38 +-
meta/lib/oeqa/runtime/cases/rpm.py | 55 +-
meta/lib/oeqa/runtime/cases/scp.py | 2 +
meta/lib/oeqa/runtime/cases/ssh.py | 2 +
meta/lib/oeqa/runtime/cases/stap.py | 6 +-
meta/lib/oeqa/runtime/cases/xorg.py | 2 +
meta/lib/oeqa/runtime/context.py | 7 +-
meta/lib/oeqa/sdk/cases/perl.py | 25 +-
meta/lib/oeqa/selftest/cases/devtool.py | 65 +
meta/lib/oeqa/selftest/cases/distrodata.py | 4 +-
meta/lib/oeqa/selftest/cases/resulttooltests.py | 94 +
meta/lib/oeqa/selftest/cases/runqemu.py | 5 +
meta/lib/oeqa/selftest/cases/runtime_test.py | 4 +-
meta/lib/oeqa/selftest/cases/signing.py | 2 +-
meta/lib/oeqa/selftest/context.py | 3 +-
meta/lib/oeqa/targetcontrol.py | 12 +-
meta/lib/oeqa/utils/buildproject.py | 5 +
meta/lib/oeqa/utils/dump.py | 2 +-
meta/lib/oeqa/utils/httpserver.py | 37 +-
meta/lib/oeqa/utils/qemurunner.py | 3 +-
meta/lib/oeqa/utils/qemutinyrunner.py | 2 +-
meta/recipes-core/busybox/busybox.inc | 5 +-
...sive-let-s-rework-the-recursive-logic-to-.patch | 252 +++
...eserializing-state-always-use-read_line-L.patch | 250 +++
...sure-we-have-enough-space-for-the-DHCP6-o.patch | 39 +
...n-t-resolve-pathnames-when-traversing-rec.patch | 643 +++++++
.../systemd/systemd/0002-Make-tmpfiles-safe.patch | 1828 ++++++++++++++++++++
...-not-store-the-iovec-entry-for-process-co.patch | 193 +++
...ld-set-a-limit-on-the-number-of-fields-1k.patch | 60 +
...ote-set-a-limit-on-the-number-of-fields-i.patch | 79 +
...nal-fix-out-of-bounds-read-CVE-2018-16866.patch | 49 +
.../systemd/systemd/CVE-2019-6454.patch | 210 +++
...e-receive-an-invalid-dbus-message-ignore-.patch | 61 +
meta/recipes-core/systemd/systemd_237.bb | 13 +-
.../libtool/libtool-cross_2.4.6.bb | 8 +
.../libtool/libtool/multilib.patch | 23 +
meta/recipes-devtools/libtool/libtool_2.4.6.bb | 6 +
.../run-postinsts/run-postinsts/run-postinsts | 21 +-
.../run-postinsts/run-postinsts.service | 1 -
.../cpio-2.12/0001-Fix-segfault-with-append.patch | 87 +
meta/recipes-extended/cpio/cpio_2.12.bb | 1 +
...code-native_2018f.bb => tzcode-native_2018i.bb} | 8 +-
.../tzdata/{tzdata_2018f.bb => tzdata_2018i.bb} | 4 +-
.../pybootchartgui => lib/resulttool}/__init__.py | 0
scripts/lib/resulttool/manualexecution.py | 142 ++
scripts/lib/resulttool/merge.py | 42 +
scripts/lib/resulttool/regression.py | 192 ++
scripts/lib/resulttool/report.py | 150 ++
scripts/lib/resulttool/resultutils.py | 131 ++
scripts/lib/resulttool/store.py | 99 ++
.../resulttool/template/test_report_full_text.txt | 44 +
scripts/oe-git-archive | 19 +-
scripts/resulttool | 93 +
scripts/runqemu | 63 +-
scripts/runqemu-gen-tapdevs | 27 +-
83 files changed, 5298 insertions(+), 309 deletions(-)
create mode 100644 meta/classes/multilib_script.bbclass
delete mode 100644 meta/lib/oeqa/files/test.pl
create mode 100644 meta/lib/oeqa/files/testresults/testresults.json
create mode 100644 meta/lib/oeqa/selftest/cases/resulttooltests.py
create mode 100644 meta/recipes-core/systemd/systemd/0001-chown-recursive-let-s-rework-the-recursive-logic-to-.patch
create mode 100644 meta/recipes-core/systemd/systemd/0001-core-when-deserializing-state-always-use-read_line-L.patch
create mode 100644 meta/recipes-core/systemd/systemd/0001-dhcp6-make-sure-we-have-enough-space-for-the-DHCP6-o.patch
create mode 100644 meta/recipes-core/systemd/systemd/0001-tmpfiles-don-t-resolve-pathnames-when-traversing-rec.patch
create mode 100644 meta/recipes-core/systemd/systemd/0002-Make-tmpfiles-safe.patch
create mode 100644 meta/recipes-core/systemd/systemd/0024-journald-do-not-store-the-iovec-entry-for-process-co.patch
create mode 100644 meta/recipes-core/systemd/systemd/0025-journald-set-a-limit-on-the-number-of-fields-1k.patch
create mode 100644 meta/recipes-core/systemd/systemd/0026-journal-remote-set-a-limit-on-the-number-of-fields-i.patch
create mode 100644 meta/recipes-core/systemd/systemd/0027-journal-fix-out-of-bounds-read-CVE-2018-16866.patch
create mode 100644 meta/recipes-core/systemd/systemd/CVE-2019-6454.patch
create mode 100644 meta/recipes-core/systemd/systemd/sd-bus-if-we-receive-an-invalid-dbus-message-ignore-.patch
create mode 100644 meta/recipes-devtools/libtool/libtool/multilib.patch
create mode 100644 meta/recipes-extended/cpio/cpio-2.12/0001-Fix-segfault-with-append.patch
rename meta/recipes-extended/tzcode/{tzcode-native_2018f.bb => tzcode-native_2018i.bb} (70%)
rename meta/recipes-extended/tzdata/{tzdata_2018f.bb => tzdata_2018i.bb} (98%)
copy scripts/{pybootchartgui/pybootchartgui => lib/resulttool}/__init__.py (100%)
create mode 100755 scripts/lib/resulttool/manualexecution.py
create mode 100644 scripts/lib/resulttool/merge.py
create mode 100644 scripts/lib/resulttool/regression.py
create mode 100644 scripts/lib/resulttool/report.py
create mode 100644 scripts/lib/resulttool/resultutils.py
create mode 100644 scripts/lib/resulttool/store.py
create mode 100644 scripts/lib/resulttool/template/test_report_full_text.txt
create mode 100755 scripts/resulttool
hooks/post-receive
--
More information about the yocto-security
mailing list