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/octave: bump to version 9.2.0
Date: Sat, 15 Jun 2024 19:05:02 +0200 [thread overview]
Message-ID: <Zm3Jvr23hF3MYpLT@landeda> (raw)
In-Reply-To: <20240615100123.641349-1-ju.o@free.fr>
Julien, All,
On 2024-06-15 12:01 +0200, Julien Olivain spake thusly:
> See release announce:
> https://octave.org/news/release/2024/06/07/octave-9.2.0-released.html
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> Patch tested on branch master at commit a4d38ef, with commands:
>
> utils/docker-run make check-package
> ...
> 0 warnings generated
>
> utils/test-pkg -p octave
> ...
> 6 builds, 3 skipped, 0 build failed, 0 legal-info failed, 0 show-info failed
>
> support/testing/run-tests \
> -d dl \
> -o output_folder \
> tests.package.test_octave
> ...
> OK
> ---
> package/octave/octave.hash | 4 ++--
> package/octave/octave.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/package/octave/octave.hash b/package/octave/octave.hash
> index 3ea5a1cd8d7..d9313734f16 100644
> --- a/package/octave/octave.hash
> +++ b/package/octave/octave.hash
> @@ -1,5 +1,5 @@
> # Locally computed after checking signature
> -# https://ftp.gnu.org/gnu/octave/octave-9.1.0.tar.lz.sig
> +# https://ftp.gnu.org/gnu/octave/octave-9.2.0.tar.lz.sig
> # using key DBD9C84E39FE1AAE99F04446B05F05B75D36644B
> -sha256 f1769f61bd10c8ade6aee352b1bbb016e5fd8fc8394896a64dc26ef675ba3cea octave-9.1.0.tar.lz
> +sha256 dcb2c098701cfcbc083f07e90e146261d15cdbf5e89c031032422112c89b47da octave-9.2.0.tar.lz
> sha256 3972dc9744f6499f0f9b2dbf76696f2ae7ad8af9b23dde66d6af86c9dfb36986 COPYING
> diff --git a/package/octave/octave.mk b/package/octave/octave.mk
> index 6a21bef7b87..69b292bb6b8 100644
> --- a/package/octave/octave.mk
> +++ b/package/octave/octave.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -OCTAVE_VERSION = 9.1.0
> +OCTAVE_VERSION = 9.2.0
> OCTAVE_SITE = https://ftp.gnu.org/gnu/octave
> OCTAVE_SOURCE = octave-$(OCTAVE_VERSION).tar.lz
> OCTAVE_LICENSE = GPL-3.0+
> --
> 2.45.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-06-15 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 10:01 [Buildroot] [PATCH 1/1] package/octave: bump to version 9.2.0 Julien Olivain
2024-06-15 17:05 ` 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=Zm3Jvr23hF3MYpLT@landeda \
--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