Cura 5.1.0 has been released and version 5.x is a major update https://github.com/Ultimaker/Cura/releases/tag/5.1.0 Reproducible: Always
Cura 5.1.1 was released, please update the ebuild.
Cura 5.1.1 seems to depend on PyQt6: $ ./cura_app.py Traceback (most recent call last): File "/tmp/cura/Cura-5.1.1/./cura_app.py", line 23, in <module> from PyQt6.QtNetwork import QSslConfiguration, QSslSocket ModuleNotFoundError: No module named 'PyQt6' Just pip install-ing PyQt6 was not enough, though: $ ./cura_app.py /usr/lib/python3.10/site-packages/UM/PluginRegistry.py:4: DeprecationWarning: the imp module is deprecated in favour of importlib and slated for removal in Python 3.12; see the module's documentation for alternative uses import imp Error in sys.excepthook: Traceback (most recent call last): File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 688, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 883, in exec_module File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed File "/tmp/cura/Cura-5.1.1/cura/CuraApplication.py", line 46, in <module> from UM.Settings.SettingDefinition import SettingDefinition, DefinitionPropertyType, toIntConversion ImportError: cannot import name 'toIntConversion' from 'UM.Settings.SettingDefinition' (/usr/lib/python3.10/site-packages/UM/Settings/SettingDefinition.py) Original exception was: Traceback (most recent call last): File "/tmp/cura/Cura-5.1.1/./cura_app.py", line 193, in <module> from cura.CuraApplication import CuraApplication File "/tmp/cura/Cura-5.1.1/cura/CuraApplication.py", line 46, in <module> from UM.Settings.SettingDefinition import SettingDefinition, DefinitionPropertyType, toIntConversion ImportError: cannot import name 'toIntConversion' from 'UM.Settings.SettingDefinition' (/usr/lib/python3.10/site-packages/UM/Settings/SettingDefinition.py)
>pip Note I've added dev-python/PyQt6 and PyQt6-sip to the tree back on Aug 2 (which works fine afaik, albeit mostly only used by qutebrowser-3.0.0_pre9999 currently), but it's masked alongside the rest of Qt6 -- so, if bump depends on it, will need to either wait or mask it together for testing, or at least if there's no way to disable through a USE=qt6 (which is masked globally already). Unsure for potential other issues, that doesn't look PyQt6 related.
Cura 5.2.2 is out, which make 4.13.1 even more out of date
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(-)
