From: Peter Korsgaard <peter@korsgaard.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-ruamel-yaml: bump to version 0.18.5
Date: Mon, 05 Feb 2024 12:39:26 +0100 [thread overview]
Message-ID: <87plxbta1d.fsf@48ers.dk> (raw)
In-Reply-To: <20240111053157.2928259-1-james.hilliard1@gmail.com> (James Hilliard's message of "Wed, 10 Jan 2024 22:31:57 -0700")
>>>>> "James" == James Hilliard <james.hilliard1@gmail.com> writes:
> License hash changed due to year update:
> https://sourceforge.net/p/ruamel-yaml/code/ci/56b3e2666fb275deab3eec99193c103e4edf93bb/
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> package/python-ruamel-yaml/python-ruamel-yaml.hash | 6 +++---
> package/python-ruamel-yaml/python-ruamel-yaml.mk | 4 ++--
> 2 files changed, 5 insertions(+), 5 deletions(-)
> diff --git a/package/python-ruamel-yaml/python-ruamel-yaml.hash b/package/python-ruamel-yaml/python-ruamel-yaml.hash
> index 29852a51ed..7b5dc1e29a 100644
> --- a/package/python-ruamel-yaml/python-ruamel-yaml.hash
> +++ b/package/python-ruamel-yaml/python-ruamel-yaml.hash
> @@ -1,5 +1,5 @@
> # md5, sha256 from https://pypi.org/pypi/rfc3987/json
> -md5 206bda0f33ab2c2f63777636200748b7 ruamel.yaml-0.17.21.tar.gz
> -sha256 8b7ce697a2f212752a35c1ac414471dc16c424c9573be4926b56ff3f5d23b7af ruamel.yaml-0.17.21.tar.gz
> +md5 24fac3544a3c7bd7eeaf6e4f704a056e ruamel.yaml-0.18.5.tar.gz
> +sha256 ba45629abb7022949148ce65de4a59e7ee164d30c94450389a6afdd3ebe4e9e0 ruamel.yaml-0.18.5.tar.gz
Hmm, I get a different hash:
ruamel.yaml-0.18.5.tar.gz: OK (md5: 24fac3544a3c7bd7eeaf6e4f704a056e)
ERROR: while checking hashes from package/python-ruamel-yaml//python-ruamel-yaml.hash
ERROR: ruamel.yaml-0.18.5.tar.gz has wrong sha256 hash:
ERROR: expected: ba45629abb7022949148ce65de4a59e7ee164d30c94450389a6afdd3ebe4e9e0
ERROR: got : 61917e3a35a569c1133a8f772e1226961bf5a1198bea7e23f06a0841dea1ab0e
ERROR: Incomplete download, or man-in-the-middle (MITM) attack
Any ideas?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-02-05 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 5:31 [Buildroot] [PATCH 1/1] package/python-ruamel-yaml: bump to version 0.18.5 James Hilliard
2024-02-05 11:39 ` Peter Korsgaard [this message]
2024-02-05 13:18 ` Marcus Hoffmann via buildroot
2024-02-05 16:32 ` James Hilliard
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=87plxbta1d.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox