[oe-commits] [openembedded-core] branch master-next updated (e1a9ca4 -> 0baeba5)

[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 e1a9ca4  webkitgtk: Stop disabling gold on aarch64 and mips
 discard a91ef74  glib-networking: Support building with USE_NLS=no
 discard 25b8ac1  Change ftp:// URIs to http(s)://
 discard cb70913  llvm: Update to 8.0.1
 discard 21a99a4  libedit: Move from meta-oe
 discard f87038d  python3: split out the Windows distutils installer stubs
 discard 4bb2115  python3: support recommends in manifest
 discard 62f7dc3  python3: remove empty python3-distutils-staticdev
 discard c6c9246  sstatesig: Updates to match bitbake siggen changes
 discard e106b3d  sstate/sstatesig: Update to new form of BB_HASHCHECK_FUNCTION
 discard 853e0eb  sstatesig: Update to handle BB_HASHSERVE
 discard 3f375ad  sstatesig: Adpat to recent bitbake hash equiv runqueue changes
 discard f4ba5c9  sstatesig: Add debug for incorrect hash server settings
 discard 3348370  sstatesig: Move unihash siggen code to bitbake
 discard 29fa102  classes/lib: Remove bb.build.FuncFailed
     new 655e676  python3: remove empty python3-distutils-staticdev
     new 722f9e6  python3: support recommends in manifest
     new b405eee  python3: split out the Windows distutils installer stubs
     new 302281a  libedit: Move from meta-oe
     new 0d7a8d9  llvm: Update to 8.0.1
     new c48471f  Change ftp:// URIs to http(s)://
     new d63ab3e  glib-networking: Support building with USE_NLS=no
     new 2e051b0  webkitgtk: Stop disabling gold on aarch64 and mips
     new 650d598  sanity.conf: Require bitbake 1.43.1
     new 69ad817  classes/lib: Remove bb.build.FuncFailed
     new d24a554  sstatesig: Move unihash siggen code to bitbake
     new 95795d6  sstatesig: Add debug for incorrect hash server settings
     new 5f8c903  sstatesig: Adpat to recent bitbake hash equiv runqueue changes
     new 9003cd6  sstatesig: Update to handle BB_HASHSERVE
     new 70ea2e6  sstate/sstatesig: Update to new form of BB_HASHCHECK_FUNCTION
     new 79a35cc  sstatesig: Updates to match bitbake siggen changes
     new 5148b10  linux-yocto/4.19: update to v4.19.61
     new 720e6aa  linux-yocto-dev: bump to 5.3-rcX
     new 5a88c8f  python3-git: update to 2.1.13
     new 15c65ca  runqemu: fix get portlock fail for multi users
     new a637322  ptest-runner: update from 2.3.1 to 2.3.2
     new 7a5ec4e  grub/libmpc/gdb: Use GNU_MIRROR in more recipes
     new 43b4893  insane: check if the recipe incorrectly uses DEPENDS_${PN}
     new 0baeba5  weston: change to use meson build system

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   (e1a9ca4)
            \
             N -- N -- N   refs/heads/master-next (0baeba5)

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 24 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/insane.bbclass                        |   5 +
 meta/conf/bitbake.conf                             |   2 +-
 meta/conf/sanity.conf                              |   2 +-
 meta/recipes-bsp/grub/grub2.inc                    |   2 +-
 meta/recipes-devtools/gdb/gdb-8.3.inc              |   2 +-
 ...python3-git_2.1.12.bb => python3-git_2.1.13.bb} |   4 +-
 .../wayland/weston/0001-make-error-portable.patch  |  34 ++--
 ...ch-Provide-a-default-version-that-doesn-t.patch |  93 +++++----
 meta/recipes-graphics/wayland/weston_6.0.1.bb      |  49 ++---
 meta/recipes-kernel/linux/linux-yocto-dev.bb       |   2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.19.bb   |   6 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.19.bb |   8 +-
 meta/recipes-kernel/linux/linux-yocto_4.19.bb      |  20 +-
 meta/recipes-support/libmpc/libmpc_1.1.0.bb        |   2 +-
 ...01-utils-Ensure-stdout-stderr-are-flushed.patch |  45 -----
 .../0002-use-process-groups-when-spawning.patch    |  35 ----
 ...03-utils-Ensure-pipes-are-read-after-exit.patch |  76 --------
 ...-utils-ensure-child-can-be-session-leader.patch | 212 ---------------------
 ...ptest-runner_2.3.1.bb => ptest-runner_2.3.2.bb} |   8 +-
 scripts/runqemu                                    |   9 +-
 20 files changed, 137 insertions(+), 479 deletions(-)
 rename meta/recipes-devtools/python/{python3-git_2.1.12.bb => python3-git_2.1.13.bb} (88%)
 delete mode 100644 meta/recipes-support/ptest-runner/ptest-runner/0001-utils-Ensure-stdout-stderr-are-flushed.patch
 delete mode 100644 meta/recipes-support/ptest-runner/ptest-runner/0002-use-process-groups-when-spawning.patch
 delete mode 100644 meta/recipes-support/ptest-runner/ptest-runner/0003-utils-Ensure-pipes-are-read-after-exit.patch
 delete mode 100644 meta/recipes-support/ptest-runner/ptest-runner/0004-utils-ensure-child-can-be-session-leader.patch
 rename meta/recipes-support/ptest-runner/{ptest-runner_2.3.1.bb => ptest-runner_2.3.2.bb} (69%)

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