[oe-commits] [openembedded-core] branch master-next updated (a91b5ee -> ae68c19)

[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 a91b5ee  fixup
 discard 80e36a4  image: Expand PV to avoid AUTOREV parsing failures
 discard b6b05bb  manifest.py: sort package list
 discard e16da7e  multilib.bbclass: remove invalid PACKAGE_INSTALL
 discard e3a7533  sstate.bbclass: sstate_hardcode_path(): fix for multilib
 discard 51259b4  nativesdk/sdk: Update sdk dummy providers
 discard 0f2806a  package_deb: Handle / in dependency name
 discard 409d78f  gettext: rationalise optional dependencies
 discard 29a800e  glib-2.0: rationalise build dependencies
     new fc08972  package_deb: Handle / in dependency name
     new 47218dd  nativesdk/sdk: Update sdk dummy providers
     new 537c85c  sstate.bbclass: sstate_hardcode_path(): fix for multilib
     new 50a46d2  multilib.bbclass: remove invalid PACKAGE_INSTALL
     new d2dd8f6  manifest.py: sort package list
     new f39fbb2  image: Expand PV to avoid AUTOREV parsing failures
     new ed96d6d  libgcrypt: upgrade to 1.8.2
     new 94947be  gnupg: upgrade to 2.2.4
     new 66f11e1  gnupg: enable native version
     new 4361556  gnupg: use native version for signing, rather than one provided by host
     new 5d73f30  glib-2.0: rationalise build dependencies
     new 018829c  gettext: rationalise optional dependencies
     new ae68c19  linux-firmware: Bump revision to 65b1c68c

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   (a91b5ee)
            \
             N -- N -- N   refs/heads/master-next (ae68c19)

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:
 meta/classes/sign_package_feed.bbclass                            | 2 +-
 meta/classes/sign_rpm.bbclass                                     | 6 +-----
 meta/lib/oe/gpg_sign.py                                           | 8 ++++++--
 meta/recipes-core/gettext/gettext_0.19.8.1.bb                     | 1 +
 meta/recipes-core/glib-2.0/glib.inc                               | 1 +
 meta/recipes-core/meta/nativesdk-buildtools-perl-dummy.bb         | 2 ++
 meta/recipes-core/meta/nativesdk-sdk-provides-dummy.bb            | 2 ++
 meta/recipes-core/meta/signing-keys.bb                            | 1 +
 meta/recipes-kernel/linux-firmware/linux-firmware_git.bb          | 6 +++---
 meta/recipes-support/gnupg/{gnupg_2.2.0.bb => gnupg_2.2.4.bb}     | 6 ++++--
 .../libgcrypt/{libgcrypt_1.8.1.bb => libgcrypt_1.8.2.bb}          | 4 ++--
 meta/recipes-support/libksba/libksba_1.3.5.bb                     | 2 ++
 meta/recipes-support/npth/npth_1.5.bb                             | 2 ++
 meta/recipes-support/pinentry/pinentry_1.1.0.bb                   | 2 ++
 14 files changed, 30 insertions(+), 15 deletions(-)
 rename meta/recipes-support/gnupg/{gnupg_2.2.0.bb => gnupg_2.2.4.bb} (90%)
 rename meta/recipes-support/libgcrypt/{libgcrypt_1.8.1.bb => libgcrypt_1.8.2.bb} (92%)

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