public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/8] Patch review
Date: Sun,  3 Apr 2022 16:30:21 -1000	[thread overview]
Message-ID: <cover.1649026624.git.steve@sakoman.com> (raw)

Please review this set of patches for dunfell and have comments back by end
of day Tuesday.

Passed a-full on autobuilder:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3472

The following changes since commit aa2bb4f62dd7e5c6fdf220264c3d62fbf2cc7d16:

  xserver-xorg: update to 1.20.14 (2022-03-29 11:43:54 -1000)

are available in the Git repository at:

  git://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut

Davide Gardenal (1):
  go: backport patch fix for CVE-2021-38297

Martin Jansa (1):
  boost: fix native build with glibc-2.34

Oleksandr Kravchuk (1):
  tzdata: update to 2022a

Peter Kjellerstedt (1):
  python3-jinja2: Correct HOMEPAGE

Ralph Siemsen (2):
  bluez5: fix CVE-2022-0204
  bind: update to 9.11.37

Richard Purdie (1):
  mirrors: Add missing gitsm entries for yocto/oe mirrors

Ross Burton (1):
  grub: ignore CVE-2021-46705

 meta/classes/mirrors.bbclass                  |  2 +
 meta/recipes-bsp/grub/grub2.inc               |  2 +
 .../bind/{bind_9.11.36.bb => bind_9.11.37.bb} |  4 +-
 meta/recipes-connectivity/bluez5/bluez5.inc   |  1 +
 .../bluez5/bluez5/CVE-2022-0204.patch         | 66 +++++++++++++
 meta/recipes-devtools/go/go-1.14.inc          |  4 +
 .../go/go-1.14/CVE-2021-38297.patch           | 97 +++++++++++++++++++
 .../python/python3-jinja2_2.11.3.bb           |  2 +-
 meta/recipes-extended/timezone/timezone.inc   |  6 +-
 ...e-warning-with-glibc-2.34-on-Linux-p.patch | 32 ++++++
 ...-elide-a-warning-that-caused-Solaris.patch | 24 +++++
 meta/recipes-support/boost/boost_1.72.0.bb    |  2 +
 12 files changed, 236 insertions(+), 6 deletions(-)
 rename meta/recipes-connectivity/bind/{bind_9.11.36.bb => bind_9.11.37.bb} (97%)
 create mode 100644 meta/recipes-connectivity/bluez5/bluez5/CVE-2022-0204.patch
 create mode 100644 meta/recipes-devtools/go/go-1.14/CVE-2021-38297.patch
 create mode 100644 meta/recipes-support/boost/boost/0001-Fix-Wsign-compare-warning-with-glibc-2.34-on-Linux-p.patch
 create mode 100644 meta/recipes-support/boost/boost/0001-Revert-change-to-elide-a-warning-that-caused-Solaris.patch

-- 
2.25.1



             reply	other threads:[~2022-04-04 18:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  2:30 Steve Sakoman [this message]
2022-04-04  2:30 ` [OE-core][dunfell 1/8] grub: ignore CVE-2021-46705 Steve Sakoman
2022-04-04  2:30 ` [OE-core][dunfell 2/8] go: backport patch fix for CVE-2021-38297 Steve Sakoman
2022-04-04  4:23   ` Ranjitsinh Rathod
2022-04-04  4:26     ` Steve Sakoman
2022-04-04  2:30 ` [OE-core][dunfell 3/8] bluez5: fix CVE-2022-0204 Steve Sakoman
2022-04-04  2:30 ` [OE-core][dunfell 4/8] bind: update to 9.11.37 Steve Sakoman
2022-04-04  2:30 ` [OE-core][dunfell 5/8] mirrors: Add missing gitsm entries for yocto/oe mirrors Steve Sakoman
2022-04-04  2:30 ` [OE-core][dunfell 6/8] boost: fix native build with glibc-2.34 Steve Sakoman
2022-04-04  2:30 ` [OE-core][dunfell 7/8] python3-jinja2: Correct HOMEPAGE Steve Sakoman
2022-04-04  2:30 ` [OE-core][dunfell 8/8] tzdata: update to 2022a Steve Sakoman
  -- strict thread matches above, loose matches on Subject: below --
2024-01-26 14:20 [OE-core][dunfell 0/8] Patch review Steve Sakoman
2023-01-11 14:34 Steve Sakoman
2022-11-06 16:03 Steve Sakoman
2020-12-28 14:35 Steve Sakoman
2020-10-15 14:15 Steve Sakoman
2020-06-02  0:12 Steve Sakoman
2020-05-11 14:38 Steve Sakoman

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=cover.1649026624.git.steve@sakoman.com \
    --to=steve@sakoman.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox