From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/luv: update hash
Date: Tue, 04 Jun 2019 17:50:36 +0300 [thread overview]
Message-ID: <87h895o14z.fsf@tarshish> (raw)
In-Reply-To: <20190604142527.30307-1-joerg.krause@embedded.rocks>
Hi J?rg,
On Tue, Jun 04 2019, J?rg Krause wrote:
> Upstream removed (using git force-push) and recreated version 1.29.1-1
> and re-uploaded the source tarball. Therefore, the hash has changed and
> needs to be updated.
What about the file at the default backup site?
http://sources.buildroot.net/luv/luv-1.29.1-1.tar.gz
It's the old file.
baruch
> See:
> https://github.com/luvit/luv/issues/330
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> package/luv/luv.hash | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/luv/luv.hash b/package/luv/luv.hash
> index 507299f9df..02d61b0f24 100644
> --- a/package/luv/luv.hash
> +++ b/package/luv/luv.hash
> @@ -1,3 +1,3 @@
> # Locally calculated
> -sha256 430d5d8ad6b22e3e6284b8cdcfc7cea93e7459039bc12375a8a89bfbd034751c luv-1.29.1-1.tar.gz
> +sha256 572cf3887f4ca03d2761664aa8a098909b445164d8263015693893902558d4cd luv-1.29.1-1.tar.gz
> sha256 cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30 LICENSE.txt
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2019-06-04 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 14:25 [Buildroot] [PATCH] package/luv: update hash Jörg Krause
2019-06-04 14:50 ` Baruch Siach [this message]
2019-06-04 18:37 ` Jörg Krause
2019-06-04 21:48 ` 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=87h895o14z.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox