NLopt fails to build with Python 3.13.0a2. /builddir/build/BUILD/nlopt-2.7.1/redhat-linux-build/src/swig/CMakeFiles/nlopt_python.dir/nloptPYTHON_wrap.cxx: In function ‘double func_python(unsigned int, const double*, double*, void*)’: /builddir/build/BUILD/nlopt-2.7.1/redhat-linux-build/src/swig/CMakeFiles/nlopt_python.dir/nloptPYTHON_wrap.cxx:5103:22: error: ‘PyEval_CallObject’ was not declared in this scope; did you mean ‘PyObject_CallObject’? 5103 | PyObject *result = PyEval_CallObject((PyObject *) f, arglist); | ^~~~~~~~~~~~~~~~~ | PyObject_CallObject /builddir/build/BUILD/nlopt-2.7.1/redhat-linux-build/src/swig/CMakeFiles/nlopt_python.dir/nloptPYTHON_wrap.cxx: In function ‘void mfunc_python(unsigned int, double*, unsigned int, const double*, double*, void*)’: /builddir/build/BUILD/nlopt-2.7.1/redhat-linux-build/src/swig/CMakeFiles/nlopt_python.dir/nloptPYTHON_wrap.cxx:5140:19: error: ‘PyEval_CallObject’ was not declared in this scope; did you mean ‘PyObject_CallObject’? 5140 | PyObject *res = PyEval_CallObject((PyObject *) f, arglist); | ^~~~~~~~~~~~~~~~~ | PyObject_CallObject According to https://docs.python.org/3.13/whatsnew/3.13.html: Remove PyEval_CallObject(), PyEval_CallObjectWithKeywords(): use PyObject_CallNoArgs() or PyObject_Call() instead. Warning: PyObject_Call() positional arguments must be a tuple and must not be NULL, keyword arguments must be a dict or NULL, whereas removed functions checked arguments type and accepted NULL positional and keyword arguments. To replace PyEval_CallObjectWithKeywords(func, NULL, kwargs) with PyObject_Call(), pass an empty tuple as positional arguments using PyTuple_New(0). 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-rawhide-x86_64/06766197-NLopt/ For all our attempts to build NLopt with Python 3.13, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/NLopt/ 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.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle. Changing version to 40.
*** Bug 2291478 has been marked as a duplicate of this bug. ***
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/ This package fails to install and maintainers are advised to take one of the following actions: - Fix this bug and close this bugzilla once the update makes it to the repository. (The same script that posted this comment will eventually close this bugzilla when the fixed package reaches the repository, so you don't have to worry about it.) or - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet. or - Orphan the package if you no longer plan to maintain it. If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue. This package may be orphaned in 7+ weeks. This is the first reminder (step 3) from the policy. Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.
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/ This package fails to install and maintainers are advised to take one of the following actions: - Fix this bug and close this bugzilla once the update makes it to the repository. (The same script that posted this comment will eventually close this bugzilla when the fixed package reaches the repository, so you don't have to worry about it.) or - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet. or - Orphan the package if you no longer plan to maintain it. If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue. This package may be orphaned in 4+ weeks. This is the second reminder (step 4) from the policy. Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.
This package has been orphaned. You can pick it up at https://src.fedoraproject.org/rpms/NLopt by clicking button "Take". If nobody picks it up, it will be retired and removed from a distribution.
This should be an issue on swig side. Seems later swig support python3.13, but they haven't made a release for it yet, and I have bad blood with them so they would not be listening to me.
I don't think so... $ fedpkg clone NLopt $ cd NLopt [NLopt (rawhide)]$ fedpkg prep [NLopt (rawhide %)]$ cd nlopt-2.7.1 [nlopt-2.7.1 (rawhide %)]$ rg PyEval_CallObject src/swig/nlopt-python.i 137: PyObject *result = PyEval_CallObject((PyObject *) f, arglist); 174: PyObject *res = PyEval_CallObject((PyObject *) f, arglist); This needs to be corrected in src/swig/nlopt-python.i
Oh ok I'll open an issue for that then
Resolved in https://github.com/stevengj/nlopt/commit/d716820578d226976fbb4fa68478758dad1c79b0 benson_muite
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
I'm going to assume you plan to fix it.
This package has failed to build with Python 3.13 so far. Fedora 41 is already in the Beta Freeze phase. What's your plan going forward? Will the package be fixed in time for the Final Freeze of Fedora 41 (planned on Oct 15th 2024)? If you don't plan or can't fix the package before Fedora 41 goes into the Final Freeze phase, please retire the package. You can unretire it anytime during the Fedora 41 lifecycle - doing this now will simply ensure that we don't release Fedora with a broken package. Thank you!
Trying with the fix at https://github.com/stevengj/nlopt/issues/565
Fixed https://src.fedoraproject.org/rpms/NLopt/tree/f56cb68889eb55ee40e16c5dcd0119d1dac836db
FEDORA-2024-ac73e736a3 (NLopt-2.8.0^202409167cdebfe-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ac73e736a3
FEDORA-2024-ac73e736a3 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-ac73e736a3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-ac73e736a3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-ac73e736a3 (NLopt-2.8.0^202409167cdebfe-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.