KDE Gear projects with failing CI (master) (31 December 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. VERY BAD NEWS: kunifiedpush FreeBSD tests have been failing for 4 consecutive weeks and have now been removed from require-passing-tests-on Good news: 2 repositories got fixed Cheers, Albert
KDE Gear projects with failing CI (release/24.12) (31 December 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 2 projects are still failing, Good news: 1 project was fixed akonadiconsole - 2nd week * https://invent.kde.org/pim/akonadiconsole/-/pipelines/849842 * Compilation fails * There is a MR with questions open. Laurent if you're reading this, please follow up on https://invent.kde.org/pim/akonadiconsole/-/merge_requests/18 neochat - 2nd week * https://invent.kde.org/network/neochat/-/pipelines/853939 * texthandlertest crashes on a nullptr access Cheers, Albert
Compile error in kcoreaddons
Hello, I just wanted to do some coding in a KDE application. Therefore I started to set up my development environment using kde-builder. I followed the instructions defined on the kde-builder web page. While compilation of kcoreaddons I get a build aboard. The error message is: /usr/include/qt6/QtCore/qglobal.h:13:12: fatal: ‘type_traits’ file not found The search using locate type_traits results in: /usr/i686-w64-mingw32/sys-root/mingw/include/c++/type_traits /usr/i686-w64-mingw32/sys-root/mingw/include/c++/bits/cpp_type_traits.h /usr/i686-w64-mingw32/sys-root/mingw/include/c++/experimental/type_traits /usr/i686-w64-mingw32/sys-root/mingw/include/c++/ext/type_traits.h /usr/i686-w64-mingw32/sys-root/mingw/include/c++/tr1/type_traits /usr/i686-w64-mingw32/sys-root/mingw/include/c++/tr2/type_traits /usr/include/c++/14/type_traits /usr/include/c++/14/bits/cpp_type_traits.h /usr/include/c++/14/experimental/type_traits /usr/include/c++/14/ext/type_traits.h /usr/include/c++/14/tr1/type_traits /usr/include/c++/14/tr2/type_traits /usr/include/qt6/QtCore/q20type_traits.h /usr/include/qt6/QtCore/qxptype_traits.h /usr/lib64/python3.13/site-packages/pyarrow/src/arrow/python/type_traits.h /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/type_traits /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/bits/cpp_type_traits.h /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/experimental/type_traits /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/ext/type_traits.h /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/tr1/type_traits /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++/tr2/type_traits System details Fedora 41 Could somebody give advice how to proceed? Regards Thomas
Re: Move Breeze to Framework
On Montag, 30. Dezember 2024 18:51:39 Mitteleuropäische Normalzeit Nate Graham wrote: > A long term concern I have is that it's messy and unpleasant to have > default styling data scattered across so many places. Ideally we'd be > able to centralize *all* data about a particular style in a single repo, > so that making changes is easy and that repo can be swapped out for > another one in the future. Just for clarification: Do you want a single repo with multiple frameworks? Or do you want a single Breeze framework and every app needs to load the Breeze theme to be able to use Breeze colors, Breeze icons and the Breeze widget style? Sorry for my ignorance, but do Kirigami apps actually use the Breeze widget style? I'm pretty sure that they do use the color theme and the icons. Regards, Ingo signature.asc Description: This is a digitally signed message part.
