Recent change in default python to 3.12 means freecad can no longer use the default PYTHON_SINGLE_TARGET. This required a freecad and a lot of deps to have python-3.11 target set for them. Reproducible: Always Steps to Reproduce: USE="addonmgr -cloud -debug -designer fem gui idf image inspection material -netgen openscad part-design path -pcl points -python_single_target_python3_10 python_single_target_python3_12 -qt6 raytracing robot show surface techdraw -test tux" emerge -vp freecad Actual Results: required to enable 3.12 single target python + 3.11 for many deps: dev-python/appdirs python_targets_python3_11 dev-python/cairocffi python_targets_python3_11 dev-python/cffi python_targets_python3_11 dev-python/contourp python_targets_python3_11 dev-python/contourpy python_targets_python3_11 dev-python/cppy python_targets_python3_11 dev-python/cycler python_targets_python3_11 dev-python/fonttools python_targets_python3_11 dev-python/fs python_targets_python3_11 dev-python/gitdb python_targets_python3_11 dev-python/GitPython python_targets_python3_11 dev-python/kiwisolver python_targets_python3_11 dev-python/matplotlib python_targets_python3_11 dev-python/olefile python_targets_python3_11 dev-python/pillow python_targets_python3_11 dev-python/pivy python_targets_python3_11 dev-python/ply python_targets_python3_11 dev-python/pybind11 python_targets_python3_11 dev-python/pycparser python_targets_python3_11 dev-python/pyparsing python_targets_python3_11 dev-python/PyQt5 python_targets_python3_11 dev-python/PyQt5-sip python_targets_python3_11 dev-python/PyQt-builder python_targets_python3_11 dev-python/python-dateutil python_targets_python3_11 dev-python/pytz python_targets_python3_11 dev-python/sip python_targets_python3_11 dev-python/six python_targets_python3_11 dev-python/smmap python_targets_python3_11 dev-python/wxpython python_targets_python3_11 dev-python/xcffib python_targets_python3_11 media-gfx/freecad python_single_target_python3_11 sci-libs/med python_single_target_python3_11 sys-devel/clang:15/15g1 python_single_target_python3_11 Expected Results: ability to use default python single target setting
Python 3.12 requires using qt6 since pyside2 is no longer maintained upstream and is not compatible with 3.12. Unfortunatly there are still many issues with qt6 in 0.21.2 that need fixing. The next releasse should address most of these problems and open the door for python 3.12 compatibility.
negril, could you try figure something out?
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=08ebd7d12caf2b39beec97a97a3f7253477b46b1 commit 08ebd7d12caf2b39beec97a97a3f7253477b46b1 Author: Andrew Ammerlaan <andrewammerlaan@gentoo.org> AuthorDate: 2024-06-03 14:50:21 +0000 Commit: Andrew Ammerlaan <andrewammerlaan@gentoo.org> CommitDate: 2024-06-03 14:50:21 +0000 media-gfx/freecad: backport various qt6 fixes enable py3.12 for qt6 builds Bug: https://bugs.gentoo.org/933439 Signed-off-by: Andrew Ammerlaan <andrewammerlaan@gentoo.org> .../freecad/files/freecad-0.21.2-navcube-qt6.patch | 29 ++++ .../freecad/files/freecad-0.21.2-py312-qt6.patch | 186 +++++++++++++++++++++ .../freecad/files/freecad-0.21.2-qtsvg-qt6.patch | 148 ++++++++++++++++ ...d-0.21.2-r2.ebuild => freecad-0.21.2-r3.ebuild} | 18 +- media-gfx/freecad/freecad-9999.ebuild | 8 +- 5 files changed, 380 insertions(+), 9 deletions(-)
Backported the python 3.12 fixes from upstream as an intermediate solution. But this is only effective when using qt6, and that is not quiet ready yet according to upstream. Also added two other qt6 patches that Arch is adding to their package.
Is freecad with qt6 usable at all? I'm asking because it is quite a task to find the right use flags, and last time I tried freecad would frequently crash anyway
(In reply to Alexey Korepanov from comment #5) > Is freecad with qt6 usable at all? > > I'm asking because it is quite a task to find the right use flags, and last > time I tried freecad would frequently crash anyway There are a bunch of open issues on the upstream bug tracker[1], but it is mostly usable. Whether or not these issues are a problem for you really depends on your use case. This[2] I think is the biggest one, but we do have the patch for the navcube in ::gentoo now. [1] https://github.com/FreeCAD/FreeCAD/issues?q=is%3Aissue+is%3Aopen+label%3A%223rd+party%3A+Qt+6%22+ [2] https://github.com/FreeCAD/FreeCAD/issues/13303
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=57b1623c4a6e23ad5fa73c44304665d2c0fb8d27 commit 57b1623c4a6e23ad5fa73c44304665d2c0fb8d27 Author: Andrew Ammerlaan <andrewammerlaan@gentoo.org> AuthorDate: 2024-09-15 15:38:15 +0000 Commit: Andrew Ammerlaan <andrewammerlaan@gentoo.org> CommitDate: 2024-09-15 15:42:15 +0000 media-gfx/freecad: misc bug fixes, qt6 by default - fix issue where path with spaces is not properly passed on - add USE=smesh for smesh module, because it requires vtk - add missing rdep asciidoctor - add missing dep ms-gsl - qt6 by default for 1,0_rc1 (this rc fixes several qt6 issues) Bug: https://bugs.gentoo.org/933439 Closes: https://bugs.gentoo.org/927660 Closes: https://bugs.gentoo.org/939704 Closes: https://bugs.gentoo.org/935303 Closes: https://bugs.gentoo.org/939175 Closes: https://bugs.gentoo.org/933821 Signed-off-by: Andrew Ammerlaan <andrewammerlaan@gentoo.org> ...ad-1.0_rc1.ebuild => freecad-1.0_rc1-r1.ebuild} | 22 +++++++++++-------- media-gfx/freecad/freecad-9999.ebuild | 25 ++++++++++++++-------- media-gfx/freecad/metadata.xml | 3 +++ 3 files changed, 32 insertions(+), 18 deletions(-)
