From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH/next 1/1] package/minizip-zlib: bump to version 1.2.12
Date: Mon, 5 Sep 2022 21:54:50 +0200 [thread overview]
Message-ID: <20220905195450.GI1490660@scaer> (raw)
In-Reply-To: <20220904211117.218817-1-fontaine.fabrice@gmail.com>
Fabrice, All,
On 2022-09-04 23:11 +0200, Fabrice Fontaine spake thusly:
> Update hash of README (version and year updated with
> https://github.com/madler/zlib/commit/21767c654d31d2dccdde4330529775c6c5fd5389)
>
> https://github.com/madler/zlib/blob/v1.2.12/ChangeLog
There seems to be quite some fixes identified in that changelog. Do you
think this warrants going in master, or is it for next?
Regards,
Yann E. MORIN.
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/minizip-zlib/minizip-zlib.hash | 4 ++--
> package/minizip-zlib/minizip-zlib.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/package/minizip-zlib/minizip-zlib.hash b/package/minizip-zlib/minizip-zlib.hash
> index 4d2c5c29d3..e6ca974e2f 100644
> --- a/package/minizip-zlib/minizip-zlib.hash
> +++ b/package/minizip-zlib/minizip-zlib.hash
> @@ -1,4 +1,4 @@
> # From http://www.zlib.net/
> -sha256 4ff941449631ace0d4d203e3483be9dbc9da454084111f97ea0a2114e19bf066 zlib-1.2.11.tar.xz
> +sha256 7db46b8d7726232a621befaab4a1c870f00a90805511c0e0090441dac57def18 zlib-1.2.12.tar.xz
> # License files, locally calculated
> -sha256 7960b6b1cc63e619abb77acaea5427159605afee8c8b362664f4effc7d7f7d15 README
> +sha256 fc2c3368901700f0acdeb1d8afeaca5923296768ec6824ecdf627aac396001fd README
> diff --git a/package/minizip-zlib/minizip-zlib.mk b/package/minizip-zlib/minizip-zlib.mk
> index 935877678d..ec0c3da7d6 100644
> --- a/package/minizip-zlib/minizip-zlib.mk
> +++ b/package/minizip-zlib/minizip-zlib.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -MINIZIP_ZLIB_VERSION = 1.2.11
> +MINIZIP_ZLIB_VERSION = 1.2.12
> MINIZIP_ZLIB_SOURCE = zlib-$(MINIZIP_ZLIB_VERSION).tar.xz
> MINIZIP_ZLIB_SITE = http://www.zlib.net
> MINIZIP_ZLIB_LICENSE = Zlib
> --
> 2.35.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-09-05 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 21:11 [Buildroot] [PATCH/next 1/1] package/minizip-zlib: bump to version 1.2.12 Fabrice Fontaine
2022-09-05 19:54 ` Yann E. MORIN [this message]
2022-09-17 14:25 ` Thomas Petazzoni
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=20220905195450.GI1490660@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox