From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <tim.orling@konsulko.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 4/4] python3-zipp: upgrade 3.21.0 -> 3.23.0
Date: Fri, 08 Aug 2025 13:00:21 +0200 [thread overview]
Message-ID: <DBWZSZFJPU0Q.85U7OINILZ2R@bootlin.com> (raw)
In-Reply-To: <a3eb2194866253dce443cbdfe1815109f45c40aa.1754591996.git.tim.orling@konsulko.com>
On Thu Aug 7, 2025 at 8:44 PM CEST, Tim Orling via lists.openembedded.org wrote:
> From: Tim Orling <tim.orling@konsulko.com>
>
> License-Update: add copyright year; update to match SPDX license text
>
> v3.23.0
> * Features
> - Add a compatibility shim for Python 3.13 and earlier. (#145)
>
> v3.22.0
> * Features
> - Backported simplified tests from python/cpython#123424. (#142)
> * Bugfixes
> - Fixed .name, .stem, and other basename-based properties on Windows when
> working with a zipfile on disk. (#133)
>
> https://github.com/jaraco/zipp/blob/main/NEWS.rst#v3230
> https://github.com/jaraco/zipp/blob/main/NEWS.rst#v3220
>
> Comparing changes:
> https://github.com/jaraco/zipp/compare/v3.21.0...v3.23.0
>
> Signed-off-by: Tim Orling <tim.orling@konsulko.com>
> ---
Hi Tim,
Thanks for the patch.
It looks like this is breaking in several builds:
ERROR: lib32-python3-zipp-3.23.0-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/qemux86-world/build/build/tmp/work/x86-pokymllib32-linux/lib32-python3-zipp/3.23.0/temp/run.do_compile.3832240' failed with exit code 1
...
| ERROR Missing dependencies:
| coherent.licensed
https://autobuilder.yoctoproject.org/valkyrie/#/builders/59/builds/2177
https://autobuilder.yoctoproject.org/valkyrie/#/builders/111/builds/924
https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/2236
https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/2206
https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/2027
https://autobuilder.yoctoproject.org/valkyrie/#/builders/25/builds/2184
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2250
Can you have a look at this failure please?
Best regards,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-08-08 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 18:44 [PATCH 0/4] Recipe upgrades for 2025-08-07 tim.orling
2025-08-07 18:44 ` [PATCH 1/4] python3-maturin: upgrade 1.9.1 -> 1.9.3 tim.orling
2025-08-07 18:44 ` [PATCH 2/4] python3-cryptography{-vectors}: upgrade to 45.0.6 tim.orling
2025-08-07 18:44 ` [PATCH 3/4] python3-certifi: upgrade 2025.7.9 -> 2025.8.3 tim.orling
2025-08-07 18:44 ` [PATCH 4/4] python3-zipp: upgrade 3.21.0 -> 3.23.0 tim.orling
2025-08-08 11:00 ` Mathieu Dubois-Briand [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=DBWZSZFJPU0Q.85U7OINILZ2R@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tim.orling@konsulko.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.