From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Gilles Talis <gilles.talis@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/iozone: bump to version 3.506
Date: Sun, 3 Mar 2024 17:46:37 +0100 [thread overview]
Message-ID: <ZeSpbbY296lkWfgG@landeda> (raw)
In-Reply-To: <20240303151913.286560-1-gilles.talis@gmail.com>
Gilles, All,
On 2024-03-03 11:19 -0400, Gilles Talis spake thusly:
> - Upstream archive moved back to tar from tgz
> - For change log, see end of file:
> https://www.iozone.org/src/current/Changes.txt
>
> Signed-off-by: Gilles Talis <gilles.talis@gmail.com>
Applied to next, thanks.
Regards,
Yann E. MORIN.
> ---
> Changes v1->v2 (review from Julien Olivain):
> - Added license information (file and hash)
> - Updated commit log with archive format and change log
> ---
> package/iozone/iozone.hash | 3 ++-
> package/iozone/iozone.mk | 7 +++----
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/package/iozone/iozone.hash b/package/iozone/iozone.hash
> index 9ecf1d1af8..936ab5a646 100644
> --- a/package/iozone/iozone.hash
> +++ b/package/iozone/iozone.hash
> @@ -1,2 +1,3 @@
> # Locally calculated
> -sha256 5a52f5017e022e737f5b55f320cc6ada0f2a8c831a5f996cce2a44e03e91c038 iozone3_493.tgz
> +sha256 114ce5c071873b9a2c7ba6e73d05d5ef7e66564392acbfcdc0b3261db10fcbe7 iozone3_506.tar
> +sha256 bff7909fd698708d15613a4fb977a193cff98f44ef170c2dc1dd502974df75b2 docs/License.txt
> diff --git a/package/iozone/iozone.mk b/package/iozone/iozone.mk
> index 2df4a2aa84..b1b29d1098 100644
> --- a/package/iozone/iozone.mk
> +++ b/package/iozone/iozone.mk
> @@ -4,12 +4,11 @@
> #
> ################################################################################
>
> -IOZONE_VERSION = 3.493
> -IOZONE_SOURCE = iozone$(subst .,_,$(IOZONE_VERSION)).tgz
> +IOZONE_VERSION = 3.506
> +IOZONE_SOURCE = iozone$(subst .,_,$(IOZONE_VERSION)).tar
> IOZONE_SITE = http://www.iozone.org/src/current
> IOZONE_LICENSE = IOzone license (NO DERIVED WORKS ALLOWED)
> -# IOzone license details can be found at:
> -# http://www.iozone.org/docs/Iozone_License.txt
> +IOZONE_LICENSE_FILES = docs/License.txt
>
> # AIO support not available on uClibc, use the linux (non-aio) target.
> ifeq ($(BR2_TOOLCHAIN_USES_UCLIBC),y)
> --
> 2.39.2
>
> _______________________________________________
> 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:[~2024-03-03 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 15:19 [Buildroot] [PATCH v2] package/iozone: bump to version 3.506 Gilles Talis
2024-03-03 15:50 ` Julien Olivain
2024-03-03 16:46 ` 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=ZeSpbbY296lkWfgG@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=gilles.talis@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