From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libzlib: bump to version 1.2.13
Date: Tue, 25 Oct 2022 20:22:50 +0200 [thread overview]
Message-ID: <20221025202250.656b2750@windsurf> (raw)
In-Reply-To: <20221023165026.13707-1-fontaine.fabrice@gmail.com>
On Sun, 23 Oct 2022 18:50:26 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> - Drop all patches (already in version)
> - Replace README by LICENSE file added with
> https://github.com/madler/zlib/commit/352cb28d12baf02863ff5d4d96be0587ced419a1
>
> https://github.com/madler/zlib/releases/tag/v1.2.13
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...hat-discarded-provided-CC-definition.patch | 28 ---------------
> package/libzlib/0002-fix-CVE-2022-37434.patch | 35 -------------------
> .../0003-fix-CVE-2022-37434-regression.patch | 32 -----------------
> package/libzlib/libzlib.hash | 4 +--
> package/libzlib/libzlib.mk | 7 ++--
> 5 files changed, 4 insertions(+), 102 deletions(-)
> delete mode 100644 package/libzlib/0001-Fix-configure-issue-that-discarded-provided-CC-definition.patch
> delete mode 100644 package/libzlib/0002-fix-CVE-2022-37434.patch
> delete mode 100644 package/libzlib/0003-fix-CVE-2022-37434-regression.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-10-25 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 16:50 [Buildroot] [PATCH 1/1] package/libzlib: bump to version 1.2.13 Fabrice Fontaine
2022-10-25 18:22 ` Thomas Petazzoni via buildroot [this message]
[not found] <20221023165026.13707-1-fontaine.fabrice__23420.659061388$1666543861$gmane$org@gmail.com>
2022-10-31 20:35 ` Bernd Kuhls
2022-11-04 8:09 ` Peter Korsgaard
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=20221025202250.656b2750@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox