From: akuster808 <akuster808@gmail.com>
To: Khem Raj <raj.khem@gmail.com>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>
Subject: kirkstone merge request: Aug 10th
Date: Thu, 10 Aug 2023 10:17:38 -0400 [thread overview]
Message-ID: <14bbe32a-ff58-e649-b436-266da366f927@gmail.com> (raw)
The following changes since commit 4da92ed9be41734f6ced46b981958e2e868cbff2:
python3-gcovr: Fix parsing of gcc-11 gcov metadata (2023-07-25
07:24:25 -0400)
are available in the Git repository at:
https://git.openembedded.org/meta-openembedded kirkstone-next
for you to fetch changes up to 594c9cf6d3205c8e40ff772383fd9ab7dd3ed2cc:
redis: upgrade 7.0.11 -> 7.0.12 (2023-08-03 16:50:52 -0400)
----------------------------------------------------------------
J.D. Schroeder (1):
Fix groupname gid change warning
Narpat Mali (2):
python3-django: upgrade 3.2.19 -> 3.2.20
python3-django: upgrade 4.2.1 -> 4.2.3
Polampalli, Archana (2):
yasm: fix CVE-2023-31975
redis: upgrade 7.0.11 -> 7.0.12
Urade, Yogita (1):
zabbix: fix CVE-2023-29450
Urade, Yogitag (1):
zabbix: fix CVE-2023-29449
meta-networking/recipes-daemons/cyrus-sasl/cyrus-sasl_2.1.28.bb | 1 +
meta-networking/recipes-daemons/radvd/radvd.inc | 1 +
meta-oe/recipes-connectivity/zabbix/zabbix/CVE-2023-29449.patch | 247
++++++++++++++++++++++++++++
meta-oe/recipes-connectivity/zabbix/zabbix/CVE-2023-29450.patch | 241
+++++++++++++++++++++++++++
meta-oe/recipes-connectivity/zabbix/zabbix_5.4.12.bb | 2 +
meta-oe/recipes-devtools/yasm/yasm/CVE-2023-31975.patch | 29 ++++
meta-oe/recipes-devtools/yasm/yasm_git.bb | 1 +
.../0001-src-Do-not-reset-FINAL_LIBS.patch | 0
.../0006-Define-correct-gregs-for-RISCV32.patch | 0
.../redis/{redis-7.0.11 => redis-7.0.12}/GNU_SOURCE-7.patch | 0
.../hiredis-use-default-CC-if-it-is-set.patch | 0
.../redis/{redis-7.0.11 => redis-7.0.12}/init-redis-server | 0
.../lua-update-Makefile-to-use-environment-build-setting.patch | 0
.../{redis-7.0.11 => redis-7.0.12}/oe-use-libc-malloc.patch | 0
.../redis/{redis-7.0.11 => redis-7.0.12}/redis.conf | 0
.../redis/{redis-7.0.11 => redis-7.0.12}/redis.service | 0
.../recipes-extended/redis/{redis_7.0.11.bb => redis_7.0.12.bb} | 2 +-
.../{python3-django_3.2.19.bb => python3-django_3.2.20.bb} | 4 +-
.../python/{python3-django_4.2.1.bb => python3-django_4.2.3.bb} | 4 +-
19 files changed, 527 insertions(+), 5 deletions(-)
create mode 100644
meta-oe/recipes-connectivity/zabbix/zabbix/CVE-2023-29449.patch
create mode 100644
meta-oe/recipes-connectivity/zabbix/zabbix/CVE-2023-29450.patch
create mode 100644 meta-oe/recipes-devtools/yasm/yasm/CVE-2023-31975.patch
rename meta-oe/recipes-extended/redis/{redis-7.0.11 =>
redis-7.0.12}/0001-src-Do-not-reset-FINAL_LIBS.patch (100%)
rename meta-oe/recipes-extended/redis/{redis-7.0.11 =>
redis-7.0.12}/0006-Define-correct-gregs-for-RISCV32.patch (100%)
rename meta-oe/recipes-extended/redis/{redis-7.0.11 =>
redis-7.0.12}/GNU_SOURCE-7.patch (100%)
rename meta-oe/recipes-extended/redis/{redis-7.0.11 =>
redis-7.0.12}/hiredis-use-default-CC-if-it-is-set.patch (100%)
rename meta-oe/recipes-extended/redis/{redis-7.0.11 =>
redis-7.0.12}/init-redis-server (100%)
rename meta-oe/recipes-extended/redis/{redis-7.0.11 =>
redis-7.0.12}/lua-update-Makefile-to-use-environment-build-setting.patch
(100%)
rename meta-oe/recipes-extended/redis/{redis-7.0.11 =>
redis-7.0.12}/oe-use-libc-malloc.patch (100%)
rename meta-oe/recipes-extended/redis/{redis-7.0.11 =>
redis-7.0.12}/redis.conf (100%)
rename meta-oe/recipes-extended/redis/{redis-7.0.11 =>
redis-7.0.12}/redis.service (100%)
rename meta-oe/recipes-extended/redis/{redis_7.0.11.bb =>
redis_7.0.12.bb} (96%)
rename meta-python/recipes-devtools/python/{python3-django_3.2.19.bb
=> python3-django_3.2.20.bb} (59%)
rename meta-python/recipes-devtools/python/{python3-django_4.2.1.bb =>
python3-django_4.2.3.bb} (61%)
next reply other threads:[~2023-08-10 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 14:17 akuster808 [this message]
2023-08-10 14:44 ` kirkstone merge request: Aug 10th Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14bbe32a-ff58-e649-b436-266da366f927@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.