From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: "Raphaël Mélotte" <raphael.melotte@mind.be>,
"Asaf Kahlon" <asafka7@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/mupdf: bump to version 1.21.0
Date: Sat, 10 Dec 2022 22:10:35 +0100 [thread overview]
Message-ID: <20221210211035.GF1044805@scaer> (raw)
In-Reply-To: <20221210201240.3504734-1-james.hilliard1@gmail.com>
James, All,
On 2022-12-10 13:12 -0700, James Hilliard spake thusly:
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> package/mupdf/mupdf.hash | 4 ++--
> package/mupdf/mupdf.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/package/mupdf/mupdf.hash b/package/mupdf/mupdf.hash
> index fa24e741c7..6785aa163a 100644
> --- a/package/mupdf/mupdf.hash
> +++ b/package/mupdf/mupdf.hash
> @@ -1,8 +1,8 @@
> # From https://mupdf.com/downloads/index.html:
> -sha1 f27108668e876b47d7438e2a8b2295654e66f42d mupdf-1.20.3-source.tar.lz
> +sha1 27d75cae256450abb9f50cd00b3e5a895fc684cf mupdf-1.21.0-source.tar.lz
>
> # Locally computed:
> -sha256 6f73f63ef8aa81991dfd023d4426a548827d1d74e0bfcf2a013acad63b651868 mupdf-1.20.3-source.tar.lz
> +sha256 f23fc1ad9081375d9c5f2318d6e6e5c5be490ecb70b10ed7167932afbe1ccfb5 mupdf-1.21.0-source.tar.lz
>
> # Hash for license files:
> sha256 57c8ff33c9c0cfc3ef00e650a1cc910d7ee479a8bc509f6c9209a7c2a11399d6 COPYING
> diff --git a/package/mupdf/mupdf.mk b/package/mupdf/mupdf.mk
> index 1fc54b2d35..e93a41bd00 100644
> --- a/package/mupdf/mupdf.mk
> +++ b/package/mupdf/mupdf.mk
> @@ -5,7 +5,7 @@
> ################################################################################
>
> # python-pymupdf's version must match mupdf's version
As the comment states, both packages must have the same version, so they
must be updated in the same patch.
Applied to master as a single patch, thanks.
Regards,
Yann E. MORIN.
> -MUPDF_VERSION = 1.20.3
> +MUPDF_VERSION = 1.21.0
> MUPDF_SOURCE = mupdf-$(MUPDF_VERSION)-source.tar.lz
> MUPDF_SITE = https://mupdf.com/downloads/archive
> MUPDF_LICENSE = AGPL-3.0+
> --
> 2.34.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
prev parent reply other threads:[~2022-12-10 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 20:12 [Buildroot] [PATCH 1/2] package/mupdf: bump to version 1.21.0 James Hilliard
2022-12-10 20:12 ` [Buildroot] [PATCH 2/2] package/python-pymupdf: " James Hilliard
2022-12-10 21:10 ` Yann E. MORIN [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=20221210211035.GF1044805@scaer \
--to=yann.morin.1998@free.fr \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=raphael.melotte@mind.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.