[oe-commits] [openembedded-core] branch master-next updated (b25d873 -> bcf521c)

[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 b25d873  perl/modules: Add various missing ptest perl module dependencies (not complete)
 discard aff2a0d  m4: Add coreutils and dffutils dependency for ptest
 discard 271c32b  libpcre: Add make dependency for ptest
 discard 75cccaf  openssh: Add sudo dependency for ptest
 discard 3f2894b  bash: Fix bash-ptest dependencies
 discard d418238  perl-rdepends: Add missing module dependencies
 discard 1b18dc5  libmodulemd: fix erroneous linking against v2 library when v1 was requested
 discard 77bd035  btrfs-tools: update to 5.1
 discard 52acd43  epiphany: update to 3.32.2
 discard 5ba5811  webkitgtk: update to 2.24.2
 discard f555cf0  usbutils: upgrade 010->012
 discard 689e0d9  dnf: upgrade 4.2.2 -> 4.2.6
 discard 8fd14d2  freetype: upgrade 2.9.1 -> 2.10.0
 discard c12fd0d  acpica: upgrade 20190405 -> 20190509
 discard c29dbbf  gst-examples: upgrade to 1.16.0
 discard 1586f92  libdnf: upgrade 0.28.1 -> 0.33.0
     new 7e7e0c9  gst-examples: upgrade to 1.16.0
     new afcbbed  acpica: upgrade 20190405 -> 20190509
     new 36e308e  freetype: upgrade 2.9.1 -> 2.10.0
     new aa6900d  usbutils: upgrade 010->012
     new d967e7f  webkitgtk: update to 2.24.2
     new 9591243  epiphany: update to 3.32.2
     new a314b47  btrfs-tools: update to 5.1
     new c7fab9d  libmodulemd: fix erroneous linking against v2 library when v1 was requested
     new 42ccc5f  perl-rdepends: Add missing module dependencies
     new db1384d  bash: Fix bash-ptest dependencies
     new 62eb1d5  openssh: Add sudo dependency for ptest
     new 8e587a5  libpcre: Add make dependency for ptest
     new 0d9a58e  m4: Add coreutils and dffutils dependency for ptest
     new bcf521c  perl/modules: Add various missing ptest perl module dependencies (not complete)

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

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/recipes-devtools/dnf/{dnf_4.2.6.bb => dnf_4.2.2.bb}            | 2 +-
 meta/recipes-devtools/libdnf/{libdnf_0.33.0.bb => libdnf_0.28.1.bb} | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-devtools/dnf/{dnf_4.2.6.bb => dnf_4.2.2.bb} (98%)
 rename meta/recipes-devtools/libdnf/{libdnf_0.33.0.bb => libdnf_0.28.1.bb} (95%)

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