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/ Your package (Mayavi) Fails To Install in Fedora 41: can't install python3-mayavi: - nothing provides python3.12dist(numpy) needed by python3-mayavi-4.8.2-1.fc41.x86_64 - nothing provides python3.12dist(packaging) needed by python3-mayavi-4.8.2-1.fc41.x86_64 - nothing provides python3.12dist(pygments) needed by python3-mayavi-4.8.2-1.fc41.x86_64 - nothing provides python(abi) = 3.12 needed by python3-mayavi-4.8.2-1.fc41.x86_64 If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock: $ mock -r fedora-41-x86_64 --config-opts mirrored=False install python3-mayavi P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages Thanks!
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.
Fails to build with: /var/tmp/rpm-tmp.X20HP0: line 52: 251 Segmentation fault (core dumped) CFLAGS="${CFLAGS:-${RPM_OPT_FLAGS}}" LDFLAGS="${LDFLAGS:-${RPM_LD_FLAGS}}" /usr/bin/python3 setup.py build --executable="/usr/bin/python3 -sP"
Looks like it segfaults inside of some VTK code. I'm working on updating vtk to a newer version and will look again after that.
I have updated vtk (will open a PR as soon as new-sources is finished) but the build still fails: https://copr.fedorainfracloud.org/coprs/davidsch/testing/build/7721897/ It is again a segfault in python. Do you have an (easy) method for getting backtraces from mock?
I have a backtrace from valgrind: ==251== Invalid read of size 8 [...] ==251== Address 0x8 is not stack'd, malloc'd or (recently) free'd ==251== ==251== ==251== Process terminating with default action of signal 11 (SIGSEGV) ==251== Access not within mapped region at address 0x8 ==251== at 0x49C0BBF: PyDict_SetItem (in /usr/lib64/libpython3.13.so.1.0) ==251== by 0x4AB131F: ??? (in /usr/lib64/libpython3.13.so.1.0) ==251== by 0x301422EC: PyVTKTemplate_New (in /usr/lib64/libvtkWrappingPythonCore3.13.so.9.3) ==251== by 0x2FDE575D: ??? (in /usr/lib64/python3.13/site-packages/vtkmodules/vtkCommonCore.cpython-313-x86_64-linux-gnu.so) ==251== by 0x2FDE5C0D: PyVTKAddFile_vtkArrayIteratorTemplate (in /usr/lib64/python3.13/site-packages/vtkmodules/vtkCommonCore.cpython-313-x86_64-linux-gnu.so) ==251== by 0x2FFA6FE7: real_initvtkCommonCore (in /usr/lib64/python3.13/site-packages/vtkmodules/vtkCommonCore.cpython-313-x86_64-linux-gnu.so) ==251== by 0x4ABCCEB: ??? (in /usr/lib64/libpython3.13.so.1.0) ==251== by 0x4ABC6DA: ??? (in /usr/lib64/libpython3.13.so.1.0) ==251== by 0x4AEF1F9: ??? (in /usr/lib64/libpython3.13.so.1.0) ==251== by 0x4A106EA: ??? (in /usr/lib64/libpython3.13.so.1.0) ==251== by 0x49EFFAC: _PyEval_EvalFrameDefault (in /usr/lib64/libpython3.13.so.1.0) ==251== by 0x4A0CAF7: ??? (in /usr/lib64/libpython3.13.so.1.0) That seems like it should be easy enough to fix for someone knowing the code.
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!
I just checked, and it FTBFS in both rawhide and f41 as of today.
mock -r fedora-rawhide-x86_64 -n -N --install python3-vtk mock -r fedora-rawhide-x86_64 -n -N --shell <mock-chroot> sh-5.2# python3 -c 'import vtk' Segmentation fault (core dumped) ... and that is what crashes the Mayavi build (in tvtk/_setup.py). So, I'd say the problem is vtk. The Fedora vtk package does not try importing it. Reassign?
_This_ bug is about FTI, and that'll remain a valid issue until the package is rebuilt. Orion is aware of the issue. He's doing vtk fixes in a pull request: https://src.fedoraproject.org/rpms/vtk/pull-request/15
https://src.fedoraproject.org/rpms/vtk/pull-request/15 makes this build.
FEDORA-2024-286c09b59e (Mayavi-4.8.2-3.fc41 and vtk-9.2.6-18.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-286c09b59e
FEDORA-2024-286c09b59e 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-286c09b59e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-286c09b59e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Discussed at a blocker review meeting [1], agreed on the following: All six proposed FEs - 2291477 , 2291818 , 2275052 , 2291961 , 2301218 , 2283616 - are accepted as they are fails-to-install bugs and by precedent we accept these if there are no unusual factors involved, to keep the frozen tree as installable as possible [1] https://meetbot-raw.fedoraproject.org//meeting_matrix_fedoraproject-org/2024-10-14/
FEDORA-2024-286c09b59e (Mayavi-4.8.2-3.fc41 and vtk-9.2.6-18.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.