Update on this error. Following merged patch has fixed this issue. I did the git pull locally to get these changes and rebased my patch to include this. Patch: 970038: Migrate upper functional job to Python 3.13 | https://review.opendev.org/c/openstack/cinder/+/970038 Migrate upper functional job to Python 3.13 ... because Python 3.13 is now part of the tested runtimes. Note that installation of PCRE(3) package is now limited to doc profile because it's required by whereto, which is used only in doc target of tox. This is required because the package is no longer available in Debian Trixie . Depends-on: https://review.opendev.org/960639 Change-Id: I7c27dde32dde0d6f62041963d920f4b626d90c2e Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com> Regards, Nimesh Desai From: Takashi Kajinami <kajinamit@oss.nttdata.com> Date: Wednesday, 21 January 2026 at 8:42 PM To: Stephen Finucane <stephenfin@redhat.com>, Pierre Riteau <pierre@stackhpc.com>, Nimesh Desai <Nimesh.Desai@ibm.com> Cc: openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org> Subject: [EXTERNAL] Re: Zuul failures for openstack-tox-py313 Just in case anyone is wondering why we are seeing similar failures now ... After we had some discussions during the attempt to add py313 functional tests, we decided to migrate the existing py313 unit tests (aka openstack-tox-py313) from Ubuntu Noble to Debian Trixie so that we can use the python package built and provided by distribution (Python 3.13 is the default python in Trixie). Using the OS package is more efficient than using pyenv to build the required version of python runtime and helps us save CI resources. Please pay some attention to py313 job for a while. In case you see any failure during bindep task that indicates that you have to update bindep.txt. I spent some time to replace obsolete pcre3 package and have been taking care of it but there might be a few other problems I've not yet noticed. On 1/21/26 9:40 PM, Stephen Finucane wrote:
That was my patch so I'd like to highlight that I've abandoned that in favour of https://review.opendev.org/c/openstack/python-openstackclient/+/974019 <https://review.opendev.org/c/openstack/python-openstackclient/+/974019 > which is a more future-proof approach.
Stephen
On Wed, 2026-01-21 at 11:08 +0100, Pierre Riteau wrote:
Hi,
This has been experienced by many OpenStack projects in the past few days. You just need to adjust bindep to handle the lack of this package on Debian Trixie. See an example here: https://review.opendev.org/c/openstack/python-openstackclient/+/973973 <https://review.opendev.org/c/openstack/python-openstackclient/+/973973 >
Cheers, Pierre Riteau (priteau)
On Wed, 21 Jan 2026 at 07:26, Nimesh Desai <Nimesh.Desai@ibm.com <mailto:Nimesh.Desai@ibm.com>> wrote:
Hi, I am observing following error in the zuul run the given patch. There have been no changes in this patch recently, but zuul started failing for this package error.
Is this also seen in other patches?
Patch: [IBM SVf Driver] Define meaningful names for error constants | https://review.opendev.org/c/openstack/cinder/+/959683 <https://review.opendev.org/c/openstack/cinder/+/959683 > Zuul target: openstack-tox-py313 Zuul error: https://zuul.opendev.org/t/openstack/build/9491515d2dbb473c922ba1e3ba13b19b <https://zuul.opendev.org/t/openstack/build/9491515d2dbb473c922ba1e3ba13b19b >
*No package matching 'libpcre3-dev' is available*
2026-01-19 03:30:29.510623 | TASK [bindep : Install distro packages from bindep] 2026-01-19 03:30:31.956565 | debian-trixie | ERROR 2026-01-19 03:30:31.956930 | debian-trixie | { 2026-01-19 03:30:31.957003 | debian-trixie | "msg": "No package matching 'libpcre3-dev' is available" 2026-01-19 03:30:31.957062 | debian-trixie | }
Regards,
Nimesh Desai