[oe-commits] [openembedded-core] branch master-next updated (be234fd -> cc5de02)

[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 be234fd  dbus: Fix dependencies
 discard 6dfab8c  valgrind: fix call/cachegrind ptests
 discard f42a398  valgrind: adjust test filters and expected output
 discard f561c6d  valgrind: update the ptest subdirs list
 discard 0f869c7  valgrind: do not strip the package or ptests
 discard 91dfc1b  valgrind: fix vg_regtest return code
 discard 8c1dd00  perf: make sure that the tools/include/uapi/asm-generic directory exists
 discard 2cbdf13  gdb: Upgrade from 8.2.1 to 8.3
 discard 6f0cd5e  ptest: Add RDEPENDS frpm PN-ptest to PN package
     new 6653e53  perf: make sure that the tools/include/uapi/asm-generic directory exists
     new 485f39a  valgrind: fix vg_regtest return code
     new 1d4956d  valgrind: Include debugging symbols in ptests
     new 346bce4  valgrind: update the ptest subdirs list
     new b7a7d2b  valgrind: adjust test filters and expected output
     new dd41bd1  valgrind: fix call/cachegrind ptests
     new 8e47574  dbus-test: Improve ptest dependencies dependencies
     new 8a68af6  ptest: Add RDEPENDS frpm PN-ptest to PN package
     new cc5de02  glib-2.0: fix last failing ptest

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

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:
 meta/conf/distro/include/tcmode-default.inc        |  2 +-
 .../glib-2.0/glib-2.0/fix-nl-abaltmon.patch        | 44 +++++++++-
 .../gdb/{gdb-8.3.inc => gdb-8.2.1.inc}             | 12 ++-
 meta/recipes-devtools/gdb/gdb-cross-canadian.inc   |  1 +
 ...canadian_8.3.bb => gdb-cross-canadian_8.2.1.bb} |  0
 .../gdb/{gdb-cross_8.3.bb => gdb-cross_8.2.1.bb}   |  0
 .../0001-Fix-build-with-latest-GCC-9.0-tree.patch  | 50 +++++++++++
 ...Define-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch | 23 ++---
 .../0008-Use-exorted-definitions-of-SIGRTMIN.patch | 16 ++--
 ...-AArch64-Fix-the-gdb-build-with-musl-libc.patch | 52 ++++++++++++
 meta/recipes-devtools/gdb/gdb/CVE-2017-9778.patch  | 99 ++++++++++++++++++++++
 ...dling.patch => gdbserver-ctrl-c-handling.patch} |  0
 .../gdb/{gdb_8.3.bb => gdb_8.2.1.bb}               |  0
 meta/recipes-devtools/valgrind/valgrind_3.15.0.bb  |  7 +-
 14 files changed, 278 insertions(+), 28 deletions(-)
 rename meta/recipes-devtools/gdb/{gdb-8.3.inc => gdb-8.2.1.inc} (73%)
 rename meta/recipes-devtools/gdb/{gdb-cross-canadian_8.3.bb => gdb-cross-canadian_8.2.1.bb} (100%)
 rename meta/recipes-devtools/gdb/{gdb-cross_8.3.bb => gdb-cross_8.2.1.bb} (100%)
 create mode 100644 meta/recipes-devtools/gdb/gdb/0001-Fix-build-with-latest-GCC-9.0-tree.patch
 create mode 100644 meta/recipes-devtools/gdb/gdb/0012-AArch64-Fix-the-gdb-build-with-musl-libc.patch
 create mode 100644 meta/recipes-devtools/gdb/gdb/CVE-2017-9778.patch
 rename meta/recipes-devtools/gdb/gdb/{0001-gdbserver-ctrl-c-handling.patch => gdbserver-ctrl-c-handling.patch} (100%)
 rename meta/recipes-devtools/gdb/{gdb_8.3.bb => gdb_8.2.1.bb} (100%)

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