From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Jaipaul Cheernam" <jaipaul.cheernam@est.tech>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 11/12] python3-pycryptodome: upgrade 3.24.1 -> 4.2.0
Date: Tue, 27 Oct 2026 09:16:44 +0100 [thread overview]
Message-ID: <DMFH04O6U4SD.23GTK0R8VRCA2@bootlin.com> (raw)
In-Reply-To: <20261026103138.3137-11-jaipaul.cheernam@est.tech>
On Mon Oct 26, 2026 at 11:31 AM CET, Jaipaul Cheernam wrote:
> From: Upgrade Helper <auh@yoctoproject.org>
>
> ChangeLog: https://www.pycryptodome.org/src/changelog#october-2026
> https://github.com/Legrandin/pycryptodome/blob/v4.2.0/Changelog.rst#420-24-october-2026
>
> License-Update: Update to license text [1], [2] and [3]
>
> [1] https://github.com/Legrandin/pycryptodome/commit/65aa57f08db0afb1a3d3887164a0027654b55931
> [2] https://github.com/Legrandin/pycryptodome/commit/43b28d7170ccebfc51c9148e723aa881fb32a1dc
> [3] https://github.com/Legrandin/pycryptodome/commit/04a1ad1d286eb843ac62abfc05ed58df99eaf27b
>
> Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> ---
Hi Jaipaul,
Thanks for your patch.
Should you upgrade the pycryptodomex recipe at the same time? Both
recipes include python-pycryptodome.inc, so now we have a QA error:
NOTE: recipe python3-pycryptodomex-3.24.1-r0: task do_populate_lic: Started
ERROR: python3-pycryptodomex-3.24.1-r0 do_populate_lic: QA Issue: python3-pycryptodomex: The LIC_FILES_CHKSUM does not match for file://LICENSE.rst;md5=a514b4a7ad24677ae50f3becb03404e3
python3-pycryptodomex: The new md5 checksum is 29242a70410a4eeff488a28164e7ab93
python3-pycryptodomex: Here is the selected license text:
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/4922
Can you have a look at the issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-10-27 8:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 10:31 [PATCH 01/12] libsoup: upgrade 3.8.0 -> 3.8.1 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 02/12] libsolv: upgrade 0.7.40 -> 0.7.41 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 03/12] patch: upgrade 2.8 -> 2.8.1 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 04/12] python3-certifi: upgrade 2026.10.19 -> 2026.10.23 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 05/12] python3-cython: upgrade 3.2.9 -> 3.3.0 Jaipaul Cheernam
2026-10-27 8:11 ` [OE-core] " Mathieu Dubois-Briand
2026-10-27 11:19 ` Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 06/12] python3-hypothesis: upgrade 6.169.0 -> 6.170.9 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 07/12] valgrind: upgrade 3.27.1 -> 3.28.0 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 08/12] librsvg: upgrade 2.63.3 -> 2.63.4 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 09/12] libslirp: upgrade 4.9.5 -> 4.9.6 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 10/12] python3-jsonpointer: upgrade 3.4 -> 3.5 Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 11/12] python3-pycryptodome: upgrade 3.24.1 -> 4.2.0 Jaipaul Cheernam
2026-10-26 10:51 ` Patchtest results for " patchtest
2026-10-26 10:57 ` [PATCH v2] " Jaipaul Cheernam
2026-10-27 8:16 ` Mathieu Dubois-Briand [this message]
2026-10-27 8:45 ` [OE-core] [PATCH 11/12] " Jaipaul Cheernam
2026-10-26 10:31 ` [PATCH 12/12] python3-wcwidth: upgrade 0.9.1 -> 0.9.4 Jaipaul Cheernam
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=DMFH04O6U4SD.23GTK0R8VRCA2@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=jaipaul.cheernam@est.tech \
--cc=openembedded-core@lists.openembedded.org \
/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