Bug 2319698 - python-pyemd fails to build with setuptools 74+
Summary: python-pyemd fails to build with setuptools 74+
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pyemd
Version: 42
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2372059 (view as bug list)
Depends On:
Blocks: F42FTBFS PYTHON3.14 F43FTBFS F43FailsToInstall SETUPTOOLS74 NUMPY2 2333956 2372070
TreeView+ depends on / blocked
 
Reported: 2024-10-18 10:12 UTC by Miro Hrončok
Modified: 2025-08-05 15:34 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-08-05 15:33:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github wmayner pyemd issues 68 0 None open Numpy 2.1: Changed value for emd_samples -- unit tests fail 2025-01-11 11:28:33 UTC

Description Miro Hrončok 2024-10-18 10:12:53 UTC
Dear package maintainer,

this bugzilla is automated becasue the number of impacted packages it too high to go trough manually.

It appears that your package failed to build with setuptools 74.1.3 and wheel 0.44 in

  https://copr.fedorainfracloud.org/coprs/churchyard/setuptools-74/package/python-pyemd/

While it succeeded with setuptools 69.2.0 and wheel 0.43 in

  https://copr.fedorainfracloud.org/coprs/churchyard/setuptools-control/package/python-pyemd/

This usually means this package fails to build with setuptools 74+

We plan to update setuptools to version 74 or newer in Fedora 42. This is an approved Fedora 42 Change:

  https://fedoraproject.org/wiki/Changes/Setuptools_74+



Please analyze the failure and fix it in rawhide. Thanks.


You can use the builds from the churchyard/setuptools-74 copr for local testing.

  mock -r fedora-rawhide-x86_64 --addrepo 'https://download.copr.fedorainfracloud.org/results/churchyard/setuptools-74/fedora-rawhide-$basearch/'


One of the most common problems is that the setup.py test command cannot be used. If that is the case here, run the tests in %check differently, e.g. via %pytest, %tox, %{python3} -m unittest, etc.


If you need help, reach out to me in this bugzilla.

Comment 1 Miro Hrončok 2024-10-29 10:58:39 UTC
I plan to update setuptools to 74.x in rawhide this week.

At that point, this package will fail to build from source if not fixed.

Comment 2 Ankur Sinha (FranciscoD) 2024-10-29 11:15:13 UTC
Sure, we'll the FTBFS once it's filed.

Comment 3 Ankur Sinha (FranciscoD) 2024-10-29 11:15:41 UTC
We'll *fix* the FTBFS once it's filed..

Comment 4 Miro Hrončok 2024-12-10 14:56:07 UTC
+ /usr/bin/pytest
============================= test session starts ==============================
platform linux -- Python 3.13.1, pytest-8.3.4, pluggy-1.5.0 -- /usr/bin/python3
cachedir: .pytest_cache
rootdir: /builddir/build/BUILD/python-pyemd-1.0.0-build/pyemd-1.0.0
configfile: pytest.ini
collecting ... collected 36 items

README.rst::README.rst PASSED                                            [  2%]
test/test_pyemd.py::test_emd_1 PASSED                                    [  5%]
test/test_pyemd.py::test_emd_2 PASSED                                    [  8%]
test/test_pyemd.py::test_emd_3 Fatal Python error: Aborted

Current thread 0x00007fed2c842740 (most recent call first):
  File "/builddir/build/BUILD/python-pyemd-1.0.0-build/pyemd-1.0.0/test/test_pyemd.py", line 49 in test_emd_3
  File "/usr/lib/python3.13/site-packages/_pytest/python.py", line 159 in pytest_pyfunc_call
  File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 103 in _multicall
  File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 513 in __call__
  File "/usr/lib/python3.13/site-packages/_pytest/python.py", line 1627 in runtest
  File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 174 in pytest_runtest_call
  File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 103 in _multicall
  File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 513 in __call__
  File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 242 in <lambda>
  File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 341 in from_call
  File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 241 in call_and_report
  File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 132 in runtestprotocol
  File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 113 in pytest_runtest_protocol
  File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 103 in _multicall
  File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 513 in __call__
  File "/usr/lib/python3.13/site-packages/_pytest/main.py", line 362 in pytest_runtestloop
  File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 103 in _multicall
  File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 513 in __call__
  File "/usr/lib/python3.13/site-packages/_pytest/main.py", line 337 in _main
  File "/usr/lib/python3.13/site-packages/_pytest/main.py", line 283 in wrap_session
  File "/usr/lib/python3.13/site-packages/_pytest/main.py", line 330 in pytest_cmdline_main
  File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 103 in _multicall
  File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 513 in __call__
  File "/usr/lib/python3.13/site-packages/_pytest/config/__init__.py", line 175 in main
  File "/usr/lib/python3.13/site-packages/_pytest/config/__init__.py", line 201 in console_main
  File "/usr/bin/pytest", line 8 in <module>

Extension modules: numpy.core._multiarray_umath, numpy.core._multiarray_tests, numpy.linalg._umath_linalg, numpy.fft._pocketfft_internal, numpy.random._common, numpy.random.bit_generator, numpy.random._bounded_integers, numpy.random._mt19937, numpy.random.mtrand, numpy.random._philox, numpy.random._pcg64, numpy.random._sfc64, numpy.random._generator, pyemd.emd (total: 14)
/var/tmp/rpm-tmp.gaGyFL: line 54:   318 Aborted                 (core dumped) CFLAGS="${CFLAGS:-${RPM_OPT_FLAGS}}" LDFLAGS="${LDFLAGS:-${RPM_LD_FLAGS}}" PATH="/builddir/build/BUILD/python-pyemd-1.0.0-build/BUILDROOT/usr/bin:$PATH" PYTHONPATH="${PYTHONPATH:-/builddir/build/BUILD/python-pyemd-1.0.0-build/BUILDROOT/usr/lib64/python3.13/site-packages:/builddir/build/BUILD/python-pyemd-1.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages}" PYTHONDONTWRITEBYTECODE=1 PYTEST_ADDOPTS="${PYTEST_ADDOPTS:-} --ignore=/builddir/build/BUILD/python-pyemd-1.0.0-build/pyemd-1.0.0/.pyproject-builddir" PYTEST_XDIST_AUTO_NUM_WORKERS="${PYTEST_XDIST_AUTO_NUM_WORKERS:-2}" /usr/bin/pytest



This failure is unexpected for the setuptools update :/

Comment 5 Sandro 2025-01-11 11:28:34 UTC
The latest failure appears to be NumPy 2.x related. The setuptools issue will resurface once (if) the NumPy issue gets fixed.

Since upstream appears to be inactive, looking at the impact, only `python-pyphi` depends on it.

Comment 6 Aoife Moloney 2025-02-26 13:13:22 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 7 Karolina Surma 2025-06-11 16:02:33 UTC
*** Bug 2372059 has been marked as a duplicate of this bug. ***

Comment 8 Fedora Fails To Install 2025-06-20 19:49:08 UTC
This package has been orphaned.

You can pick it up at https://src.fedoraproject.org/rpms/python-pyemd by clicking button "Take". If nobody picks it up, it will be retired and removed from a distribution.

Comment 9 Fedora Release Engineering 2025-06-22 04:22:15 UTC
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 42.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2024-12-13).

A week before the mass branching of Fedora 43 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 41 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html

Comment 10 Fedora Release Engineering 2025-07-13 04:22:12 UTC
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 42.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2024-12-13).

A week before the mass branching of Fedora 43 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 41 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html

Comment 11 Fedora Release Engineering 2025-08-03 04:22:09 UTC
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 42.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2024-12-13).

A week before the mass branching of Fedora 43 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 41 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html

Comment 12 Fedora Fails To Install 2025-08-05 15:33:55 UTC
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

All subpackages of a package against which this bug was filled are now installable or removed from Fedora 43.

Thanks for taking care of it!


Note You need to log in before you can comment on or make changes to this bug.