[yocto-security] [OE-core CVE] branch warrior-next updated. uninative-2.4-109-ga2a0719
cve-notice at lists.openembedded.org
cve-notice at lists.openembedded.org
Wed Apr 3 06:51:14 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, warrior-next has been updated
discards e3cc41059f44cb70d81fa51aa4de87d172ebc2b3 (commit)
discards 76557bb95d4dbcfa1a06de62072697b252d64779 (commit)
discards 3fc93335fdb61e636e52ad5406e7f6ddedf3e164 (commit)
discards c27ba7dcf9c4555f01156e24ce3ab776d6dd4269 (commit)
discards 33f67e26e2a1977ffa07975e796b8207948e5717 (commit)
discards 5bb36ffd90e3b0ac3e138e4658ce419d08d97008 (commit)
discards 00cc1baebddaf0f2d73ca2c00da80df54a284b55 (commit)
discards 41dab7e5d10049885df1fd9324b36d90d428c18d (commit)
discards badbeeafd1e3838c952f82fd8db7fc0e4356032c (commit)
discards 0ef43a1c2cb14274214b3ef458bee6e12e13946c (commit)
discards 486473a82d298b4285abbeec431555eb96f0aa01 (commit)
discards e57fd2d4cc575a7329200c4842819de590e10cff (commit)
discards e95f00c5eba2dc9cf29e61d06df6204c347e9ef8 (commit)
discards 1f91e5aa7a52ee33842cc661804d63a37149a1a6 (commit)
discards 801f493d816fdf3b0d6266e56f0f2087b64d421d (commit)
via a2a0719adc428c787ee8e7748ed3465133e0e98e (commit)
via 88d5ec1f60d9a64102d63b4128b2e43ab4f38d4c (commit)
via b85f78fa46ca860df8a43354417f7125cb9e4a83 (commit)
via 2f3adb21cc5067458a12964d0bde235966a20a60 (commit)
via 4d1339af88543d85930139dbcb87a669f285ea66 (commit)
via 6eadd9f5ac2887311ae9ed133b389ae4d64a8181 (commit)
via 1756f2354745ee709886683422887efed4e10dba (commit)
via 5302047be6bcdae85a43f9b09778a91dcd03b191 (commit)
via a85a8febf04d763dd5b3d20487d528731105afab (commit)
via 50d3ec1ac994fb5968d8edf82823a7e3d1d67d21 (commit)
via 53724281eb486847bc3be824aa4513a8688ec296 (commit)
via 0ee8d4d58b2d755615ae4f7c3783b72d5aabaa63 (commit)
via 979e3f4ac1e12228d368315169a32d5ab0209e91 (commit)
via fe6d020dd609fbde7e4413cef9bbdd4e3962c82c (commit)
via 2af4d6eb2526d60b26bc5128068541ff3350fb58 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (e3cc41059f44cb70d81fa51aa4de87d172ebc2b3)
\
N -- N -- N (a2a0719adc428c787ee8e7748ed3465133e0e98e)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
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 a2a0719adc428c787ee8e7748ed3465133e0e98e
Author: Nathan Rossi <nathan at nathanrossi.com>
Date: Wed Apr 3 05:37:02 2019 +0000
devtool: standard: Handle exporting generated config fragments
The cml1 and ccmake bbclasses generate configuration fragment source
files that must be exported from the WORKDIR as a source file to be
preserved across builds. This change adds detection of the current
recipes inherited classes and for cml1 and ccmake classes checks for the
specific generated configuration fragment files. These files are then
exported by devtool and included as SRC_URI files from within the target
layer.
Signed-off-by: Nathan Rossi <nathan at nathanrossi.com>
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit 88d5ec1f60d9a64102d63b4128b2e43ab4f38d4c
Author: Nathan Rossi <nathan at nathanrossi.com>
Date: Wed Apr 3 05:37:02 2019 +0000
ccmake.bbclass: Create a cml1 style class for the CMake curses UI
The ccmake bbclass implements two tasks. The first task 'ccmake'
preserves the configured state of CMakeCache.txt (generated from the
configure task) and invokes the 'ccmake' program within a oe_terminal
execution. The user can then review, select and modify configuration
options and once satisfied with the configuration exit ccmake. Once
ccmake has exited the build can be run and the updated configuration
should be reflected in the output build.
The ccmake bbclass has a second task 'ccmake_diffconfig' to compute the
differences in configuration which was modified by ccmake. Since there
are many ways to persist the configuration changes within recipes and
layer configuration, the differences are emitted as a bitbake recipe
fragment (configuration.inc) using EXTRA_OECMAKE as well as a CMake
script file which can be used as a input to cmake via the '-C' argument.
Both files are generated in the WORKDIR of the build and the paths to
the files are written as output from the build. It is then up to the
user to take this configuration and apply it to the desired location.
Signed-off-by: Nathan Rossi <nathan at nathanrossi.com>
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
commit b85f78fa46ca860df8a43354417f7125cb9e4a83
Author: Nathan Rossi <nathan at nathanrossi.com>
Date: Wed Apr 3 05:37:02 2019 +0000
cmake-native: Enable ccmake by default and depend on ncurses
Enable the building of the curses based ui for cmake. This depends on
ncurses.
Signed-off-by: Nathan Rossi <nathan at nathanrossi.com>
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
-----------------------------------------------------------------------
Summary of changes:
meta/classes/ccmake.bbclass | 6 +--
.../asciidoc/asciidoc/auto-catalogs.patch | 53 ----------------------
meta/recipes-extended/asciidoc/asciidoc_8.6.9.bb | 9 +---
scripts/lib/wic/engine.py | 2 +-
4 files changed, 6 insertions(+), 64 deletions(-)
delete mode 100644 meta/recipes-extended/asciidoc/asciidoc/auto-catalogs.patch
hooks/post-receive
--
More information about the yocto-security
mailing list