[oe-commits] [openembedded-core] branch master-next updated (c2261d2 -> 4f68ae7)

[git at git.openembedded.org]

This is an automated email from the git hooks/post-receive script.

rpurdie pushed a change to branch master-next
in repository openembedded-core.

 discard c2261d2  valgrind: Dont strip off -mcpu
 discard a4d5ed5  arm-tunes: Remove -march option if mcpu is already added
 discard 41930b9  rootfs-postcommands: call preset-all for read-only-rootfs
 discard 624ad42  systemd-systemctl-native: simplify and support preset-all
 discard e859ec0  systemd: create preset files instead of installing in image
 discard b1c870e  systemd-conf: simplify creation of machine-specific configuration
 discard 22fb8c0  systemd: do not create machine-id
     new ac83d22  arm-tunes: Remove -march option if mcpu is already added
     new a8ab788  valgrind: Dont strip off -mcpu
     new 1264eca  systemd: do not create machine-id
     new 843d952  systemd: Update recent CVE patches
     new edc0c44  oeqa/manual: Add manual runtime 'compiance' testcases to json
     new 20eb437  oeqa/manual/sdk.json: Updated toolchain tarball to core-image-sato
     new 4f68ae7  base.bbclass: Use bb.event.ParseStarted for HOSTTOOLS

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (c2261d2)
            \
             N -- N -- N   refs/heads/master-next (4f68ae7)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 7 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 meta/classes/base.bbclass                          |  11 +-
 meta/classes/rootfs-postcommands.bbclass           |   2 -
 meta/classes/systemd.bbclass                       |  33 ++---
 meta/lib/oeqa/manual/compliance-test.json          | 142 +++++++++++++++++++++
 meta/lib/oeqa/manual/sdk.json                      |  14 +-
 meta/recipes-core/systemd/systemd-conf.bb          |  48 +++----
 .../systemd/systemd-systemctl/systemctl            |  36 +++++-
 ...-not-store-the-iovec-entry-for-process-co.patch |   6 +-
 ...ld-set-a-limit-on-the-number-of-fields-1k.patch |  56 --------
 ...rnald-set-a-limit-on-the-number-of-fields.patch | 139 ++++++++++++++++++++
 ...nal-fix-out-of-bounds-read-CVE-2018-16866.patch |  49 +++++++
 ...ote-set-a-limit-on-the-number-of-fields-i.patch |  84 ------------
 .../0027-journal-fix-syslog_parse_identifier.patch |  77 -----------
 ...not-remove-multiple-spaces-after-identifi.patch |  84 ------------
 meta/recipes-core/systemd/systemd_239.bb           |  22 ++--
 15 files changed, 432 insertions(+), 371 deletions(-)
 create mode 100644 meta/lib/oeqa/manual/compliance-test.json
 delete 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/0025-journald-set-a-limit-on-the-number-of-fields.patch
 create mode 100644 meta/recipes-core/systemd/systemd/0026-journal-fix-out-of-bounds-read-CVE-2018-16866.patch
 delete mode 100644 meta/recipes-core/systemd/systemd/0026-journal-remote-set-a-limit-on-the-number-of-fields-i.patch
 delete mode 100644 meta/recipes-core/systemd/systemd/0027-journal-fix-syslog_parse_identifier.patch
 delete mode 100644 meta/recipes-core/systemd/systemd/0028-journal-do-not-remove-multiple-spaces-after-identifi.patch

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.