[oe-commits] [openembedded-core] branch master-next updated (9fde7ff -> 1ed45a2)

git at git.openembedded.org git at git.openembedded.org
Thu Aug 17 10:56:15 UTC 2017


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 9fde7ff  connman: Remove musl patch that's no longer needed
 discard c3e7aff  packagefeed-stability.bbclass: change another bb.plain to bb.note
 discard 4c98c63  sqlite3: upgrade to 3.2.0
 discard 2899a37  ncurses: 6.0+20161126 -> 6.0+20170715
 discard 6ef8866  gpgme: 1.8.0 -> 1.9.0
 discard d1c2f97  gnupg: 2.1.20 -> 2.1.23
 discard 9dd81ff  libgcrypt: 1.7.8 -> 1.8.0
 discard a46e0b8  elfutils: 0.168 -> 0.170
 discard 70740ae  dhcp: 4.3.5 -> 4.3.6
 discard 5e620d4  bash: 4.3.30 -> 4.4
 discard 8acea90  apr-util: 1.5.4 -> 1.6.0
 discard 6df8475  cross-canadian.bbclass: add ilp32 support
 discard 935b285  package.bbclass: support persistent /var/log
 discard 40fdf0d  initscripts: support persistent /var/log
 discard 8b1cbe5  base-files: respect VOLATILE_LOG_DIR
 discard 3073ef9  bitbake.conf: add VOLATILE_LOG_DIR variable
 discard 4823bf6  shadow: fix CVE-2017-12424
 discard fbc4059  nss: 3.30.2 -> 3.31.1
 discard e98d8be  harfbuzz: upgrade to 1.4.8
 discard 3baa48c  screen: upgrade to 4.6.1
 discard bc022bb  copy_buildsystem/py: adds meta-skeleton layer in the eSDK installation.
     new 76c9ba6  screen: upgrade to 4.6.1
     new f6f6d13  harfbuzz: upgrade to 1.4.8
     new 86838f1  nss: 3.30.2 -> 3.31.1
     new 896495d  shadow: fix CVE-2017-12424
     new 016bafc  bitbake.conf: add VOLATILE_LOG_DIR variable
     new fc19114  base-files: respect VOLATILE_LOG_DIR
     new 50914c4  initscripts: support persistent /var/log
     new 6b22e24  package.bbclass: support persistent /var/log
     new 6c5e50d  cross-canadian.bbclass: add ilp32 support
     new a67800e  apr-util: 1.5.4 -> 1.6.0
     new ffb9627  bash: 4.3.30 -> 4.4
     new f228511  dhcp: 4.3.5 -> 4.3.6
     new bc911f8  elfutils: 0.168 -> 0.170
     new 6f15fa1  libgcrypt: 1.7.8 -> 1.8.0
     new b3eb2b1  gnupg: 2.1.20 -> 2.1.23
     new 937c531  ncurses: 6.0+20161126 -> 6.0+20170715
     new ba2b307  sqlite3: upgrade to 3.2.0
     new 31ab1ae  packagefeed-stability.bbclass: change another bb.plain to bb.note
     new f39af4a  connman: Remove musl patch that's no longer needed
     new 0a9916a  mc: unify curses initialization
     new d563422  build-appliance-image: Don't use COREBASE/LICENSE for checksumming
     new aa611f5  gpgme: 1.8.0 -> 1.9.0
     new 1ed45a2  gpgme: remove local m4/python.m4

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   (9fde7ff)
            \
             N -- N -- N   refs/heads/master-next (1ed45a2)

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 23 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/lib/oe/copy_buildsystem.py                    |  8 ---
 .../images/build-appliance-image_15.0.0.bb         |  3 +-
 ...3697-tty_init-unify-curses-initialization.patch | 66 ++++++++++++++++++++++
 meta/recipes-extended/mc/mc_4.8.19.bb              |  1 +
 meta/recipes-support/gpgme/gpgme_1.9.0.bb          |  1 +
 5 files changed, 69 insertions(+), 10 deletions(-)
 create mode 100644 meta/recipes-extended/mc/files/0002-Ticket-3697-tty_init-unify-curses-initialization.patch

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


More information about the Openembedded-commits mailing list