[oe-commits] [meta-openembedded] branch master-next updated (00166ab -> 0b5dbf3)

[git at git.openembedded.org]

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

khem pushed a change to branch master-next
in repository meta-openembedded.

 discard 00166ab  krb5: fix CVE-2018-20217
 discard 95874ba  xmlrpc-c: inherit binconfig
 discard 7a307c1  krb5: Add PACKAGECONFIG pkinit
 discard 5169ec2  openhpi: Add PACKAGECONFIG snmp-bc
 discard 3df6adc  freeradius: Add PACKAGECONFIG openssl/rlm-eap-fast/rlm-eap-pwd
 discard 4ec7958  lvm2/libdevmapper: 2.03.01 -> 2.03.02
 discard 6260111  vim: remove xfce vim bbappend
 discard 63d7536  spdlog: add first recipe
 discard c4ddc14  lmsensors: read cpu information fail on ppc
 discard 68f8022  firewalld: add new recipe
     new 6ded201  lmsensors: read cpu information fail on ppc
     new 1ccc5f9  spdlog: add first recipe
     new 41f3f81  vim: remove xfce vim bbappend
     new 50248bf  freeradius: Add PACKAGECONFIG openssl/rlm-eap-fast/rlm-eap-pwd
     new 90892eb  openhpi: Add PACKAGECONFIG snmp-bc
     new 24d7a77  krb5: Add PACKAGECONFIG pkinit
     new e860611  xmlrpc-c: inherit binconfig
     new ef6be43  krb5: fix CVE-2018-20217
     new 0b5dbf3  Revert "meta-oe: fixup LAYERDEPENDS to include meta-python"

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   (00166ab)
            \
             N -- N -- N   refs/heads/master-next (0b5dbf3)

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 9 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:
 ...g-in-a-separate-directory-outside-the-sou.patch | 77 --------------------
 .../firewalld/files/firewalld.init                 | 48 -------------
 .../firewalld/firewalld_0.6.3.bb                   | 83 ----------------------
 meta-oe/conf/layer.conf                            |  1 -
 ...cntl.h-for-O_-defines-and-fcntl-signature.patch | 30 ++++++++
 .../lvm2/files/0005-do-not-build-manual.patch      | 13 ++--
 ...tart-lvm2-monitor.service-after-tmp.mount.patch | 13 ++--
 ...evmapper_2.03.02.bb => libdevmapper_2.03.01.bb} |  0
 meta-oe/recipes-support/lvm2/lvm2.inc              |  7 +-
 .../0001-explicitly-do-not-install-libdm.patch     | 32 +++------
 ...toring-service-shouldn-t-refer-to-lvmetad.patch | 31 ++++++++
 .../lvm2/{lvm2_2.03.02.bb => lvm2_2.03.01.bb}      |  3 +-
 12 files changed, 85 insertions(+), 253 deletions(-)
 delete mode 100644 meta-networking/recipes-connectivity/firewalld/files/0001-fix-building-in-a-separate-directory-outside-the-sou.patch
 delete mode 100644 meta-networking/recipes-connectivity/firewalld/files/firewalld.init
 delete mode 100644 meta-networking/recipes-connectivity/firewalld/firewalld_0.6.3.bb
 create mode 100644 meta-oe/recipes-support/lvm2/files/0003-include-fcntl.h-for-O_-defines-and-fcntl-signature.patch
 rename meta-oe/recipes-support/lvm2/{libdevmapper_2.03.02.bb => libdevmapper_2.03.01.bb} (100%)
 create mode 100644 meta-oe/recipes-support/lvm2/lvm2/0001-lvm2-monitoring-service-shouldn-t-refer-to-lvmetad.patch
 rename meta-oe/recipes-support/lvm2/{lvm2_2.03.02.bb => lvm2_2.03.01.bb} (92%)

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