[oe-commits] [meta-openembedded] branch master-next updated (0355ac4 -> 4a2fcae)

[git at git.openembedded.org]

This is an automated email from the git hooks/post-receive script.

khem pushed a change to branch master-next
in repository meta-openembedded.

 discard 0355ac4  python3-pillow: add 5.4.1
 discard 5f740fe  opencv: fix installed-vs-shipped QA WARNING
 discard 950bfeb  dnsmasq: avoid conflict with systemd-resolved
 discard db265bb  hdf5: fix installed-vs-shipped QA WARNING
 discard 3e2f686  netkit-rsh: don't build under musl
 discard 5534fd2  klibc: Upgrade to 2.0.6 release
 discard 17d951b  python-pyflame: Disable for risv architecture
 discard 5a69cc9  librcf: bump to 3.0.251
 discard 83935a2  librelp: Upgrade to 1.4.0
 discard 980c635  krb5: Upgrade to 1.17
 discard 6015558  crash: Upgrade to 7.2.5
 discard 6624178  cpulimit: introduce support for this package
     new f7f0621  crash: Upgrade to 7.2.5
     new b3eeaf4  krb5: Upgrade to 1.17
     new 666c23a  librelp: Upgrade to 1.4.0
     new 0597e79  python-pyflame: Disable for risv architecture
     new 9d8943f  klibc: Upgrade to 2.0.6 release
     new 059aa89  netkit-rsh: don't build under musl
     new 02f0502  hdf5: fix installed-vs-shipped QA WARNING
     new 93c5f47  dnsmasq: avoid conflict with systemd-resolved
     new 3189c0d  opencv: fix installed-vs-shipped QA WARNING
     new 4a2fcae  python3-pillow: add 5.4.1

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   (0355ac4)
            \
             N -- N -- N   refs/heads/master-next (4a2fcae)

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 10 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:
 .../librcf/librcf/0001-Add-CMake-build-files.patch | 135 ++++++++++++++++-----
 .../librcf/0001-Check-for-__powerpc__-define.patch |  28 +++++
 ...lientStub.hpp-fix-a-clang-compiling-issue.patch |  35 ++++++
 ...yptionFilter.cpp-replace-old-state-define.patch |  38 ------
 .../librcf/librcf/aarch64-support.patch            |  13 ++
 .../librcf/librcf/mips-support.patch               |  19 +++
 meta-oe/recipes-devtools/librcf/librcf_2.2.0.0.bb  |  53 ++++++++
 meta-oe/recipes-devtools/librcf/librcf_3.0.251.bb  |  40 ------
 meta-oe/recipes-support/cpulimit/cpulimit_0.2.bb   |  19 ---
 9 files changed, 253 insertions(+), 127 deletions(-)
 create mode 100644 meta-oe/recipes-devtools/librcf/librcf/0001-Check-for-__powerpc__-define.patch
 create mode 100644 meta-oe/recipes-devtools/librcf/librcf/0001-ClientStub.hpp-fix-a-clang-compiling-issue.patch
 delete mode 100644 meta-oe/recipes-devtools/librcf/librcf/0001-OpenSslEncryptionFilter.cpp-replace-old-state-define.patch
 create mode 100644 meta-oe/recipes-devtools/librcf/librcf/aarch64-support.patch
 create mode 100644 meta-oe/recipes-devtools/librcf/librcf/mips-support.patch
 create mode 100644 meta-oe/recipes-devtools/librcf/librcf_2.2.0.0.bb
 delete mode 100644 meta-oe/recipes-devtools/librcf/librcf_3.0.251.bb
 delete mode 100644 meta-oe/recipes-support/cpulimit/cpulimit_0.2.bb

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