[oe-commits] [meta-openembedded] branch master-next updated (68e05a0 -> 8047cd6)

[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 68e05a0  mozjs: Upgrade to 60.9.0
 discard 9f13c8a  python3-pytoml,python3-jsmin: Add recipes
 discard 7574402  meta-python: update recipes to use python3 classes
 discard ecedc8f  meta-python: rename python2 recipes to python3 eqiuvalent
 discard 6ee8f3f  meta-python: remove python2 recipes from layer
 discard dd6f601  cherokee: Use python3 native during build
 discard fab0841  meta-oe: Remove using python2
     new e066e7f  meta-oe: Remove using python2
     new ba6758c  cherokee: Use python3 native during build
     new 25e98b7  meta-python: remove python2 recipes from layer
     new d2c39d1  meta-python: rename python2 recipes to python3 eqiuvalent
     new 238b791  meta-python: update recipes to use python3 classes
     new 4e884c9  python3-pytoml,python3-jsmin: Add recipes
     new bb80512  autoconf-2.13-native: initial add
     new 2233aa0  mozjs: upgrade 60.5.2 -> 60.9.0 and rework
     new 9a5d0d7  fatcat: Add recipe
     new 43b61b2  drbd-utils: fix flex-native tool dependency
     new a6991d0  unbound: Use HOST_SYS instead of TARGET_PREFIX for libtool
     new 5f42f4f  dovecot: fix gettext tool dependency
     new 8047cd6  ndisc6: fix coreutils-native tool dependency

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   (68e05a0)
            \
             N -- N -- N   refs/heads/master-next (8047cd6)

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:
 ...unistd.h-not-argp.h-for-all-POSIX-systems.patch |   37 +
 .../recipes-utils/fatcat/fatcat_1.1.0.bb           |   18 +
 .../recipes-support/dovecot/dovecot_2.2.36.4.bb    |    2 +-
 .../recipes-support/drbd/drbd-utils_9.11.0.bb      |    2 +
 .../recipes-support/ndisc6/ndisc6_git.bb           |    2 +
 .../recipes-support/unbound/unbound_1.9.4.bb       |    2 +-
 .../autoconf-2.13/autoconf-2.13-native_2.13.bb     |   67 +
 ...onfig.guess-config.sub-install-to-destdir.patch |   67 +
 .../0001-do-not-create-python-environment.patch    |   15 +-
 ...se-autoconf-2.13-to-refresh-old.configure.patch |   42 -
 ...010-fix-cross-compilation-on-i586-targets.patch |   20 +-
 .../mozjs/mozjs/old-configure.patch                | 9982 --------------------
 meta-oe/recipes-extended/mozjs/mozjs_60.9.0.bb     |   64 +-
 13 files changed, 235 insertions(+), 10085 deletions(-)
 create mode 100644 meta-filesystems/recipes-utils/fatcat/fatcat/0001-Use-unistd.h-not-argp.h-for-all-POSIX-systems.patch
 create mode 100644 meta-filesystems/recipes-utils/fatcat/fatcat_1.1.0.bb
 create mode 100644 meta-oe/recipes-devtools/autoconf-2.13/autoconf-2.13-native_2.13.bb
 create mode 100644 meta-oe/recipes-devtools/autoconf-2.13/autoconf-2.13/0001-Add-config.guess-config.sub-install-to-destdir.patch
 delete mode 100644 meta-oe/recipes-extended/mozjs/mozjs/0004-do-not-use-autoconf-2.13-to-refresh-old.configure.patch
 delete mode 100644 meta-oe/recipes-extended/mozjs/mozjs/old-configure.patch

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