[oe-commits] [openembedded-core] branch master-next updated (d04f4e4 -> f5c7e23)

[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 d04f4e4  gpgme: remove local m4/python.m4
 discard 1e32d07  gpgme: 1.8.0 -> 1.9.0
 discard 7106e6f  build-appliance-image: Don't use COREBASE/LICENSE for checksumming
 discard 1763fa6  mc: unify curses initialization
 discard 2160902  connman: Remove musl patch that's no longer needed
 discard f976df0  packagefeed-stability.bbclass: change another bb.plain to bb.note
 discard 2afdd36  sqlite3: upgrade to 3.2.0
 discard 3192d89  ncurses: 6.0+20161126 -> 6.0+20170715
 discard 386cb3c  gnupg: 2.1.20 -> 2.1.23
     add a4ad070  ncurses: 6.0+20161126 -> 6.0+20170715
     add 95b802b  sqlite3: upgrade to 3.2.0
     add ccb9684  packagefeed-stability.bbclass: change another bb.plain to bb.note
     add 5dc1700  connman: Remove musl patch that's no longer needed
     add fc89bfa  mc: unify curses initialization
     add e12fa3a  build-appliance-image: Don't use COREBASE/LICENSE for checksumming
     add b18a7ad  gpgme: 1.8.0 -> 1.9.0
     add f5c7e23  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   (d04f4e4)
            \
             N -- N -- N   refs/heads/master-next (f5c7e23)

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.

No new revisions were added by this update.

Summary of changes:
 .../gnupg/0003-dirmngr-uses-libgpg-error.patch     | 32 ----------------------
 ...en.sh-fix-find-version-for-beta-checking.patch} | 17 +++++-------
 .../gnupg/gnupg/dirmngr-uses-libgpg-error.patch    | 16 +++++++++++
 ...instead-of-pth-config.patch => pkgconfig.patch} | 29 +++++---------------
 ... => use-pkgconfig-instead-of-npth-config.patch} | 21 +++-----------
 .../gnupg/{gnupg_2.1.23.bb => gnupg_2.1.20.bb}     | 14 +++++-----
 6 files changed, 41 insertions(+), 88 deletions(-)
 delete mode 100644 meta/recipes-support/gnupg/gnupg/0003-dirmngr-uses-libgpg-error.patch
 rename meta/recipes-support/gnupg/gnupg/{0004-autogen.sh-fix-find-version-for-beta-checking.patch => autogen.sh-fix-find-version-for-beta-checking.patch} (58%)
 create mode 100644 meta/recipes-support/gnupg/gnupg/dirmngr-uses-libgpg-error.patch
 rename meta/recipes-support/gnupg/gnupg/{0001-Use-pkg-config-to-find-pth-instead-of-pth-config.patch => pkgconfig.patch} (81%)
 rename meta/recipes-support/gnupg/gnupg/{0002-use-pkgconfig-instead-of-npth-config.patch => use-pkgconfig-instead-of-npth-config.patch} (81%)
 rename meta/recipes-support/gnupg/{gnupg_2.1.23.bb => gnupg_2.1.20.bb} (69%)

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