From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Nicolas Tran <nicolas.tran@smile.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3] package/dust: new package
Date: Wed, 27 Jul 2022 09:45:34 +0200 [thread overview]
Message-ID: <20220727094534.5e912b16@windsurf> (raw)
In-Reply-To: <20220726155115.2024965-1-nicolas.tran@smile.fr>
Hello Nicolas,
On Tue, 26 Jul 2022 17:51:15 +0200
Nicolas Tran <nicolas.tran@smile.fr> wrote:
> diff --git a/package/dust/dust.hash b/package/dust/dust.hash
> new file mode 100644
> index 0000000000..82043b497d
> --- /dev/null
> +++ b/package/dust/dust.hash
> @@ -0,0 +1,3 @@
> +# Locally computed
> +sha256 8231d045a0cca286355e89a41758b05f43238d52721bfc78e0b9bc19789bebde dust-0.8.1.tar.gz
The hash doesn't match here:
ERROR: dust-0.8.1.tar.gz has wrong sha256 hash:
ERROR: expected: 8231d045a0cca286355e89a41758b05f43238d52721bfc78e0b9bc19789bebde
ERROR: got : 271cc0f1978049b2dbfece633b85d4dd0184df346bd93720062c13e4332f2549
ERROR: Incomplete download, or man-in-the-middle (MITM) attack
Could you check on your side if the hash of your tarball is really
271cc0f1978049b2dbfece633b85d4dd0184df346bd93720062c13e4332f2549 ?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-27 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 15:51 [Buildroot] [PATCH v3] package/dust: new package Nicolas Tran
2022-07-27 7:45 ` Thomas Petazzoni via buildroot [this message]
2022-07-27 8:52 ` Nicolas TRAN
2022-07-27 9:22 ` Thomas Petazzoni via buildroot
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=20220727094534.5e912b16@windsurf \
--to=buildroot@buildroot.org \
--cc=nicolas.tran@smile.fr \
--cc=thomas.petazzoni@bootlin.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 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.