[oe-commits] [openembedded-core] branch master-next updated (81e7e1a -> 5c199ad)

[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 81e7e1a  libva-utils: upgrade 2.4.0 -> 2.5.0
 discard 7a4ba51  libva: upgrade 2.4.1 -> 2.5.0
 discard 1070d8f  openssl: fix multilib files conflict
 discard d2dff7b  xmlcatalog: hold libxml2-native dependency
 discard 23b3970  libxslt: fix CVE-2019-13117 CVE-2019-13118
 discard 106f42d  gnupg: upgrade 2.2.16 -> 2.2.17
 discard e216ce2  binutils: fix CVE-2019-12972 CVE-2019-9071
 discard 1a155ab  gnome-themes-standard: remove
 discard 11a21af  gtk+: remove GTK+ 2
 discard 7c550a0  u-boot: Provide tasks to generate default U-Boot environment(s) images
 discard 16138bd  package: Force rebuild for testing
     new 6c42e08  binutils: fix CVE-2019-12972 CVE-2019-9071
     new 9a43a5b  gnupg: upgrade 2.2.16 -> 2.2.17
     new 8e71181  libxslt: fix CVE-2019-13117 CVE-2019-13118
     new 91f6556  xmlcatalog: hold libxml2-native dependency
     new 76c530f  openssl: fix multilib files conflict
     new 28c9260  libva: upgrade 2.4.1 -> 2.5.0
     new 5c199ad  libva-utils: upgrade 2.4.0 -> 2.5.0

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   (81e7e1a)
            \
             N -- N -- N   refs/heads/master-next (5c199ad)

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/package.bbclass                       |   3 -
 meta/recipes-bsp/u-boot/u-boot.inc                 |  41 --------
 .../gnome/gnome-themes-standard_3.22.3.bb          |  46 +++++++++
 meta/recipes-gnome/gtk+/gtk+.inc                   | 107 +++++++++++++++++++++
 ...ok-into-HOME-when-looking-for-gtk-modules.patch |  29 ++++++
 meta/recipes-gnome/gtk+/gtk+/doc-fixes.patch       |  22 +++++
 .../hardcoded_libtool.patch}                       |  37 +++----
 .../gtk+/gtk+/strict-prototypes.patch              |  24 +++++
 meta/recipes-gnome/gtk+/gtk+/toggle-font.diff      | 102 ++++++++++++++++++++
 meta/recipes-gnome/gtk+/gtk+/xsettings.patch       |  20 ++++
 meta/recipes-gnome/gtk+/gtk+_2.24.32.bb            |  35 +++++++
 11 files changed, 398 insertions(+), 68 deletions(-)
 create mode 100644 meta/recipes-gnome/gnome/gnome-themes-standard_3.22.3.bb
 create mode 100644 meta/recipes-gnome/gtk+/gtk+.inc
 create mode 100644 meta/recipes-gnome/gtk+/gtk+/0001-Do-not-look-into-HOME-when-looking-for-gtk-modules.patch
 create mode 100644 meta/recipes-gnome/gtk+/gtk+/doc-fixes.patch
 copy meta/recipes-gnome/gtk+/{gtk+3/0001-Hardcoded-libtool.patch => gtk+/hardcoded_libtool.patch} (55%)
 create mode 100644 meta/recipes-gnome/gtk+/gtk+/strict-prototypes.patch
 create mode 100644 meta/recipes-gnome/gtk+/gtk+/toggle-font.diff
 create mode 100644 meta/recipes-gnome/gtk+/gtk+/xsettings.patch
 create mode 100644 meta/recipes-gnome/gtk+/gtk+_2.24.32.bb

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