[oe-commits] [openembedded-core] branch master-next updated (a339404 -> 4a87b65)

git at git.openembedded.org git at git.openembedded.org
Wed Jul 17 18:27:17 UTC 2019


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 a339404  python3: upgrade 3.7.3 -> 3.7.4
 discard d2054c0  python: fix CVE-2019-9740
 discard b0dc570  wic: add support for kernel with initramfs bundled
 discard 682ef99  nasm: fix CVE-2018-19755
 discard f61f222  opkg/package/rootfs_ipk: allow overwriting OPKGLIBDIR
 discard 9e1acf3  defaultsetup.conf: enable select init manager
     add 81eae38  opkg/package/rootfs_ipk: allow overwriting OPKGLIBDIR
     add 4a46516  nasm: fix CVE-2018-19755
     add bac984f  wic: add support for kernel with initramfs bundled
     add 8eddac3  python: fix CVE-2019-9740
     add 73579c8  python3: upgrade 3.7.3 -> 3.7.4
     new 2935a9f  defaultsetup.conf: enable select init manager
     new 01a8b7c  kernel-fitimage: uboot-sign: fix missing signature
     new 14654d3  subversion: set CVE vendor to Apache
     new 8db227a  boost: set CVE vendor to Boost
     new 320f39f  git: set CVE vendor to git-scm
     new e197110  ed: set CVE vendor to avoid false positives
     new 42f2388  busybox: enable unicode support
     new ecd8781  cve-check.bbclass: initialize to_append
     new db547d0  oe/copy_buildsystem: move layer into layers directory
     new 400d4c1  freetype: add --tag CC to libtool arguments
     new 466c1fc  cve-check: allow comparison of Vendor as well as Product
     new e1c50ee  flex: set CVE_PRODUCT to include vendor
     new 76f433a  cve-update-db-native: use SQL placeholders instead of format strings
     new 4a87b65  ltp: getrlimit03: adjust-a-bit-of-code-to-compatiable-with mips32

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   (a339404)
            \
             N -- N -- N   refs/heads/master-next (4a87b65)

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 14 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/cve-check.bbclass                     | 13 ++--
 meta/classes/uboot-sign.bbclass                    |  4 +-
 meta/lib/oe/copy_buildsystem.py                    |  8 ++-
 meta/recipes-core/busybox/busybox/unicode.cfg      | 10 +++
 meta/recipes-core/busybox/busybox_1.31.0.bb        |  1 +
 meta/recipes-core/meta/cve-update-db-native.bb     |  2 +-
 meta/recipes-devtools/flex/flex_2.6.0.bb           |  3 +
 meta/recipes-devtools/git/git.inc                  |  2 +
 .../subversion/subversion_1.12.0.bb                |  2 +
 meta/recipes-extended/ed/ed_1.15.bb                |  2 +
 ...-adjust-a-bit-of-code-to-compatiable-with.patch | 62 ++++++++++++++++++
 ...efine-TST_ABI-32-64-to-detect-target-type.patch | 74 ++++++++++++++++++++++
 meta/recipes-extended/ltp/ltp_20190115.bb          |  2 +
 .../freetype/freetype/use-right-libtool.patch      |  2 +-
 meta/recipes-support/boost/boost.inc               |  2 +
 15 files changed, 181 insertions(+), 8 deletions(-)
 create mode 100644 meta/recipes-core/busybox/busybox/unicode.cfg
 create mode 100644 meta/recipes-extended/ltp/ltp/0001-getrlimit03-adjust-a-bit-of-code-to-compatiable-with.patch
 create mode 100644 meta/recipes-extended/ltp/ltp/0001-lapi-Define-TST_ABI-32-64-to-detect-target-type.patch

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


More information about the Openembedded-commits mailing list