[oe-commits] [meta-openembedded] branch master-next updated (badab30 -> c218a0a)

[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 badab30  twm: upgrade to 1.0.10
 discard 341787d  leveldb: restrict building for mips64
 discard 4475a37  Replaced cryptograpy by crypt.
 discard 9bf9ca0  dvb-apps: Disable static libraries
 discard 5d5edf2  bdwgc: upgrade 7.6.10 -> 7.6.12
 discard f1b7288  libc-bench: Upgrade to use new location for SRC_URI
 discard bfceb24  firewalld: add new recipe
 discard 6829efb  octave: Exclude from world builds
 discard 832f42e  mariadb: Upgrade to 5.5.63
     new 5242f52  octave: Exclude from world builds
     new ca0abec  firewalld: add new recipe
     new 4b225fc  libc-bench: Upgrade to use new location for SRC_URI
     new 1a289f7  bdwgc: upgrade 7.6.10 -> 7.6.12
     new 35bc2ca  dvb-apps: Disable static libraries
     new befa59e  Replaced cryptograpy by crypt.
     new ba75d0e  leveldb: restrict building for mips64
     new 1524b15  twm: upgrade to 1.0.10
     new b9dc7a0  mariadb: Upgrade to 10.3.13
     new c218a0a  libdbd-mysql-perl: fix do_compile failure

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   (badab30)
            \
             N -- N -- N   refs/heads/master-next (c218a0a)

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 10 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:
 ...-native_5.5.63.bb => mariadb-native_10.3.13.bb} |   1 +
 meta-oe/recipes-dbs/mysql/mariadb.inc              |  29 ++--
 .../mariadb/0001-disable-ucontext-on-musl.patch    |   8 +-
 .../mysql/mariadb/change-cc-to-cc-version.patch    |  26 ----
 .../mariadb/configure.cmake-fix-valgrind.patch     |  27 ++--
 .../mysql/mariadb/fix-a-building-failure.patch     |  16 ++-
 .../mysql/mariadb/fix-cmake-module-path.patch      |  29 ----
 .../mysql/mariadb/fix-mysqlclient-r-version.patch  | 160 ---------------------
 .../mysql/mariadb/remove-bad-path.patch            |  18 ---
 ...CMakeLists.txt-fix-gen_lex_hash-not-found.patch |  65 +++++++++
 ...es-CMakeLists.txt-fix-do_populate_sysroot.patch |  34 +++++
 .../{mariadb_5.5.63.bb => mariadb_10.3.13.bb}      |   2 +-
 .../0001-Use-API-function-for-reconnect.patch      |  53 +++++++
 .../perl/libdbd-mysql-perl_4.043.bb                |   1 +
 14 files changed, 199 insertions(+), 270 deletions(-)
 rename meta-oe/recipes-dbs/mysql/{mariadb-native_5.5.63.bb => mariadb-native_10.3.13.bb} (88%)
 delete mode 100644 meta-oe/recipes-dbs/mysql/mariadb/change-cc-to-cc-version.patch
 delete mode 100644 meta-oe/recipes-dbs/mysql/mariadb/fix-cmake-module-path.patch
 delete mode 100644 meta-oe/recipes-dbs/mysql/mariadb/fix-mysqlclient-r-version.patch
 delete mode 100644 meta-oe/recipes-dbs/mysql/mariadb/remove-bad-path.patch
 create mode 100644 meta-oe/recipes-dbs/mysql/mariadb/sql-CMakeLists.txt-fix-gen_lex_hash-not-found.patch
 create mode 100644 meta-oe/recipes-dbs/mysql/mariadb/support-files-CMakeLists.txt-fix-do_populate_sysroot.patch
 rename meta-oe/recipes-dbs/mysql/{mariadb_5.5.63.bb => mariadb_10.3.13.bb} (88%)
 create mode 100644 meta-oe/recipes-devtools/perl/libdbd-mysql-perl/0001-Use-API-function-for-reconnect.patch

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