From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/open2300: add hash file
Date: Sun, 22 Dec 2019 10:57:54 +0100 [thread overview]
Message-ID: <20191222105754.188b7bd2@windsurf> (raw)
In-Reply-To: <20191222083707.3448-1-heiko.thiery@gmail.com>
On Sun, 22 Dec 2019 09:37:08 +0100
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> - add sha256 tarball hash
> - add sha256 license hash
>
> Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
> ---
> package/open2300/open2300.hash | 2 ++
> 1 file changed, 2 insertions(+)
> create mode 100644 package/open2300/open2300.hash
>
> diff --git a/package/open2300/open2300.hash b/package/open2300/open2300.hash
> new file mode 100644
> index 0000000000..913cccf4d2
> --- /dev/null
> +++ b/package/open2300/open2300.hash
> @@ -0,0 +1,2 @@
We need a comment at the top of the file that says where the hashes come from.
> +sha256 f4239d2f16d52156586d06be38f06a3eb58168377e243a8de8720b66e33ddb8f open2300-12.tar.gz
The source code for this package is fetched from Subversion. Are the
tarballs we create out of SVN repositories reproducible ? I guess so,
but let's loop in Yann Morin for some additional feedback on this.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-22 9:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 8:37 [Buildroot] [PATCH] package/open2300: add hash file Heiko Thiery
2019-12-22 9:57 ` Thomas Petazzoni [this message]
2019-12-22 10:08 ` Yann E. MORIN
2019-12-22 10:56 ` Heiko Thiery
2019-12-22 11:05 ` Yann E. MORIN
2019-12-22 12:50 ` Heiko Thiery
2019-12-22 13:00 ` Yann E. MORIN
2019-12-22 11:00 ` Heiko Thiery
2019-12-22 11:07 ` Yann E. MORIN
2019-12-22 13:11 ` 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=20191222105754.188b7bd2@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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