Since package is configured with qmlui, this dependency should not be necessary. Plese check.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=de73af3b97023aeb77e961b81aff8256364671c2 commit de73af3b97023aeb77e961b81aff8256364671c2 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2023-10-21 18:16:22 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2023-10-21 21:04:18 +0000 app-misc/qlcplus: add 5.0.0_beta2, fix dependencies, drop virtualx - add missing pkg_postrm() phase Bug: https://bugs.gentoo.org/915785 See also: https://github.com/gentoo/gentoo/pull/26074 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> app-misc/qlcplus/Manifest | 1 + app-misc/qlcplus/qlcplus-5.0.0_beta2.ebuild | 89 +++++++++++++++++++++++++++++ 2 files changed, 90 insertions(+)
5.0.0_beta2 has a few reports open about being crashy, also it is old. Maybe a snapshot would be worthwhile?
5.0.0_beta3 available: https://github.com/mcallegari/qlcplus/releases/tag/QLC%2B_5.0.0_beta3
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9a0b4a4a873c79847235ed7bf3e0c6c828dda3d6 commit 9a0b4a4a873c79847235ed7bf3e0c6c828dda3d6 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2024-01-16 10:46:22 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2024-01-16 11:52:02 +0000 app-misc/qlcplus: add 5.0.0_beta3 Bug: https://bugs.gentoo.org/915785 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> app-misc/qlcplus/Manifest | 1 + app-misc/qlcplus/qlcplus-5.0.0_beta3.ebuild | 90 +++++++++++++++++++++++++++++ 2 files changed, 91 insertions(+)
Jannis, do you think this is good enough to add back ~amd64 keyword for broader testing?
Hi Andreas, yes, I would say we can keyword beta-3 with ~amd64. It might even make sense to slot this package since v5 is not ready for "production" shows and people might still want v4 while having v5 installed to evaluate?
Did upstream enable it to be installed side-by-side without collisions?
(In reply to Andreas Sturmlechner from comment #7) > Did upstream enable it to be installed side-by-side without collisions? Upstream did not change anything. For the "static data" that is common between the versions (/usr/share/qlcplus/ and /lib/udev/rules.d), I might have to do a "qlcplus-shared", "qlcplus-data" or "qlcplus-common" ebuild. The executables are already named differently (/usr/bin/qlcplus vs /usr/bin/qlcplus-qml). It's just the libraries in /usr/lib64/qt5/plugins/qlcplus and /usr/lib64/libqlcplus* that do collide. The former might be inter-changeable (need to check), the latter is probably not. Might work when one further modifies the variables.pri file: https://github.com/mcallegari/qlcplus/blob/master/variables.pri#L92 Do you think it's worth the effort?
(In reply to jannis from comment #8) > Do you think it's worth the effort? I don't think so. Just track upstream's progress on this, but at some point we might have to drop the old stuff no matter what.
4.14.0 was released last month with Qt6 support: https://github.com/mcallegari/qlcplus/releases/tag/QLC%2B_4.14.0 We should then consider cleaning up 5.0.0_beta* unless some current snapshot can be built with Qt6 as well.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c750c4475ff2beb30287067dea46b35601cfd1d2 commit c750c4475ff2beb30287067dea46b35601cfd1d2 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2025-02-13 17:52:46 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2025-02-13 20:27:59 +0000 profiles: Mask dev-qt/qt3d[gamepad] ... in order to be able to mask dev-qt/qtgamepad:5. Last package to depend on dev-qt/qt3d itself is app-misc/qlcplus. Bug: https://bugs.gentoo.org/915785 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> profiles/base/package.use.mask | 4 ++++ 1 file changed, 4 insertions(+)
Confirmed, I will be working on that. Just need to fly home from the US first ;)
Just a short status update: I got a working build using Qt6 and cmake. Ebuild needs a bit more polishing and cleanup
The build I have is unstable and crashes sporadically: Thread 47 "QThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff7f7fe6c0 (LWP 1319)] 0x00007ffff54d5114 in ?? () from /usr/lib64/libQt6Qml.so.6 (gdb) bt #0 0x00007ffff54d5114 in ??? () at /usr/lib64/libQt6Qml.so.6 #1 0x00007ffff54d5580 in QV4::MemoryManager::allocData(unsigned long) () at /usr/lib64/libQt6Qml.so.6 #2 0x00007ffff551cd1b in QV4::ArrayData::realloc(QV4::Object*, QV4::Heap::ArrayData::Type, unsigned int, bool) () at /usr/lib64/libQt6Qml.so.6 #3 0x00007ffff551eec7 in QV4::ArrayData::insert(QV4::Object*, unsigned int, QV4::Value const*, bool) () at /usr/lib64/libQt6Qml.so.6 #4 0x00007ffff55661d9 in QV4::Object::arraySet(unsigned int, QV4::Value const&) () at /usr/lib64/libQt6Qml.so.6 #5 0x00007ffff5632c1a in QV4::Object::virtualDefineOwnProperty(QV4::Managed*, QV4::PropertyKey, QV4::Property const*, QV4::PropertyAttributes) () at /usr/lib64/libQt6Qml.so.6 #6 0x00007ffff5632e2d in ??? () at /usr/lib64/libQt6Qml.so.6 #7 0x00007ffff5630bbc in QV4::Object::internalPut(QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/lib64/libQt6Qml.so.6 #8 0x00007ffff5630e87 in QV4::Object::internalPut(QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/lib64/libQt6Qml.so.6 #9 0x00007ffff5630e87 in QV4::Object::internalPut(QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/lib64/libQt6Qml.so.6 #10 0x00007ffff54c6152 in ??? () at /usr/lib64/libQt6Qml.so.6 #11 0x00007ffff54c619c in QV4::Runtime::StoreElement::call(QV4::ExecutionEngine*, QV4::Value const&, QV4::Value const&, QV4::Value const&) () at /usr/lib64/libQt6Qml.so.6 #12 0x00007fffa25ff39e in ??? () #13 0x0000000000000000 in ??? () I will be rebuilding Qt (6.8.2) and qlcplus with debugging information to investigate
More luck with 4.14.1, maybe?
(In reply to Andreas Sturmlechner from comment #15) > More luck with 4.14.1, maybe? Thanks for the patience! Yes, I talked to the upstream devs and 4.14.1 is supposed to fix most of the issues they had with Qt6. PR is open: https://github.com/gentoo/gentoo/pull/41452 This is my first cmake-based ebuilds so comments for improvement are highly appreciated. Thanks :) I also decided to drop 5.x for now, waiting for the next upstream release of that as well.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=810e8ff1307d19af445ec9ed8795f2e1b447d5cd commit 810e8ff1307d19af445ec9ed8795f2e1b447d5cd Author: Jannis Achstetter <kripton@kripserver.net> AuthorDate: 2025-04-04 19:48:38 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2025-04-04 21:15:06 +0000 app-misc/qlcplus: drop 4.13.1, 5.0.0_beta3 Not compatible with Qt6 Closes: https://bugs.gentoo.org/915785 Signed-off-by: Jannis Achstetter <kripton@kripserver.net> Closes: https://github.com/gentoo/gentoo/pull/41452 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> app-misc/qlcplus/Manifest | 2 - app-misc/qlcplus/qlcplus-4.13.1.ebuild | 85 --------------------------- app-misc/qlcplus/qlcplus-5.0.0_beta3.ebuild | 90 ----------------------------- 3 files changed, 177 deletions(-) Additionally, it has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c4fe59578b47747dd2d541267a29c0c3b9f13998 commit c4fe59578b47747dd2d541267a29c0c3b9f13998 Author: Jannis Achstetter <kripton@kripserver.net> AuthorDate: 2025-04-04 19:47:39 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2025-04-04 21:15:06 +0000 app-misc/qlcplus: version bump to 4.14.1 Compatible with Qt6, moving from qmake to cmake. Bug: https://bugs.gentoo.org/915785 Signed-off-by: Jannis Achstetter <kripton@kripserver.net> Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> app-misc/qlcplus/Manifest | 1 + app-misc/qlcplus/qlcplus-4.14.1.ebuild | 71 ++++++++++++++++++++++++++++++++++ 2 files changed, 72 insertions(+)
