From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jesse Taube <mr.bossman075@gmail.com>
Cc: buildroot@buildroot.org, Marcus Hoffmann <buildroot@bubu1.eu>
Subject: Re: [Buildroot] [PATCH 1/2] package/picotool, pico-sdk: Bump version to 2.1.1
Date: Tue, 6 Jan 2026 22:09:50 +0100 [thread overview]
Message-ID: <20260106220950.309a96ad@windsurf> (raw)
In-Reply-To: <20250805000352.4062434-1-Mr.Bossman075@gmail.com>
Hello Jesse,
Sorry for the delay in getting back to you.
On Mon, 4 Aug 2025 20:03:51 -0400
Jesse Taube <mr.bossman075@gmail.com> wrote:
> pico-sdk and picotool 2.x.x adds support for the rp2350 bump package to
> latest version.
>
> Signed-off-by: Jesse Taube <Mr.Bossman075@gmail.com>
This commit breaks the download:
ERROR: while checking hashes from package/pico-sdk/pico-sdk.hash
ERROR: pico-sdk-2.1.1.tar.gz has wrong sha256 hash:
ERROR: expected: 979af5c5aa5a07990544bc65e24a2121c096abd72ad0e6a03e7c524302e0f26e
ERROR: got : 179c5531e75ac7f82d0679e70b6e8881f871738dc0ef17baf3b4ff4679291c41
ERROR: Incomplete download, or man-in-the-middle (MITM) attack
Also, I'll reply to PATCH 2/2, because I'm not sure it should be a
separate patch.
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
prev parent reply other threads:[~2026-01-06 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 0:03 [Buildroot] [PATCH 1/2] package/picotool, pico-sdk: Bump version to 2.1.1 Jesse Taube
2025-08-05 0:03 ` [Buildroot] [PATCH 2/2] package/pico-sdk: Clone submodules for picotool Jesse Taube
2026-01-06 21:12 ` Thomas Petazzoni via buildroot
2026-01-12 21:20 ` Jesse T
2026-01-06 21:09 ` Thomas Petazzoni via buildroot [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=20260106220950.309a96ad@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@bubu1.eu \
--cc=mr.bossman075@gmail.com \
--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.