From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/meson: bump to version 0.50.1
Date: Wed, 24 Apr 2019 21:54:18 +0200 [thread overview]
Message-ID: <20190424215418.31099575@windsurf> (raw)
In-Reply-To: <20190424185857.55349-1-aduskett@gmail.com>
Hello Adam,
On Wed, 24 Apr 2019 14:58:57 -0400
aduskett at gmail.com wrote:
> diff --git a/package/meson/meson.hash b/package/meson/meson.hash
> index fadef6df8a..c3964bc8a8 100644
> --- a/package/meson/meson.hash
> +++ b/package/meson/meson.hash
> @@ -1,4 +1,4 @@
> # Locally calculated after checking pgp signature
> -# https://github.com/mesonbuild/meson/releases/download/0.49.2/meson-0.49.2.tar.gz.asc
> -sha256 ef9f14326ec1e30d3ba1a26df0f92826ede5a79255ad723af78a2691c37109fd meson-0.49.2.tar.gz
> +# https://github.com/mesonbuild/meson/releases/download/0.50.1/meson-0.50.1.tar.gz.asc
> +sha256 e9f52047f26636ee512439c01755064656db5faecdd68e9af09dc772d829198c meson-0.50.1.tar.gz
This hash was matching the tarball automatically generated by Github
(which we download through the 'github' macro), which definitely
doesn't match the GPG signature from the upstream developers.
Instead, we should keep using the upstream-provided tarball, which does
match the GPG signature.
I fixed that and applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-04-24 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 18:58 [Buildroot] [PATCH 1/1] package/meson: bump to version 0.50.1 aduskett at gmail.com
2019-04-24 19:54 ` Thomas Petazzoni [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=20190424215418.31099575@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