[oe-commits] [meta-openembedded] branch master-next updated (7ad615b -> ebc7b9e)

[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 7ad615b  read-edid: Upgrade to 3.0.2
 discard be2444d  vsftpd: allow getdents64 in the seccomp sandbox
 discard 16e88d9  autofs: upgrade to 5.1.5
 discard 4795e7d  libxklavier: Fix keyboard layout bug for xfce4-settings
 discard 98457cd  libmtp: fix paths for packages
 discard 61a4a63  libcereal: Allow empty package
 discard 2239325  libdvbcsa: Add recipe
 discard 5a22c97  dvb-apps: linux dvb apps package support
 discard 1349128  postgresql: upgrade to 11.1
 discard c1921f7  phoronix-test-suite: upgrade to 8.2.0
 discard b4ef28b  libmtp: upgrade 1.1.5 -> 1.1.16 and rework
     new a1ee96c  phoronix-test-suite: upgrade to 8.2.0
     new 6f1d9e2  postgresql: upgrade to 11.1
     new 1b65ebd  dvb-apps: linux dvb apps package support
     new e4b175c  libdvbcsa: Add recipe
     new e23284f  libcereal: Allow empty package
     new 97055da  libxklavier: Fix keyboard layout bug for xfce4-settings
     new 35249c8  autofs: upgrade to 5.1.5
     new 4224a09  vsftpd: allow getdents64 in the seccomp sandbox
     new 7fd1474  read-edid: Upgrade to 3.0.2
     new 882d907  thin-provisioning tools: use sh on path for txt2man
     new 3e59433  libtinyxml2: update to 7.0.1
     new 4e81430  miniupnpd: Update to 2.1.20180706
     new ebc7b9e  poppler: Upgrade to 0.71.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   (7ad615b)
            \
             N -- N -- N   refs/heads/master-next (ebc7b9e)

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 13 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:
 ...d_2.0.20180203.bb => miniupnpd_2.1.20180706.bb} |   5 +-
 .../libmtp/libmtp-1.1.5/69-libmtp.rules            | 999 +++++++++++++++++++++
 .../libmtp/libmtp-1.1.5/glibc-2.20.patch           |  36 +
 .../libmtp/0001-Use-native-mtp-hotplug.patch       |  43 -
 .../recipes-connectivity/libmtp/libmtp_1.1.16.bb   |  47 -
 .../recipes-connectivity/libmtp/libmtp_1.1.5.bb    |  58 ++
 .../{libtinyxml2_6.2.0.bb => libtinyxml2_7.0.1.bb} |   2 +-
 .../{poppler_0.70.1.bb => poppler_0.71.0.bb}       |   4 +-
 .../files/use-sh-on-path.patch                     |  21 +
 .../thin-provisioning-tools_0.7.6.bb               |   1 +
 10 files changed, 1120 insertions(+), 96 deletions(-)
 rename meta-networking/recipes-connectivity/miniupnpd/{miniupnpd_2.0.20180203.bb => miniupnpd_2.1.20180706.bb} (91%)
 create mode 100644 meta-oe/recipes-connectivity/libmtp/libmtp-1.1.5/69-libmtp.rules
 create mode 100644 meta-oe/recipes-connectivity/libmtp/libmtp-1.1.5/glibc-2.20.patch
 delete mode 100644 meta-oe/recipes-connectivity/libmtp/libmtp/0001-Use-native-mtp-hotplug.patch
 delete mode 100644 meta-oe/recipes-connectivity/libmtp/libmtp_1.1.16.bb
 create mode 100644 meta-oe/recipes-connectivity/libmtp/libmtp_1.1.5.bb
 rename meta-oe/recipes-support/libtinyxml2/{libtinyxml2_6.2.0.bb => libtinyxml2_7.0.1.bb} (88%)
 rename meta-oe/recipes-support/poppler/{poppler_0.70.1.bb => poppler_0.71.0.bb} (94%)
 create mode 100644 meta-oe/recipes-support/thin-provisioning-tools/files/use-sh-on-path.patch

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