https://bugzilla.redhat.com/show_bug.cgi?id=2251779
Bug ID: 2251779
Summary: python-zope-testrunner fails to build with Python
3.13: ImportError: cannot import name
'_start_new_thread' from 'threading'
Product: Fedora
Version: rawhide
Status: NEW
Component: python-zope-testrunner
Assignee: loganjerry(a)gmail.com
Reporter: ksurma(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: aurelien(a)bompard.org,
epel-packagers-sig(a)lists.fedoraproject.org,
infra-sig(a)lists.fedoraproject.org, ksurma(a)redhat.com,
loganjerry(a)gmail.com, mhroncok(a)redhat.com,
michel(a)michel-slm.name
Blocks: 2244836 (PYTHON3.13)
Target Milestone: ---
Classification: Fedora
python-zope-testrunner fails to build with Python 3.13.0a1.
This report is automated and not very verbose, but we'll try to get back here
with details.
+ python3 -m unittest discover -s zope/testrunner -t .
.........................................E
======================================================================
ERROR: zope.testrunner.tests.test_threadsupport
(unittest.loader._FailedTest.zope.testrunner.tests.test_threadsupport)
----------------------------------------------------------------------
ImportError: Failed to import test module:
zope.testrunner.tests.test_threadsupport
Traceback (most recent call last):
File "/usr/lib64/python3.13/unittest/loader.py", line 394, in _find_test_path
module = self._get_module_from_name(name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.13/unittest/loader.py", line 337, in
_get_module_from_name
__import__(name)
File
"/builddir/build/BUILDROOT/python-zope-testrunner-6.2-1.fc40.x86_64/usr/lib/python3.13/site-packages/zope/testrunner/tests/test_threadsupport.py",
line 16, in <module>
from threading import _start_new_thread
ImportError: cannot import name '_start_new_thread' from 'threading'
(/usr/lib64/python3.13/threading.py). Did you mean: '_start_joinable_thread'?
----------------------------------------------------------------------
Ran 42 tests in 0.014s
https://docs.python.org/3.13/whatsnew/3.13.html
For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.13/fedora-r…
For all our attempts to build python-zope-testrunner with Python 3.13, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/python-…
Testing and mass rebuild of packages is happening in copr.
You can follow these instructions to test locally in mock if your package
builds with Python 3.13:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/
Let us know here if you have any questions.
Python 3.13 is planned to be included in Fedora 41.
To make that update smoother, we're building Fedora packages with all
pre-releases of Python 3.13.
A build failure prevents us from testing all dependent packages (transitive
[Build]Requires),
so if this package is required a lot, it's important for us to get it fixed
soon.
We'd appreciate help from the people who know this package best,
but if you don't want to work on this now, let us know so we can try to work
around it on our side.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2244836
[Bug 2244836] Python 3.13
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2251779
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2271387
Bug ID: 2271387
Summary: python-tblib fails to build with Python 3.13:
traceback pointing characters changed
Product: Fedora
Version: rawhide
Status: NEW
Component: python-tblib
Assignee: quantum.analyst(a)gmail.com
Reporter: ksurma(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
ksurma(a)redhat.com, mhroncok(a)redhat.com,
michel(a)michel-slm.name,
python-packagers-sig(a)lists.fedoraproject.org,
quantum.analyst(a)gmail.com
Blocks: 2244836 (PYTHON3.13)
Target Milestone: ---
Classification: Fedora
python-tblib fails to build with Python 3.13.0a5.
____________________________ test_install[class-5]
_____________________________
tests/test_pickle_exception.py:95: in test_install
assert expected_format_exception ==
strip_locations(''.join(format_exception(type(exc), exc, exc.__traceback__)))
E assert 'Traceback (most recent call last):\n File
"/builddir/build/BUILD/tblib-3.0.0/tests/test_pickle_exception.py", line 47, in
test_install\n 1 / 0 # noqa: B018\nZeroDivisionError: division by
zero\n\nDuring handling of the above exception, another exception
occurred:\n\nTraceback (most recent call last):\n File
"/builddir/build/BUILD/tblib-3.0.0/tests/test_pickle_exception.py", line 50, in
test_install\n raise ValueError(\'blah\')\nValueError: blah\n\nThe above
exception was the direct cause of the following exception:\n\nTraceback (most
recent call last):\n File
"/builddir/build/BUILD/tblib-3.0.0/tests/test_pickle_exception.py", line 59, in
test_install\n raise new_e from e\ntest_pickle_exception.CustomError:
foo\nnote 1\nnote 2\n' == 'Traceback (most recent call last):\n File
"/builddir/build/BUILD/tblib-3.0.0/tests/test_pickle_exception.py", line 47, in
test_install\n 1 / 0 # noqa: B018\n ~~^~~~~\nZeroDivisionError: division
by zero\n\nDuring handling of the above exception, another exception
occurred:\n\nTraceback (most recent call last):\n File
"/builddir/build/BUILD/tblib-3.0.0/tests/test_pickle_exception.py", line 50, in
test_install\n raise ValueError(\'blah\')\n ^^^^^^^\nValueError:
blah\n\nThe above exception was the direct cause of the following
exception:\n\nTraceback (most recent call last):\n File
"/builddir/build/BUILD/tblib-3.0.0/tests/test_pickle_exception.py", line 59, in
test_install\n raise new_e from e\n
^^^^^^^^^^^\ntest_pickle_exception.CustomError: foo\nnote 1\nnote 2\n'
E Traceback (most recent call last):
E File
"/builddir/build/BUILD/tblib-3.0.0/tests/test_pickle_exception.py", line 47, in
test_install
E 1 / 0 # noqa: B018
E - ~~^~~~~
E ZeroDivisionError: division by zero
E
E During handling of the above exception, another exception occurred:
E
E Traceback (most recent call last):
E File
"/builddir/build/BUILD/tblib-3.0.0/tests/test_pickle_exception.py", line 50, in
test_install
E raise ValueError('blah')
E - ^^^^^^^
E ValueError: blah
E
E The above exception was the direct cause of the following exception:
E
E Traceback (most recent call last):
E File
"/builddir/build/BUILD/tblib-3.0.0/tests/test_pickle_exception.py", line 59, in
test_install
E raise new_e from e
E - ^^^^^^^^^^^
E test_pickle_exception.CustomError: foo
E note 1
E note 2
=========================== short test summary info
============================
FAILED tests/test_pickle_exception.py::test_install[global-1] - assert
'Trace...
FAILED tests/test_pickle_exception.py::test_install[global-2] - assert
'Trace...
FAILED tests/test_pickle_exception.py::test_install[global-3] - assert
'Trace...
FAILED tests/test_pickle_exception.py::test_install[global-4] - assert
'Trace...
FAILED tests/test_pickle_exception.py::test_install[global-5] - assert
'Trace...
FAILED tests/test_pickle_exception.py::test_install[instance-1] - assert
'Tra...
FAILED tests/test_pickle_exception.py::test_install[instance-2] - assert
'Tra...
FAILED tests/test_pickle_exception.py::test_install[instance-3] - assert
'Tra...
FAILED tests/test_pickle_exception.py::test_install[instance-4] - assert
'Tra...
FAILED tests/test_pickle_exception.py::test_install[instance-5] - assert
'Tra...
FAILED tests/test_pickle_exception.py::test_install[class-1] - assert
'Traceb...
FAILED tests/test_pickle_exception.py::test_install[class-2] - assert
'Traceb...
FAILED tests/test_pickle_exception.py::test_install[class-3] - assert
'Traceb...
FAILED tests/test_pickle_exception.py::test_install[class-4] - assert
'Traceb...
FAILED tests/test_pickle_exception.py::test_install[class-5] - assert
'Traceb...
======================== 15 failed, 28 passed in 0.92s
=========================
https://docs.python.org/3.13/whatsnew/3.13.html
For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.13/fedora-r…
For all our attempts to build python-tblib with Python 3.13, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/python-…
Testing and mass rebuild of packages is happening in copr.
You can follow these instructions to test locally in mock if your package
builds with Python 3.13:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/
Let us know here if you have any questions.
Python 3.13 is planned to be included in Fedora 41.
To make that update smoother, we're building Fedora packages with all
pre-releases of Python 3.13.
A build failure prevents us from testing all dependent packages (transitive
[Build]Requires),
so if this package is required a lot, it's important for us to get it fixed
soon.
We'd appreciate help from the people who know this package best,
but if you don't want to work on this now, let us know so we can try to work
around it on our side.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2244836
[Bug 2244836] Python 3.13
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2271387
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2263594
Bug ID: 2263594
Summary: python-dask-2024.2.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: python-dask
Keywords: FutureFeature, Triaged
Assignee: quantum.analyst(a)gmail.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
jonathan(a)almalinux.org,
python-packagers-sig(a)lists.fedoraproject.org,
quantum.analyst(a)gmail.com
Target Milestone: ---
Classification: Fedora
Releases retrieved: 2024.2.0
Upstream release that is considered latest: 2024.2.0
Current version/release in rawhide: 2024.1.1-1.fc40~bootstrap
URL: https://github.com/dask/dask/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_M…
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from Anitya:
https://release-monitoring.org/project/18909/
To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-dask
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2263594
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2283772
Bug ID: 2283772
Summary: CVE-2024-4741 openssl3: openssl: Use After Free with
SSL_free_buffers [epel-8]
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: openssl3
Keywords: Security, SecurityTracking
Severity: high
Priority: high
Assignee: michel(a)michel-slm.name
Reporter: ybuenos(a)redhat.com
CC: epel-packagers-sig(a)lists.fedoraproject.org,
michel(a)michel-slm.name
Target Milestone: ---
Classification: Fedora
More information about this security flaw is available in the following bug:
http://bugzilla.redhat.com/show_bug.cgi?id=2283757
Disclaimer: Community trackers are created by Red Hat Product Security team on
a best effort basis. Package maintainers are required to ascertain if the flaw
indeed affects their package, before starting the update process.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2283772
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2256773
Bug ID: 2256773
Summary: OpenImageIO with OpenColorIO
Product: Fedora EPEL
Version: epel9
Status: NEW
Component: OpenImageIO
Assignee: hobbes1069(a)gmail.com
Reporter: manuel.rais(a)nousvoir.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
hobbes1069(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
OpenImageIO is build without OpenColorIO support
Version-Release number of selected component (if applicable):
How reproducible:
oiiotool -help : the command output shows No OpenColorIO, color config:
built-in
Steps to Reproduce:
1.
2.
3.
Actual results:
oiiotool cannot use Opencolor profile to change image colors
Expected results:
oiiotool should read opencolor profiles
Additional info:
In this folder
https://github.com/AcademySoftwareFoundation/OpenImageIO/tree/master/src/bu…,
several bash scripts can be found to build OpenImageIO dependencies.
https://github.com/AcademySoftwareFoundation/OpenImageIO/blob/master/src/bu…
is one of them.
I've tested to build locally and it works.
Is it possible to add this feature to OpenImageIO rpm package ?
Thanks
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2256773
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2283521
Bug ID: 2283521
Summary: python-rasterio fails to build with Python 3.13:
test_create_sidecar_mask and test_update_tags fail
Product: Fedora
Version: rawhide
Status: NEW
Component: python-rasterio
Assignee: quantum.analyst(a)gmail.com
Reporter: ksurma(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
jonathan(a)almalinux.org, ksurma(a)redhat.com,
mhroncok(a)redhat.com,
python-packagers-sig(a)lists.fedoraproject.org,
quantum.analyst(a)gmail.com
Blocks: 2244836 (PYTHON3.13)
Target Milestone: ---
Classification: Fedora
python-rasterio fails to build with Python 3.13.0b1.
___________________________ test_create_sidecar_mask
___________________________
data = local('/tmp/pytest-of-mockbuild/pytest-0/test_create_sidecar_mask0')
def test_create_sidecar_mask(data):
"""Write a .msk sidecar mask."""
with rasterio.open(str(data.join('RGB.byte.tif')), 'r+') as dst:
blue = dst.read(1, masked=False)
mask = 255 * (blue == 0).astype('uint8')
dst.write_mask(mask)
# There should be a .msk file in this case.
assert data.join('RGB.byte.tif').exists()
> assert data.join('RGB.byte.tif.msk').exists()
E AssertionError: assert False
E + where False = <bound method LocalPath.exists of
local('/tmp/pytest-of-mockbuild/pytest-0/test_create_sidecar_mask0/RGB.byte.tif.msk')>()
E + where <bound method LocalPath.exists of
local('/tmp/pytest-of-mockbuild/pytest-0/test_create_sidecar_mask0/RGB.byte.tif.msk')>
=
local('/tmp/pytest-of-mockbuild/pytest-0/test_create_sidecar_mask0/RGB.byte.tif.msk').exists
E + where
local('/tmp/pytest-of-mockbuild/pytest-0/test_create_sidecar_mask0/RGB.byte.tif.msk')
= <bound method LocalPath.join of
local('/tmp/pytest-of-mockbuild/pytest-0/test_create_sidecar_mask0')>('RGB.byte.tif.msk')
E + where <bound method LocalPath.join of
local('/tmp/pytest-of-mockbuild/pytest-0/test_create_sidecar_mask0')> =
local('/tmp/pytest-of-mockbuild/pytest-0/test_create_sidecar_mask0').join
tests/test_mask_creation.py:44: AssertionError
------------------------------ Captured log call
-------------------------------
DEBUG rasterio._env:env.py:326 GDAL data files are available at built-in
paths.
DEBUG rasterio._env:env.py:326 PROJ data files are available at built-in
paths.
DEBUG rasterio._env:env.py:326 Started GDALEnv: self=<rasterio._env.GDALEnv
object at 0x7f381ad60a60>.
DEBUG rasterio._env:env.py:362 Stopped GDALEnv <rasterio._env.GDALEnv object
at 0x7f381ad60a60>.
DEBUG rasterio._env:env.py:326 GDAL data files are available at built-in
paths.
DEBUG rasterio._env:env.py:326 PROJ data files are available at built-in
paths.
DEBUG rasterio._env:env.py:326 Started GDALEnv: self=<rasterio._env.GDALEnv
object at 0x7f381ad60f10>.
DEBUG rasterio._env:env.py:362 Stopped GDALEnv <rasterio._env.GDALEnv object
at 0x7f381ad60f10>.
_______________________________ test_update_tags
_______________________________
data = local('/tmp/pytest-of-mockbuild/pytest-0/test_update_tags0')
@pytest.mark.gdalbin
def test_update_tags(data):
tiffname = str(data.join('RGB.byte.tif'))
with rasterio.open(tiffname, 'r+') as f:
f.update_tags(a='1', b='2')
f.update_tags(1, c=3)
with pytest.raises(IndexError):
f.update_tags(4, d=4)
assert f.tags() == {'AREA_OR_POINT': 'Area', 'a': '1', 'b': '2'}
assert ('c', '3') in f.tags(1).items()
info = subprocess.check_output(["gdalinfo", tiffname]).decode('utf-8')
> assert re.search(r'Metadata:\W+a=1\W+AREA_OR_POINT=Area\W+b=2', info)
E AssertionError: assert None
E + where None = <function search at
0x7f384bcf0a40>('Metadata:\\W+a=1\\W+AREA_OR_POINT=Area\\W+b=2', 'Driver:
GTiff/GeoTIFF\nFiles:
/tmp/pytest-of-mockbuild/pytest-0/test_update_tags0/RGB.byte.tif\nSize is 791,
718\nCoo...CS_MAXIMUM=255\n STATISTICS_MEAN=48.113056354743\n
STATISTICS_MINIMUM=0\n STATISTICS_STDDEV=60.112778509941\n')
E + where <function search at 0x7f384bcf0a40> = re.search
tests/test_update.py:23: AssertionError
------------------------------ Captured log call
-------------------------------
DEBUG rasterio._env:env.py:326 GDAL data files are available at built-in
paths.
DEBUG rasterio._env:env.py:326 PROJ data files are available at built-in
paths.
DEBUG rasterio._env:env.py:326 Started GDALEnv: self=<rasterio._env.GDALEnv
object at 0x7f381c1a0670>.
DEBUG rasterio._env:env.py:362 Stopped GDALEnv <rasterio._env.GDALEnv object
at 0x7f381c1a0670>.
DEBUG rasterio._env:env.py:326 GDAL data files are available at built-in
paths.
DEBUG rasterio._env:env.py:326 PROJ data files are available at built-in
paths.
DEBUG rasterio._env:env.py:326 Started GDALEnv: self=<rasterio._env.GDALEnv
object at 0x7f381bf085e0>.
INFO rasterio._env:test_update.py:19 GDAL signalled an error: err_no=5,
msg='RGB.byte.tif: GDALDataset::GetRasterBand(4) - Illegal band #\n'
DEBUG rasterio._env:env.py:362 Stopped GDALEnv <rasterio._env.GDALEnv object
at 0x7f381bf085e0>.
https://docs.python.org/3.13/whatsnew/3.13.html
For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.13/fedora-r…
For all our attempts to build python-rasterio with Python 3.13, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/python-…
Testing and mass rebuild of packages is happening in copr.
You can follow these instructions to test locally in mock if your package
builds with Python 3.13:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/
Let us know here if you have any questions.
Python 3.13 is planned to be included in Fedora 41.
To make that update smoother, we're building Fedora packages with all
pre-releases of Python 3.13.
A build failure prevents us from testing all dependent packages (transitive
[Build]Requires),
so if this package is required a lot, it's important for us to get it fixed
soon.
We'd appreciate help from the people who know this package best,
but if you don't want to work on this now, let us know so we can try to work
around it on our side.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2244836
[Bug 2244836] Python 3.13
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2283521
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2279882
Bug ID: 2279882
Summary: There is no LibRaw-devel-0.21.1-1.el9 in aarch64
repositories
Product: Fedora EPEL
Version: epel9
Hardware: aarch64
OS: Linux
Status: NEW
Component: LibRaw-epel
Severity: medium
Assignee: ngompa13(a)gmail.com
Reporter: yaroslav(a)fedevych.name
CC: epel-packagers-sig(a)lists.fedoraproject.org,
michel(a)michel-slm.name, ngompa13(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
There are in fact two bugs. First, there is LibRaw-0.21.1-1.el9 package, but
the corresponding -devel package is of version 0.20.2-0.el9.6. Second, the
-devel package has the symlink /usr/lib64/libraw_r.so which it shouldn't have,
and it's broken as it points to nonexistent libraw_r.so.20.0.0 — but there is
libraw_r.so.23.0.0.
This breaks linking all things that want to link against libraw_r.
Version-Release number of selected component (if applicable):
0.21.1-1.el9, 0.20.2-0.el9.6
How reproducible:
As of 2024-05-09, always.
Steps to Reproduce:
1. Try to rebuild ImageMagick for CentOS Stream 9 in mock for aarch64.
Actual results:
The package fails to build with the linker unable to find -lraw_r.
Expected results:
The package builds correctly.
Additional info:
This doesn't happen on x86_64 as the base and -devel packages are of the same
version there.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2279882
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…