new version Reproducible: Always
Created attachment 569924 [details] cura 4.0.0 ebuild
Created attachment 569926 [details, diff] cura 4.0.0 patch
Created attachment 569928 [details] curaengine 4.0.0 ebuild
Created attachment 569930 [details] fdm-materials 4.0.0 ebuild
Created attachment 569932 [details] uranium 4.0.0 ebuild
Created attachment 569934 [details, diff] uranium 4.0.0 patch
Created attachment 569936 [details] libarcus 4.0.0 ebuild
Created attachment 569938 [details] libcharon 4.0.0 ebuild
Created attachment 569940 [details] libsavitar 4.0.0 ebuild
Created attachment 569942 [details, diff] libsavitar 4.0.0 patch
(In reply to qwertyqwertyq from comment #5) > Created attachment 569932 [details] > uranium 4.0.0 ebuild Review comment: Uranium 4.0 "README.md" still lists "Shapely" as requirement. However, unlike "uranium-3.6.0.ebuild" the new ebuild does not have this requirement anymore. Is this intentional? It looks as if an older ebuild version was used as base, when "Shapely" was not yet required.
I agree, shapely still seems to be a dependency, I suspect you copied the 3.4.1 ebuild instead of the 3.6.0. I am preparing a PR with all ebuilds but I ran into this issue: https://github.com/Ultimaker/Cura/issues/5488 Does the preview functionality work for you?
(In reply to Mathy Vanvoorden from comment #12) > I am preparing a PR with all ebuilds but I ran into this issue: > > https://github.com/Ultimaker/Cura/issues/5488 > > Does the preview functionality work for you? Not the original reporter, but: For me the preview button also crashes, like described above.
Mathy Vanvoorden, please add to your PR for uranium ebuild following fix: IUSE="debug doc test" src_configure() { if ! use debug; then sed -i 's/logging.DEBUG/logging.ERROR/' plugins/ConsoleLogger/ConsoleLogger.py || die sed -i 's/logging.DEBUG/logging.ERROR/' plugins/FileLogger/FileLogger.py || die fi ... } This will disable flooding logs with DEBUG messages. Thanks.
Is using debug USE flag is the best way to handle that? Also, is there no runtime flag we can toggle?
I suppose, debug USE flag is intended to handle all debug features, dumps, debug logs etc., isn't it? Debug level is hardcoded in uranium loggers code, so i think it's impossible to change it at runtime: https://github.com/Ultimaker/Uranium/blob/master/plugins/ConsoleLogger/ConsoleLogger.py#L27 https://github.com/Ultimaker/Uranium/blob/master/plugins/FileLogger/FileLogger.py#L15
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=efe6b66e73ed6b1c177e93668757045860edc49e commit efe6b66e73ed6b1c177e93668757045860edc49e Author: Michael Perlov <perlovka@gmail.com> AuthorDate: 2019-08-04 16:14:25 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2019-08-25 17:59:07 +0000 media-gfx/cura: version bump to 4.2.1 Closes: https://bugs.gentoo.org/680988 Closes: https://bugs.gentoo.org/687324 Closes: https://bugs.gentoo.org/691144 Package-Manager: Portage-2.3.72, Repoman-2.3.17 Signed-off-by: Michael Perlov <perlovka@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/12618 Signed-off-by: Joonas Niilola <juippis@gentoo.org> media-gfx/cura/Manifest | 1 + media-gfx/cura/cura-4.2.1.ebuild | 53 ++++++++++++++++++++++ .../cura/files/cura-4.2.1-fix-install-paths.patch | 41 +++++++++++++++++ 3 files changed, 95 insertions(+)
