[oe-commits] [openembedded-core] branch master updated (67b1941 -> ca73740)

[git at git.openembedded.org]

This is an automated email from the git hooks/post-receive script.

rpurdie pushed a change to branch master
in repository openembedded-core.

    from 67b1941  cmake: Avoid passing empty prefix to os.path.relpath
     new cdd6f41  vim: Update to 8.1.1518 to fix CVE-2019-12735
     new 9bc68bc  util-linux: upgrade to 2.33.2
     new 8ed0cf0  multilib: add override for image recipe
     new d4ad8d9  qemu: fix qemu ptest cannot work
     new c6b49cb  kernel-fitimage: uboot-sign: Check UBOOT_DTB_BINARY before adding deps
     new ca73740  bluez: fix test case failures with GCC 9

The 6 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/kernel-fitimage.bbclass               |   2 +-
 meta/classes/multilib.bbclass                      |   2 +
 meta/classes/uboot-sign.bbclass                    |   2 +-
 meta/recipes-connectivity/bluez5/bluez5.inc        |   1 +
 .../bluez5/bluez5/gcc9-fixes.patch                 | 301 +++++++++++++++++++++
 meta/recipes-core/util-linux/util-linux.inc        |  18 +-
 .../{util-linux_2.32.1.bb => util-linux_2.33.2.bb} |   4 +-
 meta/recipes-devtools/qemu/qemu.inc                |   7 +-
 .../{vim-tiny_8.1.1240.bb => vim-tiny_8.1.1518.bb} |   0
 meta/recipes-support/vim/vim.inc                   |   2 +-
 .../vim/{vim_8.1.1240.bb => vim_8.1.1518.bb}       |   0
 11 files changed, 321 insertions(+), 18 deletions(-)
 create mode 100644 meta/recipes-connectivity/bluez5/bluez5/gcc9-fixes.patch
 rename meta/recipes-core/util-linux/{util-linux_2.32.1.bb => util-linux_2.33.2.bb} (72%)
 rename meta/recipes-support/vim/{vim-tiny_8.1.1240.bb => vim-tiny_8.1.1518.bb} (100%)
 rename meta/recipes-support/vim/{vim_8.1.1240.bb => vim_8.1.1518.bb} (100%)

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