public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/dash: bump to version 0.5.13.2
Date: Sat, 21 Mar 2026 21:45:18 +0200	[thread overview]
Message-ID: <87h5q9otkh.fsf@tarshish> (raw)
In-Reply-To: <20260321180002.2450859-1-giulio.benetti@benettiengineering.com> (Giulio Benetti's message of "Sat, 21 Mar 2026 19:00:02 +0100")

Hi Giulio,

On Sat, Mar 21 2026, Giulio Benetti wrote:
> For change log, see:
> https://git.kernel.org/pub/scm/utils/dash/dash.git/log/?h=b308564a1ff6530f9fd3e7dd7b19aabae32ed375
>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
>  package/dash/dash.hash | 6 +++---
>  package/dash/dash.mk   | 2 +-
>  2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/package/dash/dash.hash b/package/dash/dash.hash
> index 85f8f3bf82..7ed0f0d3da 100644
> --- a/package/dash/dash.hash
> +++ b/package/dash/dash.hash
> @@ -1,7 +1,7 @@
> -# From http://gondor.apana.org.au/~herbert/dash/files/dash-0.5.13.1.tar.gz.sha512sum
> +# From http://gondor.apana.org.au/~herbert/dash/files/dash-0.5.13.2.tar.gz.sha512sum
>  # After checking pgp signature
>  # using key 9F9D45FE50AE361530983792C7271D0A49B18BA7

Actually, the hash below appears in the linked signed message. No check
of signature is required to validate the hash. So mention of pgp
signature can be removed.

baruch

> -sha512
> 6b3d67f76e74853349fe99121b2ee96d32da9863042744e03984eb6a01bf437eee2f2e81fbdd0436090abfecacc2f5589960820c3d0d5f3dd580948d38d5dc1d
> dash-0.5.13.1.tar.gz
> +sha512
> 7e9a06409eec925fc83c81192cab420a76ec25821f0a4cec8db4a93b00e51d343438b8cfe56069b4d7fb185f529d1b5171a7603525de00a7852298425b2f433f
> dash-0.5.13.2.tar.gz
>  # Locally calculated
> -sha256  d9271bce09c127d9866e25c011582ddc75ab988958a04bc4d8553a3b8f30e370  dash-0.5.13.1.tar.gz
> +sha256  e7136826b1eed6ce3193e8affa2f70b1b2b9168dd91ffa7ddb4f46e9e62054fe  dash-0.5.13.2.tar.gz
>  sha256  254a7894923ff62e69184a991dcbccae97edee58a1105e8efbe78caf10595d72  COPYING
> diff --git a/package/dash/dash.mk b/package/dash/dash.mk
> index 143972f01a..547fe8c9b0 100644
> --- a/package/dash/dash.mk
> +++ b/package/dash/dash.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -DASH_VERSION = 0.5.13.1
> +DASH_VERSION = 0.5.13.2
>  DASH_SITE = http://gondor.apana.org.au/~herbert/dash/files
>  DASH_LICENSE = BSD-3-Clause, GPL-2.0+ (mksignames.c)
>  DASH_LICENSE_FILES = COPYING

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-03-21 19:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-21 18:00 [Buildroot] [PATCH] package/dash: bump to version 0.5.13.2 Giulio Benetti
2026-03-21 19:45 ` Baruch Siach via buildroot [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=87h5q9otkh.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=giulio.benetti@benettiengineering.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