From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: "Raphaël Mélotte" <raphael.melotte@mind.be>,
"Asaf Kahlon" <asafka7@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package: {, python-py}mupdf: bump to 1.22.0
Date: Tue, 13 Jun 2023 14:50:10 +0200 [thread overview]
Message-ID: <87ilbrwmpp.fsf@48ers.dk> (raw)
In-Reply-To: <20230513195134.GF2582048@scaer> (Yann E. MORIN's message of "Sat, 13 May 2023 21:51:34 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Raphaël, All,
> On 2023-04-18 12:58 +0200, Raphaël Mélotte spake thusly:
>> Also remove the last two '*_IGNORE_CVES', since the corresponding
>> patches have been removed (they are now part of upstream) in
>> 1fb64680bffbda1e5fb952150652f73205322707.
>>
>> Signed-off-by: Raphaël Mélotte <raphael.melotte@mind.be>
>> ---
>> package/mupdf/mupdf.hash | 4 ++--
>> package/mupdf/mupdf.mk | 8 +-------
>> package/python-pymupdf/python-pymupdf.hash | 4 ++--
>> package/python-pymupdf/python-pymupdf.mk | 4 ++--
>> 4 files changed, 7 insertions(+), 13 deletions(-)
>>
>> diff --git a/package/mupdf/mupdf.hash b/package/mupdf/mupdf.hash
>> index ef91abee18..1f636097ed 100644
>> --- a/package/mupdf/mupdf.hash
>> +++ b/package/mupdf/mupdf.hash
>> @@ -1,8 +1,8 @@
>> # From https://mupdf.com/downloads/index.html:
>> -sha1 f759d914ec6ad6a3b96f994630ff70b75823831b mupdf-1.21.1-source.tar.lz
>> +sha1 b9907729d604f0bf3846b45cd5891e10d7a66e24 mupdf-1.22.0-source.tar.lz
>>
>> # Locally computed:
>> -sha256 66a43490676c7f7c2ff74067328ef13285506fcc758d365ae27ea3668bd5e620 mupdf-1.21.1-source.tar.lz
>> +sha256 bed78a0abf8496b30c523497292de979db633eca57e02f6cd0f3c7c042551c3e mupdf-1.22.0-source.tar.lz
>>
>> # Hash for license files:
>> sha256 57c8ff33c9c0cfc3ef00e650a1cc910d7ee479a8bc509f6c9209a7c2a11399d6 COPYING
>> diff --git a/package/mupdf/mupdf.mk b/package/mupdf/mupdf.mk
>> index d6cc407c49..08894d7980 100644
>> --- a/package/mupdf/mupdf.mk
>> +++ b/package/mupdf/mupdf.mk
>> @@ -5,7 +5,7 @@
>> ################################################################################
>>
>> # python-pymupdf's version must match mupdf's version
>> -MUPDF_VERSION = 1.21.1
>> +MUPDF_VERSION = 1.22.0
>> MUPDF_SOURCE = mupdf-$(MUPDF_VERSION)-source.tar.lz
>> MUPDF_SITE = https://mupdf.com/downloads/archive
>> MUPDF_LICENSE = AGPL-3.0+
>> @@ -22,12 +22,6 @@ MUPDF_DEPENDENCIES = \
>> xlib_libX11 \
>> zlib
>>
>> -# 0002-Bug-703366-Fix-double-free-of-object-during-linearization.patch
>> -MUPDF_IGNORE_CVES += CVE-2021-3407
>> -
>> -# 0003-Bug-703791-Stay-within-hash-table-max-key-size-in-cached-color-converter.patch
>> -MUPDF_IGNORE_CVES += CVE-2021-37220
> Dropping those exclusion should have been in a seaprate patch, because
> they were alreadyu incorrect even before the bump to 1.22.0 (we no
> longer have those two patches).
> So, I split that into its own patch.
Committed the drop-CVE-ignore part to 2023.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-06-13 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 10:58 [Buildroot] [PATCH 1/1] package: {, python-py}mupdf: bump to 1.22.0 Raphaël Mélotte
2023-05-13 19:51 ` Yann E. MORIN
2023-06-13 12:50 ` Peter Korsgaard [this message]
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=87ilbrwmpp.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--cc=raphael.melotte@mind.be \
--cc=yann.morin.1998@free.fr \
/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