From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Manuel Diener <manuel.diener@oss.othermo.de>
Cc: buildroot@buildroot.org, James Hilliard <james.hilliard1@gmail.com>
Subject: Re: [Buildroot] [PATCH 2/3] package/python-pydantic-core: bump to version 2.46.3
Date: Tue, 28 Apr 2026 21:39:23 +0200 [thread overview]
Message-ID: <bf650d16faa9e9732306bcd50e2f7d8d@free.fr> (raw)
In-Reply-To: <20260428073542.1027653-2-manuel.diener@oss.othermo.de>
Hi Manuel,
Thanks for the patch. I have a comment, see below.
On 28/04/2026 09:35, Manuel Diener wrote:
> Signed-off-by: Manuel Diener <manuel.diener@oss.othermo.de>
> ---
> package/python-pydantic-core/python-pydantic-core.hash | 2 +-
> package/python-pydantic-core/python-pydantic-core.mk | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/package/python-pydantic-core/python-pydantic-core.hash
> b/package/python-pydantic-core/python-pydantic-core.hash
> index 61775e5522..c1a77fdb47 100644
> --- a/package/python-pydantic-core/python-pydantic-core.hash
> +++ b/package/python-pydantic-core/python-pydantic-core.hash
> @@ -1,4 +1,4 @@
> # Locally calculated after vendoring
> -sha256
> cc643029337df7a2e90799cedbd75fef0636c6a467e74d22f4dfec4c1959359e
> python-pydantic-core-2.41.5-cargo5.tar.gz
> +sha256
> 0b4e5e3e499cbc2d23ab37206fffd0d3ce2f935e7f005e1fa8ef934ade26704a
> python-pydantic-core-2.46.3-cargo4.tar.gz
This patch removes a cargo5 hash to replace it with a cargo4.
Running command:
make python-pydantic-core-source
fails with:
ERROR: No hash found for python-pydantic-core-2.46.3-cargo5.tar.gz
BR_FMT_VERSION_cargo was updated to -cargo5 in commit
https://gitlab.com/buildroot.org/buildroot/-/commit/f1f96c1ad006c9a65ac39b500ccd1c8581dd2fc5
Could you send an updated patch with the correct cargo5
hash, please?
> # Locally computed sha256 checksums
> sha256
> 2afdd30d54b4d62b6f488a6bcc1546e84ec5061f13f4209c03d012348783795a
> LICENSE
[...]
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-04-28 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 7:35 [Buildroot] [PATCH 1/3] package/python-pydantic: bump to version 2.13.3 Manuel Diener
2026-04-28 7:35 ` [Buildroot] [PATCH 2/3] package/python-pydantic-core: bump to version 2.46.3 Manuel Diener
2026-04-28 19:39 ` Julien Olivain via buildroot [this message]
2026-04-29 11:46 ` [Buildroot] [PATCH v2] " Manuel Diener
2026-04-29 20:55 ` Julien Olivain via buildroot
2026-04-28 7:35 ` [Buildroot] [PATCH 3/3] package/python-pydantic-settings: bump to version 2.14.0 Manuel Diener
2026-04-29 20:53 ` [Buildroot] [PATCH 1/3] package/python-pydantic: bump to version 2.13.3 Julien Olivain 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=bf650d16faa9e9732306bcd50e2f7d8d@free.fr \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=ju.o@free.fr \
--cc=manuel.diener@oss.othermo.de \
/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