Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Armin Kuster" <akuster808@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [hardknott 0/6] Patch review April 24th
Date: Sun, 25 Apr 2021 13:56:36 -0700	[thread overview]
Message-ID: <87d755d5-1068-dd5a-58e1-7ffbec9310b7@gmail.com> (raw)
In-Reply-To: <CA+chaQeSzuwXe2YRgc68xek+ZygZ7D16Q3jj=jBrTico5TvCEA@mail.gmail.com>



On 4/24/21 3:36 AM, Martin Jansa wrote:
> Please take
> https://git.openembedded.org/meta-openembedded/commit/?id=b5ad9c011db2581cc84e5daa139acf73a0f6f5c0
> as well to fix
> https://git.openembedded.org/meta-openembedded/commit/?h=hardknott&id=98a26903f770aa8698770817bdaf6175367917e1
> merged in previous PR.

Hardknott already has that commit. Was this meant for Gatesgarth?

-armin
>
> On Sat, Apr 24, 2021 at 3:12 AM Armin Kuster <akuster808@gmail.com
> <mailto:akuster808@gmail.com>> wrote:
>
>     These have been sent to the list already so shorter review cycle.
>     Please have feedback by Sunday.
>
>     The following changes since commit
>     2297d4ee04b47bc574f8879732d9e213ab7bf685:
>
>       wireguard: update to v1.0.20210219 +1 (2021-04-18 13:49:13 -0700)
>
>     are available in the Git repository at:
>
>       git://git.openembedded.org/meta-openembedded-contrib
>     <http://git.openembedded.org/meta-openembedded-contrib>
>     stable/hardknott-nut
>      
>     http://cgit.openembedded.org/meta-openembedded-contrib/log/?h=stable/hardknott-nut
>
>     Chen Qi (2):
>       tigervnc: upgrade to 1.11.0
>       python3-django: upgrade to 2.2.20
>
>     Mingli Yu (2):
>       php: Upgrade to 7.4.16
>       python3-cryptography: Upgrade to 3.3.2
>
>     Stefan Ghinea (1):
>       python3-django: fix CVE-2021-28658
>
>     Ulrich Ölmann (1):
>       v4l-utils: fix reproducibility
>
>      .../php/php/CVE-2020-7069.patch               | 158
>     ------------------
>      .../php/php/CVE-2020-7070.patch               |  24 ---
>      .../php/{php_7.4.9.bb <http://php_7.4.9.bb> => php_7.4.16.bb
>     <http://php_7.4.16.bb>}       |   7 +-
>      ...002-do-not-build-tests-sub-directory.patch |  21 +--
>      ...vnc-add-fPIC-option-to-COMPILE_FLAGS.patch |  36 ++--
>      ...{tigervnc_1.10.1.bb <http://tigervnc_1.10.1.bb> =>
>     tigervnc_1.11.0.bb <http://tigervnc_1.11.0.bb>} |  13 +-
>      ...c-autodetect-availability-of-systemd.patch |  47 ++++++
>      ...ct-installation-of-50-rc_keymap.conf.patch |  40 +++++
>      .../v4l2apps/v4l-utils_1.20.0.bb <http://v4l-utils_1.20.0.bb>   
>               |  11 +-
>      ...3.3.1.bb <http://3.3.1.bb> => python3-cryptography_3.3.2.bb
>     <http://python3-cryptography_3.3.2.bb>} |   2 +-
>      ...ngo_2.2.16.bb <http://ngo_2.2.16.bb> =>
>     python3-django_2.2.20.bb <http://python3-django_2.2.20.bb>} |   4 +-
>      11 files changed, 130 insertions(+), 233 deletions(-)
>      delete mode 100644
>     meta-oe/recipes-devtools/php/php/CVE-2020-7069.patch
>      delete mode 100644
>     meta-oe/recipes-devtools/php/php/CVE-2020-7070.patch
>      rename meta-oe/recipes-devtools/php/{php_7.4.9.bb
>     <http://php_7.4.9.bb> => php_7.4.16.bb <http://php_7.4.16.bb>} (97%)
>      rename meta-oe/recipes-graphics/tigervnc/{tigervnc_1.10.1.bb
>     <http://tigervnc_1.10.1.bb> => tigervnc_1.11.0.bb
>     <http://tigervnc_1.11.0.bb>} (89%)
>      create mode 100644
>     meta-oe/recipes-multimedia/v4l2apps/v4l-utils/0008-configure.ac-autodetect-availability-of-systemd.patch
>      create mode 100644
>     meta-oe/recipes-multimedia/v4l2apps/v4l-utils/0009-keytable-restrict-installation-of-50-rc_keymap.conf.patch
>      rename
>     meta-python/recipes-devtools/python/{python3-cryptography_3.3.1.bb
>     <http://python3-cryptography_3.3.1.bb> =>
>     python3-cryptography_3.3.2.bb
>     <http://python3-cryptography_3.3.2.bb>} (94%)
>      rename
>     meta-python/recipes-devtools/python/{python3-django_2.2.16.bb
>     <http://python3-django_2.2.16.bb> => python3-django_2.2.20.bb
>     <http://python3-django_2.2.20.bb>} (41%)
>
>     -- 
>     2.17.1
>
>
>     
>


  reply	other threads:[~2021-04-25 20:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24 10:11 [hardknott 0/6] Patch review April 24th Armin Kuster
2021-04-24 10:11 ` [hardknott 1/6] v4l-utils: fix reproducibility Armin Kuster
2021-04-24 10:11 ` [hardknott 2/6] python3-django: fix CVE-2021-28658 Armin Kuster
2021-04-24 10:11 ` [hardknott 3/6] tigervnc: upgrade to 1.11.0 Armin Kuster
2021-04-24 10:11 ` [hardknott 4/6] python3-django: upgrade to 2.2.20 Armin Kuster
2021-04-24 10:11 ` [hardknott 5/6] php: Upgrade to 7.4.16 Armin Kuster
2021-04-24 10:11 ` [hardknott 6/6] python3-cryptography: Upgrade to 3.3.2 Armin Kuster
2021-04-24 10:36 ` [oe] [hardknott 0/6] Patch review April 24th Martin Jansa
2021-04-25 20:56   ` Armin Kuster [this message]
2021-04-25 21:41     ` Martin Jansa
2021-04-25 22:34       ` Armin Kuster

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=87d755d5-1068-dd5a-58e1-7ffbec9310b7@gmail.com \
    --to=akuster808@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@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