All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Daniel Lang <dalang@gmx.at>
Cc: Richard Braun <rbraun@sceen.net>,
	Martin Bark <martin@barkynet.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/{tzdata,zic}: fix hash origin URL
Date: Sun, 14 May 2023 16:09:03 +0200	[thread overview]
Message-ID: <20230514140903.GI2582048@scaer> (raw)
In-Reply-To: <20230514133637.3556558-1-dalang@gmx.at>

Daniel, All,

On 2023-05-14 15:36 +0200, Daniel Lang spake thusly:
> 179ae2f ("package/tzdata: bump version to 2023c") forgot to update the
> URL of the hash files.
> 
> Signed-off-by: Daniel Lang <dalang@gmx.at>

Thanks for fixing my mess! :-)

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/tzdata/tzdata.hash | 2 +-
>  package/zic/zic.hash       | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/package/tzdata/tzdata.hash b/package/tzdata/tzdata.hash
> index 3422655a71..5488625ddd 100644
> --- a/package/tzdata/tzdata.hash
> +++ b/package/tzdata/tzdata.hash
> @@ -1,4 +1,4 @@
> -# From https://mm.icann.org/pipermail/tz-announce/2022-October/000075.html
> +# From https://mm.icann.org/pipermail/tz-announce/2023-March/000079.html
>  sha512  608bd286ebcbd0004cfdc1da183273f08aff61f90c8867661154453d77a05d421e4c46ad6d066a1fe2e87d5c82ec0f1c0224667a3b35f3180a3eb7f6ff84cbf5  tzdata2023c.tar.gz
>  # Locally computed:
>  sha256  0613408568889f5739e5ae252b722a2659c02002839ad970a63dc5e9174b27cf  LICENSE
> diff --git a/package/zic/zic.hash b/package/zic/zic.hash
> index 6a7f9f2f94..a2720a27ba 100644
> --- a/package/zic/zic.hash
> +++ b/package/zic/zic.hash
> @@ -1,4 +1,4 @@
> -# From https://mm.icann.org/pipermail/tz-announce/2022-October/000075.html
> +# From https://mm.icann.org/pipermail/tz-announce/2023-March/000079.html
>  sha512  fa18bae9c0e7c061bc9d5f5f2eb9967f0e4ddb2baafdee9887fa30cd0c60f4aa6f21eacffb17df0d59d26ff54d08c5dcefa98159309eba497e86443624913a82  tzcode2023c.tar.gz
>  # Locally computed:
>  sha256  0613408568889f5739e5ae252b722a2659c02002839ad970a63dc5e9174b27cf  LICENSE
> -- 
> 2.40.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:[~2023-05-14 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-14 13:36 [Buildroot] [PATCH] package/{tzdata,zic}: fix hash origin URL Daniel Lang
2023-05-14 14:09 ` Yann E. MORIN [this message]
2023-06-13 21:37 ` Peter Korsgaard

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=20230514140903.GI2582048@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=dalang@gmx.at \
    --cc=martin@barkynet.com \
    --cc=rbraun@sceen.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.