From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/z3: bump to version 4.12.1
Date: Sun, 5 Feb 2023 15:43:40 +0100 [thread overview]
Message-ID: <20230205144340.GP2960@scaer> (raw)
In-Reply-To: <20230205130355.797050-1-ju.o@free.fr>
Julien, All,
On 2023-02-05 14:03 +0100, Julien Olivain spake thusly:
> For change log since v4.12.0, see:
> - https://github.com/Z3Prover/z3/releases/tag/z3-4.12.1
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> Patch tested on branch master at commit 8bb9627 with commands:
>
> make check-package
> ...
> 0 warnings generated
>
> support/testing/run-tests \
> -d dl -o output_folder \
> tests.package.test_z3
> ...
> OK
>
> ./utils/test-pkg -p z3
> ...
> 6 builds, 4 skipped, 0 build failed, 0 legal-info failed, 0 show-info failed
> ---
> package/z3/z3.hash | 2 +-
> package/z3/z3.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/z3/z3.hash b/package/z3/z3.hash
> index 517e2f4923..8a511c3fe5 100644
> --- a/package/z3/z3.hash
> +++ b/package/z3/z3.hash
> @@ -1,3 +1,3 @@
> # Locally calculated
> -sha256 5f575f0a3950760436217da1cc1a714569b6d4f664a75bb6775876328cf0a580 z3-4.12.0.tar.gz
> +sha256 a3735fabf00e1341adcc70394993c05fd3e2ae167a3e9bb46045e33084eb64a3 z3-4.12.1.tar.gz
> sha256 e617cad2ab9347e3129c2b171e87909332174e17961c5c3412d0799469111337 LICENSE.txt
> diff --git a/package/z3/z3.mk b/package/z3/z3.mk
> index ecd79325dc..45c412ad12 100644
> --- a/package/z3/z3.mk
> +++ b/package/z3/z3.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -Z3_VERSION = 4.12.0
> +Z3_VERSION = 4.12.1
> Z3_SITE = $(call github,Z3Prover,z3,z3-$(Z3_VERSION))
> Z3_LICENSE = MIT
> Z3_LICENSE_FILES = LICENSE.txt
> --
> 2.39.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:[~2023-02-05 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 13:03 [Buildroot] [PATCH 1/1] package/z3: bump to version 4.12.1 Julien Olivain
2023-02-05 14:43 ` 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=20230205144340.GP2960@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=ju.o@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