[oe-commits] [meta-openembedded] branch master-next updated (51d714c -> 6c52082)

[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 51d714c  utilities: Fix build failure with -Werror=maybe-uninitialized
 discard 03ea53d  gvfs: 1.39.92 -> 1.40.0
 discard dcfae29  libgtop: 2.38.0 -> 2.40.0
 discard 56cc86c  cxxtest: update to 4.4
 discard f910abb  cppunit: update to 1.14.0
 discard c67f05d  libuv: update to 1.27.0
 discard b8159ea  libev: update to 4.25
 discard 8b5f1fd  igmpproxy: update to 0.2.1
 discard 160b366  packagegroup-tools-bluetooth: fix rdepends
 discard 9deda3b  blueman: update to 2.0.8
     new 521a3b0  packagegroup-tools-bluetooth: fix rdepends
     new 5097915  igmpproxy: update to 0.2.1
     new f38ae87  libev: update to 4.25
     new bac3f1d  libuv: update to 1.27.0
     new f216dad  cppunit: update to 1.14.0
     new 93ddf99  cxxtest: update to 4.4
     new ad3e07a  libgtop: 2.38.0 -> 2.40.0
     new 440edf5  gvfs: 1.39.92 -> 1.40.0
     new 4ce1fb5  utilities: Fix build failure with -Werror=maybe-uninitialized
     new 6cb4e90  python3-pillow: add 5.4.1
     new f0c1ee7  nodejs: fix target ldflags using
     new f67f786  nbench-byte: update SRC_URI
     new 3a9b5f4  log4cplus: update to 2.0.3
     new 6c52082  blueman: update to 2.0.8

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   (51d714c)
            \
             N -- N -- N   refs/heads/master-next (6c52082)

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 14 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:
 .../blueman/0001-Fix-building-on-musl.patch        | 56 ++++++++++++++++++++
 .../recipes-connectivity/blueman/blueman_2.0.8.bb  |  1 +
 .../nbench-byte/nbench-byte_2.2.3.bb               |  2 +-
 .../{log4cplus_2.0.2.bb => log4cplus_2.0.3.bb}     |  4 +-
 .../nodejs/nodejs/0006-Use-target-ldflags.patch    | 24 +++++++++
 meta-oe/recipes-devtools/nodejs/nodejs_10.15.1.bb  |  1 +
 .../0001-explicitly-set-compile-options.patch      | 39 ++++++++++++++
 .../0001-support-cross-compiling.patch             | 61 ++++++++++++++++++++++
 .../python/python3-pillow_5.4.1.bb                 | 28 ++++++++++
 9 files changed, 213 insertions(+), 3 deletions(-)
 create mode 100644 meta-networking/recipes-connectivity/blueman/blueman/0001-Fix-building-on-musl.patch
 rename meta-oe/recipes-devtools/log4cplus/{log4cplus_2.0.2.bb => log4cplus_2.0.3.bb} (81%)
 create mode 100644 meta-oe/recipes-devtools/nodejs/nodejs/0006-Use-target-ldflags.patch
 create mode 100644 meta-python/recipes-devtools/python/python3-pillow/0001-explicitly-set-compile-options.patch
 create mode 100644 meta-python/recipes-devtools/python/python3-pillow/0001-support-cross-compiling.patch
 create mode 100644 meta-python/recipes-devtools/python/python3-pillow_5.4.1.bb

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