Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Michael Vetter <jubalh@iodoru.org>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/jasper: bump to version 2.0.33
Date: Thu, 27 Jan 2022 20:28:37 +0100	[thread overview]
Message-ID: <20220127192837.GP457876@scaer> (raw)
In-Reply-To: <20220127180456.2338773-2-fontaine.fabrice@gmail.com>

Fabrice, All,

On 2022-01-27 19:04 +0100, Fabrice Fontaine spake thusly:
> https://github.com/jasper-software/jasper/blob/version-2.0.33/NEWS
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/jasper/jasper.hash | 2 +-
>  package/jasper/jasper.mk   | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/jasper/jasper.hash b/package/jasper/jasper.hash
> index 67653a8e88..410bcfc683 100644
> --- a/package/jasper/jasper.hash
> +++ b/package/jasper/jasper.hash
> @@ -1,3 +1,3 @@
>  # Locally calculated
> -sha256  6b4e5f682be0ab1a5acb0eeb6bf41d6ce17a658bb8e2dbda95de40100939cc88  jasper-2.0.28.tar.gz
> +sha256  28d28290cc2eaf70c8756d391ed8bcc8ab809a895b9a67ea6e89da23a611801a  jasper-2.0.33.tar.gz
>  sha256  4ad1bb42aff888c4403d792e6e2c5f1716d6c279fea70b296333c9d577d30b81  LICENSE
> diff --git a/package/jasper/jasper.mk b/package/jasper/jasper.mk
> index 59c5b3d66a..05168db763 100644
> --- a/package/jasper/jasper.mk
> +++ b/package/jasper/jasper.mk
> @@ -4,8 +4,8 @@
>  #
>  ################################################################################
>  
> -JASPER_VERSION = 2.0.28
> -JASPER_SITE = $(call github,jasper-software,jasper,version-$(JASPER_VERSION))
> +JASPER_VERSION = 2.0.33
> +JASPER_SITE = https://github.com/jasper-software/jasper/releases/download/version-$(JASPER_VERSION)
>  JASPER_INSTALL_STAGING = YES
>  JASPER_LICENSE = JasPer-2.0
>  JASPER_LICENSE_FILES = LICENSE
> -- 
> 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

  reply	other threads:[~2022-01-27 19:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 18:04 [Buildroot] [PATCH 1/2] package/jasper: use JAS_ENABLE_DOC Fabrice Fontaine
2022-01-27 18:04 ` [Buildroot] [PATCH 2/2] package/jasper: bump to version 2.0.33 Fabrice Fontaine
2022-01-27 19:28   ` Yann E. MORIN [this message]
2022-01-27 19:28 ` [Buildroot] [PATCH 1/2] package/jasper: use JAS_ENABLE_DOC Yann E. MORIN

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=20220127192837.GP457876@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=jubalh@iodoru.org \
    /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