This package does not support Python 3.11. Please test it with Python 3.11 as a matter of urgency as the default will change in early June, as per message on gentoo-dev: https://archives.gentoo.org/gentoo-dev/message/abb5788ea81c7bbf4d40a2995b682eb9. Please check the information provided in the tracker. Ask in #gentoo-python on IRC if need any help.
Ping. Python 3.11 is now default.
running the official python procedure fails at step 2 when setting: */* PYTHON_TARGETS: -* python3_10 python3_11 */* PYTHON_SINGLE_TARGET: -* python3_11 !!! The ebuild selected to satisfy "media-gfx/cura" has unmet requirements. - media-gfx/cura-4.13.1-r1::gentoo USE="usb -debug -test -zeroconf" ABI_X86="(64)" PYTHON_SINGLE_TARGET="-python3_10" The following REQUIRED_USE flag constraints are unsatisfied: python_single_target_python3_10
What is the actual problem that Cura has with python 3.11? I notice that Debian Bookworm packages a Cura version that is slightly older even and they are on python 3.11 as well...
So, here is what I tried: I modified all of sip-4.19.25-r1.ebuild libarcus-4.13.1.ebuild libcharon-4.13.0.ebuild libsavitar-4.13.0.ebuild pynest2d-4.13_beta.ebuild uranium-4.13.0-r1.ebuild cura-4.13.1-r1.ebuild to say "..11" instead of "..10" in their PYTHON_COMPAT declaration. I also applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=2062144 to sip-4.19.25 to make it build under python 3.11. Everything built just find and cura seems to be running correctly as well.
We lack the people that uses it that are willing to maintain it. You are more than welcome to become maintainer or proxy-maintainer and send a pull request reintroducing Cura into ::gentoo and moving forward make sure it is kept in a good shape.
No worries, if you don't have the resources to keep it in tree I can just put it in my overlay. The suggested alternatives of media-gfx/prusaslicer and media-gfx/superslicer do not work for me since they both depend on media-gfx/openvdb, which is masked as broken on ppc64.
(In reply to Marcus Comstedt from comment #6) > No worries, if you don't have the resources to keep it in tree I can just put > it in my overlay. > > The suggested alternatives of media-gfx/prusaslicer and media-gfx/superslicer > do not work for me since they both depend on media-gfx/openvdb, which is > masked > as broken on ppc64. If you're happy to look after it, you can proxy maintain it in ::gentoo.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=caa3e0c2f34c0b0f0d3f73a89dea0ddc6c9cfea2 commit caa3e0c2f34c0b0f0d3f73a89dea0ddc6c9cfea2 Author: Jakov Smolić <jsmolic@gentoo.org> AuthorDate: 2023-08-12 12:38:30 +0000 Commit: Jakov Smolić <jsmolic@gentoo.org> CommitDate: 2023-08-12 12:42:26 +0000 media-gfx/cura: treeclean Closes: https://bugs.gentoo.org/896982 Closes: https://bugs.gentoo.org/905769 Closes: https://bugs.gentoo.org/864109 Signed-off-by: Jakov Smolić <jsmolic@gentoo.org> media-gfx/cura/Manifest | 1 - media-gfx/cura/cura-4.13.1-r1.ebuild | 89 ---------------------- .../cura/files/cura-4.12.1-code-style-test.patch | 18 ----- media-gfx/cura/metadata.xml | 27 ------- profiles/package.mask | 9 --- 5 files changed, 144 deletions(-)
